This Claude skill facilitates comprehensive security framework alignment and compliance planning. It provides expert guidance on mapping organizational practices to global standards including ISO 27001:2022, SOC 2, NIST CSF 2.0, and CIS Controls v8. By bridging the gap between high-level regulatory requirements and technical implementation, it helps teams conduct gap analyses, prioritize security tasks, and prepare for formal audits with actionable code examples and control matrices.
Use Cases
Audit Preparation: Streamline the readiness process for ISO 27001 or SOC 2 certifications by identifying required evidence, documenting control narratives, and performing pre-assessment checklists.
Cross-Framework Mapping: Harmonize multiple security standards into a unified control set to eliminate redundant efforts and ensure consistent compliance across different jurisdictions.
Technical Control Implementation: Translate abstract framework requirements into concrete technical configurations and .NET/C# code implementations for access control, logging, and secure configuration.
Cyber Hygiene Prioritization: Use CIS Controls Implementation Groups (IG1-IG3) to identify and execute 'quick win' security improvements based on risk and resource availability.
Secure Development Lifecycle (SSDLC): Align software development processes with ISO Annex A.8 and NIST CSF 'Protect' functions to ensure security is integrated into the build pipeline.
name
security-frameworks
description
Security framework alignment including ISO 27001, SOC 2, NIST CSF 2.0, and CIS Controls mapping
allowed-tools
Read, Glob, Grep, Write, Edit, Task
Security Frameworks Planning
Comprehensive guidance for security framework alignment and control mapping before development begins.
Clauses 4-10: Management System Requirements
├── 4. Context of the organization
├── 5. Leadership
├── 6. Planning
├── 7. Support
├── 8. Operation
├── 9. Performance evaluation
└── 10. Improvement
Annex A: 93 Controls in 4 Themes
├── A.5 Organizational controls (37)
├── A.6 People controls (8)
├── A.7 Physical controls (14)
└── A.8 Technological controls (34)
Key Controls for Development
Control
Title
Implementation
A.5.1
Policies for information security
Document security policies
A.5.15
Access control
RBAC, least privilege
A.5.23
Information security for cloud services
Cloud security controls
A.8.4
Access to source code
Git access, code review
A.8.8
Management of technical vulnerabilities
Vulnerability scanning
A.8.9
Configuration management
IaC, hardening
A.8.25
Secure development lifecycle
SSDLC
A.8.28
Secure coding
OWASP, static analysis
A.8.29
Security testing
DAST, penetration testing
A.8.31
Separation of environments
Dev/Test/Prod isolation
ISMS Implementation Approach
// Control implementation tracking
public class IsmsControlTracker
{
public record ControlStatus
{
public required string ControlId { get; init; } // e.g., "A.8.28"
public required string ControlTitle { get; init; }
public required ImplementationStatus Status { get; init; }
public required string Owner { get; init; }
public required List<string> Evidence { get; init; }
public required DateTimeOffset LastReviewDate { get; init; }
public required DateTimeOffset NextReviewDate { get; init; }
public string? GapDescription { get; init; }
public string? RemediationPlan { get; init; }
}
public enum ImplementationStatus
{
NotApplicable,
NotImplemented,
PartiallyImplemented,
FullyImplemented
}
public GapAnalysisReport GenerateGapAnalysis(
IEnumerable<ControlStatus> controls)
{
var gaps = controls
.Where(c => c.Status != ImplementationStatus.FullyImplemented
&& c.Status != ImplementationStatus.NotApplicable)
.OrderBy(c => c.ControlId);
return new GapAnalysisReport
{
TotalControls = controls.Count(),
FullyImplemented = controls.Count(c =>
c.Status == ImplementationStatus.FullyImplemented),
PartiallyImplemented = controls.Count(c =>
c.Status == ImplementationStatus.PartiallyImplemented),
NotImplemented = controls.Count(c =>
c.Status == ImplementationStatus.NotImplemented),
NotApplicable = controls.Count(c =>
c.Status == ImplementationStatus.NotApplicable),
Gaps = gaps.ToList()
};
}
}
SOC 2
Trust Services Criteria (TSC)
Category
Description
Key Criteria
Security (Required)
System protected against unauthorized access
CC6.x
Availability
System available for operation
A1.x
Processing Integrity
System processing is complete, accurate
PI1.x
Confidentiality
Confidential information protected
C1.x
Privacy
Personal information protected
P1.x-P8.x
Common Criteria (Security)
CC1 - Control Environment
CC2 - Communication and Information
CC3 - Risk Assessment
CC4 - Monitoring Activities
CC5 - Control Activities
CC6 - Logical and Physical Access Controls
CC7 - System Operations
CC8 - Change Management
CC9 - Risk Mitigation
SOC 2 Control Examples
## CC6.1 - Logical Access Security
### Control Description
The entity implements logical access security software, infrastructure,
and architectures over protected information assets to protect them
from security events to meet the entity's objectives.
### Implementation
- Authentication via Azure AD with MFA required
- RBAC with least privilege principle
- Service accounts with managed identities
- API access via OAuth 2.0 tokens
### Evidence
- Azure AD configuration export
- Role assignment documentation
- Access review reports (quarterly)
- MFA enforcement policy