Security Audit

Security Audit

Establish scope and inputs

• Determine whether the audit targets a merge/pull request, local diff, specific files, or a broader codebase area.
• If a merge/pull request is referenced:
  1. fetch merge/pull request to determine the source branch and target branch;
  2. fetch the diffs between source branch and target branch to audit the changes;
• If a diff or file list is already provided, proceed without re-fetching.
• If the scope is ambiguous, infer it from the conversation history and available artifacts.
• Scope the audit to the affected code paths and any critical adjacent components.

Audit checklist

• Authentication and authorization correctness, including privilege boundaries.
• Input validation and injection risks (SQLi, XSS, command injection, SSRF).
• Secrets management (hardcoded tokens, leaked credentials, unsafe logging).
• Data protection (encryption at rest/in transit, PII handling, data minimization).
• Dependency and supply-chain risks (unsafe or outdated libraries).
• Error handling that may leak sensitive details.
• Cryptography usage (weak algorithms, insecure randomness, misuse).
• API security (rate limiting, CORS, authentication on endpoints).

Response format

• Summary: 1-3 bullets on overall posture and hotspots.
• Findings: group by severity (Critical/High/Medium/Low) with clear remediation.
• Recommendations: non-blocking improvements and follow-ups.
• Tests/Validation: security tests to run or missing coverage.