Security Audit

Challenge the change from an attacker and misuse perspective before it ships.

Context

Security audit is the focused quality pass for abuse resistance. It is narrower than full security architecture work and deeper than ordinary code review. Use it when a change crosses trust boundaries, handles sensitive data, touches authn/authz, introduces new dependencies, or materially changes deployment exposure.

In Prodcraft, security audit exists to stop avoidable release risk. It should produce concrete findings tied to the current slice, not a generic list of best practices.

Inputs

• source-code -- The implementation under audit, including configuration and integration points visible in the change.
• architecture-doc -- Trust boundaries, component interactions, and intended control points.
• threat-model -- Known attacker capabilities, abuse cases, and assumptions to verify when one exists.
• intake-brief -- Must include quality_target_context with runtime_context, exposure_profile, production_target, non_targets, and evidence_refs.

Process