[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KB2KT1JDXSC6B030GMJQNW":3,"skill-same:01M6KB2KT1JDXSC6B030GMJQNW":104},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":6,"updatedAt":61,"install":62,"resources":75},"01M6KB2KT1JDXSC6B030GMJQNW","security-pen-testing",null,"Use when the user asks to perform security audits, penetration testing, vulnerability scanning, OWASP Top 10 checks, or offensive security assessments. Covers static analysis, dependency scanning, secret detection, API security testing, and pen test report generation.","afaizalam2003\u002FMaster-claude-skill","afaizalam2003","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F222019359?v=4","01M6K8F2XNT0HKBPF00JQ78SV3","Faiz Alam","01M6K8F31EBXAPER0EG8R9HTR5",3,"MIT","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fsecurity-pen-testing\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"security","pen testing","security pen testing","testing","scanning","static","top","offensive","penetration","api security","test report","dependency","owasp top 10","static analysis","api","vulnerability","api security testing","analysis","owasp","penetration testing","2026-11-10 10:12:30",false,"---\nname: \"security-pen-testing\"\ndescription: \"Use when the user asks to perform security audits, penetration testing, vulnerability scanning, OWASP Top 10 checks, or offensive security assessments. Covers static analysis, dependency scanning, secret detection, API security testing, and pen test report generation.\"\n---\n\n# Security Penetration Testing\n\nHands-on offensive security testing skill for finding vulnerabilities before attackers do. This is NOT compliance checking (see senior-secops) or security policy writing (see senior-security) — this is about systematic vulnerability discovery through authorized testing.\n\n---\n\n## Table of Contents\n\n- [Overview](#overview)\n- [OWASP Top 10 Systematic Audit](#owasp-top-10-systematic-audit)\n- [Static Analysis](#static-analysis)\n- [Dependency Vulnerability Scanning](#dependency-vulnerability-scanning)\n- [Secret Scanning](#secret-scanning)\n- [API Security Testing](#api-security-testing)\n- [Web Vulnerability Testing](#web-vulnerability-testing)\n- [Infrastructure Security](#infrastructure-security)\n- [Pen Test Report Generation](#pen-test-report-generation)\n- [Responsible Disclosure Workflow](#responsible-disclosure-workflow)\n- [Workflows](#workflows)\n- [Anti-Patterns](#anti-patterns)\n- [Cross-References](#cross-references)\n\n---\n\n## Overview\n\n### What This Skill Does\n\nThis skill provides the methodology, checklists, and automation for **offensive security testing** — actively probing systems to discover exploitable vulnerabilities. It covers web applications, APIs, infrastructure, and supply chain security.\n\n### Distinction from Other Security Skills\n\n| Skill | Focus | Approach |\n|-------|-------|----------|\n| **security-pen-testing** (this) | Finding vulnerabilities | Offensive — simulate attacker techniques |\n| senior-secops | Security operations | Defensive — monitoring, incident response, SIEM |\n| senior-security | Security policy | Governance — policies, frameworks, risk registers |\n| skill-security-auditor | CI\u002FCD gates | Automated — pre-merge security checks |\n\n### Prerequisites\n\nAll testing described here assumes **written authorization** from the system owner. Unauthorized testing is illegal under the CFAA and equivalent laws worldwide. Always obtain a signed scope-of-work or rules-of-engagement document before starting.\n\n---\n\n## OWASP Top 10 Systematic Audit\n\nUse the vulnerability scanner tool for automated checklist generation:\n\n```bash\n# Generate OWASP checklist for a web application\npython scripts\u002Fvulnerability_scanner.py --target web --scope full\n\n# Quick API-focused scan\npython scripts\u002Fvulnerability_scanner.py --target api --scope quick --json\n```\n\n### Quick Reference\n\n| # | Category | Key Tests |\n|---|----------|-----------|\n| A01 | Broken Access Control | IDOR, vertical escalation, CORS, JWT claim manipulation, forced browsing |\n| A02 | Cryptographic Failures | TLS version, password hashing, hardcoded keys, weak PRNG |\n| A03 | Injection | SQLi, NoSQLi, command injection, template injection, XSS |\n| A04 | Insecure Design | Rate limiting, business logic abuse, multi-step flow bypass |\n| A05 | Security Misconfiguration | Default credentials, debug mode, security headers, directory listing |\n| A06 | Vulnerable Components | Dependency audit (npm\u002Fpip\u002Fgo), EOL checks, known CVEs |\n| A07 | Auth Failures | Brute force, session cookie flags, session invalidation, MFA bypass |\n| A08 | Integrity Failures | Unsafe deserialization, SRI checks, CI\u002FCD pipeline integrity |\n| A09 | Logging Failures | Auth event logging, sensitive data in logs, alerting thresholds |\n| A10 | SSRF | Internal IP access, cloud metadata endpoints, DNS rebinding |\n\n```bash\n# Audit dependencies\npython scripts\u002Fdependency_auditor.py --file package.json --severity high\npython scripts\u002Fdependency_auditor.py --file requirements.txt --json\n```\n\nSee [owasp_top_10_checklist.md](references\u002Fowasp_top_10_checklist.md) for detailed test procedures, code patterns to detect, remediation steps, and CVSS scoring guidance for each category.\n\n---\n\n## Static Analysis\n\n**Recommended tools:** CodeQL (custom queries for project-specific patterns), Semgrep (rule-based scanning with auto-fix), ESLint security plugins (`eslint-plugin-security`, `eslint-plugin-no-unsanitized`).\n\nKey patterns to detect: SQL injection via string concatenation, hardcoded JWT secrets, unsafe YAML\u002Fpickle deserialization, missing security middleware (e.g., Express without Helmet).\n\nSee [attack_patterns.md](references\u002Fattack_patterns.md) for code patterns and detection payloads across injection types.\n\n---\n\n## Dependency Vulnerability Scanning\n\n**Ecosystem commands:** `npm audit`, `pip audit`, `govulncheck .\u002F...`, `bundle audit check`\n\n**CVE Triage Workflow:**\n1. **Collect** — Run ecosystem audit tools, aggregate findings\n2. **Deduplicate** — Group by CVE ID across direct and transitive deps\n3. **Prioritize** — Critical + exploitable + reachable = fix immediately\n4. **Remediate** — Upgrade, patch, or mitigate with compensating controls\n5. **Verify** — Rerun audit to confirm fix, update lock files\n\n```bash\npython scripts\u002Fdependency_auditor.py --file package.json --severity critical --json\n```\n\n---\n\n## Secret Scanning\n\n**Tools:** TruffleHog (git history + filesystem), Gitleaks (regex-based with custom rules).\n\n```bash\n# Scan git history for verified secrets\ntrufflehog git file:\u002F\u002F. --only-verified --json\n\n# Scan filesystem\ntrufflehog filesystem . --json\n```\n\n**Integration points:** Pre-commit hooks (gitleaks, trufflehog), CI\u002FCD gates (GitHub Actions with `trufflesecurity\u002Ftrufflehog@main`). Configure `.gitleaks.toml` for custom rules (AWS keys, API keys, private key headers) and allowlists for test fixtures.\n\n---\n\n## API Security Testing\n\n### Authentication Bypass\n\n- **JWT manipulation:** Change `alg` to `none`, RS256-to-HS256 confusion, claim modification (`role: \"admin\"`, `exp: 9999999999`)\n- **Session fixation:** Check if session ID changes after authentication\n\n### Authorization Flaws\n\n- **IDOR\u002FBOLA:** Change resource IDs in every endpoint — test read, update, delete across users\n- **BFLA:** Regular user tries admin endpoints (expect 403)\n- **Mass assignment:** Add privileged fields (`role`, `is_admin`) to update requests\n\n### Rate Limiting & GraphQL\n\n- **Rate limiting:** Rapid-fire requests to auth endpoints; expect 429 after threshold\n- **GraphQL:** Test introspection (should be disabled in prod), query depth attacks, batch mutations bypassing rate limits\n\nSee [attack_patterns.md](references\u002Fattack_patterns.md) for complete JWT manipulation payloads, IDOR testing methodology, BFLA endpoint lists, GraphQL introspection\u002Fdepth\u002Fbatch attack patterns, and rate limiting bypass techniques.\n\n---\n\n## Web Vulnerability Testing\n\n| Vulnerability | Key Tests |\n|--------------|-----------|\n| **XSS** | Reflected (script\u002Fimg\u002Fsvg payloads), Stored (persistent fields), DOM-based (innerHTML + location.hash) |\n| **CSRF** | Replay without token (expect 403), cross-session token replay, check SameSite cookie attribute |\n| **SQL Injection** | Error-based (`' OR 1=1--`), union-based enumeration, time-based blind (`SLEEP(5)`), boolean-based blind |\n| **SSRF** | Internal IPs, cloud metadata endpoints (AWS\u002FGCP\u002FAzure), IPv6\u002Fhex\u002Fdecimal encoding bypasses |\n| **Path Traversal** | `..\u002F..\u002F..\u002Fetc\u002Fpasswd`, URL encoding, double encoding bypasses |\n\nSee [attack_patterns.md](references\u002Fattack_patterns.md) for complete test payloads (XSS filter bypasses, context-specific XSS, SQL injection per database engine, SSRF bypass techniques, and DOM-based XSS source\u002Fsink pairs).\n\n---\n\n## Infrastructure Security\n\n**Key checks:**\n- **Cloud storage:** S3 bucket public access (`aws s3 ls s3:\u002F\u002Fbucket --no-sign-request`), bucket policies, ACLs\n- **HTTP security headers:** HSTS, CSP (no `unsafe-inline`\u002F`unsafe-eval`), X-Content-Type-Options, X-Frame-Options, Referrer-Policy\n- **TLS configuration:** `nmap --script ssl-enum-ciphers -p 443 target.com` or `testssl.sh` — reject TLS 1.0\u002F1.1, RC4, 3DES, export-grade ciphers\n- **Port scanning:** `nmap -sV target.com` — flag dangerous open ports (FTP\u002F21, Telnet\u002F23, Redis\u002F6379, MongoDB\u002F27017)\n\n---\n\n## Pen Test Report Generation\n\nGenerate professional reports from structured findings:\n\n```bash\n# Generate markdown report from findings JSON\npython scripts\u002Fpentest_report_generator.py --findings findings.json --format md --output report.md\n\n# Generate JSON report\npython scripts\u002Fpentest_report_generator.py --findings findings.json --format json --output report.json\n```\n\n### Findings JSON Format\n\n```json\n[\n  {\n    \"title\": \"SQL Injection in Login Endpoint\",\n    \"severity\": \"critical\",\n    \"cvss_score\": 9.8,\n    \"cvss_vector\": \"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H\",\n    \"category\": \"A03:2021 - Injection\",\n    \"description\": \"The \u002Fapi\u002Flogin endpoint is vulnerable to SQL injection via the email parameter.\",\n    \"evidence\": \"Request: POST \u002Fapi\u002Flogin {\\\"email\\\": \\\"' OR 1=1--\\\", \\\"password\\\": \\\"x\\\"}\\nResponse: 200 OK with admin session token\",\n    \"impact\": \"Full database access, authentication bypass, potential remote code execution\",\n    \"remediation\": \"Use parameterized queries. Replace string concatenation with prepared statements.\",\n    \"references\": [\"https:\u002F\u002Fcwe.mitre.org\u002Fdata\u002Fdefinitions\u002F89.html\"]\n  }\n]\n```\n\n### Report Structure\n\n1. **Executive Summary**: Business impact, overall risk level, top 3 findings\n2. **Scope**: What was tested, what was excluded, testing dates\n3. **Methodology**: Tools used, testing approach (black\u002Fgray\u002Fwhite box)\n4. **Findings Table**: Sorted by severity with CVSS scores\n5. **Detailed Findings**: Each with description, evidence, impact, remediation\n6. **Remediation Priority Matrix**: Effort vs. impact for each fix\n7. **Appendix**: Raw tool output, full payload lists\n\n---\n\n## Responsible Disclosure Workflow\n\nResponsible disclosure is **mandatory** for any vulnerability found during authorized testing. Standard timeline: report on day 1, follow up at day 7, status update at day 30, public disclosure at day 90.\n\n**Key principles:** Never exploit beyond proof of concept, encrypt all communications, do not access real user data, document everything with timestamps.\n\nSee [responsible_disclosure.md](references\u002Fresponsible_disclosure.md) for full disclosure timelines (standard 90-day, accelerated 30-day, extended 120-day), communication templates, legal considerations, bug bounty program integration, and CVE request process.\n\n---\n\n## Workflows\n\n### Workflow 1: Quick Security Check (15 Minutes)\n\nFor pre-merge reviews or quick health checks:\n\n```bash\n# 1. Generate OWASP checklist\npython scripts\u002Fvulnerability_scanner.py --target web --scope quick\n\n# 2. Scan dependencies\npython scripts\u002Fdependency_auditor.py --file package.json --severity high\n\n# 3. Check for secrets in recent commits\n# (Use gitleaks or trufflehog as described in Secret Scanning section)\n\n# 4. Review HTTP security headers\ncurl -sI https:\u002F\u002Ftarget.com | grep -iE \"(strict-transport|content-security|x-frame|x-content-type)\"\n```\n\n**Decision**: If any critical or high findings, block the merge.\n\n### Workflow 2: Full Penetration Test (Multi-Day Assessment)\n\n**Day 1 — Reconnaissance:**\n1. Map the attack surface: endpoints, authentication flows, third-party integrations\n2. Run automated OWASP checklist (full scope)\n3. Run dependency audit across all manifests\n4. Run secret scan on full git history\n\n**Day 2 — Manual Testing:**\n1. Test authentication and authorization (IDOR, BOLA, BFLA)\n2. Test injection points (SQLi, XSS, SSRF, command injection)\n3. Test business logic flaws\n4. Test API-specific vulnerabilities (GraphQL, rate limiting, mass assignment)\n\n**Day 3 — Infrastructure and Reporting:**\n1. Check cloud storage permissions\n2. Verify TLS configuration and security headers\n3. Port scan for unnecessary services\n4. Compile findings into structured JSON\n5. Generate pen test report\n\n```bash\n# Generate final report\npython scripts\u002Fpentest_report_generator.py --findings findings.json --format md --output pentest-report.md\n```\n\n### Workflow 3: CI\u002FCD Security Gate\n\nAutomated security checks on every PR: secret scanning (TruffleHog), dependency audit (`npm audit`, `pip audit`), SAST (Semgrep with `p\u002Fsecurity-audit`, `p\u002Fowasp-top-ten`), and security headers check on staging.\n\n**Gate Policy**: Block merge on critical\u002Fhigh findings. Warn on medium. Log low\u002Finfo.\n\n---\n\n## Anti-Patterns\n\n1. **Testing in production without authorization** — Always get written permission and use staging\u002Ftest environments when possible\n2. **Ignoring low-severity findings** — Low findings compound; a chain of lows can become a critical exploit path\n3. **Skipping responsible disclosure** — Every vulnerability found must be reported through proper channels\n4. **Relying solely on automated tools** — Tools miss business logic flaws, chained exploits, and novel attack vectors\n5. **Testing without a defined scope** — Scope creep leads to legal liability; document what is and isn't in scope\n6. **Reporting without remediation guidance** — Every finding must include actionable remediation steps\n7. **Storing evidence insecurely** — Pen test evidence (screenshots, payloads, tokens) is sensitive; encrypt and restrict access\n8. **One-time testing** — Security testing must be continuous; integrate into CI\u002FCD and schedule periodic assessments\n\n---\n\n## Cross-References\n\n| Skill | Relationship |\n|-------|-------------|\n| [senior-secops](..\u002Fsenior-secops\u002FSKILL.md) | Defensive security operations — monitoring, incident response, SIEM configuration |\n| [senior-security](..\u002Fsenior-security\u002FSKILL.md) | Security policy and governance — frameworks, risk registers, compliance |\n| [dependency-auditor](..\u002F..\u002Fengineering\u002Fdependency-auditor\u002FSKILL.md) | Deep supply chain security — SBOMs, license compliance, transitive risk |\n| [code-reviewer](..\u002Fcode-reviewer\u002FSKILL.md) | Code review practices — includes security review checklist |\n","# Security Penetration Testing\n\nHands-on offensive security testing skill for finding vulnerabilities before attackers do. This is NOT compliance checking (see senior-secops) or security policy writing (see senior-security) — this is about systematic vulnerability discovery through authorized testing.\n\n---\n\n## Table of Contents\n\n- [Overview](#overview)\n- [OWASP Top 10 Systematic Audit](#owasp-top-10-systematic-audit)\n- [Static Analysis](#static-analysis)\n- [Dependency Vulnerability Scanning](#dependency-vulnerability-scanning)\n- [Secret Scanning](#secret-scanning)\n- [API Security Testing](#api-security-testing)\n- [Web Vulnerability Testing](#web-vulnerability-testing)\n- [Infrastructure Security](#infrastructure-security)\n- [Pen Test Report Generation](#pen-test-report-generation)\n- [Responsible Disclosure Workflow](#responsible-disclosure-workflow)\n- [Workflows](#workflows)\n- [Anti-Patterns](#anti-patterns)\n- [Cross-References](#cross-references)\n\n---\n\n## Overview\n\n### What This Skill Does\n\nThis skill provides the methodology, checklists, and automation for **offensive security testing** — actively probing systems to discover exploitable vulnerabilities. It covers web applications, APIs, infrastructure, and supply chain security.\n\n### Distinction from Other Security Skills\n\n| Skill | Focus | Approach |\n|-------|-------|----------|\n| **security-pen-testing** (this) | Finding vulnerabilities | Offensive — simulate attacker techniques |\n| senior-secops | Security operations | Defensive — monitoring, incident response, SIEM |\n| senior-security | Security policy | Governance — policies, frameworks, risk registers |\n| skill-security-auditor | CI\u002FCD gates | Automated — pre-merge security checks |\n\n### Prerequisites\n\nAll testing described here assumes **written authorization** from the system owner. Unauthorized testing is illegal under the CFAA and equivalent laws worldwide. Always obtain a signed scope-of-work or rules-of-engagement document before starting.\n\n---\n\n## OWASP Top 10 Systematic Audit\n\nUse the vulnerability scanner tool for automated checklist generation:\n\n```bash\n# Generate OWASP checklist for a web application\npython scripts\u002Fvulnerability_scanner.py --target web --scope full\n\n# Quick API-focused scan\npython scripts\u002Fvulnerability_scanner.py --target api --scope quick --json\n```\n\n### Quick Reference\n\n| # | Category | Key Tests |\n|---|----------|-----------|\n| A01 | Broken Access Control | IDOR, vertical escalation, CORS, JWT claim manipulation, forced browsing |\n| A02 | Cryptographic Failures | TLS version, password hashing, hardcoded keys, weak PRNG |\n| A03 | Injection | SQLi, NoSQLi, command injection, template injection, XSS |\n| A04 | Insecure Design | Rate limiting, business logic abuse, multi-step flow bypass |\n| A05 | Security Misconfiguration | Default credentials, debug mode, security headers, directory listing |\n| A06 | Vulnerable Components | Dependency audit (npm\u002Fpip\u002Fgo), EOL checks, known CVEs |\n| A07 | Auth Failures | Brute force, session cookie flags, session invalidation, MFA bypass |\n| A08 | Integrity Failures | Unsafe deserialization, SRI checks, CI\u002FCD pipeline integrity |\n| A09 | Logging Failures | Auth event logging, sensitive data in logs, alerting thresholds |\n| A10 | SSRF | Internal IP access, cloud metadata endpoints, DNS rebinding |\n\n```bash\n# Audit dependencies\npython scripts\u002Fdependency_auditor.py --file package.json --severity high\npython scripts\u002Fdependency_auditor.py --file requirements.txt --json\n```\n\nSee [owasp_top_10_checklist.md](references\u002Fowasp_top_10_checklist.md) for detailed test procedures, code patterns to detect, remediation steps, and CVSS scoring guidance for each category.\n\n---\n\n## Static Analysis\n\n**Recommended tools:** CodeQL (custom queries for project-specific patterns), Semgrep (rule-based scanning with auto-fix), ESLint security plugins (`eslint-plugin-security`, `eslint-plugin-no-unsanitized`).\n\nKey patterns to detect: SQL injection via string concatenation, hardcoded JWT secrets, unsafe YAML\u002Fpickle deserialization, missing security middleware (e.g., Express without Helmet).\n\nSee [attack_patterns.md](references\u002Fattack_patterns.md) for code patterns and detection payloads across injection types.\n\n---\n\n## Dependency Vulnerability Scanning\n\n**Ecosystem commands:** `npm audit`, `pip audit`, `govulncheck .\u002F...`, `bundle audit check`\n\n**CVE Triage Workflow:**\n1. **Collect** — Run ecosystem audit tools, aggregate findings\n2. **Deduplicate** — Group by CVE ID across direct and transitive deps\n3. **Prioritize** — Critical + exploitable + reachable = fix immediately\n4. **Remediate** — Upgrade, patch, or mitigate with compensating controls\n5. **Verify** — Rerun audit to confirm fix, update lock files\n\n```bash\npython scripts\u002Fdependency_auditor.py --file package.json --severity critical --json\n```\n\n---\n\n## Secret Scanning\n\n**Tools:** TruffleHog (git history + filesystem), Gitleaks (regex-based with custom rules).\n\n```bash\n# Scan git history for verified secrets\ntrufflehog git file:\u002F\u002F. --only-verified --json\n\n# Scan filesystem\ntrufflehog filesystem . --json\n```\n\n**Integration points:** Pre-commit hooks (gitleaks, trufflehog), CI\u002FCD gates (GitHub Actions with `trufflesecurity\u002Ftrufflehog@main`). Configure `.gitleaks.toml` for custom rules (AWS keys, API keys, private key headers) and allowlists for test fixtures.\n\n---\n\n## API Security Testing\n\n### Authentication Bypass\n\n- **JWT manipulation:** Change `alg` to `none`, RS256-to-HS256 confusion, claim modification (`role: \"admin\"`, `exp: 9999999999`)\n- **Session fixation:** Check if session ID changes after authentication\n\n### Authorization Flaws\n\n- **IDOR\u002FBOLA:** Change resource IDs in every endpoint — test read, update, delete across users\n- **BFLA:** Regular user tries admin endpoints (expect 403)\n- **Mass assignment:** Add privileged fields (`role`, `is_admin`) to update requests\n\n### Rate Limiting & GraphQL\n\n- **Rate limiting:** Rapid-fire requests to auth endpoints; expect 429 after threshold\n- **GraphQL:** Test introspection (should be disabled in prod), query depth attacks, batch mutations bypassing rate limits\n\nSee [attack_patterns.md](references\u002Fattack_patterns.md) for complete JWT manipulation payloads, IDOR testing methodology, BFLA endpoint lists, GraphQL introspection\u002Fdepth\u002Fbatch attack patterns, and rate limiting bypass techniques.\n\n---\n\n## Web Vulnerability Testing\n\n| Vulnerability | Key Tests |\n|--------------|-----------|\n| **XSS** | Reflected (script\u002Fimg\u002Fsvg payloads), Stored (persistent fields), DOM-based (innerHTML + location.hash) |\n| **CSRF** | Replay without token (expect 403), cross-session token replay, check SameSite cookie attribute |\n| **SQL Injection** | Error-based (`' OR 1=1--`), union-based enumeration, time-based blind (`SLEEP(5)`), boolean-based blind |\n| **SSRF** | Internal IPs, cloud metadata endpoints (AWS\u002FGCP\u002FAzure), IPv6\u002Fhex\u002Fdecimal encoding bypasses |\n| **Path Traversal** | `..\u002F..\u002F..\u002Fetc\u002Fpasswd`, URL encoding, double encoding bypasses |\n\nSee [attack_patterns.md](references\u002Fattack_patterns.md) for complete test payloads (XSS filter bypasses, context-specific XSS, SQL injection per database engine, SSRF bypass techniques, and DOM-based XSS source\u002Fsink pairs).\n\n---\n\n## Infrastructure Security\n\n**Key checks:**\n- **Cloud storage:** S3 bucket public access (`aws s3 ls s3:\u002F\u002Fbucket --no-sign-request`), bucket policies, ACLs\n- **HTTP security headers:** HSTS, CSP (no `unsafe-inline`\u002F`unsafe-eval`), X-Content-Type-Options, X-Frame-Options, Referrer-Policy\n- **TLS configuration:** `nmap --script ssl-enum-ciphers -p 443 target.com` or `testssl.sh` — reject TLS 1.0\u002F1.1, RC4, 3DES, export-grade ciphers\n- **Port scanning:** `nmap -sV target.com` — flag dangerous open ports (FTP\u002F21, Telnet\u002F23, Redis\u002F6379, MongoDB\u002F27017)\n\n---\n\n## Pen Test Report Generation\n\nGenerate professional reports from structured findings:\n\n```bash\n# Generate markdown report from findings JSON\npython scripts\u002Fpentest_report_generator.py --findings findings.json --format md --output report.md\n\n# Generate JSON report\npython scripts\u002Fpentest_report_generator.py --findings findings.json --format json --output report.json\n```\n\n### Findings JSON Format\n\n```json\n[\n  {\n    \"title\": \"SQL Injection in Login Endpoint\",\n    \"severity\": \"critical\",\n    \"cvss_score\": 9.8,\n    \"cvss_vector\": \"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H\",\n    \"category\": \"A03:2021 - Injection\",\n    \"description\": \"The \u002Fapi\u002Flogin endpoint is vulnerable to SQL injection via the email parameter.\",\n    \"evidence\": \"Request: POST \u002Fapi\u002Flogin {\\\"email\\\": \\\"' OR 1=1--\\\", \\\"password\\\": \\\"x\\\"}\\nResponse: 200 OK with admin session token\",\n    \"impact\": \"Full database access, authentication bypass, potential remote code execution\",\n    \"remediation\": \"Use parameterized queries. Replace string concatenation with prepared statements.\",\n    \"references\": [\"https:\u002F\u002Fcwe.mitre.org\u002Fdata\u002Fdefinitions\u002F89.html\"]\n  }\n]\n```\n\n### Report Structure\n\n1. **Executive Summary**: Business impact, overall risk level, top 3 findings\n2. **Scope**: What was tested, what was excluded, testing dates\n3. **Methodology**: Tools used, testing approach (black\u002Fgray\u002Fwhite box)\n4. **Findings Table**: Sorted by severity with CVSS scores\n5. **Detailed Findings**: Each with description, evidence, impact, remediation\n6. **Remediation Priority Matrix**: Effort vs. impact for each fix\n7. **Appendix**: Raw tool output, full payload lists\n\n---\n\n## Responsible Disclosure Workflow\n\nResponsible disclosure is **mandatory** for any vulnerability found during authorized testing. Standard timeline: report on day 1, follow up at day 7, status update at day 30, public disclosure at day 90.\n\n**Key principles:** Never exploit beyond proof of concept, encrypt all communications, do not access real user data, document everything with timestamps.\n\nSee [responsible_disclosure.md](references\u002Fresponsible_disclosure.md) for full disclosure timelines (standard 90-day, accelerated 30-day, extended 120-day), communication templates, legal considerations, bug bounty program integration, and CVE request process.\n\n---\n\n## Workflows\n\n### Workflow 1: Quick Security Check (15 Minutes)\n\nFor pre-merge reviews or quick health checks:\n\n```bash\n# 1. Generate OWASP checklist\npython scripts\u002Fvulnerability_scanner.py --target web --scope quick\n\n# 2. Scan dependencies\npython scripts\u002Fdependency_auditor.py --file package.json --severity high\n\n# 3. Check for secrets in recent commits\n# (Use gitleaks or trufflehog as described in Secret Scanning section)\n\n# 4. Review HTTP security headers\ncurl -sI https:\u002F\u002Ftarget.com | grep -iE \"(strict-transport|content-security|x-frame|x-content-type)\"\n```\n\n**Decision**: If any critical or high findings, block the merge.\n\n### Workflow 2: Full Penetration Test (Multi-Day Assessment)\n\n**Day 1 — Reconnaissance:**\n1. Map the attack surface: endpoints, authentication flows, third-party integrations\n2. Run automated OWASP checklist (full scope)\n3. Run dependency audit across all manifests\n4. Run secret scan on full git history\n\n**Day 2 — Manual Testing:**\n1. Test authentication and authorization (IDOR, BOLA, BFLA)\n2. Test injection points (SQLi, XSS, SSRF, command injection)\n3. Test business logic flaws\n4. Test API-specific vulnerabilities (GraphQL, rate limiting, mass assignment)\n\n**Day 3 — Infrastructure and Reporting:**\n1. Check cloud storage permissions\n2. Verify TLS configuration and security headers\n3. Port scan for unnecessary services\n4. Compile findings into structured JSON\n5. Generate pen test report\n\n```bash\n# Generate final report\npython scripts\u002Fpentest_report_generator.py --findings findings.json --format md --output pentest-report.md\n```\n\n### Workflow 3: CI\u002FCD Security Gate\n\nAutomated security checks on every PR: secret scanning (TruffleHog), dependency audit (`npm audit`, `pip audit`), SAST (Semgrep with `p\u002Fsecurity-audit`, `p\u002Fowasp-top-ten`), and security headers check on staging.\n\n**Gate Policy**: Block merge on critical\u002Fhigh findings. Warn on medium. Log low\u002Finfo.\n\n---\n\n## Anti-Patterns\n\n1. **Testing in production without authorization** — Always get written permission and use staging\u002Ftest environments when possible\n2. **Ignoring low-severity findings** — Low findings compound; a chain of lows can become a critical exploit path\n3. **Skipping responsible disclosure** — Every vulnerability found must be reported through proper channels\n4. **Relying solely on automated tools** — Tools miss business logic flaws, chained exploits, and novel attack vectors\n5. **Testing without a defined scope** — Scope creep leads to legal liability; document what is and isn't in scope\n6. **Reporting without remediation guidance** — Every finding must include actionable remediation steps\n7. **Storing evidence insecurely** — Pen test evidence (screenshots, payloads, tokens) is sensitive; encrypt and restrict access\n8. **One-time testing** — Security testing must be continuous; integrate into CI\u002FCD and schedule periodic assessments\n\n---\n\n## Cross-References\n\n| Skill | Relationship |\n|-------|-------------|\n| [senior-secops](..\u002Fsenior-secops\u002FSKILL.md) | Defensive security operations — monitoring, incident response, SIEM configuration |\n| [senior-security](..\u002Fsenior-security\u002FSKILL.md) | Security policy and governance — frameworks, risk registers, compliance |\n| [dependency-auditor](..\u002F..\u002Fengineering\u002Fdependency-auditor\u002FSKILL.md) | Deep supply chain security — SBOMs, license compliance, transitive risk |\n| [code-reviewer](..\u002Fcode-reviewer\u002FSKILL.md) | Code review practices — includes security review checklist |\n",{"name":5,"description":7},"main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","engineering-team\u002Fsecurity-pen-testing",2,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill","https:\u002F\u002Fgithub.com\u002Fafaizalam2003","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fmdfaizalam2003\u002F","2026-04-01 04:35:43",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill security-pen-testing",{"tool":68,"command":69},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill security-pen-testing",{"tool":71,"command":72},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill security-pen-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fsecurity-pen-testing\u002FSKILL.md",true,[76,82,86,90,96,100],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fattack_patterns.md","REFERENCE","参考文档",15372,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fsecurity-pen-testing\u002Freferences\u002Fattack_patterns.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fowasp_top_10_checklist.md",18137,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fsecurity-pen-testing\u002Freferences\u002Fowasp_top_10_checklist.md",{"path":87,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fresponsible_disclosure.md",11452,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fsecurity-pen-testing\u002Freferences\u002Fresponsible_disclosure.md",{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"scripts\u002Fdependency_auditor.py","SCRIPT","脚本",21056,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fsecurity-pen-testing\u002Fscripts\u002Fdependency_auditor.py",{"path":97,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":98,"sourceHtmlUrl":99},"scripts\u002Fpentest_report_generator.py",19028,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fsecurity-pen-testing\u002Fscripts\u002Fpentest_report_generator.py",{"path":101,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":102,"sourceHtmlUrl":103},"scripts\u002Fvulnerability_scanner.py",27269,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fsecurity-pen-testing\u002Fscripts\u002Fvulnerability_scanner.py",[105,134,159,184,214,234],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":114,"publishedAt":49},"01M6KC4E8MYR9DBAZTAXHKYMMH","soc2-compliance","Use when the user asks to prepare for SOC 2 audits, map Trust Service Criteria, build control matrices, collect audit evidence, perform gap analysis, or assess SOC 2 Type I vs Type II readiness.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fsoc2-compliance\u002FSKILL.md",[111],{"categoryNo":112,"categoryName":113,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务",[115,116,117,118,119,120,121,46,122,123,124,125,126,127,128,129,130,131,132,133],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","use","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess","for",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":49},"01M6KC461R3GKGZ1TAYHVR1MW9","risk-management-specialist","Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[141,142,143,144,145,146,147,148,46,122,149,150,151,152,153,154,155,156,157,158],"risk","risk management specialist","management","risk management","risk evaluation","product","Evaluation","lifecycle","risk matrix","iso","medical","iso 14971","identification","information","post-production","tree","matrix","implementing",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":49},"01M6KC3HF5ZFSSP2NZF68PEPFB","regulatory-affairs-head","Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[166,167,168,169,170,171,172,173,174,122,175,176,177,178,179,180,181,182,183,133],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","strategy","standards","queries","manage","strategies","de","users","respond","medical devices","manager",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":196,"publishedAt":49},"01M6KC34Z8M1559EY1CXYBJB1A","quality-manager-qms-iso13485","ISO 13485 Quality Management System implementation and maintenance for medical device organizations. Provides QMS design, documentation control, internal auditing, CAPA management, and certification support. Use when working with medical device quality systems, preparing for ISO 13485 audits, managing regulatory compliance documentation, setting up corrective actions, or building audit preparation programs. Useful for quality management, audit preparation, regulatory compliance, medical device documentation, and corrective action workflows.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[190,193],{"categoryNo":191,"categoryName":192,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":194,"categoryName":195,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师",[197,198,183,199,200,201,202,203,204,122,205,206,207,208,209,210,211,212,133,213],"quality manager qms iso13485","quality","design","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":221,"publishedAt":49},"01M6KC2FXHBHXYX2ZZ17Y3GDB4","quality-manager-qmr","Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[220],{"categoryNo":112,"categoryName":113,"taxonomyType":26,"taxonomyTypeDesc":27},[222,198,183,223,224,225,226,227,115,228,204,229,167,230,231,232,150,209,133,233],"quality manager qmr","review","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":235,"name":236,"nameZh":6,"description":237,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":238,"categories":239,"keywords":247,"publishedAt":49},"01M6KC1VRR5JTDBNZANHPS6VR6","quality-documentation-manager","Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[240,243,246],{"categoryNo":241,"categoryName":242,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":244,"categoryName":245,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":112,"categoryName":113,"taxonomyType":26,"taxonomyTypeDesc":27},[248,249,198,183,223,250,251,119,204,252,253,254,255,256,151,257,258,259,260,133],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]