security-audit

Perform a retroactive security audit by analyzing completed code implementations to verify threat mitigations and identify vulnerabilities across authentication, data storage, and external integrations. The process generates a SECURITY.md with prioritized remediation guidance.

Map code vulnerabilities to OWASP Top 10 and MITRE ATT&CK frameworks by conducting systematic code-level and dependency audits. This standardizes findings into actionable formats, documenting risk levels and prioritized fixes within a generated SECURITY.md artifact.

Threat modeling secures external integrations and dependencies by defining scope to identify critical assets, trust boundaries, and adversaries. This structured approach ensures systematic code-level audits effectively verify mitigations and uncover hidden vulnerabilities.

Yes, you can generate a SECURITY.md file with prioritized remediation guidance for your repository. The audit examines completed phase implementations, maps findings to OWASP Top 10, and outputs structured documentation of risks and fixes.

Yes, this security audit covers authentication and authorization code review. It systematically examines these completed implementations, alongside data storage and external integrations, to verify effective threat mitigations and identify potential vulnerabilities.

Run a security audit on project dependencies when completing implementation phases to verify threat mitigations are effective. Mapping dependency updates to MITRE ATT&CK and OWASP Top 10 ensures vulnerabilities are documented with prioritized fixes in SECURITY.md.