Pentest readiness and findings audit
Review pentest scope, rules of engagement, and previously collected findings.
Customize the recipe
0/1500 characters
Prompt preview
# Pentest readiness and findings audit Review pentest scope, rules of engagement, and previously collected findings. ## 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 Threat Model](https://github.com/openai/skills/blob/main/skills/.curated/security-threat-model/SKILL.md) (Skill) — Map assets, access boundaries, and risk from supplied architecture and source evidence. - [OWASP ASVS](https://github.com/OWASP/ASVS) (Repository) — Map observed web security controls to relevant verification requirements. - [OWASP Cheat Sheet Series](https://github.com/OWASP/CheatSheetSeries) (Repository) — Reference defensive guidance for authentication, sessions, data handling, and secure configuration. ## Workflow Review the supplied scope, authorization, rules of engagement, architecture, and any completed pentest report. Summarize findings by affected control and business impact, check evidence and retest coverage, and identify gaps for the authorized human testing team. ## Deliverable A pentest readiness and findings review with scope gaps, evidence-backed priorities, and retest acceptance criteria. - Minimalism: Apply this style to report presentation only. Plain Markdown is sufficient. ## Acceptance checks - [ ] Separate findings supported by supplied evidence from topics the existing pentest did not verify. - [ ] Describe expected secure outcomes and retest criteria without executable exploit steps or payloads. - [ ] 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 Threat Model
Map assets, access boundaries, and risk from supplied architecture and source evidence.
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
OWASP Cheat Sheet Series
Reference defensive guidance for authentication, sessions, data handling, and secure configuration.
License · CC-BY-SA-4.0
34.2K GitHub stars