[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M783TWEMKAS79SB7VT9885PQ":3,"skill-same:01M783TWEMKAS79SB7VT9885PQ":72},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M783TWEMKAS79SB7VT9885PQ","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.","motivatedc-creator\u002FSaafy","motivatedc-creator","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F250662783?v=4","01M782H2D8C7XJGXMJC3YHQAWK","Happy Haris","01M782H2ERMBYEM1NSPPPC06S0",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fsecurity-pen-testing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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](engineering\u002Fskills\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](engineering\u002Fskills\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","55ae24ca5523c0499dd70b2874ef674a0e66a85b","engineering-team\u002Fskills\u002Fsecurity-pen-testing","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator","2026-07-04 02:45:55",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add motivatedc-creator\u002FSaafy --skill security-pen-testing",{"tool":36,"command":37},"bunx","bunx skills add motivatedc-creator\u002FSaafy --skill security-pen-testing",{"tool":39,"command":40},"pnpm","pnpm dlx skills add motivatedc-creator\u002FSaafy --skill security-pen-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fsecurity-pen-testing\u002FSKILL.md",true,[44,50,54,58,64,68],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"references\u002Fattack_patterns.md","REFERENCE","参考文档",15372,"https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fsecurity-pen-testing\u002Freferences\u002Fattack_patterns.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fowasp_top_10_checklist.md",18137,"https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fsecurity-pen-testing\u002Freferences\u002Fowasp_top_10_checklist.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fresponsible_disclosure.md",11452,"https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fsecurity-pen-testing\u002Freferences\u002Fresponsible_disclosure.md",{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"scripts\u002Fdependency_auditor.py","SCRIPT","脚本",21056,"https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fsecurity-pen-testing\u002Fscripts\u002Fdependency_auditor.py",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"scripts\u002Fpentest_report_generator.py",19028,"https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fsecurity-pen-testing\u002Fscripts\u002Fpentest_report_generator.py",{"path":69,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":70,"sourceHtmlUrl":71},"scripts\u002Fvulnerability_scanner.py",27269,"https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering-team\u002Fskills\u002Fsecurity-pen-testing\u002Fscripts\u002Fvulnerability_scanner.py",[73,80,87,94,101,108],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M78558T3RQ22S1B5H0FJAY1Y","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7854YEAAV883M2PKS04TQEK","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7854NCGDBQ6Q0QG2YY4VHSX","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M78549YZMPYGC1F6S7ZJ4VF8","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M78541PWEQMBPN91PEZZK8H7","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M7853P7CWJNW5G0Z99YB6H5D","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]