security-compliance-skills-suite-claude skill by reason-machines

🔒 Security & Compliance Skills Suite

Skill by ara.so — Security Skills collection.

A comprehensive skill suite for security audits, vulnerability management, compliance frameworks (GDPR, SOC2, ISO27001), and incident response. Derived from hesreallyhim/awesome-claude-code with specialized commands and workflows for security professionals.

What This Project Does

This skill suite provides AI coding agents with 10 specialized security commands and 5 multi-step workflows to:

Perform OWASP Top-10 vulnerability scans
Audit dependencies for known CVEs
Generate GDPR/SOC2/ISO27001 compliance reports
Create STRIDE threat models
Detect secrets and credentials in code
Audit IAM permissions for least-privilege violations
Orchestrate security incident response
Design zero-trust architectures

All commands use structured output with progress tracking, severity-sorted findings, and actionable remediation steps.

Installation

Method 1: Direct Clone

# Clone to Claude Code skills directory
mkdir -p ~/.claude/skills
git clone https://github.com/sparkfinderoven/r01-hesreallyhim-awesome-claude-code-security.git \
  ~/.claude/skills/security-compliance-suite
 
# Register in Claude Code session

Method 2: Manual Setup

Verification

In a Claude Code session:

Core Commands

`/owasp-scan` - OWASP Top-10 Vulnerability Scan

Scans code for OWASP Top-10 vulnerabilities with CVSS scores and remediation guidance.

Usage:

Example:

Output Structure:

`/dep-cve` - Dependency CVE Scanner

Scans project dependencies for known CVEs with exploitability scores.

Usage:

Example:

Supported Ecosystems:

Python: requirements.txt, Pipfile, pyproject.toml
JavaScript: package.json, package-lock.json, yarn.lock
Ruby: Gemfile.lock
Java: pom.xml, build.gradle
Go: go.mod, go.sum
Rust: Cargo.lock

Output Example:

`/gdpr-audit` - GDPR Compliance Audit

Maps data flows, identifies consent gaps, and generates DPA checklist.

Usage:

Example:

Analysis Coverage:

Personal data collection points
Lawful basis for processing (Article 6)
Consent mechanisms (Article 7)
Data subject rights implementation (Articles 15-22)
Data retention policies (Article 5)
Third-party data processors (Article 28)
Data breach notification (Articles 33-34)

Output Example:

`/soc2-readiness` - SOC 2 Type II Readiness Assessment

Gap analysis across all 5 Trust Service Criteria.

Usage:

Example:

Trust Service Criteria:

CC: Common Criteria (governance, risk assessment, monitoring)
A: Availability (uptime, incident management)
C: Confidentiality (data protection, encryption)
P: Processing Integrity (data accuracy, completeness)
PI: Privacy (notice, choice, access)

Output Example:

`/threat-model` - STRIDE Threat Modeling

Generates STRIDE threat models from architecture diagrams with risk matrices.

Usage:

Example:

STRIDE Categories:

Spoofing: Authentication threats
Tampering: Integrity threats
Repudiation: Non-repudiation threats
Information Disclosure: Confidentiality threats
Denial of Service: Availability threats
Elevation of Privilege: Authorization threats

Output Example:

`/secret-detect` - Secret Detection

Pre-commit hook configuration with entropy scanning.

Usage:

Example:

Detection Patterns:

AWS keys (AKIA*, ASIA*)
API keys (high-entropy strings)
Private keys (BEGIN PRIVATE KEY)
OAuth tokens
Database credentials
JWT secrets
Slack/Discord webhooks

Setup Output:

History Scan Example:

`/iam-audit` - IAM Least-Privilege Audit

Audits IAM roles for over-permissioned access, stale credentials, and MFA gaps.

Usage:

Example:

Configuration:

Output Example:

`/incident-playbook` - Security Incident Response

Orchestrates incident response: triage → contain → eradicate → recover → lessons.

Usage:

Example:

Incident Types:

breach: Data breach / unauthorized access
ransomware: Ransomware infection
ddos: Distributed denial of service
insider: Insider threat / privilege abuse

Playbook Flow:

`/privacy-policy` - Privacy Policy Generator

Generates GDPR/CCPA-compliant privacy policies from data inventory.

Usage:

Example:

Input (Data Inventory):

Generated Policy Sections:

Multi-Step Workflows

`secure-sdlc` - Secure Software Development Lifecycle

Shift-left security workflow: threat model → SAST → DAST → pen test → sign-off.

Usage:

Workflow Stages:

`breach-response` - Data Breach Response

Orchestrates breach response: detect → assess → notify → remediate → post-mortem.

Usage:

Workflow:

`compliance-audit` - Full Compliance Audit

End-to-end audit: scope → gap analysis → evidence collection → remediation plan.

Usage:

`zero-trust-design` - Zero Trust Architecture

Design workflow: identity → network → workload → data layer security.

Usage:

Design Layers:

`vendor-security` - Third-Party Vendor Assessment

Vendor risk assessment: questionnaire → risk scoring → decision framework.

Usage:

Assessment Domains:

Security certifications (SOC 2, ISO 27001)
Data processing agreements
Incident response capabilities
Business continuity plans
Subprocessor disclosure

Configuration

Global Settings

Create ~/.security-skills/config.yaml:

Environment Variables

Common Patterns

Pattern 1: Pre-Deployment Security Gate

Pattern 2: Continuous Compliance Monitoring

Pattern 3: Incident Response Automation

Pattern 4: Shift-Left Security in CI/CD

# .github/workflows/security.yml
name: Security Checks
on: [push, pull_request]
 
jobs:
  security:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      
      - name: OWASP Scan
        run: /owasp-scan ./src --format=json --output=owasp.json
        
      - name: Dependency CVE Check
        run: /dep-cve --scope=all --output=json --output=cve.json
        
      - name: Secret Detection
        run: /secret-detect

security-compliance-skills-suite-claude

Documentation

Documentation