CSA Cloud Controls Matrix with 197 controls and CAIQ support
- version
- 0.1.0
- GitHub stars
- 436
Install
/plugin install csa-ccm@grc-engineering-suiteRun it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.
Contents
Discovered from sourceSkills 1
CSA CCM Expert
Deep expertise in Cloud Security Alliance Cloud Controls Matrix (CCM) for cloud service providers, cloud consumers, and cloud security professionals.
Expertise Areas
CSA Alliance Overview
Mission: Promote best practices for secure cloud computing Founded: 2008 Membership: 500+ corporate members, 100,000+ individual members globally Key Programs:
- Cloud Controls Matrix (CCM)
- Consensus Assessments Initiative Questionnaire (CAIQ)
- STAR (Security, Trust, Assurance, and Risk) Registry
- Certificate of Cloud Security Knowledge (CCSK)
Cloud Controls Matrix (CCM)
Current Version: CCM v4.0 (released 2021) Control Objectives: 197 controls across 17 domains Purpose: Provide cloud-specific security controls framework Scope: Applies to all cloud service models (IaaS, PaaS, SaaS) and deployment models (public, private, hybrid, multi-cloud)
Key Features:
- Cloud-specific security controls
- Shared responsibility model alignment
- Framework harmonization (ISO, SOC, PCI, NIST, GDPR)
- CAIQ self-assessment tool
- CSA STAR certification program
17 CCM Domains (197 Controls)
1. A&A - Audit and Assurance (6 controls)
Independent verification and compliance validation.
Key Controls:
- A&A-01: Audit Planning - Scope, objectives, methodology
- A&A-02: Independent Audits - Third-party assessments (SOC 2, ISO 27001)
- A&A-03: Regulatory Mapping - Framework alignment documentation
- A&A-04: Audit Controls Assurance - Evidence collection and retention
- A&A-05: SOC 2 Reporting - AICPA attestation
- A&A-06: Annual Certification - Ongoing compliance validation
Implementation Priorities:
- SOC 2 Type II certification (annual)
- ISO 27001 certification
- Third-party penetration testing
- CAIQ self-assessment publication (CSA STAR Level 1)
2. AIS - Application & Interface Security (11 controls)
Secure software development and API protection.
Key Controls:
- AIS-01: Application Security - SDLC integration
- AIS-03: API Security - Authentication, authorization, rate limiting
- AIS-04: Automated Security Testing - SAST/DAST/IAST
- AIS-10: Secure Coding - OWASP Top 10 mitigation
- AIS-11: Third-Party Software - Vendor security assessment
Cloud-Specific Considerations:
- API-first architecture security
- Microservices security
- Serverless security (AWS Lambda, Azure Functions)
- Container security (Docker, Kubernetes)
- CI/CD pipeline security (DevSecOps)
OWASP Top 10 Cloud Risks:
- Broken authentication and session management
- Sensitive data exposure
- Broken access control
- Security misconfiguration
- Cross-site scripting (XSS)
- Insecure deserialization
- Using components with known vulnerabilities
- Insufficient logging and monitoring
- SQL injection
- Server-side request forgery (SSRF)
3. BCR - Business Continuity & Operational Resilience (11 controls)
High availability and disaster recovery.
Key Controls:
- BCR-01: Business Continuity Planning - BCP documentation
- BCR-04: Disaster Recovery - DR plan and testing
- BCR-06: Service Availability - SLA targets and monitoring
- BCR-07: Backup - 3-2-1 backup strategy
- BCR-09: Business Continuity Testing - Annual DR drills
Cloud Resilience Patterns:
- Multi-region deployment (active-active, active-passive)
- Auto-scaling and load balancing
- Database replication (synchronous, asynchronous)
- Chaos engineering (failure injection testing)
- Disaster recovery SLAs: RTO (Recovery Time Objective), RPO (Recovery Point Objective)
SLA Tiers:
- 99.9% ("three nines"): 8.76 hours downtime/year
- 99.95%: 4.38 hours downtime/year
- 99.99% ("four nines"): 52.56 minutes downtime/year
- 99.999% ("five nines"): 5.26 minutes downtime/year
4. CCC - Change Control & Configuration Management (9 controls)
Managing changes and maintaining secure configurations.
Key Controls:
- CCC-04: Change Management - CAB approval process
- CCC-05: Baseline Configuration - CIS Benchmarks, vendor hardening guides
- CCC-06: Configuration Inventory - Asset and configuration tracking
- CCC-07: Quality Testing - Pre-production validation
Cloud Configuration Management:
- Infrastructure as Code (IaC): Terraform, CloudFormation, ARM templates
- Configuration drift detection
- Policy as Code (OPA, Sentinel, Cloud Custodian)
- Immutable infrastructure patterns
- GitOps workflows
CIS Benchmarks for Cloud:
- AWS Foundations Benchmark
- Azure Foundations Benchmark
- Google Cloud Platform Foundations Benchmark
- Kubernetes Benchmark
5. CEK - Cryptography, Encryption & Key Management (15 controls)
Data protection through cryptographic controls.
Key Controls:
- CEK-01: Encryption at Rest - AES-256 for storage
- CEK-02: Encryption in Transit - TLS 1.2+ for communications
- CEK-03: Encryption Algorithms - Strong cryptography (AES-256, RSA-2048+)
- CEK-05: Key Management - Key lifecycle (generation, storage, rotation, destruction)
- CEK-07: Key Storage - Hardware Security Module (HSM), FIPS 140-2
- CEK-08: Key Rotation - Automated rotation schedules
Cloud Key Management Services:
- AWS: KMS (Key Management Service), CloudHSM
- Azure: Key Vault, Managed HSM
- GCP: Cloud KMS, Cloud HSM
- Multi-cloud: HashiCorp Vault
Encryption Standards:
- Symmetric: AES-256 (Advanced Encryption Standard)
- Asymmetric: RSA-2048 or higher, ECC (Elliptic Curve Cryptography)
- Hashing: SHA-256, SHA-384, SHA-512
- TLS: TLS 1.2 minimum (TLS 1.3 preferred)
- FIPS 140-2: Level 2+ for key storage
Key Rotation Best Practices:
- Encryption keys: Annual rotation minimum
- Customer-managed keys (CMK): Quarterly or upon personnel changes
- SSL/TLS certificates: 90-day automated rotation (Let's Encrypt)
- API keys: 90-day rotation or upon compromise
6. DCS - Data Security & Privacy Lifecycle Management (12 controls)
Data governance from creation to deletion.
Key Controls:
- DCS-01: Classification - Data categorization scheme
- DCS-02: Secure Disposal - Crypto erase, data sanitization
- DCS-05: Data Retention - Policy-driven retention schedules
- DCS-06: Data Loss Prevention - DLP tools and policies
- DCS-07: Data Inventory - Data mapping and discovery
Data Classification Scheme:
- Public: No confidentiality impact
- Internal: Internal use only
- Confidential: Competitive harm if disclosed
- Restricted: Regulatory/legal protection required (PII, PHI, PCI, IP)
Cloud Data Lifecycle:
- Create: Data generation and ingestion
- Store: Encryption, access control, backup
- Use: Processing, analytics, transformation
- Share: Controlled distribution, DLP
- Archive: Long-term retention, compliance
- Destroy: Secure deletion, crypto erase
Data Residency and Sovereignty:
- Geographic data storage requirements (GDPR, CCPA, data localization laws)
- Cloud region selection (EU, US, APAC)
- Cross-border data transfer mechanisms (SCCs, BCRs, adequacy decisions)
7. DSP - Data Security & Privacy (13 controls)
Privacy-specific controls for personal data.
Key Controls:
- DSP-01: Privacy Impact Assessment - DPIA for high-risk processing
- DSP-03: Data Subject Rights - GDPR Articles 15-22 (access, erasure, portability)
- DSP-07: Cross-Border Transfer - Standard Contractual Clauses (SCCs)
- DSP-08: Data Breach Notification - 72-hour reporting (GDPR)
Privacy Regulations:
- GDPR (EU): General Data Protection Regulation
- CCPA/CPRA (California): Consumer Privacy Act
- LGPD (Brazil): Lei Geral de Proteção de Dados
- PDPA (Singapore): Personal Data Protection Act
- POPIA (South Africa): Protection of Personal Information Act
Data Subject Rights (GDPR):
- Article 15: Right of access
- Article 16: Right to rectification
- Article 17: Right to erasure ("right to be forgotten")
- Article 18: Right to restriction of processing
- Article 20: Right to data portability
- Article 21: Right to object
- Article 22: Automated decision-making and profiling
Privacy-Enhancing Technologies (PETs):
- Pseudonymization and anonymization
- Differential privacy
- Homomorphic encryption
- Secure multi-party computation
- Zero-knowledge proofs
8. GRC - Governance, Risk & Compliance (14 controls)
Security governance and risk management.
Key Controls:
- GRC-01: Governance Program - Security framework (ISO 27001, NIST CSF)
- GRC-02: Risk Management Framework - ISO 31000 alignment
- GRC-03: Risk Assessment - Annual enterprise risk assessment
- GRC-07: Security Metrics - KPIs and KRIs
- GRC-08: Executive Reporting - Board/C-level dashboards
Risk Assessment Methodologies:
- Qualitative: Risk matrices (likelihood × impact)
- Quantitative: FAIR (Factor Analysis of Information Risk)
- Hybrid: Combination of qualitative and quantitative
Risk Treatment Options:
- Mitigate: Implement controls to reduce risk
- Transfer: Insurance, outsourcing
- Accept: Risk within tolerance
- Avoid: Eliminate risk-causing activity
Security Metrics (KPIs/KRIs):
- Mean Time to Detect (MTTD)
- Mean Time to Respond (MTTR)
- Vulnerability remediation SLA compliance
- Patch compliance percentage
- Security awareness training completion rate
- Failed login attempts and account lockouts
- Critical security incidents per quarter
9. HRS - Human Resources (10 controls)
Personnel security and awareness.
Key Controls:
- HRS-01: Background Screening - Pre-employment checks
- HRS-04: Security Awareness Training - Annual mandatory training
- HRS-08: Access Revocation - Immediate deprovisioning on termination
Security Awareness Topics:
- Phishing and social engineering
- Password security and MFA
- Data classification and handling
- Incident reporting procedures
- Clean desk and clear screen policies
- Acceptable use policies
- BYOD and remote work security
Insider Threat Indicators:
- Unusual access patterns (after hours, bulk downloads)
- Policy violations
- Disgruntled behavior
- Financial difficulties
- Unauthorized tool usage
10. IAM - Identity & Access Management (16 controls)
Controlling access to resources.
Key Controls:
- IAM-01: User Access Policy - Least privilege principle
- IAM-03: User Access Reviews - Quarterly recertification
- IAM-05: Privileged Access Management - PAM solution
- IAM-06: Multi-Factor Authentication - MFA for all users
- IAM-08: Single Sign-On - Centralized authentication
Cloud IAM Patterns:
- Identity Federation: SAML 2.0, OAuth 2.0, OpenID Connect (OIDC)
- SSO Providers: Okta, Azure AD, Auth0, Ping Identity
- Cloud-Native IAM: AWS IAM, Azure AD, GCP IAM
- Privileged Access Management: CyberArk, BeyondTrust, Delinea
MFA Methods (in order of security):
- FIDO2/WebAuthn: Hardware security keys (YubiKey)
- Authenticator Apps: TOTP (Google Authenticator, Microsoft Authenticator)
- Push Notifications: Okta Verify, Duo Push
- SMS/Voice: Least secure, vulnerable to SIM swapping
Just-in-Time (JIT) Access:
- Temporary privilege elevation
- Time-bounded access (1-8 hours)
- Approval workflows
- Automated revocation
Zero Trust Principles:
- Verify explicitly (identity, device, location)
- Least privilege access
- Assume breach (micro-segmentation, monitoring)
11. IPY - Interoperability & Portability (5 controls)
Preventing vendor lock-in.
Key Controls:
- IPY-01: Data Portability - Customer data export APIs
- IPY-03: API Interoperability - Standards-based APIs
- IPY-04: Vendor Lock-In Prevention - Exit planning
Data Portability Standards:
- Open formats: JSON, XML, CSV
- Industry standards: FHIR (healthcare), HL7, EDIFACT
- API standards: REST, GraphQL, gRPC
Cloud Exit Strategies:
- Data migration tools and APIs
- Service decommissioning procedures
- Knowledge transfer documentation
- Transition assistance SLAs
12. IVS - Infrastructure & Virtualization Security (13 controls)
Cloud infrastructure and network security.
Key Controls:
- IVS-01: Network Security - Segmentation, firewalls, security groups
- IVS-03: Hypervisor Hardening - Virtualization security
- IVS-05: Container Security - Docker, Kubernetes hardening
- IVS-12: Network Architecture - Defense in depth
Cloud Network Security:
- Virtual Private Cloud (VPC): Network isolation
- Security Groups: Stateful firewall rules
- Network ACLs: Stateless subnet-level firewalls
- Web Application Firewall (WAF): OWASP Top 10 protection
- DDoS Protection: AWS Shield, Azure DDoS Protection
Container Security Controls:
- Image scanning (vulnerability detection)
- Registry security (signed images, access control)
- Runtime protection (anomaly detection)
- Kubernetes security: RBAC, Pod Security Standards, Network Policies
Zero Trust Network Architecture (ZTNA):
- Micro-segmentation
- Software-defined perimeter (SDP)
- Identity-based access (not network location)
- Continuous verification
13. LOG - Logging & Monitoring (13 controls)
Security event logging and monitoring.
Key Controls:
- LOG-01: Audit Logging - Comprehensive event capture
- LOG-04: Log Retention - 1 year minimum (varies by regulation)
- LOG-06: Log Review and Analysis - Automated correlation
- LOG-08: SIEM - Centralized log aggregation
- LOG-11: Log Access Control - Restricted access to logs
Cloud SIEM Solutions:
- Cloud-Native: AWS Security Hub, Azure Sentinel, Google Chronicle
- Third-Party: Splunk, Elastic SIEM, Sumo Logic, Datadog
- Open Source: ELK Stack (Elasticsearch, Logstash, Kibana), Wazuh
Critical Security Events to Log:
- Authentication events (success, failure, lockout)
- Authorization changes (privilege escalation)
- Resource creation/deletion
- Configuration changes
- Network connections (allowed, denied)
- Data access (sensitive data queries)
- Administrative actions
Log Retention Requirements:
- SOC 2: 1 year online, 6 years archived
- PCI DSS: 1 year online, 3 months immediately available
- HIPAA: 6 years
- GDPR: As necessary, then deletion
Immutable Logging:
- Write-Once-Read-Many (WORM) storage
- AWS S3 Object Lock
- Azure Immutable Blob Storage
- Log forwarding to external SIEM (no delete permissions)
14. SEF - Security Incident Management (10 controls)
Incident detection, response, and recovery.
Key Controls:
- SEF-01: Incident Response Plan - NIST 800-61 framework
- SEF-02: Incident Response Team - CSIRT/SOC 24/7
- SEF-05: Incident Response Testing - Annual tabletop exercises
- SEF-09: Security Operations Center - 24/7 monitoring
NIST 800-61 Incident Response Lifecycle:
- Preparation: IR plan, tools, training
- Detection & Analysis: SIEM alerts, threat intelligence
- Containment: Isolate affected systems
- Eradication: Remove threat actor, malware
- Recovery: Restore systems and services
- Post-Incident Activity: Lessons learned, improvement
Incident Severity Levels:
- Critical (P1): Data breach, ransomware, complete outage
- High (P2): Unauthorized access, partial outage
- Medium (P3): Malware detected, policy violation
- Low (P4): Failed login attempts, suspicious activity
Security Operations Center (SOC):
- 24/7 monitoring: Real-time threat detection
- Tiered structure: L1 (triage), L2 (investigation), L3 (threat hunting)
- SOAR: Security Orchestration, Automation, and Response
- Threat Intelligence: IOCs, TTPs, MITRE ATT&CK
Cloud Incident Response Challenges:
- Shared responsibility (provider vs. customer)
- Ephemeral infrastructure (containers, serverless)
- Multi-cloud complexity
- Forensics in virtualized environments
- Legal/regulatory notification requirements
15. STA - Supply Chain Management (11 controls)
Third-party and vendor risk management.
Key Controls:
- STA-01: Third-Party Assessment - Vendor due diligence
- STA-03: Vendor Contracts - Security requirements and SLAs
- STA-06: Cloud Service Providers - Sub-processor management
- STA-11: Software Supply Chain - SBOM (Software Bill of Materials)
Third-Party Risk Assessment:
- Security questionnaires (SIG, CAIQ, VSAQ)
- Financial stability review
- Compliance certifications (SOC 2, ISO 27001)
- Right to audit clauses
- Breach notification obligations
- Data Processing Agreements (DPAs)
Software Supply Chain Security:
- Dependency scanning (Snyk, Dependabot)
- SBOM generation and analysis
- Signed artifacts (code signing)
- Private package repositories
- Vendor vulnerability disclosure programs
Shared Responsibility in Cloud:
- IaaS: Customer responsible for OS, apps, data
- PaaS: Customer responsible for apps, data
- SaaS: Customer responsible for data, access management
16. TVM - Threat & Vulnerability Management (13 controls)
Proactive security testing and remediation.
Key Controls:
- TVM-01: Vulnerability Scanning - Weekly automated scans
- TVM-02: Vulnerability Remediation - SLA-based patching
- TVM-03: Penetration Testing - Annual external pentests
- TVM-07: Patch Management - Timely OS/software updates
Vulnerability Remediation SLAs:
- Critical: 7 days
- High: 30 days
- Medium: 90 days
- Low: 180 days (or next maintenance window)
Penetration Testing Types:
- Black Box: No prior knowledge
- White Box: Full knowledge (credentials, architecture)
- Gray Box: Partial knowledge
- Red Team: Adversarial simulation
- Purple Team: Collaborative red/blue team
Vulnerability Scanning Tools:
- Network: Nessus, Qualys, Rapid7 InsightVM
- Web App: Burp Suite, OWASP ZAP, Acunetix
- Container: Aqua, Prisma Cloud, Anchore
- IaC: Checkov, tfsec, Terraform Sentinel
- Cloud: AWS Inspector, Azure Security Center, GCP Security Command Center
Bug Bounty Programs:
- Platforms: HackerOne, Bugcrowd, Synack
- Scope: In-scope assets and vulnerabilities
- Rewards: $100 - $100,000+ based on severity
- Responsible Disclosure: 90-day disclosure timeline
17. UEM - Universal Endpoint Management (7 controls)
Endpoint and mobile device security.
Key Controls:
- UEM-02: Endpoint Protection - Antivirus/EDR
- UEM-03: Endpoint Encryption - Full disk encryption
- UEM-04: Mobile Device Management - MDM/MAM
Endpoint Detection and Response (EDR):
- CrowdStrike Falcon
- Microsoft Defender for Endpoint
- SentinelOne
- Carbon Black
Mobile Device Management (MDM):
- Microsoft Intune
- Jamf (Apple devices)
- VMware Workspace ONE
- MobileIron
Endpoint Security Controls:
- Full disk encryption (BitLocker, FileVault)
- Application whitelisting
- Patch management
- Remote wipe capability
- Conditional access policies
Cloud Service Models
IaaS - Infrastructure as a Service
Examples: AWS EC2, Azure VMs, Google Compute Engine
Provider Responsibilities:
- Physical infrastructure (data centers, servers, storage)
- Network infrastructure (routers, switches, firewalls)
- Hypervisor and virtualization
Customer Responsibilities:
- Operating system hardening and patching
- Application security
- Data encryption
- Identity and access management
- Network security (security groups, NACLs)
- Logging and monitoring
Key CCM Domains: IVS, CCC, LOG, TVM
PaaS - Platform as a Service
Examples: AWS Elastic Beanstalk, Azure App Service, Google App Engine, Heroku
Provider Responsibilities:
- Infrastructure (IaaS responsibilities)
- Operating system and runtime
- Middleware
Customer Responsibilities:
- Application code security
- Application configuration
- Data protection
- User access management
Key CCM Domains: AIS, CEK, DCS, IAM
SaaS - Software as a Service
Examples: Salesforce, Microsoft 365, Google Workspace, Slack, Zoom
Provider Responsibilities:
- Infrastructure (IaaS responsibilities)
- Platform (PaaS responsibilities)
- Application functionality and security
Customer Responsibilities:
- User access management
- Data classification
- Usage monitoring
- Integration security
Key CCM Domains: IAM, DSP, A&A, GRC
CAIQ (Consensus Assessments Initiative Questionnaire)
Purpose: Standardized cloud security questionnaire Current Version: CAIQ v4.0 (aligned to CCM v4.0) Questions: 197 yes/no questions with evidence Use Cases:
- Vendor security assessments
- RFP responses
- Customer due diligence
- CSA STAR Level 1 self-assessment
CAIQ Response Format:
- Question: Yes/No question about control implementation
- Answer: Yes or No
- Evidence: Description of implementation, policies, tools, certifications
CAIQ Completion Time:
- Initial: 40-80 hours
- Annual Update: 10-20 hours
CSA STAR (Security, Trust, Assurance, and Risk)
Purpose: Public registry of cloud provider security posture
STAR Levels:
Level 1: Self-Assessment
- Submit completed CAIQ
- Free CSA STAR registration
- Publicly accessible in STAR Registry
- No third-party validation
Level 2: Certification
- Third-party audit (SOC 2, ISO 27001, C5)
- CAIQ + audit report
- Enhanced credibility
- Annual recertification
Level 3: Continuous Monitoring
- Real-time security posture visibility
- Automated control monitoring
- Continuous assurance
- CloudTrust Protocol integration
STAR Certification Options:
- SOC 2: AICPA Trust Services (US-focused)
- ISO 27001: International standard
- C5: German Federal Office for Information Security (BSI)
Framework Mappings
CCM v4.0 comprehensively maps to major compliance frameworks:
ISO/IEC 27001:2022
- Coverage: All 93 Annex A controls
- CCM Advantage: 197 controls provide deeper cloud-specific guidance
- Use Case: CCM implementation satisfies ISO 27001 requirements
Example Mappings:
- ISO A.8.24 (Cryptography) ↔ CEK-01, CEK-02, CEK-03, CEK-05
- ISO A.5.16 (Identity Management) ↔ IAM-01, IAM-02, IAM-03, IAM-04
- ISO A.8.15 (Logging) ↔ LOG-01, LOG-03, LOG-04, LOG-11
SOC 2 Type II (Trust Services Criteria)
- Coverage: All Common Criteria (CC) and additional criteria (A, C, P, PI)
- CCM Advantage: Detailed technical controls for cloud environments
- Use Case: CCM evidence supports SOC 2 audits
Trust Services Criteria:
- CC: Common Criteria (security, availability, confidentiality)
- A: Availability
- C: Confidentiality
- P: Processing Integrity
- PI: Privacy
PCI DSS v4.0
- Coverage: All 12 PCI DSS requirements
- CCM Advantage: Cloud-specific cardholder data protection
- Use Case: Cloud environments storing/processing payment data
Example Mappings:
- PCI 3.5.1 (Disk Encryption) ↔ CEK-01
- PCI 8.4.2 (MFA) ↔ IAM-06
- PCI 10.2.1 (Audit Logging) ↔ LOG-01
NIST Cybersecurity Framework (CSF) 2.0
- Coverage: All 6 functions (Govern, Identify, Protect, Detect, Respond, Recover)
- CCM Advantage: Implementation guidance for CSF categories
- Use Case: CSF-aligned cloud security programs
NIST CSF Functions:
- Govern (GV): GRC domain
- Identify (ID): GRC, STA, TVM
- Protect (PR): CEK, IAM, IVS, HRS
- Detect (DE): LOG, SEF, TVM
- Respond (RS): SEF
- Recover (RC): BCR
GDPR (General Data Protection Regulation)
- Coverage: Articles 5, 25, 28, 32, 33, 35
- CCM Advantage: Privacy by design and DPIA guidance
- Use Case: Cloud processing of EU personal data
Example Mappings:
- GDPR Article 32 (Security) ↔ CEK-01, CEK-02, IAM-06, LOG-01
- GDPR Article 35 (DPIA) ↔ DSP-01
- GDPR Article 33 (Breach Notification) ↔ SEF-04, DSP-08
Multi-Framework Compliance Strategy
Single Control, Multiple Frameworks: Implementing CEK-01 (Encryption at Rest) satisfies:
- ISO 27001 A.8.24
- SOC 2 CC6.1
- PCI DSS 3.5.1
- NIST 800-53 SC-28
- HIPAA 164.312(a)(2)(iv)
- GDPR Article 32(1)(a)
Benefits:
- Reduced audit burden
- Consistent control implementation
- Single evidence repository
- Cost-effective compliance
- Cloud-specific best practices
Implementation Roadmap
Phase 1: Foundation (Months 1-3)
- Conduct gap assessment against CCM v4.0
- Prioritize high-risk domains (CEK, IAM, LOG)
- Document current control state
- Establish governance structure (GRC-01)
Phase 2: Core Controls (Months 4-9)
- Implement encryption (CEK-01, CEK-02)
- Deploy MFA and SSO (IAM-06, IAM-08)
- Centralize logging (LOG-08 SIEM)
- Establish incident response (SEF-01, SEF-02)
- Vulnerability management (TVM-01, TVM-03)
Phase 3: Advanced Controls (Months 10-15)
- Privileged access management (IAM-05)
- DLP implementation (DCS-06)
- Container security (IVS-05)
- Third-party risk program (STA-01)
- Business continuity testing (BCR-09)
Phase 4: Certification (Months 16-18)
- Complete CAIQ v4.0
- SOC 2 Type II audit
- ISO 27001 certification
- CSA STAR Level 2 registration
- Continuous monitoring (STAR Level 3)
Common Implementation Challenges
-
Shared Responsibility Confusion:
- Unclear control ownership (cloud provider vs. customer)
- Solution: Document responsibility matrix by service model
-
Multi-Cloud Complexity:
- Inconsistent controls across AWS, Azure, GCP
- Solution: Cloud-agnostic tools and policies
-
DevOps Speed vs. Security:
- Security gates slow down deployments
- Solution: Shift-left security, automated controls
-
Ephemeral Infrastructure:
- Containers and serverless difficult to monitor/audit
- Solution: Immutable infrastructure, comprehensive logging
-
Vendor Risk Management:
- Hundreds of SaaS applications and cloud services
- Solution: Automated vendor assessments, CAIQ repository
-
Data Residency:
- Multi-jurisdictional data protection laws
- Solution: Regional data architecture, encryption everywhere
Cost Considerations
CCM Implementation:
- Gap Assessment: $20K-$50K (consultant)
- Control Implementation: $100K-$500K (tools, personnel, remediation)
- Annual Maintenance: $50K-$150K
Certifications:
- SOC 2 Type II: $50K-$150K (auditor fees)
- ISO 27001: $30K-$100K (certification body)
- Penetration Testing: $25K-$75K (annual)
- CAIQ Completion: $10K-$30K (internal effort or consultant)
Return on Investment:
- Reduced vendor questionnaires (100+ hours/year saved)
- Faster sales cycles (trusted certifications)
- Lower breach risk (insurance discounts)
- Multi-framework efficiency (30-50% effort reduction)
Capabilities
- CCM v4.0 control implementation guidance (all 197 controls)
- CAIQ completion and STAR registry submission
- Cloud service model assessment (IaaS, PaaS, SaaS)
- Shared responsibility matrix development
- Framework mapping (ISO 27001, SOC 2, PCI DSS, NIST, HIPAA, GDPR)
- Gap analysis and remediation roadmaps
- Cloud security architecture review
- Multi-cloud and hybrid cloud security
- Container and Kubernetes security (IVS-05)
- API security and DevSecOps integration (AIS domain)
- Encryption and key management (CEK domain)
- Identity federation and Zero Trust (IAM domain)
- Cloud SIEM and logging architecture (LOG domain)
- Cloud incident response planning (SEF domain)
- Third-party cloud risk management (STA domain)
- CSA STAR Level 1/2/3 certification guidance
Commands 5
CSA CCM Assessment
Evaluates organizational readiness for Cloud Security Alliance Cloud Controls Matrix (CCM) compliance.
Arguments
$1- Assessment scope (required: full, domain-specific, service-model)$2- Cloud service model (optional: IaaS, PaaS, SaaS, hybrid)
CSA CCM Overview
Purpose: Provide cloud-specific security controls framework Current Version: CCM v4.0 (197 control objectives) Domains: 17 security domains Use Cases: Cloud provider assessments, cloud security posture, multi-framework compliance
Cloud Service Models
| Model | Description | Provider Responsibility | Consumer Responsibility |
|---|---|---|---|
| IaaS | Infrastructure as a Service | Physical infrastructure, network | OS, apps, data, identity |
| PaaS | Platform as a Service | Infrastructure + OS + runtime | Applications, data |
| SaaS | Software as a Service | Full stack | Data, access management |
| Hybrid | Mixed deployment | Shared based on architecture | Shared based on architecture |
17 CCM Domains
-
A&A - Audit and Assurance
- Independent audits and assessments
- Compliance reporting
- Control attestations
-
AIS - Application & Interface Security
- Secure software development lifecycle
- API security
- Application vulnerability management
-
BCR - Business Continuity & Operational Resilience
- Business impact analysis
- Disaster recovery planning
- Service availability
-
CCC - Change Control & Configuration Management
- Configuration baselines
- Change management processes
- Version control
-
CEK - Cryptography, Encryption & Key Management
- Data encryption (at rest, in transit)
- Key lifecycle management
- Cryptographic standards compliance
-
DCS - Data Security & Privacy Lifecycle Management
- Data classification
- Data retention and disposal
- Privacy controls
-
DSP - Data Security & Privacy
- Personal data protection
- Data subject rights
- Privacy by design
-
GRC - Governance, Risk & Compliance
- Security governance framework
- Risk management program
- Compliance management
-
HRS - Human Resources
- Personnel security
- Background checks
- Security awareness training
-
IAM - Identity & Access Management
- Authentication and authorization
- Privileged access management
- Identity federation
-
IPY - Interoperability & Portability
- Data portability
- API standardization
- Vendor lock-in prevention
-
IVS - Infrastructure & Virtualization Security
- Hypervisor security
- Container security
- Network segmentation
-
LOG - Logging & Monitoring
- Security event logging
- Log retention and protection
- Security monitoring
-
SEF - Security Incident Management
- Incident response plan
- Incident handling procedures
- Forensics capabilities
-
STA - Supply Chain Management, Transparency & Accountability
- Third-party risk management
- Vendor security assessments
- Supply chain transparency
-
TVM - Threat & Vulnerability Management
- Vulnerability scanning
- Penetration testing
- Threat intelligence
-
UEM - Universal Endpoint Management
- Endpoint security controls
- Mobile device management
- Bring Your Own Device (BYOD) policies
Assessment Output
- Overall CCM Readiness: Compliance percentage across 197 controls
- Domain Maturity Scores: Breakdown by 17 domains
- Service Model Gaps: IaaS/PaaS/SaaS specific deficiencies
- Shared Responsibility Analysis: Provider vs. customer control ownership
- Framework Alignment: Mapping to ISO 27001, SOC 2, PCI-DSS, NIST
- CAIQ Readiness: Preparation for Consensus Assessments
- Remediation Roadmap: Prioritized action plan by domain
Shared Responsibility Model
IaaS Example Controls
- Customer: OS hardening, application security, data encryption, IAM
- Provider: Physical security, network infrastructure, hypervisor
PaaS Example Controls
- Customer: Application code security, data protection, user access
- Provider: OS patching, runtime security, platform infrastructure
SaaS Example Controls
- Customer: User management, data classification, access policies
- Provider: Application security, infrastructure, encryption, logging
Framework Mapping
CCM maps to major compliance frameworks:
- ISO 27001/27002: Information security management
- SOC 2: Trust Services Criteria
- PCI DSS: Payment card security
- NIST CSF/800-53: Federal security standards
- GDPR: Privacy and data protection
- HIPAA: Healthcare security
Assessment Types
Full Assessment
- All 197 controls across 17 domains
- Complete control implementation review
- Evidence collection and validation
- Comprehensive gap analysis
Domain-Specific Assessment
- Focus on specific domain (e.g., CEK, IAM, LOG)
- Deep dive into domain controls
- Targeted remediation planning
Service Model Assessment
- Tailored to IaaS, PaaS, or SaaS deployment
- Shared responsibility analysis
- Model-specific control applicability
Examples
# Full CCM assessment for SaaS provider
/ccm:assess full SaaS
# Domain-specific assessment for encryption
/ccm:assess domain-specific CEK
# IaaS cloud infrastructure assessment
/ccm:assess full IaaS
# Hybrid cloud environment assessment
/ccm:assess full hybrid
CAIQ Integration
Assessment prepares organization for CSA CAIQ (Consensus Assessments Initiative Questionnaire):
- Self-assessment questionnaire
- 197 yes/no questions aligned to CCM
- Publicly sharable security posture
- Customer due diligence tool
CSA CAIQ Generator
Generates responses for the Cloud Security Alliance Consensus Assessments Initiative Questionnaire (CAIQ), a standardized self-assessment tool for cloud service providers.
Arguments
$1- CAIQ version (required: v4.0, lite)$2- Output format (optional: markdown, json, excel, csv)$3- Response mode (optional: full, draft, template)
CAIQ Overview
Purpose: Standardized cloud security questionnaire Audience: Cloud service providers, customers conducting vendor due diligence Structure: 197 yes/no questions aligned to CCM v4.0 Use Cases:
- Vendor security assessments
- RFP responses
- Customer due diligence
- Publicly shareable security posture
- CSA STAR Level 1 self-assessment
CAIQ Versions
CAIQ v4.0 (Full)
- Questions: 197 aligned to CCM v4.0
- Response Format: Yes/No + Evidence
- Domains: All 17 CCM domains
- Effort: 40-80 hours to complete
- Use Case: Comprehensive cloud security assessment
CAIQ Lite
- Questions: Reduced subset (~50 questions)
- Response Format: Yes/No
- Domains: Core security domains only
- Effort: 10-20 hours to complete
- Use Case: Quick vendor assessments, initial due diligence
CAIQ Question Structure
Each CAIQ question follows this format:
Control ID: CCM domain and control number (e.g., CEK-01)
Question: Yes/No question about control implementation
Response Options:
- Yes: Control is fully implemented
- No: Control is not implemented or partially implemented
Evidence: Description of how control is implemented, including:
- Policies and procedures
- Technical implementations
- Third-party certifications
- Audit reports
- Responsible party
17 Domain Breakdown
A&A - Audit and Assurance (6 questions)
Example questions:
- Do you conduct annual independent audits or assessments?
- Do you have SOC 2 Type II certification?
- Are third-party audit reports available to customers?
Key Evidence:
- SOC 2 Type II reports
- ISO 27001 certificates
- Penetration test reports
- CAIQ self-assessment
AIS - Application & Interface Security (11 questions)
Example questions:
- Do you follow a secure software development lifecycle (SDLC)?
- Are APIs protected with authentication and authorization?
- Do you perform automated application security testing (SAST/DAST)?
Key Evidence:
- SDLC documentation
- OWASP Top 10 mitigation
- API authentication mechanisms (OAuth, API keys)
- SAST/DAST tool reports
BCR - Business Continuity & Operational Resilience (11 questions)
Example questions:
- Do you have a documented business continuity plan (BCP)?
- Do you test disaster recovery procedures annually?
- Are SLA targets defined and monitored (e.g., 99.9% uptime)?
Key Evidence:
- BCP/DR documentation
- DR test results
- SLA metrics and uptime reports
- Redundancy architecture
CCC - Change Control & Configuration Management (9 questions)
Example questions:
- Do you have a formal change management process?
- Are baseline configurations defined and enforced?
- Is configuration management automated (IaC)?
Key Evidence:
- Change Advisory Board (CAB) procedures
- CIS Benchmarks or hardening guides
- Infrastructure as Code (Terraform, CloudFormation)
- Configuration management tools
CEK - Cryptography, Encryption & Key Management (15 questions)
Example questions:
- Is data encrypted at rest?
- Is data encrypted in transit (TLS 1.2+)?
- Are encryption keys managed in a Hardware Security Module (HSM)?
- Is key rotation automated?
Key Evidence:
- Encryption policies
- TLS/SSL configuration
- AWS KMS, Azure Key Vault, or HSM usage
- Key rotation procedures
- FIPS 140-2 compliance
DCS - Data Security & Privacy Lifecycle Management (12 questions)
Example questions:
- Is data classified according to sensitivity?
- Are data retention policies defined and enforced?
- Is Data Loss Prevention (DLP) implemented?
- Are test environments using anonymized data?
Key Evidence:
- Data classification scheme
- Retention schedules
- DLP tool implementation
- Data anonymization procedures
DSP - Data Security & Privacy (13 questions)
Example questions:
- Do you conduct Data Protection Impact Assessments (DPIAs)?
- Can customers exercise data subject rights (access, deletion, portability)?
- Is consent management implemented?
- Are data breaches reported within 72 hours?
Key Evidence:
- DPIA documentation
- Data subject request portal
- Consent management platform
- Breach notification procedures
- GDPR/CCPA compliance programs
GRC - Governance, Risk & Compliance (14 questions)
Example questions:
- Is there an information security governance framework?
- Are risk assessments conducted annually?
- Are security policies reviewed and updated regularly?
- Is there executive-level security oversight (CISO, security committee)?
Key Evidence:
- Security governance framework
- Risk assessment reports
- Policy management system
- Board/executive reporting
- CISO role definition
HRS - Human Resources (10 questions)
Example questions:
- Are background checks conducted on employees?
- Is annual security awareness training mandatory?
- Are access rights revoked immediately upon termination?
Key Evidence:
- Background check procedures
- Training completion records
- Deprovisioning workflows
- Contractor security agreements
IAM - Identity & Access Management (16 questions)
Example questions:
- Is multi-factor authentication (MFA) required for all users?
- Are privileged accounts managed separately?
- Are access reviews conducted quarterly?
- Is Single Sign-On (SSO) implemented?
Key Evidence:
- SSO implementation (Okta, Azure AD)
- MFA enforcement policies
- Privileged Access Management (PAM) solution
- Access review logs
IPY - Interoperability & Portability (5 questions)
Example questions:
- Can customers export their data in standard formats?
- Are APIs based on industry standards?
- Is there a documented exit/offboarding process?
Key Evidence:
- Data export tools/APIs
- Standard data formats (JSON, CSV, XML)
- Customer offboarding documentation
IVS - Infrastructure & Virtualization Security (13 questions)
Example questions:
- Is network segmentation implemented?
- Are hypervisors hardened and patched?
- Is container security scanning performed?
- Are production and non-production environments separated?
Key Evidence:
- Network architecture diagrams
- CIS Benchmarks compliance
- Container scanning tools (Aqua, Prisma Cloud)
- Environment isolation policies
LOG - Logging & Monitoring (13 questions)
Example questions:
- Are security events logged centrally (SIEM)?
- Are audit logs retained for at least 1 year?
- Is real-time security monitoring implemented?
- Are logs protected from tampering (immutable storage)?
Key Evidence:
- SIEM solution (Splunk, ELK, Sentinel)
- Log retention policies
- Real-time alerting configuration
- Immutable log storage (WORM, S3 Object Lock)
SEF - Security Incident Management (10 questions)
Example questions:
- Is there a documented incident response plan?
- Is there a 24/7 Security Operations Center (SOC)?
- Are incident response procedures tested annually?
- Is there a threat intelligence program?
Key Evidence:
- Incident response plan (NIST 800-61)
- SOC operations documentation
- Incident response test results
- Threat intelligence sources
STA - Supply Chain Management, Transparency & Accountability (11 questions)
Example questions:
- Are third-party vendors assessed for security risks?
- Are Data Processing Agreements (DPAs) in place for sub-processors?
- Do vendor contracts include right-to-audit clauses?
- Is Software Bill of Materials (SBOM) maintained?
Key Evidence:
- Vendor risk assessment process
- Third-party security questionnaires
- DPAs with sub-processors
- SBOM for software dependencies
TVM - Threat & Vulnerability Management (13 questions)
Example questions:
- Is vulnerability scanning performed regularly?
- Are critical vulnerabilities patched within 7 days?
- Is annual penetration testing conducted?
- Is there a vulnerability disclosure/bug bounty program?
Key Evidence:
- Vulnerability scanning tools (Nessus, Qualys)
- Patch management SLAs
- Penetration test reports
- Bug bounty program (HackerOne)
UEM - Universal Endpoint Management (7 questions)
Example questions:
- Is Endpoint Detection and Response (EDR) deployed?
- Is full disk encryption required on all endpoints?
- Are mobile devices managed through MDM?
- Can lost/stolen devices be remotely wiped?
Key Evidence:
- EDR solution deployment
- Encryption policies (BitLocker, FileVault)
- MDM platform (Intune, Jamf)
- Remote wipe capabilities
Response Best Practices
Complete Evidence Requirements
For "Yes" Responses:
- Policy Reference: Name of policy/procedure
- Implementation Details: How control is technically implemented
- Responsible Party: Team/role accountable
- Supporting Evidence: Certifications, audit reports, tool screenshots
- Frequency: How often control is performed/reviewed
For "No" Responses:
- Explanation: Why control is not implemented
- Compensating Controls: Alternative measures in place
- Roadmap: Plans to implement (if applicable)
- Risk Acceptance: Documented decision not to implement (if applicable)
Example Response (CEK-01: Encryption at Rest)
Question: Is data encrypted at rest using industry-standard encryption algorithms?
Answer: Yes
Evidence: "All customer data is encrypted at rest using AES-256 encryption. Encryption is implemented using AWS Key Management Service (KMS) with customer-managed keys (CMKs). Database encryption uses Transparent Data Encryption (TDE) on Amazon RDS. File storage in S3 uses server-side encryption (SSE-KMS). Encryption is enforced through AWS Service Control Policies (SCPs) preventing unencrypted resource creation. This control is documented in our Cryptography Policy (v2.1) and verified in our annual SOC 2 Type II audit. Responsible party: Security Engineering team."
Output Formats
Markdown Format
- Human-readable
- Easy to review and edit
- Suitable for internal documentation
- GitHub/Confluence compatible
JSON Format
- Machine-readable
- API integration
- Automated processing
- Version control friendly
Excel Format
- Spreadsheet for collaborative editing
- CSA STAR Registry compatible
- Filter and sort capabilities
- Conditional formatting for completeness
CSV Format
- Simple import/export
- Database integration
- Lightweight format
- Universal compatibility
Response Modes
Full Mode
- Complete CAIQ with all 197 questions
- Detailed evidence for each "Yes" response
- Explanation for each "No" response
- Ready for CSA STAR submission
Draft Mode
- Placeholder responses based on common implementations
- Requires customization with organization-specific details
- Highlights areas needing evidence collection
- Starting point for completion
Template Mode
- Empty CAIQ structure
- Question list without responses
- Evidence guidance for each question
- Self-completion format
CSA STAR Registry
CAIQ Use in STAR:
- Level 1 (Self-Assessment): Submit completed CAIQ
- Level 2 (Certification): CAIQ + third-party audit (ISO 27001, SOC 2)
- Level 3 (Continuous Monitoring): CAIQ + ongoing monitoring
Public Visibility: STAR Level 1 and 2 published in CSA STAR Registry for customer transparency
CAIQ Completion Workflow
-
Information Gathering (Week 1-2)
- Collect policies, procedures, architecture diagrams
- Identify control owners across teams
- Gather audit reports and certifications
-
Response Drafting (Week 3-5)
- Answer yes/no questions
- Draft evidence descriptions
- Document compensating controls
-
Internal Review (Week 6)
- Legal review (privacy, contracts)
- Security team validation
- Executive approval for public disclosure
-
Finalization (Week 7-8)
- Format for chosen output
- CSA STAR submission (if applicable)
- Customer distribution
Common Challenges
- Evidence Collection: Gathering artifacts from multiple teams
- Consistency: Ensuring responses align with audit reports
- Public Disclosure: Balancing transparency with security through obscurity
- Maintenance: Keeping CAIQ current as controls change
- Shared Responsibility: Articulating cloud provider vs. customer responsibilities
Examples
# Generate full CAIQ v4.0 in markdown format with draft responses
/ccm:caiq-generate v4.0 markdown draft
# Create CAIQ Lite template in Excel
/ccm:caiq-generate lite excel template
# Generate complete CAIQ in JSON for API integration
/ccm:caiq-generate v4.0 json full
# Create markdown template for manual completion
/ccm:caiq-generate v4.0 markdown template
Benefits of CAIQ
For Cloud Service Providers
- Standardized way to communicate security posture
- Reduce repetitive customer questionnaires
- Demonstrate transparency and accountability
- Marketing differentiator (CSA STAR)
- Efficient RFP response process
For Cloud Customers
- Consistent vendor assessment format
- Alignment to CCM and other frameworks
- Comparable security evaluations
- Reduced due diligence time
- Trust through CSA validation
Integration with Other Assessments
CAIQ Complements:
- SOC 2 Type II: CAIQ references SOC 2 controls
- ISO 27001: Evidence overlap with ISO certification
- Vendor Questionnaires: Maps to SIG, VSAQ, custom questionnaires
- Contract Requirements: Security exhibits and DPAs
- Internal Audits: Control testing and validation
CSA CCM Domain Guidance
Provides detailed implementation guidance for CSA Cloud Controls Matrix domains and their 197 control objectives.
Arguments
$1- Domain abbreviation (required: A&A, AIS, BCR, CCC, CEK, DCS, DSP, GRC, HRS, IAM, IPY, IVS, LOG, SEF, STA, TVM, UEM)$2- Service model context (optional: IaaS, PaaS, SaaS)
17 CCM Domains
A&A - Audit and Assurance
Independent verification of security controls and compliance posture.
Control Objectives (6 controls):
- A&A-01: Audit Planning - Scope and objectives defined
- A&A-02: Independent Audits - Third-party assessments
- A&A-03: Information System Regulatory Mapping - Compliance alignment
- A&A-04: Audit Controls Assurance - Evidence collection
- A&A-05: SOC 2 Reporting - AICPA attestation
- A&A-06: Annual Certification - Ongoing compliance validation
Key Implementation:
- Engage independent auditors (SOC 2 Type II, ISO 27001)
- Maintain control evidence repository
- Map controls to regulatory requirements
- Conduct annual compliance reviews
AIS - Application & Interface Security
Secure design, development, and deployment of applications and APIs.
Control Objectives (11 controls):
- AIS-01: Application Security - SDLC integration
- AIS-02: Application Security Baseline - Minimum standards
- AIS-03: API Security - Interface protection
- AIS-04: Automated Application Security Testing - SAST/DAST
- AIS-05: Application Vulnerability Remediation - Patch management
- AIS-06: Production Code Changes - Change control
- AIS-07: Unsupported Software - Lifecycle management
- AIS-08: Application Security Training - Developer awareness
- AIS-09: Code Review - Peer/automated review
- AIS-10: Secure Coding - OWASP Top 10 prevention
- AIS-11: Third-Party Software - Vendor assessment
Key Implementation:
- OWASP Top 10 mitigation in SDLC
- API authentication (OAuth, API keys, JWT)
- Automated security testing in CI/CD
- Regular vulnerability scanning and remediation
BCR - Business Continuity & Operational Resilience
Maintaining availability during disruptions and disasters.
Control Objectives (11 controls):
- BCR-01: Business Continuity Planning - BCP documentation
- BCR-02: Business Impact Analysis - Critical function identification
- BCR-03: Resilience Architecture - Redundancy and failover
- BCR-04: Disaster Recovery - DR plan and testing
- BCR-05: Equipment Maintenance - Preventive maintenance
- BCR-06: Service Availability - SLA targets (99.9%, 99.99%)
- BCR-07: Backup - Data backup procedures
- BCR-08: Backup Verification - Restore testing
- BCR-09: Business Continuity Testing - Annual BCP/DR tests
- BCR-10: Environmental Risks - Physical threats mitigation
- BCR-11: Power Failures - UPS and generator backup
Key Implementation:
- Multi-region deployment for resilience
- Automated backup with 3-2-1 rule
- Annual DR testing and tabletop exercises
- SLA monitoring and incident response
CCC - Change Control & Configuration Management
Managing changes to systems and maintaining secure configurations.
Control Objectives (9 controls):
- CCC-01: New Development/Acquisition - Approval process
- CCC-02: Unauthorized Software - Whitelist/blacklist
- CCC-03: Production Changes - CAB approval
- CCC-04: Change Management - Documented procedures
- CCC-05: Baseline Configuration - Security standards
- CCC-06: Configuration Inventory - Asset tracking
- CCC-07: Quality Testing - Pre-production validation
- CCC-08: Outsourced Development - Vendor oversight
- CCC-09: Change Impact Analysis - Risk assessment
Key Implementation:
- Infrastructure as Code (IaC) with version control
- Change Advisory Board (CAB) for production changes
- CIS Benchmarks or vendor hardening guides
- Configuration management tools (Ansible, Puppet, Chef)
CEK - Cryptography, Encryption & Key Management
Protecting data through cryptographic controls.
Control Objectives (15 controls):
- CEK-01: Encryption at Rest - Data protection
- CEK-02: Encryption in Transit - TLS/SSL
- CEK-03: Encryption Algorithm - Strong crypto (AES-256)
- CEK-04: Key Generation - Secure random generation
- CEK-05: Key Management - Lifecycle management
- CEK-06: Key Access - Privileged access control
- CEK-07: Key Storage - Hardware Security Module (HSM)
- CEK-08: Key Rotation - Regular key changes
- CEK-09: Key Destruction - Secure deletion
- CEK-10: Sensitive Data Protection - PII/PHI encryption
- CEK-11: Certificate Management - PKI lifecycle
- CEK-12: Cryptographic Module Validation - FIPS 140-2
- CEK-13: Encryption Policy - Standards documentation
- CEK-14: Quantum-Safe Cryptography - Future-proofing
- CEK-15: Data in Use Encryption - Memory protection
Key Implementation:
- Cloud provider key management (AWS KMS, Azure Key Vault)
- TLS 1.2+ for all communications
- Automated certificate rotation
- HSM for key storage (FIPS 140-2 Level 2+)
DCS - Data Security & Privacy Lifecycle Management
Managing data throughout its lifecycle from creation to disposal.
Control Objectives (12 controls):
- DCS-01: Classification - Data categorization
- DCS-02: Secure Disposal - Sanitization and destruction
- DCS-03: Handling/Labeling/Security Policy - Data marking
- DCS-04: Nonproduction Data - Test data protection
- DCS-05: Data Retention - Policy enforcement
- DCS-06: Data Loss Prevention - DLP tools
- DCS-07: Data Inventory - Data mapping
- DCS-08: Data Flow Documentation - System diagrams
- DCS-09: Data Ownership - Accountability
- DCS-10: Data Minimization - Collect only necessary data
- DCS-11: eDiscovery - Legal hold procedures
- DCS-12: Data Anonymization - De-identification techniques
Key Implementation:
- Data classification scheme (Public, Internal, Confidential, Restricted)
- DLP policies for sensitive data exfiltration prevention
- Retention schedules aligned to regulations
- Secure data disposal (crypto erase, shredding)
DSP - Data Security & Privacy
Privacy-specific controls for personal data protection.
Control Objectives (13 controls):
- DSP-01: Privacy Impact Assessment - DPIA for high-risk processing
- DSP-02: Data Privacy Notice - Transparency
- DSP-03: Data Subject Rights - Access, erasure, portability
- DSP-04: Consent Management - Opt-in/opt-out
- DSP-05: Privacy by Design - Proactive privacy
- DSP-06: Data Processing Agreement - Third-party contracts
- DSP-07: Cross-Border Data Transfer - Adequacy/SCCs
- DSP-08: Data Breach Notification - 72-hour reporting
- DSP-09: Children's Privacy - COPPA compliance
- DSP-10: Marketing Communications - CAN-SPAM
- DSP-11: Cookies and Tracking - Consent mechanisms
- DSP-12: Automated Decision-Making - GDPR Article 22
- DSP-13: Data Protection Officer - Privacy governance
Key Implementation:
- GDPR/CCPA compliance programs
- Privacy-enhancing technologies (PETs)
- Consent management platforms
- Data subject request portal
GRC - Governance, Risk & Compliance
Establishing security governance and managing organizational risk.
Control Objectives (14 controls):
- GRC-01: Governance Program - Security framework
- GRC-02: Risk Management Framework - ISO 31000 alignment
- GRC-03: Risk Assessment - Annual/ad-hoc assessments
- GRC-04: Risk Treatment - Mitigation strategies
- GRC-05: Policy Management - Documentation and review
- GRC-06: Compliance Monitoring - Continuous compliance
- GRC-07: Security Metrics - KPIs and KRIs
- GRC-08: Executive Reporting - Board/C-level dashboards
- GRC-09: Internal Audit - Audit program
- GRC-10: Regulatory Intelligence - Law/regulation tracking
- GRC-11: Legal and Regulatory Compliance - Multi-jurisdiction
- GRC-12: Contracts and Agreements - Security terms
- GRC-13: Data Protection Authority - DPA registration
- GRC-14: Security Strategy - Multi-year roadmap
Key Implementation:
- GRC platform (ServiceNow, Archer, OneTrust)
- Risk register with heat maps
- Quarterly board reporting on security posture
- Policy review cycle (annual minimum)
HRS - Human Resources
Personnel security from hiring through termination.
Control Objectives (10 controls):
- HRS-01: Background Screening - Pre-employment checks
- HRS-02: Employment Agreements - Confidentiality clauses
- HRS-03: Roles and Responsibilities - Job descriptions
- HRS-04: Security Awareness Training - Annual training
- HRS-05: Role-Based Training - Specialized training
- HRS-06: Disciplinary Process - Policy violations
- HRS-07: Return of Assets - Termination procedures
- HRS-08: Access Revocation - Immediate termination of access
- HRS-09: Contractors and Third Parties - Non-employee security
- HRS-10: Training Records - Documentation
Key Implementation:
- Background checks for all employees
- Annual security awareness training (phishing, data handling)
- Automated deprovisioning on termination
- Contractor security acknowledgments
IAM - Identity & Access Management
Controlling who has access to what resources.
Control Objectives (16 controls):
- IAM-01: User Access Policy - Least privilege principle
- IAM-02: User Access Provisioning - Joiner/mover/leaver
- IAM-03: User Access Reviews - Periodic recertification
- IAM-04: User Access Revocation - Timely deprovisioning
- IAM-05: Privileged Access Management - Admin controls
- IAM-06: Multi-Factor Authentication - MFA for all users
- IAM-07: Password Policy - Complexity and rotation
- IAM-08: Single Sign-On - Centralized authentication
- IAM-09: Identity Federation - SAML/OAuth
- IAM-10: Service Accounts - Non-human identity management
- IAM-11: Just-in-Time Access - Temporary elevation
- IAM-12: Segregation of Duties - Conflict prevention
- IAM-13: Account Lockout - Brute force protection
- IAM-14: Session Management - Timeout and termination
- IAM-15: Biometric Authentication - Advanced authentication
- IAM-16: Identity Governance - IAM program oversight
Key Implementation:
- SSO with SAML/OIDC (Okta, Azure AD, Auth0)
- MFA for all accounts (hardware tokens, authenticator apps)
- Privileged Access Management (PAM) solution
- Quarterly access reviews and recertification
IPY - Interoperability & Portability
Preventing vendor lock-in and enabling data portability.
Control Objectives (5 controls):
- IPY-01: Data Portability - Customer data export
- IPY-02: Standard Formats - Open/standardized formats
- IPY-03: API Interoperability - Standard APIs
- IPY-04: Vendor Lock-In Prevention - Exit planning
- IPY-05: Service Migration - Transition assistance
Key Implementation:
- Data export APIs and tools
- Support for industry-standard formats (JSON, CSV, XML)
- Documented exit procedures
- No proprietary data formats
IVS - Infrastructure & Virtualization Security
Securing cloud infrastructure, hypervisors, and containers.
Control Objectives (13 controls):
- IVS-01: Network Security - Segmentation and firewalls
- IVS-02: Network Intrusion Detection - IDS/IPS
- IVS-03: Hypervisor Hardening - Virtualization security
- IVS-04: OS Hardening - Secure baselines
- IVS-05: Container Security - Docker/Kubernetes
- IVS-06: VM Isolation - Multi-tenancy controls
- IVS-07: Clock Synchronization - NTP
- IVS-08: Wireless Security - WiFi encryption
- IVS-09: Bring Your Own Device - BYOD policy
- IVS-10: Mobile Device Management - MDM solution
- IVS-11: Production/Non-Production Separation - Environment isolation
- IVS-12: Network Architecture - Defense in depth
- IVS-13: Secure Remote Access - VPN/bastion hosts
Key Implementation:
- Network segmentation (VPCs, subnets, security groups)
- CIS Benchmarks for OS hardening
- Container scanning (Aqua, Twistlock, Prisma Cloud)
- Zero Trust network architecture
LOG - Logging & Monitoring
Comprehensive security event logging and real-time monitoring.
Control Objectives (13 controls):
- LOG-01: Audit Logging - Event capture
- LOG-02: Security Event Logging - Security-relevant events
- LOG-03: Log Integrity - Tamper protection
- LOG-04: Log Retention - Compliance-driven retention
- LOG-05: Clock Synchronization - Time accuracy (NTP)
- LOG-06: Log Review and Analysis - Automated/manual review
- LOG-07: Security Monitoring - Real-time alerting
- LOG-08: SIEM - Centralized log aggregation
- LOG-09: Alerting and Notification - Incident alerting
- LOG-10: User Activity Monitoring - Privileged user tracking
- LOG-11: Log Access Control - Restricted access
- LOG-12: Audit Log Backup - Offline copies
- LOG-13: Performance Monitoring - System health
Key Implementation:
- SIEM solution (Splunk, ELK, Azure Sentinel)
- Log retention: 1 year minimum (varies by regulation)
- Real-time alerting for critical security events
- Immutable log storage (WORM, S3 Object Lock)
SEF - Security Incident Management
Detecting, responding to, and recovering from security incidents.
Control Objectives (10 controls):
- SEF-01: Incident Response Plan - Documented procedures
- SEF-02: Incident Response Team - CSIRT/SOC
- SEF-03: Incident Classification - Severity levels
- SEF-04: Incident Reporting - Internal/external reporting
- SEF-05: Incident Response Testing - Annual tabletops
- SEF-06: Forensics - Evidence collection
- SEF-07: Post-Incident Review - Lessons learned
- SEF-08: Threat Intelligence - IOC sharing
- SEF-09: Security Operations Center - 24/7 monitoring
- SEF-10: Incident Metrics - MTTD/MTTR tracking
Key Implementation:
- NIST 800-61 incident response framework
- Security Operations Center (SOC) 24/7
- Incident response playbooks
- Forensics tools and chain of custody procedures
STA - Supply Chain Management, Transparency & Accountability
Managing third-party and supply chain security risks.
Control Objectives (11 controls):
- STA-01: Third-Party Assessment - Vendor due diligence
- STA-02: Vendor Risk Management - Ongoing monitoring
- STA-03: Vendor Contracts - Security requirements
- STA-04: Supply Chain Transparency - Visibility
- STA-05: Outsourced Services - Managed service oversight
- STA-06: Cloud Service Providers - Sub-processor management
- STA-07: Data Processing Agreements - GDPR DPAs
- STA-08: Right to Audit - Contractual audit rights
- STA-09: Vendor Termination - Offboarding procedures
- STA-10: Supply Chain Incident Response - Coordinated response
- STA-11: Software Supply Chain - SBOM management
Key Implementation:
- Vendor security questionnaires (SIG, CAIQ)
- Third-party risk management platform
- Annual vendor assessments
- Software Bill of Materials (SBOM) for dependencies
TVM - Threat & Vulnerability Management
Identifying and remediating security vulnerabilities.
Control Objectives (13 controls):
- TVM-01: Vulnerability Scanning - Automated scanning
- TVM-02: Vulnerability Remediation - SLA-based patching
- TVM-03: Penetration Testing - Annual pentests
- TVM-04: Red Team Exercises - Advanced threat simulation
- TVM-05: Threat Intelligence - IOCs and TTPs
- TVM-06: Security Testing - SAST/DAST integration
- TVM-07: Patch Management - Timely updates
- TVM-08: Critical Patch SLA - Emergency patching
- TVM-09: Vulnerability Disclosure Program - Responsible disclosure
- TVM-10: Bug Bounty - Crowdsourced security testing
- TVM-11: Security Advisories - Vendor notifications
- TVM-12: Asset Discovery - Shadow IT identification
- TVM-13: Attack Surface Management - External exposure
Key Implementation:
- Vulnerability scanning (Nessus, Qualys, Rapid7)
- Patch management: Critical (7 days), High (30 days), Medium (90 days)
- Annual penetration testing
- Bug bounty program (HackerOne, Bugcrowd)
UEM - Universal Endpoint Management
Securing all endpoint devices accessing cloud services.
Control Objectives (7 controls):
- UEM-01: Endpoint Security Policy - Standards
- UEM-02: Endpoint Protection - Antivirus/EDR
- UEM-03: Endpoint Encryption - Full disk encryption
- UEM-04: Mobile Device Management - MDM/MAM
- UEM-05: BYOD Security - Personal device controls
- UEM-06: Remote Wipe - Lost/stolen device protection
- UEM-07: Endpoint Compliance - Configuration enforcement
Key Implementation:
- Endpoint Detection and Response (EDR) solution
- MDM for corporate/BYOD devices (Intune, Jamf, MobileIron)
- Full disk encryption (BitLocker, FileVault)
- Conditional access policies
Output
- Domain Overview: Purpose, objectives, and cloud relevance
- Control Objective List: All controls within domain
- Implementation Guidance: Technical and procedural requirements
- Cloud Service Model Considerations: IaaS/PaaS/SaaS variations
- Common Gaps: Typical deficiencies in cloud environments
- Evidence Requirements: What auditors look for
- Framework Mappings: ISO 27001, SOC 2, NIST alignment
- Tool Recommendations: Cloud-native and third-party solutions
Examples
# Get detailed guidance for Encryption domain
/ccm:domain-guidance CEK
# Review IAM requirements for SaaS context
/ccm:domain-guidance IAM SaaS
# Understand logging requirements for IaaS
/ccm:domain-guidance LOG IaaS
# Deep dive into incident management
/ccm:domain-guidance SEF
Cloud-Specific Considerations
IaaS Focus Domains
- IVS: Infrastructure & Virtualization Security
- CCC: Change Control & Configuration Management
- LOG: Logging & Monitoring
PaaS Focus Domains
- AIS: Application & Interface Security
- CEK: Cryptography, Encryption & Key Management
- DCS: Data Security & Privacy Lifecycle
SaaS Focus Domains
- IAM: Identity & Access Management
- DSP: Data Security & Privacy
- A&A: Audit and Assurance
CSA Cloud Controls Matrix (CCM) Evidence Checklist
Generates comprehensive evidence collection checklists for CSA CCM v4 controls, optimized for cloud-native environments (AWS, Azure, GCP) with STAR attestation guidance.
Never commit evidence artifacts to source control. The outputs below include real usernames, credential reports, MFA device states, and privileged-account inventories.
.gitignorecoversevidence/by default sogit add -Awill not sweep it up, but durable storage is your responsibility. Use an encrypted, access-controlled evidence locker (encrypted S3 with least-privilege IAM, a GRC platform, or a shared drive with full-disk encryption and MFA-gated access).
Usage
/csa-ccm:evidence-checklist <control-id> [--cloud-provider <aws|azure|gcp>] [--export <format>]
Arguments
<control-id>: CSA CCM control (e.g., "IAM-02", "DSP-04", "IVS-01") or domain (e.g., "Identity & Access Management", "Data Security & Privacy")--cloud-provider: Target cloud platform (aws,azure,gcp, ormulti). Default:aws--export: Export format (json,csv,markdown). Default:markdown
Example: Identity & Access Management Evidence
/csa-ccm:evidence-checklist IAM-02 --cloud-provider aws
Output:
CSA Cloud Controls Matrix v4 Evidence Checklist
Control: IAM-02 - Credential Lifecycle / Provision Management
Domain: Identity & Access Management (IAM)
Cloud Provider: AWS
STAR Level: Level 1 (Self-Assessment) / Level 2 (Third-Party Audit)
## Control Specification
Applications and systems are able to uniquely identify and authenticate users accessing cloud services. Cloud service provider shall use secure, industry-recognized processes for identity and access management.
## Cloud Implementation Notes
For AWS environments, this control requires:
- IAM user lifecycle management (creation, modification, deletion)
- Automated provisioning via Identity Center (SSO) or third-party IdP
- Service account management (IAM roles, service principals)
- Credential rotation policies
- Least privilege enforcement
## Evidence Requirements
### Required Documentation
□ **Identity and Access Management Policy**
- Scope: All cloud platforms (AWS, Azure, GCP)
- Required elements:
- Credential lifecycle procedures
- Identity proofing requirements
- Automated provisioning integration (SCIM, SAML)
- Credential rotation schedules
- Privileged access management
- Service account governance
- Update frequency: Annually
- Approver: CISO or Cloud Security lead
- Evidence: Signed IAM policy v1.x
□ **Cloud Identity Architecture Diagram**
- Show: IdP integration (Okta, Azure AD, etc.) → AWS SSO/Azure AD/GCP Workforce Identity
- Include: User authentication flow, federated access, MFA enforcement points
- Format: Visio, Lucidchart, or draw.io diagram
- Update frequency: When architecture changes
- Evidence: Architecture diagram v1.x + narrative description
□ **Provisioning/Deprovisioning Procedures**
- Step-by-step user onboarding to cloud platforms
- Step-by-step user offboarding process
- Automated SCIM provisioning configuration
- Emergency access procedures
- Evidence: SOP document with screenshots
### Automated Evidence Collection (AWS)
✓ **IAM User Inventory**
```bash
# Complete IAM user list
aws iam list-users --output json > evidence/ccm-iam-02-users-$(date +%Y%m%d).json
# IAM credential report (shows password age, MFA status, access key age)
aws iam generate-credential-report
aws iam get-credential-report --output text | base64 -d \
> evidence/ccm-iam-02-credential-report-$(date +%Y%m%d).csv
# User creation dates (for lifecycle tracking)
aws iam list-users | jq -r '.Users[] | [.UserName, .CreateDate] | @csv' \
> evidence/ccm-iam-02-user-creation-dates-$(date +%Y%m%d).csv
Collection Frequency: Monthly Retention: 12 months minimum Purpose: Demonstrates user inventory and credential age
✓ IAM Identity Center (SSO) Users
# If using AWS SSO/Identity Center
aws identitystore list-users --identity-store-id <IDENTITY-STORE-ID> \
--output json > evidence/ccm-iam-02-sso-users-$(date +%Y%m%d).json
# Permission sets assigned
aws sso-admin list-permission-sets --instance-arn <INSTANCE-ARN> \
--output json > evidence/ccm-iam-02-permission-sets-$(date +%Y%m%d).json
# Account assignments (who has access to which AWS accounts)
for account in $(aws organizations list-accounts --query 'Accounts[].Id' --output text); do
aws sso-admin list-account-assignments \
--instance-arn <INSTANCE-ARN> \
--account-id "$account" \
--permission-set-arn <PERMISSION-SET-ARN> \
--output json >> evidence/ccm-iam-02-sso-assignments-$(date +%Y%m%d).json
done
Collection Frequency: Monthly Retention: 12 months Purpose: Cloud-native federated identity evidence
✓ Service Account / IAM Role Inventory
# IAM roles (service accounts)
aws iam list-roles --output json > evidence/ccm-iam-02-roles-$(date +%Y%m%d).json
# Service-linked roles (AWS-managed)
aws iam list-roles | jq '.Roles[] | select(.Path | startswith("/aws-service-role/"))' \
> evidence/ccm-iam-02-service-linked-roles-$(date +%Y%m%d).json
# Customer-managed roles (applications)
aws iam list-roles | jq '.Roles[] | select(.Path == "/" and (.RoleName | startswith("AWSServiceRole") | not))' \
> evidence/ccm-iam-02-app-roles-$(date +%Y%m%d).json
# Role trust policies (who can assume roles)
for role in $(aws iam list-roles --query 'Roles[].RoleName' --output text); do
echo "=== $role ===" >> evidence/ccm-iam-02-role-trusts-$(date +%Y%m%d).txt
aws iam get-role --role-name "$role" --query 'Role.AssumeRolePolicyDocument' \
>> evidence/ccm-iam-02-role-trusts-$(date +%Y%m%d).txt
done
Collection Frequency: Monthly Retention: 12 months Purpose: Non-human identity inventory
✓ Credential Rotation Evidence
# Access keys older than 90 days (non-compliant)
aws iam get-credential-report --output text | base64 -d | \
awk -F',' '$10 == "true" {split($11,a,"T"); if ((systime() - mktime(gensub(/[-:]/," ","g",a[1]" "substr(a[2],1,8)))) > 90*86400) print $1, $11}' \
> evidence/ccm-iam-02-old-access-keys-$(date +%Y%m%d).txt
# Passwords older than 90 days
aws iam get-credential-report --output text | base64 -d | \
awk -F',' '$4 == "true" {split($5,a,"T"); if ((systime() - mktime(gensub(/[-:]/," ","g",a[1]" "substr(a[2],1,8)))) > 90*86400) print $1, $5}' \
> evidence/ccm-iam-02-old-passwords-$(date +%Y%m%d).txt
# Users without MFA (non-compliant)
aws iam get-credential-report --output text | base64 -d | \
awk -F',' '$4 == "true" && $8 == "false" {print $1}' \
> evidence/ccm-iam-02-no-mfa-$(date +%Y%m%d).txt
Collection Frequency: Weekly Retention: 12 months Purpose: Credential hygiene monitoring
✓ Provisioning/Deprovisioning Audit Trail
# User creation events (last 30 days)
aws cloudtrail lookup-events \
--lookup-attributes AttributeKey=EventName,AttributeValue=CreateUser \
--start-time $(date -u -d '30 days ago' +%Y-%m-%dT%H:%M:%S) \
--max-items 1000 \
--output json > evidence/ccm-iam-02-user-creation-$(date +%Y%m).json
# User deletion events (last 30 days)
aws cloudtrail lookup-events \
--lookup-attributes AttributeKey=EventName,AttributeValue=DeleteUser \
--start-time $(date -u -d '30 days ago' +%Y-%m-%dT%H:%M:%S) \
--max-items 1000 \
--output json > evidence/ccm-iam-02-user-deletion-$(date +%Y%m).json
# Permission changes (last 30 days)
for event in AttachUserPolicy DetachUserPolicy PutUserPolicy DeleteUserPolicy; do
aws cloudtrail lookup-events \
--lookup-attributes AttributeKey=EventName,AttributeValue=$event \
--start-time $(date -u -d '30 days ago' +%Y-%m-%dT%H:%M:%S) \
--max-items 1000 \
--output json >> evidence/ccm-iam-02-permission-changes-$(date +%Y%m).json
done
Collection Frequency: Monthly Retention: 12 months Purpose: Lifecycle audit trail
Automated Evidence Collection (Azure)
✓ Azure AD User Inventory
# All Azure AD users
az ad user list --output json > evidence/ccm-iam-02-azure-users-$(date +%Y%m%d).json
# Guest users (external identities)
az ad user list --filter "userType eq 'Guest'" --output json \
> evidence/ccm-iam-02-azure-guests-$(date +%Y%m%d).json
# Service principals (application identities)
az ad sp list --all --output json > evidence/ccm-iam-02-azure-sp-$(date +%Y%m%d).json
# Managed identities (for Azure resources)
az identity list --output json > evidence/ccm-iam-02-managed-identities-$(date +%Y%m%d).json
Collection Frequency: Monthly Retention: 12 months
✓ Azure AD Sign-in Logs
# Sign-in activity (last 30 days)
az monitor activity-log list \
--caller 'Microsoft.Azure.ActiveDirectory' \
--start-time $(date -u -d '30 days ago' +%Y-%m-%dT%H:%M:%S) \
--output json > evidence/ccm-iam-02-azure-signins-$(date +%Y%m).json
# Failed sign-ins (potential unauthorized access)
az monitor activity-log list \
--caller 'Microsoft.Azure.ActiveDirectory' \
--status Failed \
--start-time $(date -u -d '30 days ago' +%Y-%m-%dT%H:%M:%S) \
--output json > evidence/ccm-iam-02-azure-failed-signins-$(date +%Y%m).json
Collection Frequency: Monthly Retention: 12 months
Automated Evidence Collection (GCP)
✓ GCP IAM User Inventory
# Workforce identity users (if using Workforce Identity Federation)
gcloud identity groups memberships list \
--group-email=all-users@company.com \
--format=json > evidence/ccm-iam-02-gcp-users-$(date +%Y%m%d).json
# Service accounts
gcloud iam service-accounts list --format=json \
> evidence/ccm-iam-02-gcp-service-accounts-$(date +%Y%m%d).json
# Service account keys (check for rotation)
for sa in $(gcloud iam service-accounts list --format='value(email)'); do
echo "=== $sa ===" >> evidence/ccm-iam-02-gcp-sa-keys-$(date +%Y%m%d).txt
gcloud iam service-accounts keys list --iam-account="$sa" --format=json \
>> evidence/ccm-iam-02-gcp-sa-keys-$(date +%Y%m%d).txt
done
Collection Frequency: Monthly Retention: 12 months
Manual Evidence Collection
□ Identity Provider (IdP) Integration Configuration
- Screenshots of SAML/SCIM configuration in IdP (Okta, Azure AD, etc.)
- Screenshots of AWS SSO/Azure AD/GCP federation setup
- Attribute mapping configuration (email → username, groups → roles)
- Evidence: Screenshots + configuration export (sanitized)
- Frequency: When configuration changes, annual review
□ Automated Provisioning Evidence (Sample)
- Sample size: 10 users provisioned in last quarter
- Required elements:
- User created in IdP (Okta/Azure AD)
- SCIM sync log showing user pushed to AWS/Azure/GCP
- User appears in cloud platform within 15 minutes
- Correct permission set/role assigned based on group membership
- Evidence: SCIM logs + before/after screenshots
- Frequency: Quarterly review
□ Deprovisioning Evidence (Sample)
- Sample size: All user departures in last quarter (or 10 if >10)
- Required elements:
- User disabled in IdP
- User access to cloud revoked within 24 hours
- No subsequent login attempts after deprovisioning
- Evidence: IdP audit logs + CloudTrail/Azure AD logs
- Frequency: Quarterly review
□ Credential Rotation Policy Enforcement
- Document rotation schedules:
- User passwords: 90 days maximum
- Access keys: 90 days maximum
- Service account keys: 90 days maximum (GCP), use IAM roles instead (AWS/Azure)
- Show enforcement mechanism (IAM password policy, automated alerts)
- Evidence: IAM password policy screenshot + rotation reports
- Frequency: Annual review
□ Privileged Account Governance
- Inventory of break-glass / emergency accounts
- Usage logs for break-glass accounts (should be rare)
- Justification for service accounts with privileged access
- Evidence: Privileged account register + usage logs
- Frequency: Quarterly review
CSA STAR Attestation Requirements
For CSA STAR Level 2 (Third-Party Audit), auditor will verify:
Documentation Requirements
✓ IAM policy approved by senior management ✓ Cloud architecture diagram showing identity flows ✓ Provisioning/deprovisioning procedures documented ✓ Integration with corporate IdP (single source of truth)
Implementation Requirements
✓ Automated provisioning (SCIM or equivalent) ✓ Automated deprovisioning (<24 hours from termination) ✓ Credential rotation enforced (technical controls, not just policy) ✓ Least privilege access (no standing admin access) ✓ MFA enforced for all human access
Testing Requirements
✓ Sample 25 user creation events (show approval + provisioning) ✓ Sample 25 user termination events (show <24hr revocation) ✓ Demonstrate credential rotation (no credentials >90 days) ✓ Show orphaned account detection and remediation
Common STAR Assessment Findings
Critical Findings (Likely to fail STAR Level 2)
❌ No automated provisioning (manual account creation) ❌ No automated deprovisioning (terminated users retain access >24hrs) ❌ No credential rotation enforcement (passwords/keys >1 year old) ❌ No MFA for privileged access ❌ Shared credentials (multiple people using same account)
Moderate Findings
⚠️ Deprovisioning >24 hours but <72 hours ⚠️ Some credentials not rotated (>90 days but <180 days) ⚠️ IdP integration incomplete (some platforms manual) ⚠️ Service account proliferation without governance
Minor Findings
⚠️ Documentation incomplete (missing architecture diagrams) ⚠️ Orphaned accounts exist but detected and remediated ⚠️ Evidence retention <12 months
Remediation Guidance
If No Automated Provisioning
-
Select Identity Provider (if none exists)
- Small orgs: Okta Workforce Identity ($2-8/user/month)
- Microsoft shops: Azure AD Premium P1 ($6/user/month)
- Google Workspace: Cloud Identity Premium ($6/user/month)
-
Configure SAML/SCIM Integration
- AWS: AWS IAM Identity Center (free with AWS account)
- Azure: Native Azure AD integration
- GCP: Workforce Identity Federation
-
Implement Automated Lifecycle
- HR system → IdP (Workday/BambooHR/ADP integration)
- IdP → Cloud (SCIM provisioning)
- Termination in HR = automatic cloud access revocation
Timeline: 4-8 weeks implementation
If Credential Rotation Not Enforced
- Enable IAM Password Policy (AWS)
aws iam update-account-password-policy \
--max-password-age 90 \
--minimum-password-length 14 \
--require-symbols \
--require-numbers \
--require-uppercase-characters \
--require-lowercase-characters \
--password-reuse-prevention 24
- Implement Access Key Rotation Automation
# Lambda function to alert on old access keys
import boto3
from datetime import datetime, timedelta
def lambda_handler(event, context):
iam = boto3.client('iam')
sns = boto3.client('sns')
# Get credential report
iam.generate_credential_report()
report = iam.get_credential_report()
# Parse CSV and find old keys
old_keys = []
for line in report['Content'].decode('utf-8').split('\n')[1:]:
fields = line.split(',')
if len(fields) > 11 and fields[10] == 'true': # Key 1 active
key_age = (datetime.now() - datetime.fromisoformat(fields[11].replace('Z', '+00:00'))).days
if key_age > 90:
old_keys.append({'user': fields[0], 'age': key_age})
# Send alert
if old_keys:
sns.publish(
TopicArn='arn:aws:sns:us-east-1:123456789012:security-alerts',
Subject='IAM Access Keys Require Rotation',
Message=f"Found {len(old_keys)} access keys older than 90 days:\n" +
'\n'.join([f"{k['user']}: {k['age']} days" for k in old_keys])
)
Timeline: 1-2 weeks implementation
Cross-References
Related CSA CCM Controls
- IAM-01 - Audit Tools Access
- IAM-03 - Diagnostic / Configuration Ports Access
- IAM-07 - User Access Policy
- IAM-12 - Secure / Private Authentication
- CCC-01 - Cloud Change Control and Configuration Management
Maps to Other Frameworks
- NIST 800-53: AC-2 (Account Management), IA-4 (Identifier Management), IA-5 (Authenticator Management)
- ISO 27001:2022: A.5.15 (Access control), A.5.17 (Authentication), A.5.18 (Access rights)
- SOC 2: CC6.1, CC6.2 (Access controls, authentication)
- CMMC 2.0: IA.L2-3.5.1, IA.L2-3.5.2 (Identification and authentication)
- PCI-DSS v4: 8.2 (User identification and authentication)
Cost Estimates
Identity Platform (Annual)
- Okta Workforce: $6-10/user/month ($1,200-2,000/yr for 20 users)
- Azure AD Premium P1: $6/user/month ($1,440/yr for 20 users)
- Google Cloud Identity Premium: $6/user/month ($1,440/yr for 20 users)
Implementation (One-Time)
- IdP setup and SCIM integration: 80 hours ($8,000)
- Automated credential rotation: 40 hours ($4,000)
- Evidence collection automation: 24 hours ($2,400)
CSA STAR Assessment (If pursuing certification)
- Level 1 (Self-Assessment): Free
- Level 2 (Third-Party Audit): $25k-$75k (varies by organization size)
- Annual surveillance: $15k-$30k/year
Automation Script
#!/usr/bin/env python3
"""
CSA CCM IAM-02 Evidence Collection (Multi-Cloud)
Supports AWS, Azure, GCP
"""
import boto3
import subprocess
import json
import csv
from datetime import datetime
import os
class CCMIAMEvidence:
def __init__(self, output_dir="evidence/ccm-iam-02"):
self.output_dir = output_dir
self.timestamp = datetime.now().strftime("%Y%m%d")
os.makedirs(output_dir, exist_ok=True)
def collect_aws(self):
"""Collect AWS IAM evidence"""
print("Collecting AWS IAM evidence...")
iam = boto3.client('iam')
# User inventory
users = iam.list_users()['Users']
with open(f"{self.output_dir}/aws-iam-users-{self.timestamp}.json", 'w') as f:
json.dump(users, f, indent=2, default=str)
# Credential report
iam.generate_credential_report()
report = iam.get_credential_report()
with open(f"{self.output_dir}/aws-credential-report-{self.timestamp}.csv", 'wb') as f:
f.write(report['Content'])
# Analyze credential age
old_credentials = []
for line in csv.DictReader(report['Content'].decode('utf-8').splitlines()):
if line.get('access_key_1_active') == 'true':
key_age = (datetime.now() - datetime.fromisoformat(line['access_key_1_last_rotated'].replace('Z', '+00:00'))).days
if key_age > 90:
old_credentials.append({
'user': line['user'],
'credential_type': 'access_key_1',
'age_days': key_age
})
with open(f"{self.output_dir}/aws-old-credentials-{self.timestamp}.json", 'w') as f:
json.dump(old_credentials, f, indent=2)
print(f"✓ AWS: {len(users)} users, {len(old_credentials)} credentials >90 days")
return {'users': len(users), 'old_credentials': len(old_credentials)}
def collect_azure(self):
"""Collect Azure AD evidence"""
print("Collecting Azure AD evidence...")
# Azure CLI commands
try:
users = subprocess.check_output(['az', 'ad', 'user', 'list', '--output', 'json'])
with open(f"{self.output_dir}/azure-users-{self.timestamp}.json", 'wb') as f:
f.write(users)
user_count = len(json.loads(users))
print(f"✓ Azure: {user_count} users")
return {'users': user_count}
except subprocess.CalledProcessError as e:
print(f"⚠️ Azure collection failed (az CLI not configured?): {e}")
return {'users': 0}
def collect_gcp(self):
"""Collect GCP IAM evidence"""
print("Collecting GCP evidence...")
try:
sa_list = subprocess.check_output(['gcloud', 'iam', 'service-accounts', 'list', '--format=json'])
with open(f"{self.output_dir}/gcp-service-accounts-{self.timestamp}.json", 'wb') as f:
f.write(sa_list)
sa_count = len(json.loads(sa_list))
print(f"✓ GCP: {sa_count} service accounts")
return {'service_accounts': sa_count}
except subprocess.CalledProcessError as e:
print(f"⚠️ GCP collection failed (gcloud not configured?): {e}")
return {'service_accounts': 0}
def generate_report(self, aws_data, azure_data, gcp_data):
"""Generate summary report"""
report = f"""
CSA CCM v4 - IAM-02 Evidence Report
Generated: {datetime.now().strftime("%Y-%m-%d %H:%M:%S")}
MULTI-CLOUD IDENTITY INVENTORY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
AWS IAM Users: {aws_data.get('users', 0)}
AWS Old Credentials: {aws_data.get('old_credentials', 0)} (>90 days)
Azure AD Users: {azure_data.get('users', 0)}
GCP Service Accounts: {gcp_data.get('service_accounts', 0)}
COMPLIANCE STATUS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
{'✓ COMPLIANT' if aws_data.get('old_credentials', 0) == 0 else '✗ NON-COMPLIANT'} - Credential rotation (0 credentials >90 days required)
RECOMMENDATIONS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
"""
if aws_data.get('old_credentials', 0) > 0:
report += f"□ Rotate {aws_data['old_credentials']} AWS access keys immediately\n"
report += "□ Review user inventory for orphaned accounts\n"
report += "□ Validate IdP SCIM integration is active\n"
report += f"\nEvidence stored in: {self.output_dir}/\n"
print(report)
with open(f"{self.output_dir}/summary-report-{self.timestamp}.txt", 'w') as f:
f.write(report)
if __name__ == "__main__":
print("CSA CCM IAM-02 Evidence Collection (Multi-Cloud)")
print("=" * 60)
collector = CCMIAMEvidence()
aws_data = collector.collect_aws()
azure_data = collector.collect_azure()
gcp_data = collector.collect_gcp()
collector.generate_report(aws_data, azure_data, gcp_data)
print("\n✓ Multi-cloud evidence collection complete")
CSA STAR Level: Level 1 (Self) / Level 2 (Third-Party) Implementation Priority: 🔴 CRITICAL (Core identity control) Cloud-Native: YES (designed for cloud environments) Estimated Implementation Time: 6-12 weeks (with IdP integration)
CSA CCM Framework Mapping
Maps Cloud Security Alliance Cloud Controls Matrix controls to other major compliance frameworks including ISO 27001, SOC 2, PCI-DSS, NIST, HIPAA, and GDPR.
Arguments
$1- CCM control ID (required, e.g., CEK-01, IAM-06, LOG-08)$2- Target framework (optional: ISO27001, SOC2, PCIDSS, NIST, HIPAA, GDPR, all)
CCM Control ID Format
Structure: [Domain]-[Number]
- Domain: Three-letter abbreviation (A&A, AIS, BCR, CCC, CEK, DCS, DSP, GRC, HRS, IAM, IPY, IVS, LOG, SEF, STA, TVM, UEM)
- Number: Two-digit control number (01-99)
Examples:
CEK-01: Cryptography domain, control 01 (Encryption at Rest)IAM-06: Identity & Access Management, control 06 (Multi-Factor Authentication)LOG-08: Logging domain, control 08 (SIEM)
Framework Mapping Overview
CCM v4.0 provides comprehensive mappings to enable multi-framework compliance:
Supported Framework Mappings
- ISO/IEC 27001:2022 - Information Security Management
- SOC 2 Type II - AICPA Trust Services Criteria
- PCI DSS v4.0 - Payment Card Industry Data Security Standard
- NIST CSF 2.0 - Cybersecurity Framework
- NIST 800-53 Rev 5 - Security and Privacy Controls
- HIPAA Security Rule - Healthcare Information Protection
- GDPR - General Data Protection Regulation
- FedRAMP - Federal Risk and Authorization Management Program
- COBIT 2019 - IT Governance Framework
- CIS Controls v8 - Center for Internet Security
Common Control Mappings
Encryption Controls
CEK-01: Encryption at Rest
- ISO 27001: A.8.24 (Use of cryptography)
- SOC 2: CC6.1 (Logical and physical access controls)
- PCI DSS: 3.5.1 (Disk encryption to protect PAN)
- NIST 800-53: SC-28 (Protection of Information at Rest)
- HIPAA: 164.312(a)(2)(iv) (Encryption and decryption)
- GDPR: Article 32(1)(a) (Pseudonymisation and encryption)
CEK-02: Encryption in Transit
- ISO 27001: A.8.24 (Use of cryptography)
- SOC 2: CC6.7 (Transmission of data protected)
- PCI DSS: 4.2.1 (Strong cryptography for transmission)
- NIST 800-53: SC-8 (Transmission Confidentiality and Integrity)
- HIPAA: 164.312(e)(1) (Transmission security)
- GDPR: Article 32(1)(a) (Encryption of personal data)
CEK-05: Key Management
- ISO 27001: A.8.24 (Use of cryptography)
- SOC 2: CC6.1 (Logical and physical access controls)
- PCI DSS: 3.6.1 (Generation of strong cryptographic keys)
- NIST 800-53: SC-12 (Cryptographic Key Establishment and Management)
- HIPAA: 164.312(a)(2)(iv) (Encryption and decryption)
Identity & Access Management
IAM-01: User Access Policy
- ISO 27001: A.5.15 (Access control), A.5.16 (Identity management)
- SOC 2: CC6.1 (Logical and physical access controls)
- PCI DSS: 7.1.1 (Access limited to least privilege)
- NIST 800-53: AC-2 (Account Management)
- HIPAA: 164.308(a)(4)(i) (Access authorization)
- GDPR: Article 32(1)(b) (Confidentiality of processing systems)
IAM-06: Multi-Factor Authentication
- ISO 27001: A.5.17 (Authentication information)
- SOC 2: CC6.1 (Logical and physical access controls)
- PCI DSS: 8.4.2 (MFA for remote access)
- NIST 800-53: IA-2(1) (Multi-factor Authentication)
- HIPAA: 164.312(d) (Person or entity authentication)
- GDPR: Article 32(1)(b) (Ability to ensure confidentiality)
IAM-03: User Access Reviews
- ISO 27001: A.5.18 (Access rights review)
- SOC 2: CC6.2 (Logical and physical access review)
- PCI DSS: 7.2.4 (Review user access at least every 6 months)
- NIST 800-53: AC-2(7) (Account Management - Privileged User Accounts)
- HIPAA: 164.308(a)(4)(ii)(C) (Access establishment and modification)
Logging & Monitoring
LOG-01: Audit Logging
- ISO 27001: A.8.15 (Logging)
- SOC 2: CC7.2 (System monitoring)
- PCI DSS: 10.2.1 (Audit logs for user actions)
- NIST 800-53: AU-2 (Event Logging)
- HIPAA: 164.312(b) (Audit controls)
- GDPR: Article 32(1)(d) (Monitoring effectiveness)
LOG-08: SIEM
- ISO 27001: A.8.16 (Monitoring activities)
- SOC 2: CC7.2 (System monitoring tools)
- PCI DSS: 10.6.1 (Review logs daily)
- NIST 800-53: AU-6 (Audit Review, Analysis, and Reporting)
- HIPAA: 164.308(a)(1)(ii)(D) (Information system activity review)
LOG-04: Log Retention
- ISO 27001: A.8.15 (Logging)
- SOC 2: CC7.2 (System monitoring)
- PCI DSS: 10.5.1 (Retain audit logs at least 1 year)
- NIST 800-53: AU-11 (Audit Record Retention)
- HIPAA: 164.316(b)(2)(i) (Retain documentation 6 years)
Incident Management
SEF-01: Incident Response Plan
- ISO 27001: A.5.24 (Information security incident management planning)
- SOC 2: CC7.3 (Security incidents evaluated and responded to)
- PCI DSS: 12.10.1 (Incident response plan)
- NIST 800-53: IR-8 (Incident Response Plan)
- HIPAA: 164.308(a)(6)(i) (Security incident procedures)
- GDPR: Article 33 (Notification of a personal data breach)
SEF-04: Incident Reporting
- ISO 27001: A.5.25 (Assessment and decision on information security events)
- SOC 2: CC7.4 (Communication of security events)
- PCI DSS: 12.10.6 (Incident response procedures)
- NIST 800-53: IR-6 (Incident Reporting)
- HIPAA: 164.308(a)(6)(ii) (Identify and respond to suspected security incidents)
- GDPR: Article 33 (72-hour breach notification)
Data Privacy
DSP-01: Privacy Impact Assessment
- ISO 27001: A.5.36 (Compliance with policies and standards for information security)
- GDPR: Article 35 (Data Protection Impact Assessment)
- NIST 800-53: RA-8 (Privacy Impact Assessments)
DSP-03: Data Subject Rights
- ISO 27001: A.5.34 (Privacy and protection of PII)
- GDPR: Articles 15-22 (Rights of the data subject)
- HIPAA: 164.524 (Access of individuals to PHI)
DSP-08: Data Breach Notification
- ISO 27001: A.5.26 (Response to information security incidents)
- GDPR: Article 33 (72-hour notification to authority)
- HIPAA: 164.410 (Breach notification - 60 days)
- PCI DSS: 12.10.4 (Incident response communications)
Vulnerability Management
TVM-01: Vulnerability Scanning
- ISO 27001: A.8.8 (Management of technical vulnerabilities)
- SOC 2: CC7.1 (Security threats detected and mitigated)
- PCI DSS: 11.3.1 (Internal vulnerability scans quarterly)
- NIST 800-53: RA-5 (Vulnerability Monitoring and Scanning)
- HIPAA: 164.308(a)(8) (Evaluation of security measures)
TVM-03: Penetration Testing
- ISO 27001: A.8.8 (Management of technical vulnerabilities)
- SOC 2: CC7.1 (Security threats detected)
- PCI DSS: 11.4.1 (Penetration testing annually)
- NIST 800-53: CA-8 (Penetration Testing)
- HIPAA: 164.308(a)(8) (Evaluation)
TVM-07: Patch Management
- ISO 27001: A.8.19 (Installation of software on operational systems)
- SOC 2: CC7.1 (Security threats detected and mitigated)
- PCI DSS: 6.3.3 (Security patches installed within 30 days)
- NIST 800-53: SI-2 (Flaw Remediation)
- HIPAA: 164.308(a)(5)(ii)(B) (Protection from malicious software)
Business Continuity
BCR-04: Disaster Recovery
- ISO 27001: A.5.29 (Information security during disruption)
- SOC 2: A1.2 (Business continuity and disaster recovery)
- NIST 800-53: CP-10 (System Recovery and Reconstitution)
- HIPAA: 164.308(a)(7)(ii)(B) (Disaster recovery plan)
BCR-07: Backup
- ISO 27001: A.8.13 (Information backup)
- SOC 2: A1.2 (Data backup and recovery)
- PCI DSS: 12.9.1 (Document backup procedures)
- NIST 800-53: CP-9 (System Backup)
- HIPAA: 164.308(a)(7)(ii)(A) (Data backup plan)
Third-Party Management
STA-01: Third-Party Assessment
- ISO 27001: A.5.19 (Information security in supplier relationships)
- SOC 2: CC9.2 (Vendor management)
- PCI DSS: 12.8.2 (Service provider compliance monitoring)
- NIST 800-53: SA-9 (External System Services)
- HIPAA: 164.314(a)(1) (Business associate contracts)
- GDPR: Article 28 (Processor obligations)
Framework-Specific Views
ISO 27001:2022 Mapping
CCM provides comprehensive coverage of ISO 27001 Annex A controls (93 controls across 4 themes):
- Organizational controls (37 controls)
- People controls (8 controls)
- Physical controls (14 controls)
- Technological controls (34 controls)
CCM Coverage: 197 controls map to all 93 ISO 27001 Annex A controls with additional depth.
SOC 2 Type II Mapping
CCM aligns to AICPA Trust Services Criteria:
- CC (Common Criteria): Control environment, communication, risk assessment, monitoring
- A (Availability): System availability and business continuity
- C (Confidentiality): Protection of confidential information
- P (Processing Integrity): Complete, valid, accurate, timely processing
- PI (Privacy): Collection, use, retention, disclosure of personal information
CCM Coverage: All SOC 2 criteria mapped with cloud-specific enhancements.
PCI DSS v4.0 Mapping
CCM covers all 12 PCI DSS requirements:
- Install and maintain network security controls
- Apply secure configurations
- Protect stored account data
- Protect cardholder data with strong cryptography
- Protect all systems and networks from malicious software
- Develop and maintain secure systems and software
- Restrict access to system components and cardholder data
- Identify users and authenticate access
- Restrict physical access to cardholder data
- Log and monitor all access
- Test security of systems and networks regularly
- Support information security with policies and programs
CCM Coverage: Cloud-native controls exceed PCI DSS requirements.
NIST CSF 2.0 Mapping
CCM aligns to all 6 NIST CSF functions:
- Govern (GV): Organizational context and cybersecurity strategy
- Identify (ID): Asset management and risk assessment
- Protect (PR): Access control, awareness, data security
- Detect (DE): Continuous monitoring and detection
- Respond (RS): Incident response and communication
- Recover (RC): Recovery planning and improvements
CCM Coverage: All CSF categories and subcategories mapped.
Output
- Control Definition: CCM control objective and requirements
- Framework Mappings: Specific control mappings to:
- ISO 27001 Annex A controls
- SOC 2 Trust Services Criteria
- PCI DSS requirements
- NIST 800-53 controls
- HIPAA Security Rule standards
- GDPR articles
- Implementation Guidance: How to satisfy CCM and mapped controls
- Evidence Overlap: Artifacts satisfying multiple frameworks
- Gap Analysis: Where CCM exceeds other frameworks
- Multi-Framework Benefits: Efficiency gains from CCM implementation
Multi-Framework Compliance Benefits
Single Assessment, Multiple Certifications
- Implement CCM controls once
- Leverage evidence for ISO 27001, SOC 2, PCI DSS simultaneously
- Reduce audit fatigue and costs
- Streamline compliance programs
Cloud-First Advantage
CCM provides cloud-specific depth beyond traditional frameworks:
- Container security (Kubernetes, Docker)
- Serverless security
- Cloud-native IAM (SAML, OAuth, OIDC)
- Multi-cloud and hybrid architectures
- API security
- DevSecOps integration
Examples
# Map encryption control to all frameworks
/ccm:map-framework CEK-01 all
# Show MFA alignment with NIST
/ccm:map-framework IAM-06 NIST
# View incident response ISO 27001 mapping
/ccm:map-framework SEF-01 ISO27001
# Check GDPR alignment for privacy controls
/ccm:map-framework DSP-03 GDPR
# Map logging to PCI DSS requirements
/ccm:map-framework LOG-01 PCIDSS
# View SOC 2 mapping for backup controls
/ccm:map-framework BCR-07 SOC2
Reverse Mapping
Can also map from other frameworks to CCM:
- ISO 27001 A.8.24 → CEK-01, CEK-02, CEK-03, CEK-05, CEK-07
- PCI DSS 8.4.2 → IAM-06 (Multi-Factor Authentication)
- NIST 800-53 AU-2 → LOG-01 (Audit Logging)
- GDPR Article 33 → SEF-04, DSP-08 (Breach Notification)
- SOC 2 CC6.1 → IAM-01, IAM-05, CEK-01 (Access Controls)
This enables organizations already compliant with other frameworks to identify CCM control gaps efficiently.
Sponsors
Details
- Marketplace
- GRCEngClub/claude-grc-engineering
- Source
- plugins/frameworks/csa-ccm
- Category
- Community
More from GRCEngClub/claude-grc-engineering
All 70- cyber-essentials-plusv0.1.0
- datadog-inspectorv0.1.0
- dorav0.1.0
- drata-inspectorv0.1.0
- essential8v0.1.0
- eu-nis2v0.1.0
- fedramp-20xv0.1.0
- fedramp-rev5v0.1.0
- fedramp-sspv0.1.0
- gcp-docsv0.1.0
- gcp-inspectorv0.1.0
- gcp-secret-metadatav0.1.0
- gdprv0.1.0
- github-inspectorv0.1.0
- glbav0.1.0
- grc-auditorv0.1.0
- grc-diagramsv0.1.0
- grc-engineerv0.1.0
- grc-internalv0.1.0
- grc-loopv0.1.0
- grc-portfoliov0.1.0
- grc-reporterv0.1.0
- grc-tprmv0.1.0
- hitrustv0.1.0
