Cybersecurity & Penetration Testing

Write a professional penetration test finding for a vulnerability report. Finding: [VULNERABILITY NAME] (e.g., SQL Injection in login endpoint). Structure: 1) Title: clear, specific vulnerability name, 2) Severity: Critical/High/Medium/Low with CVSS v3.1 score and vector string, 3) Affected component: specific URL, parameter, or system, 4) Description: technical explanation of the vulnerability (2–3 sentences), 5) Evidence: reproduction steps (numbered), proof-of-concept payload, and screenshot placeholder, 6) Impact: what an attacker could achieve (specific, not generic), 7) Remediation: specific, actionable fix with code example if applicable, 8) References: CVE, CWE, OWASP link. Tone: technical, precise, professional.

Generate a detailed security assessment checklist for [OWASP CATEGORY] (e.g., A01: Broken Access Control) for a [APPLICATION TYPE: web app/API/mobile app]. For each test case: 1) Test ID (e.g., BAC-01), 2) Test name, 3) Description of what to test, 4) Testing steps (specific HTTP requests, payloads, or tools), 5) Pass/fail criteria, 6) Severity if found, 7) Remediation reference. Include 8–12 test cases covering the full attack surface for this category. Format as a structured checklist.

Write an incident response playbook for a [INCIDENT TYPE: ransomware/data breach/DDoS/phishing/insider threat] incident. Structure: 1) Detection: indicators of compromise (IOCs) to look for, detection tools and queries, 2) Initial triage: severity classification criteria, 3) Containment: immediate actions (network isolation, account lockdown), 4) Eradication: root cause removal steps, 5) Recovery: system restoration sequence, 6) Post-incident: evidence preservation, forensic analysis, lessons learned, 7) Communication: internal notification chain, external notification requirements (regulators, customers). Include decision trees for key escalation points.