์Šคํ‚ฌ security-audit
๐Ÿ”’

security-audit

์•ˆ์ „

Run Comprehensive Security Audits

๋˜ํ•œ ๋‹ค์Œ์—์„œ ์‚ฌ์šฉํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค: Consiliency,Joseph OBrien,Joseph OBrien,AppleLamps,ClementWalter

This workflow bundle orchestrates multiple security skills to conduct full penetration tests, vulnerability assessments, and security hardening across web applications and APIs.

์ง€์›: Claude Codex Code(CC)
๐Ÿฅ‰ 73 ๋ธŒ๋ก ์ฆˆ
1

์Šคํ‚ฌ ZIP ๋‹ค์šด๋กœ๋“œ

2

Claude์—์„œ ์—…๋กœ๋“œ

์„ค์ • โ†’ ๊ธฐ๋Šฅ โ†’ ์Šคํ‚ฌ โ†’ ์Šคํ‚ฌ ์—…๋กœ๋“œ๋กœ ์ด๋™

3

ํ† ๊ธ€์„ ์ผœ๊ณ  ์‚ฌ์šฉ ์‹œ์ž‘

ํ…Œ์ŠคํŠธํ•ด ๋ณด๊ธฐ

"security-audit" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. Run a security audit on my REST API

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

I will conduct a comprehensive security audit of your REST API following our structured workflow.

**Phase 1: Reconnaissance**
- Identify API endpoints and technology stack
- Gather intelligence on exposed services

**Phase 2: Vulnerability Scanning**
- Run automated vulnerability scanners
- Perform static analysis
- Scan dependencies for known vulnerabilities

**Phase 4: API Security Testing**
- Enumerate all API endpoints
- Test authentication mechanisms
- Test for rate limiting bypasses
- Test input validation and error handling

Shall I proceed with any specific phase?

"security-audit" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. Help me test for SQL injection vulnerabilities

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

I will guide you through SQL injection testing using the @sql-injection-testing skill.

**Testing Approach:**
1. Identify injection points in your application
2. Test for SQL injection using manual techniques
3. Use automated tools to enumerate vulnerabilities
4. Document proof of concept for each finding

Would you like me to proceed with testing specific endpoints?

๋ณด์•ˆ ๊ฐ์‚ฌ

์•ˆ์ „
v1 โ€ข 2/25/2026

All static findings are false positives. The 48 external_command detections are markdown code blocks using backticks for prompt examples, not actual shell execution. The Metasploit reference is a skill name to invoke, not tool execution. The weak crypto alerts are triggered by the word 'vulnerability' in context. This is a documentation-only workflow bundle with no executable code.

1
์Šค์บ”๋œ ํŒŒ์ผ
219
๋ถ„์„๋œ ์ค„ ์ˆ˜
3
๋ฐœ๊ฒฌ ์‚ฌํ•ญ
1
์ด ๊ฐ์‚ฌ ์ˆ˜
๋‚ฎ์€ ์œ„ํ—˜ ๋ฌธ์ œ (3)
False Positive: External Command Detection
Static scanner detected 48 instances of backtick usage as 'external commands'. These are markdown code block delimiters for example prompts, not actual Ruby/shell execution. No command injection risk exists.
False Positive: Metasploit Framework Reference
Static scanner flagged 'Metasploit framework' as a blocker. This is a reference to an external skill name (@metasploit-framework) to invoke, not actual Metasploit tool usage.
False Positive: Weak Cryptographic Algorithm
Static scanner flagged 'weak cryptographic algorithm' at lines 3 and 192. These are false positives triggered by the word 'vulnerability' in the description and 'Using Components with Known Vulnerabilities' from OWASP Top 10 checklist.
๊ฐ์‚ฌ์ž: claude

ํ’ˆ์งˆ ์ ์ˆ˜

38
์•„ํ‚คํ…์ฒ˜
100
์œ ์ง€๋ณด์ˆ˜์„ฑ
85
์ฝ˜ํ…์ธ 
50
์ปค๋ฎค๋‹ˆํ‹ฐ
99
๋ณด์•ˆ
83
์‚ฌ์–‘ ์ค€์ˆ˜

๋งŒ๋“ค ์ˆ˜ ์žˆ๋Š” ๊ฒƒ

Security Consultant Auditing Client Web App

Use the full workflow to conduct a comprehensive security assessment following industry-standard methodologies.

Developer Securing Own Application

Use vulnerability scanning and hardening phases to find and fix security issues before production deployment.

DevSecOps Team Running Automated Scans

Integrate scanning phases into CI/CD pipelines for continuous security validation.

์ด ํ”„๋กฌํ”„ํŠธ๋ฅผ ์‚ฌ์šฉํ•ด ๋ณด์„ธ์š”

Start Full Security Audit
Use @security-audit to run a comprehensive security audit on my web application. Start with reconnaissance and work through all phases.
Quick Vulnerability Scan
Use @security-audit to perform Phase 2 vulnerability scanning on my application. Focus on automated scanner results.
API Security Test
Use @security-audit to conduct Phase 4 API security testing. Test authentication, rate limiting, and input validation.
Generate Security Report
Use @security-audit Phase 7 reporting to document all findings and create a remediation plan for the vulnerabilities found.

๋ชจ๋ฒ” ์‚ฌ๋ก€

  • Always obtain written authorization before testing any target
  • Follow the workflow phases in order for comprehensive coverage
  • Document all findings with proof of concept evidence
  • Use the OWASP Top 10 checklist as minimum coverage baseline

ํ”ผํ•˜๊ธฐ

  • Running penetration tests without proper authorization
  • Skipping reconnaissance and jumping directly to exploitation
  • Ignoring findings from automated scanners without manual verification
  • Failing to document findings with reproducible steps

์ž์ฃผ ๋ฌป๋Š” ์งˆ๋ฌธ

Does this skill actually run security scanners?
No. This is a workflow bundle that provides guidance and orchestrates other security skills. It does not execute actual scanning tools.
Do I need other skills installed?
Yes. This workflow references other skills like scanning-tools, vulnerability-scanner, and pentest-commands. These must be available for full functionality.
Is this tool safe to use on any website?
No. Only use on systems you own or have explicit written authorization to test. Unauthorized penetration testing is illegal.
Can this generate a final security report?
The workflow includes Phase 7 for reporting, which helps structure findings and remediation steps. Final report generation requires manual compilation.
What OWASP categories are covered?
The workflow covers all OWASP Top 10 categories including injection, broken authentication, sensitive data exposure, XXE, broken access control, security misconfiguration, XSS, insecure deserialization, vulnerable components, and insufficient logging.
Does this work with Claude Code and Codex?
Yes. This skill supports claude, codex, and claude-code tools as specified in the supported_tools field.

๊ฐœ๋ฐœ์ž ์„ธ๋ถ€ ์ •๋ณด

์ž‘์„ฑ์ž

sickn33

๋ผ์ด์„ ์Šค

MIT

์ฐธ์กฐ

main

ํŒŒ์ผ ๊ตฌ์กฐ

๐Ÿ“„ SKILL.md