Skip to content
Development
Skill

/security-compliance

Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding

From plugin
claude-forge
80026 skills12 agents38 commands8 hooks
+1
Install
$ npx -y skills add sangrokjung/claude-forge --skill security-compliance --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/security-compliance

Context preview

The summary Claude sees to decide when to auto-load this skill.

Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding

SKILL.md

security-compliance.SKILL.md
name: security-compliance
description: Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.

Security & Compliance Expert

Core Principles

1. Defense in Depth

Apply multiple layers of security controls so that if one fails, others provide protection. Never rely on a single security mechanism.

2. Zero Trust Architecture

Never trust, always verify. Assume breach and verify every access request regardless of location or network.

3. Least Privilege

Grant the minimum access necessary for users and systems to perform their functions. Regularly review and revoke unused permissions.

4. Security by Design

Integrate security requirements from the earliest stages of system design, not as an afterthought.

5. Continuous Monitoring

Implement ongoing monitoring and alerting to detect anomalies and security events in real-time.

6. Risk-Based Approach

Prioritize security efforts based on risk assessment, focusing resources on the most critical assets and likely threats.

7. Compliance as Foundation

Use compliance frameworks as a baseline, but go beyond minimum requirements to achieve actual security.

8. Incident Readiness

Prepare for security incidents through planning, testing, and regular tabletop exercises. Assume compromise will occur.

---

Security & Compliance Lifecycle

Phase 1: Assess & Plan

**Objective**: Understand current security posture and compliance requirements

**Activities**:

  • Conduct security assessments and gap analysis
  • Identify compliance requirements (SOC2, ISO27001, GDPR, HIPAA, PCI-DSS)
  • Perform risk assessments and threat modeling
  • Define security policies and standards
  • Establish security governance structure
  • Create security roadmap with prioritized initiatives

**Deliverables**:

  • Risk register with prioritized risks
  • Compliance gap analysis report
  • Security architecture documentation
  • Security policies and procedures
  • Security roadmap and budget

Phase 2: Design & Architect

**Objective**: Design secure systems and architectures

**Activities**:

  • Design defense-in-depth architectures
  • Implement Zero Trust network architecture
  • Design identity and access management (IAM) systems
  • Architect data protection and encryption solutions
  • Design secure CI/CD pipelines
  • Create threat models for applications and systems
  • Define security controls and compensating controls

**Deliverables**:

  • Security architecture diagrams
  • Threat models (STRIDE, PASTA, or attack trees)
  • Data flow diagrams with security boundaries
  • Encryption and key management design
  • IAM design with RBAC/ABAC models
  • Security control matrix

Phase 3: Implement & Harden

**Objective**: Deploy security controls and harden systems

**Activities**:

  • Implement security controls (preventive, detective, corrective)
  • Configure security tools (SIEM, EDR, CASB, WAF, IDS/IPS)
  • Harden operating systems and applications
  • Implement encryption at rest and in transit
  • Deploy multi-factor authentication (MFA)
  • Configure logging and monitoring
  • Implement data loss prevention (DLP)
  • Set up vulnerability management program

**Deliverables**:

  • Hardening baselines and configuration standards
  • Deployed security tools and controls
  • Encryption implementation
  • MFA deployment
  • Security monitoring dashboards
  • Vulnerability management procedures

Phase 4: Monitor & Detect

**Objective**: Continuously monitor for threats and anomalies

**Activities**:

  • Monitor security logs and events (SIEM)
  • Analyze security alerts and anomalies
  • Conduct threat hunting
  • Perform vulnerability scanning and penetration testing
  • Monitor compliance controls
  • Track security metrics and KPIs
  • Review access logs and privileged account activity
  • Analyze threat intelligence feeds

**Deliverables**:

  • Security operations center (SOC) runbooks
  • Alert triage and escalation procedures
  • Threat hunting playbooks
  • Vulnerability scan reports
  • Penetration test reports
  • Security metrics dashboard
  • Compliance monitoring reports

Phase 5: Respond & Recover

**Objective**: Respond to security incidents and recover operations

**Activities**:

  • Execute incident response plan
  • Contain and eradicate threats
  • Perform forensic analysis
  • Recover affected systems
  • Conduct post-incident reviews
  • Update security controls based on lessons learned
  • Report incidents to stakeholders and regulators
  • Improve detection rules and response procedures

**Deliverables**:

  • Incident response reports
  • Forensic analysis findings
  • Root cause analysis
  • Remediation plans
  • Updated incident response playbooks
  • Regulatory breach notifications (if required)
  • Post-incident review and recommendations

Phase 6: Audit & Improve

**Objective**: Validate compliance and continuously improve security

**Activities**:

  • Conduct internal audits
  • Prepare for external audits (SOC2, ISO27001)
  • Perform compliance assessments
  • Review and update security policies
  • Conduct security training and awareness programs
  • Perform tabletop exercises and disaster recovery drills
  • Update risk assessments
  • Implement security improvements

**Deliverables**:

  • Audit reports (internal and external)
  • SOC2 Type II report
  • ISO27001 certification
  • Compliance attestations
  • Updated policies and procedures
  • Training completion metrics
  • Tabletop exercise results
  • Continuous improvement plan

---

Decision Frameworks

1. Risk Assessment Framework

**When to use**: Evaluating security risks and prioritizing mitigation efforts

**Process**:

1. Identify Assets
   - What systems, data, and services need protection?
   - What is the business value of each asset?
   - Who are the asset owners?

2. Identify Threats
   - What threat actors might targe
Read more
Ships withclaude-forge

Supercharge Claude Code with 11 AI agents, 36 commands & 15 skills — the claude-code plugin framework inspired by oh-my-zsh. 6-layer security hooks included. 5-min install.

Get the whole plugin

Other skills on claude-forge.