security-audit

To run a comprehensive security audit, explicitly request a full-codebase audit and provide project context. The process analyzes source code, dependencies, and configurations to generate a prioritized, actionable remediation plan.

A formal codebase security audit covers SAST, OWASP Top 10, OWASP LLM Top 10, SCA, zero-trust validation, and code quality checks. It evaluates your repository to identify security risks and produces an actionable remediation report.

Yes, you can generate a standardized SAST and SCA audit report by triggering an explicit audit request. The output is a formal markdown file named AUDIT-{PROJECT}-{YYYY-MM-DD}.md containing structured findings and remediation guidance.

Yes, the audit process includes OWASP LLM Top 10 and zero-trust validation checks alongside standard SAST and SCA scans. These checks are integrated into a single auditable process to identify and mitigate security risks.

An automated codebase security audit is ideal when you need thorough risk assessment and formal report generation with prioritized findings. It enforces artifact naming conventions and provides structured remediation guidance for complex repositories.

The security audit report uses a standardized markdown format named AUDIT-{PROJECT}-{YYYY-MM-DD}.md. It contains structured findings from SAST and SCA scans, alongside a prioritized, actionable remediation plan.