security-testing-patterns — Claude Code skill: what it does and setup
security-testing-patterns guides security testing workflows across SAST, SCA, DAST, and OWASP API audits. Use it to build CI/CD scanning pipelines and triage vulnerabilities.
MIT 154 installs ★ 71 updated 2026-06-29
npx skills add NickCrew/Claude-Cortex --skill security-testing-patterns -a claude-codeWhat security-testing-patterns does
The skill triggers on paths like **/auth/**, **/security/**, Dockerfiles, and files with secrets. It structures testing around a layered pyramid: unit encryption checks, static code analysis, dependency audits via tools like Trivy or Snyk, and dynamic runtime tests.
Detailed guides live in skills/security-testing-patterns/references/, covering topics such as fuzzing, penetration testing, and pipeline automation. The workflow organizes security into five distinct phases, moving from threat modeling to false positive filtering and fix verification.
Running DAST without proper authentication credentials leaves protected endpoints completely untested. The skill enforces authenticated scanning configurations and risk-weighted issue sorting instead of blindly fixing alerts in bulk.
What it helps with
- configure SAST and SCA scanning in CI/CD pipelines
- audit REST endpoints against OWASP API Top 10 guidelines
- filter false positives and prioritize findings by exploitability
- inspect Docker images and dependency manifests for vulnerabilities
Example prompts for the agent
- Set up a layered security testing workflow for our auth service
- Audit this Dockerfile and docker-compose setup for misconfigurations
- Review these API endpoints against OWASP security requirements
How to install security-testing-patterns
1Skills CLI (Vercel)
npx skills add NickCrew/Claude-Cortex --skill security-testing-patterns -a claude-code2Manually: put the files in place
~/.claude/skills/security-testing-patterns/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/security-testing-patterns/
1Skills CLI (Vercel)
npx skills add NickCrew/Claude-Cortex --skill security-testing-patterns -a codex2Manually: put the files in place
.agents/skills/security-testing-patterns/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add NickCrew/Claude-Cortex --skill security-testing-patterns -a cursor2Manually: put the files in place
.cursor/skills/security-testing-patterns/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install NickCrew/Claude-Cortex skills/security-testing-patterns2Manually: put the files in place
.github/skills/security-testing-patterns/SKILL.md1Skills CLI (Vercel)
npx skills add NickCrew/Claude-Cortex --skill security-testing-patterns -a gemini-cli2Platform CLI
gemini skills install https://github.com/NickCrew/Claude-Cortex --path skills/security-testing-patternsManually: put the files in place
.devin/skills/security-testing-patterns/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add NickCrew/Claude-Cortex --skill security-testing-patterns -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about security-testing-patterns
How to install security-testing-patterns in Claude Code?
Run npx skills add NickCrew/Claude-Cortex --skill security-testing-patterns -a claude-code. The instructions install into ~/.claude/skills/security-testing-patterns/SKILL.md.
What does security-testing-patterns do?
It gives the assistant guidelines and reference files for static scanning, dependency checks, dynamic testing, and manual penetration reviews.
Which files automatically trigger this skill?
It triggers on patterns matching **/auth/**, **/security/**, Dockerfile, docker-compose*.yml, and secret-related source files in Python or TypeScript.
Source text
SKILL.md · MIT
--- name: security-testing-patterns description: Security testing patterns including SAST, DAST, penetration testing, and vulnerability assessment techniques. Use when implementing security testing pipelines, conducting security audits, or validating application security controls. keywords: - DAST - SAST - fuzz testing - pen test - penetration testing - security assessment - security automation - security testing - threat detection - vulnerability scanning file_patterns: - '**/*secret*.py' - '**/*secret*.ts' - '**/Dockerfile' - '**/auth/**' - '**/docker-compose*.yml' - '**/security/**' confidence: 0.8 --- # Security Testing Patterns Expert guidance for implementing comprehensive security testing strategies including static analysis, dynamic testing, penetration testing, and vulnerability assessment. ## When to Use This Skill - Implementing security testing pipelines in CI/CD - Conducting security audits and vulnerability assessments - Validating application security controls and defenses - Performing penetration testing and security reviews - Configuring SAST/DAST tools and interpreting results - Testing authentication and authorization mechanisms - Evaluating API security and compliance with OWASP standards - Integrating security scanning into development workflows - Responding to security findings and prioritizing remediation - Training teams on security testing methodologies ## Core Concepts ### Security Testing Pyramid (Layered Approach) 1. **Unit Security Tests** - Test security functions (encryption, validation) 2. **SAST** - Static analysis during development 3. **SCA** - Dependency and component vulnerability scanning 4. **DAST** - Dynamic testing in running applications 5. **IAST** - Interactive analysis combining SAST and DAST 6. **Penetration Testing** - Manual security testing by experts 7. **Red Team Exercises** - Adversarial simulation testing ### Testing Categories **Static Testing (SAST)** - Analyzes source code without execution - Early detection in development lifecycle - Complete code coverage - High false positive rates **Dynamic Testing (DAST)** - Tests running applications - Detects runtime and configuration issues - Language agnostic - Requires deployed environment **Composition Analysis (SCA)** - Scans dependencies for vulnerabilities - Tracks license compliance - Automated remediation options **Manual Testing** - Penetration testing - Business logic validation - Complex attack scenarios ## Quick Reference | Task | Load reference | | --- | --- | | Static Application Security Testing (SAST) | `skills/security-testing-patterns/references/sast.md` | | Dynamic Application Security Testing (DAST) | `skills/security-testing-patterns/references/dast.md` | | Software Composition Analysis (SCA) | `skills/security-testing-patterns/references/sca.md` | | Penetration Testing Techniques | `skills/security-testing-patterns/references/penetration-testing.md` | | API Security Testing (OWASP Top 10) | `skills/security-testing-patterns/references/api-security.md` | | Fuzzing and Property-Based Testing | `skills/security-testing-patterns/references/fuzzing.md` | | Security Automation Pipeline | `skills/security-testing-patterns/references/automation-pipeline.md` | ## Security Testing Workflow ### Phase 1: Planning 1. Define security requirements and threat model 2. Select appropriate testing tools and techniques 3. Establish baseline security posture 4. Set severity thresholds and acceptance criteria ### Phase 2: Automated Testing 1. **SAST** - Integrate into IDE and CI/CD pipeline 2. **SCA** - Configure dependency scanning (npm audit, Snyk, Dependabot) 3. **DAST** - Schedule scans against deployed environments 4. **Container Scanning** - Scan Docker images (Trivy, Aqua) ### Phase 3: Manual Testing 1. Authentication and authorization testing 2. Business logic vulnerability assessment 3. API security testing (OWASP API Top 10) 4. Penetration testing and exploitation ### Phase 4: Analysis and Remediation 1. Triage findings by severity and exploitability 2. Eliminate false positives 3. Prioritize remediation based on risk 4. Track vulnerabilities to resolution 5. Verify fixes with regression testing ### Phase 5: Continuous Monitoring 1. Monitor for new vulnerabilities in dependencies 2. Re-scan after code changes 3. Conduct periodic penetration tests 4. Update security baselines and policies ## Common Mistakes ### Tool Selection - **Wrong**: Using only SAST or only DAST - **Right**: Layered approach combining multiple testing types ### False Positive Management - **Wrong**: Ignoring or suppressing findings without review - **Right**: Systematic triage process with security team validation ### Integration Timing - **Wrong**: Security testing only before release - **Right**: Continuous security testing throughout development ### Scope Definition - **Wrong**: Testing only main application code - **Right**: Include dependencies, APIs, infrastructure, and third-party integrations ### Remediation Priority - **Wrong**: Fixing all findings equally - **Right**: Risk-based prioritization (severity × exploitability × business impact) ### Authentication in Testing - **Wrong**: DAST scans without authentication - **Right**: Configure authenticated scanning to test protected features ## Best Practices 1. **Shift Left**: Integrate security testing early in development 2. **Continuous Testing**: Automate security scans in CI/CD pipelines 3. **Layered Approach**: Combine SAST, DAST, SCA, and manual testing 4. **Risk-Based Testing**: Prioritize testing based on threat model 5. **False Positive Management**: Establish process for triaging findings 6. **Remediation Tracking**: Use SIEM/SOAR for vulnerability management 7. **Regular Updates**: Keep security tools and signatures current 8. **Security Champions**: Train developers in security testing 9. **Metrics and KPIs**: Track security posture over time 10. **Compliance Validation**: Map tests to regulatory requirements ## Resources - **OWASP Testing Guide**: https://owasp.org/www-project-web-security-testing-guide/ - **OWASP API Security**: https://owasp.org/www-project-api-security/ - **NIST SP 800-115**: Technical Guide to Information Security Testing - **PTES**: Penetration Testing Execution Standard - **SANS Security Testing**: https://www.sans.org/security-resources/ - **HackerOne Methodology**: https://www.hackerone.com/ethical-hacker/hack-learn - **PortSwigger Academy**: https://portswigger.net/web-security
© NickCrew · MIT · NickCrew/Claude-Cortex