Glossary
Plain-language definitions for the terms that come up when you audit software your team generated with AI.
Audit Your Vibe-Coded Software- AuthenticationRead Authentication
Authentication is the process a system uses to verify that a user, service, or device is who it claims to be before creating a trusted session.
- AuthorizationRead Authorization
Authorization is the set of rules that decides which data and actions an authenticated user or service may access.
- Dependency RiskRead Dependency Risk
The exposure a product carries through the third-party packages it depends on. AI-generated code tends to add dependencies quickly, so the surface is usually wider than the team expects.
- Input ValidationRead Input Validation
Input validation checks that data entering a system has the expected type, shape, range, and meaning before the system uses it.
- Secrets ManagementRead Secrets Management
Secrets management controls how credentials, keys, tokens, and certificates are stored, delivered, rotated, and revoked.
- Test CoverageRead Test Coverage
The share of a codebase that automated tests actually exercise. In software generated with AI the number is often high while the tests verify very little.
- Threat ModelingRead Threat Modeling
Threat modeling maps what a system must protect, where trust changes, how misuse could occur, and which controls should prevent or limit it.
Audit Your Vibe-Coded Software
The full picture on auditing vibe-coded software.
