Web application security audit
Review supplied app code for weaknesses in server-side controls and data handling.
Customize the recipe
0/1500 characters
Prompt preview
# Web application security audit Review supplied app code for weaknesses in server-side controls and data handling. ## Read-only scope Review only the authorized app, site, server, or local source named or supplied by the user. Work from provided code, configuration, redacted exports, and completed test results. Use URLs and hostnames as scope identifiers. Request the missing artifacts if evidence is insufficient. Use existing offline, read-only analysis on those artifacts. Exclude live probing, vulnerability reproduction, exploit payloads, credential testing, new load generation, and changes to the target or its files. ## Tools and setup · Universal Use the linked resources as references for interpreting the supplied material. Follow the read-only scope when a linked workflow describes other actions. - [Security Best Practices](https://github.com/openai/skills/blob/main/skills/.curated/security-best-practices/SKILL.md) (Skill) — Use the language-specific guidance to identify insecure defaults and review supplied code. - [OWASP ASVS](https://github.com/OWASP/ASVS) (Repository) — Map observed web security controls to relevant verification requirements. - [Semgrep Community Edition](https://github.com/semgrep/semgrep) (Repository) — Review local static-analysis findings against their cited source and the actual control flow. ## Workflow Start with the supplied route inventory and architecture. Review applicable controls for input handling, output encoding, access decisions, uploads, and sensitive data. Triangulate existing static-analysis findings with the actual code. ## Deliverable A web application findings report mapped to applicable ASVS requirements. - Minimalism: Apply this style to report presentation only. Plain Markdown is sufficient. ## Acceptance checks - [ ] Each issue cites the affected route or source location and the relevant control. - [ ] Report coverage by reviewed component and distinguish code evidence from runtime unknowns. - [ ] Give each finding a severity, confidence, affected component, evidence reference, impact, and recommended mitigation. Explicitly list unverified controls and gaps. - [ ] Redact credentials, tokens, personal data, and sensitive values in the report.
Recipe resources
Source, setup, and compatibility details.
Security Best Practices
Use the language-specific guidance to identify insecure defaults and review supplied code.
Upstream documents Codex.
28.9K GitHub stars on the source repository
OWASP ASVS
Map observed web security controls to relevant verification requirements.
License · CC-BY-SA-4.0
3.8K GitHub stars
Semgrep Community Edition
Review local static-analysis findings against their cited source and the actual control flow.
License · LGPL-2.1
17.9K GitHub stars