ISO 27001 Annex A controls and ISMS implementation guidance
- version
- 0.1.0
- GitHub stars
- 436
Install
/plugin install iso27001@grc-engineering-suiteRun it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.
Contents
Discovered from sourceSkills 1
ISO 27001 Expert
Deep expertise in ISO/IEC 27001 Information Security Management Systems.
Expertise Areas
ISMS Requirements (Clauses 4-10)
- Clause 4: Context of the Organization
- Clause 5: Leadership
- Clause 6: Planning
- Clause 7: Support
- Clause 8: Operation
- Clause 9: Performance Evaluation
- Clause 10: Improvement
Annex A Controls (ISO 27001:2022)
- A.5: Organizational Controls (37)
- A.6: People Controls (8)
- A.7: Physical Controls (14)
- A.8: Technological Controls (34)
Total: 93 controls (reduced from 114 in 2013 version)
New Controls in 2022
- Threat intelligence
- Cloud services security
- ICT readiness for business continuity
- Physical security monitoring
- Configuration management
- Information deletion
- Data masking
- Data leakage prevention
- Monitoring activities
- Web filtering
- Secure coding
Capabilities
- ISMS documentation templates
- Statement of Applicability guidance
- Risk assessment methodology
- Certification readiness assessment
- Internal audit support
- Continual improvement guidance
Commands 8
ISO 27001 Annex A Control Domain Deep Dive
Provides comprehensive analysis of ISO 27001:2022 Annex A control domains, including control objectives, implementation guidance, cloud-specific patterns, common pitfalls, and certification audit readiness.
Usage
/iso:annex-a-deep-dive <domain> [options]
Arguments
$1- Control domain: "A.5" (Organizational), "A.6" (People), "A.7" (Physical), "A.8" (Technological)$2- Options (optional):--environment=cloud|hybrid,--show-gaps,--certification-focus
Examples
# Deep dive on Organizational Controls (A.5)
/iso:annex-a-deep-dive A.5
# Deep dive on Technological Controls for cloud
/iso:annex-a-deep-dive A.8 --environment=cloud
# Show gaps only (controls not implemented)
/iso:annex-a-deep-dive A.8 --show-gaps
# Certification audit focus
/iso:annex-a-deep-dive A.6 --certification-focus
Output - A.8 Technological Controls
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ISO 27001:2022 ANNEX A DEEP DIVE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Domain: A.8 - Technological Controls
Total Controls: 34
Environment: Cloud (AWS)
Certification Focus: Stage 2 audit preparation
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
DOMAIN OVERVIEW
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Purpose:
Technological controls address the technical security measures needed to
protect information systems, networks, and data. This domain covers everything
from endpoint security and access management to cryptography and secure
development.
Key Themes:
- User endpoint devices and remote working
- Access control and authentication
- System configuration and hardening
- Cryptography and data protection
- Secure development lifecycle
- Network security
- Logging and monitoring
- Backup and resilience
Control Count: 34 controls (largest domain in Annex A)
Typical Implementation Time: 6-12 months (cloud environment)
Average Cost: $150,000-$300,000 (including tools and implementation)
Common Audit Findings:
- Insufficient logging and monitoring (A.8.15, A.8.16)
- Weak cryptography or key management (A.8.24)
- Inadequate patch management (A.8.8)
- Poor configuration management (A.8.9)
- Insufficient backup testing (A.8.13)
Maturity Levels:
Level 1 (Ad-hoc): Manual processes, inconsistent implementation
Level 2 (Defined): Documented procedures, some automation
Level 3 (Managed): Automated controls, regular testing
Level 4 (Optimized): Continuous monitoring, self-healing systems
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CRITICAL CONTROLS (Must Implement First)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
A.8.2 - Privileged Access Rights
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Control Objective:
To limit and control the allocation and use of privileged access rights.
Why Critical:
Privileged accounts (admin, root, database admin) are the #1 target for
attackers. Compromise of privileged credentials leads to complete system
compromise, data breaches, and massive damage.
ISO Requirements:
- Privileged access rights allocated based on business need
- Regular review of privileged access (more frequent than normal access)
- Privileged actions logged and monitored
- Separation of privileged accounts from normal user accounts
- Additional authentication for privileged access
Cloud Implementation (AWS):
IAM Best Practices:
✓ No direct AdministratorAccess policy assignments
✓ Use permission sets with least privilege
✓ Require MFA for all privileged access
✓ Use AWS IAM Identity Center with time-limited sessions
✓ Separate admin accounts from daily-use accounts
Privileged Access Management:
```terraform
# Example: Time-limited privileged access
resource "aws_iam_role" "admin" {
name = "EmergencyAdminAccess"
assume_role_policy = jsonencode({
Version = "2012-10-17"
Statement = [{
Effect = "Allow"
Principal = {
AWS = "arn:aws:iam::${var.account_id}:root"
}
Action = "sts:AssumeRole"
Condition = {
IpAddress = {
"aws:SourceIp" = var.corporate_ip_ranges
}
Bool = {
"aws:MultiFactorAuthPresent" = "true"
}
}
}]
})
max_session_duration = 3600 # 1 hour maximum
}
# Log all privileged actions
resource "aws_cloudtrail" "admin_actions" {
name = "admin-audit-trail"
s3_bucket_name = aws_s3_bucket.admin_logs.id
event_selector {
read_write_type = "All"
include_management_events = true
# Filter for privileged API calls
data_resource {
type = "AWS::IAM::Role"
values = ["arn:aws:iam::${var.account_id}:role/Admin*"]
}
}
}
```
Monitoring and Alerting:
- CloudWatch alarm for AssumeRole with Admin policies
- GuardDuty for privilege escalation attempts
- Access Analyzer for overly permissive policies
Review Process:
- Monthly review of all privileged access assignments
- Quarterly justification required (business need)
- Automatic revocation after 90 days if not used
- Manager + CISO approval for privileged access
Common Pitfalls:
❌ Giving developers AdministratorAccess "temporarily" (never removed)
❌ Shared admin accounts (cannot attribute actions)
❌ No MFA requirement for admin access
❌ Privileged access never reviewed (orphaned admin accounts)
❌ No logging of privileged actions
Evidence for Audit:
□ IAM policy documents showing least privilege
□ MFA enforcement configuration
□ Monthly privileged access review reports
□ CloudTrail logs of admin API calls
□ Privileged access request/approval tickets
□ Session duration limits configuration
Effort: 24 hours (initial setup) + 4 hours/month (reviews)
Cost: $0 (AWS native) + staff time
Priority: 🔴 CRITICAL
Cross-Reference: NIST AC-6, SOC2 CC6.2
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
A.8.5 - Secure Authentication
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Control Objective:
To ensure secure authentication technologies and procedures are implemented
based on information access restrictions and the topic of access control
policy.
Why Critical:
Weak authentication is the entry point for 80%+ of security breaches.
Modern threats (credential stuffing, phishing, MFA bypass) require robust
authentication mechanisms.
ISO Requirements:
- Strong authentication for all system access
- Multi-factor authentication for sensitive systems
- Secure password policies (if passwords used)
- Authentication secrets properly protected
- Biometric authentication where appropriate
Cloud Implementation (AWS):
Identity Provider Integration:
✓ Federated authentication (Okta, Azure AD)
✓ SAML 2.0 or OIDC protocol
✓ Single Sign-On (SSO) for all applications
✓ No direct IAM user passwords (federated only)
Multi-Factor Authentication:
```yaml
# Okta MFA Policy Example
mfa_policy:
name: "Company-Wide MFA Policy"
factors_required:
- type: "okta_verify_push" # Primary
- type: "google_otp" # Backup
- type: "sms" # Last resort (being phased out)
enforcement:
workforce_users: required
privileged_users: required
api_access: required (service accounts exempt with justification)
risk_based:
enabled: true
factors:
- unusual_location: require_mfa
- new_device: require_mfa
- after_hours: require_mfa_for_sensitive_apps
```
Password Policy (for emergency/service accounts):
- Minimum 15 characters (ISO recommends strong passwords)
- Complexity requirements (upper, lower, number, special)
- Password history: 24 previous passwords
- Maximum age: 90 days
- Account lockout: 5 failed attempts, 30-minute lockout
Passwordless Authentication:
- WebAuthn/FIDO2 security keys (YubiKey)
- Biometric authentication (Touch ID, Face ID)
- Certificate-based authentication (PIV/CAC)
Session Management:
- Session timeout: 15 minutes idle for standard, 5 minutes for privileged
- Re-authentication required for sensitive operations
- Concurrent session limits
- Device trust verification
Implementation Guide:
Phase 1: Foundation (Weeks 1-4)
□ Deploy identity provider (Okta or Azure AD)
□ Migrate all users to federated authentication
□ Disable direct IAM user passwords
□ Enforce MFA for all users (100% enrollment)
Phase 2: Enhanced Security (Weeks 5-8)
□ Implement risk-based authentication
□ Deploy hardware security keys for admins
□ Configure session timeout policies
□ Implement device trust
Phase 3: Monitoring (Weeks 9-12)
□ Set up authentication monitoring
□ Configure failed login alerts
□ Implement anomaly detection
□ Create authentication dashboard
Evidence for Audit:
□ Identity provider configuration (Okta/Azure AD)
□ MFA enrollment report (100% required)
□ Password policy screenshot
□ Session timeout configuration
□ Risk-based authentication rules
□ Authentication logs (successful + failed)
□ MFA bypass exceptions (documented and approved)
Common Pitfalls:
❌ MFA optional or only for some users
❌ SMS as only MFA method (vulnerable to SIM swapping)
❌ Weak password requirements (<14 characters)
❌ No session timeout (sessions never expire)
❌ Shared service accounts without MFA
Effort: 40 hours (initial) + 2 hours/month (maintenance)
Cost: $3-$5/user/month (Okta or Azure AD with MFA)
Priority: 🔴 CRITICAL
Cross-Reference: NIST IA-2, IA-5; SOC2 CC6.1
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
A.8.9 - Configuration Management
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Control Objective:
To establish and maintain configurations, including security configurations,
of hardware, software, services, and networks.
Why Critical:
Misconfiguration is the #1 cause of cloud security incidents. Default
configurations, configuration drift, and manual changes lead to vulnerabilities.
ISO Requirements:
- Documented baseline configurations
- Configuration changes controlled and approved
- Regular review of configurations
- Detection of unauthorized changes
- Configuration documentation maintained
Cloud Implementation (AWS):
Infrastructure as Code (IaC):
```terraform
# Example: Enforced configuration baseline
module "secure_vpc" {
source = "./modules/secure-vpc"
# Security baseline enforced via Terraform
enable_flow_logs = true
enable_vpc_endpoints = true
private_subnets_only = true
enable_network_firewall = true
# Compliance tags required
tags = {
Environment = "production"
Compliance = "ISO27001"
DataClass = "sensitive"
Owner = "platform-team"
}
}
# Security group baseline
resource "aws_security_group" "baseline" {
name = "secure-baseline-sg"
description = "ISO 27001 compliant security group"
# Deny all inbound by default (best practice)
# Explicitly allow only required ports
egress {
from_port = 443
to_port = 443
protocol = "tcp"
cidr_blocks = ["0.0.0.0/0"]
description = "HTTPS outbound only"
}
lifecycle {
# Prevent accidental deletion of security groups
prevent_destroy = true
}
}
```
Configuration Management Tools:
✓ Terraform for infrastructure
✓ AWS Config for compliance monitoring
✓ AWS Systems Manager State Manager for EC2 configuration
✓ Chef/Ansible for application configuration (if needed)
Baseline Configurations:
- CIS AWS Foundations Benchmark Level 1 (minimum)
- CIS Level 2 for sensitive workloads
- Custom security baseline documented
Change Management Process:
1. All changes via pull request (Infrastructure as Code)
2. terraform plan shows proposed changes
3. Security team review required
4. Automated testing in dev environment
5. Approved changes merged to main
6. Terraform Cloud applies changes
7. AWS Config validates compliance
Configuration Drift Detection:
```python
# Lambda function: detect-configuration-drift
def lambda_handler(event, context):
# Triggered by AWS Config compliance change
# Compare actual config vs. Terraform state
actual_config = get_actual_config(event['resourceId'])
desired_config = get_terraform_state(event['resourceId'])
if actual_config != desired_config:
# Configuration drift detected
send_alert(f"Drift detected: {event['resourceId']}")
# Auto-remediate or create ticket
if event['autoRemediate']:
apply_terraform() # Restore to desired state
else:
create_jira_ticket(drift_details)
return {
'statusCode': 200,
'body': 'Drift detection complete'
}
```
Automated Compliance Checks:
- AWS Config Rules (40+ compliance rules)
- Conformance Packs (ISO 27001 pack available)
- Daily compliance reports
- Non-compliance triggers alerts
Evidence for Audit:
□ Configuration Management Policy v1.0
□ Terraform configuration repository (GitHub)
□ CIS Benchmark compliance report
□ AWS Config compliance dashboard
□ Change history (Git commits + Terraform Cloud runs)
□ Drift detection alerts and remediation
□ Configuration review meeting notes (quarterly)
Common Pitfalls:
❌ Manual changes via console (bypassing IaC)
❌ No configuration baseline documented
❌ Configuration drift not detected
❌ Changes not reviewed before applying
❌ Default configurations used (not hardened)
Effort: 80 hours (initial baseline) + 10 hours/month (maintenance)
Cost: $200/month (AWS Config) + staff time
Priority: 🔴 CRITICAL
Cross-Reference: NIST CM-2, CM-3, CM-6; SOC2 CC8.1
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
A.8.15 - Logging
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Control Objective:
To record events, generate evidence, and log information.
Why Important:
Logging is essential for incident detection, forensics, compliance, and
demonstrating control effectiveness. Inadequate logging is a TOP 3 audit finding.
ISO Requirements:
- Event logs record user activities, exceptions, faults
- Logs include: user ID, date/time, event type, success/failure
- System administrator and operator activities logged
- Log files protected against tampering and unauthorized access
- Clocks synchronized (accurate timestamps)
Cloud Implementation (AWS):
Logging Architecture:
```
Application → CloudWatch Logs → S3 (long-term)
Infrastructure → CloudTrail → S3 + CloudWatch Logs
Network → VPC Flow Logs → S3
Security Events → GuardDuty → Security Hub → S3
Access Logs → ALB/CloudFront → S3
```
CloudTrail (Audit Logging):
```terraform
resource "aws_cloudtrail" "audit" {
name = "organization-audit-trail"
s3_bucket_name = aws_s3_bucket.audit_logs.id
include_global_service_events = true
is_multi_region_trail = true
enable_log_file_validation = true # Tamper protection
# Send to CloudWatch for real-time analysis
cloud_watch_logs_group_arn = aws_cloudwatch_log_group.cloudtrail.arn
cloud_watch_logs_role_arn = aws_iam_role.cloudtrail_cloudwatch.arn
event_selector {
read_write_type = "All"
include_management_events = true
# Log data events (S3, Lambda)
data_resource {
type = "AWS::S3::Object"
values = ["arn:aws:s3:::${var.audit_bucket_name}/*"]
}
}
# Protect against tampering
kms_key_id = aws_kms_key.cloudtrail.arn
tags = {
Purpose = "ISO27001-Audit-Logging"
}
}
# Immutable log storage
resource "aws_s3_bucket" "audit_logs" {
bucket = "audit-logs-${var.account_id}"
# Object Lock prevents deletion
object_lock_enabled = true
}
resource "aws_s3_bucket_object_lock_configuration" "audit_logs" {
bucket = aws_s3_bucket.audit_logs.id
rule {
default_retention {
mode = "GOVERNANCE"
days = 365 # 1 year retention (ISO minimum)
}
}
}
```
Log Retention Requirements:
- CloudTrail: 1 year online (S3), 7 years total (Glacier)
- Application logs: 90 days online, 1 year total
- Security logs: 1 year online (compliance requirement)
- VPC Flow Logs: 90 days
Clock Synchronization:
- NTP configured on all EC2 instances
- AWS Systems Manager enforces time sync
- Verified via compliance checks
Evidence for Audit:
□ Logging Policy v1.2
□ CloudTrail configuration (multi-region, log file validation)
□ Log retention configuration (S3 lifecycle policies)
□ S3 Object Lock configuration (tamper protection)
□ Sample logs demonstrating required fields
□ NTP configuration on EC2 instances
□ Log access controls (who can view logs)
Common Pitfalls:
❌ Logs not retained long enough (ISO requires 1 year minimum)
❌ Logs not protected (can be deleted/modified)
❌ Insufficient log detail (missing user ID, timestamps)
❌ Logs not monitored (collected but never reviewed)
❌ Clock skew (inaccurate timestamps)
Effort: 24 hours (initial setup) + 2 hours/month (review)
Cost: $100-$500/month (storage, depending on volume)
Priority: 🟠 HIGH
Cross-Reference: NIST AU-2, AU-3, AU-9, AU-11; SOC2 CC7.2
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
A.8.24 - Use of Cryptography
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Control Objective:
To ensure proper and effective use of cryptography to protect the
confidentiality, authenticity, and/or integrity of information.
Why Critical:
Cryptography is the last line of defense. If all other controls fail,
encryption prevents data exposure. Weak cryptography = no protection.
ISO Requirements:
- Cryptographic policy defining use of encryption
- Appropriate cryptographic algorithms and key lengths
- Key management throughout lifecycle
- Cryptography for data at rest and in transit
- Regular review of cryptographic implementations
Cloud Implementation (AWS):
Encryption at Rest:
```terraform
# S3 default encryption (AES-256)
resource "aws_s3_bucket_server_side_encryption_configuration" "default" {
bucket = aws_s3_bucket.data.id
rule {
apply_server_side_encryption_by_default {
sse_algorithm = "aws:kms"
kms_master_key_id = aws_kms_key.s3.arn
}
bucket_key_enabled = true # Reduces KMS API calls
}
}
# RDS encryption
resource "aws_db_instance" "app" {
identifier = "app-database"
engine = "postgres"
engine_version = "15.3"
storage_encrypted = true
kms_key_id = aws_kms_key.rds.arn
# Encrypted backups
backup_retention_period = 30
backup_encryption_enabled = true
}
# EBS volume encryption (enforced account-wide)
resource "aws_ebs_encryption_by_default" "enabled" {
enabled = true
}
```
Encryption in Transit:
- TLS 1.2 or 1.3 only (TLS 1.0/1.1 disabled)
- Strong cipher suites (ECDHE, AES-GCM)
- HSTS enabled (Strict-Transport-Security header)
- Certificate management via ACM (automated renewal)
Key Management (AWS KMS):
```terraform
resource "aws_kms_key" "data_encryption" {
description = "Data encryption key (ISO 27001)"
deletion_window_in_days = 30
enable_key_rotation = true # Annual automatic rotation
policy = jsonencode({
Version = "2012-10-17"
Statement = [
{
Sid = "Enable IAM User Permissions"
Effect = "Allow"
Principal = {
AWS = "arn:aws:iam::${var.account_id}:root"
}
Action = "kms:*"
Resource = "*"
},
{
Sid = "Allow services to use key"
Effect = "Allow"
Principal = {
Service = [
"s3.amazonaws.com",
"rds.amazonaws.com",
"lambda.amazonaws.com"
]
}
Action = [
"kms:Decrypt",
"kms:DescribeKey",
"kms:CreateGrant"
]
Resource = "*"
}
]
})
tags = {
Purpose = "ISO27001-Data-Encryption"
}
}
# Key rotation monitoring
resource "aws_cloudwatch_event_rule" "kms_rotation" {
name = "kms-key-rotation-check"
description = "Alert if KMS keys not rotated annually"
schedule_expression = "cron(0 9 1 * ? *)" # Monthly check
event_pattern = jsonencode({
source = ["aws.kms"]
detail-type = ["AWS API Call via CloudTrail"]
detail = {
eventName = ["DisableKeyRotation"]
}
})
}
```
Cryptographic Standards:
- Algorithms: AES-256, RSA-2048 or higher, ECDSA P-256+
- Hashing: SHA-256 or higher (no MD5, SHA-1)
- Key Derivation: PBKDF2, bcrypt, Argon2
- TLS: Version 1.2 or 1.3 only
Prohibited/Deprecated:
✗ DES, 3DES, RC4 (weak symmetric encryption)
✗ MD5, SHA-1 (weak hashing, collision attacks)
✗ RSA-1024 or lower (insufficient key length)
✗ TLS 1.0, TLS 1.1 (deprecated, vulnerabilities)
✗ Self-signed certificates in production
Evidence for Audit:
□ Cryptography Policy v1.5
□ KMS key configuration (customer-managed keys)
□ S3 encryption configuration (all buckets)
□ RDS encryption status (all instances)
□ TLS configuration (ALB listeners, CloudFront)
□ SSL Labs test results (A+ rating required)
□ Key rotation schedule and history
□ Certificate inventory (ACM)
Common Pitfalls:
❌ Using AWS-managed keys instead of customer-managed (less control)
❌ No key rotation (keys used indefinitely)
❌ Weak TLS cipher suites allowed
❌ Hardcoded encryption keys in code
❌ Data encrypted but keys not protected
Effort: 16 hours (policy + initial setup) + 2 hours/month (review)
Cost: $1/key/month (KMS) + storage overhead (negligible)
Priority: 🔴 CRITICAL
Cross-Reference: NIST SC-12, SC-13, SC-28; SOC2 CC6.7, CC6.8
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
IMPLEMENTATION ROADMAP
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Phase 1: Critical Controls (Months 1-3)
Priority: Must-have for certification
□ A.8.2 - Privileged access rights (4 weeks)
□ A.8.5 - Secure authentication (MFA) (6 weeks)
□ A.8.9 - Configuration management (IaC) (8 weeks)
□ A.8.15 - Logging (4 weeks)
□ A.8.24 - Cryptography (3 weeks)
Effort: 320 hours
Cost: $50,000 (tools + implementation)
Phase 2: High-Priority Controls (Months 4-6)
Priority: Expected for certification
□ A.8.1 - User endpoint devices (3 weeks)
□ A.8.3 - Information access restriction (3 weeks)
□ A.8.8 - Management of technical vulnerabilities (4 weeks)
□ A.8.13 - Information backup (2 weeks)
□ A.8.16 - Monitoring activities (6 weeks)
Effort: 240 hours
Cost: $35,000
Phase 3: Medium-Priority Controls (Months 7-9)
Priority: Nice-to-have, demonstrates maturity
□ A.8.10 - Information deletion (2 weeks)
□ A.8.11 - Data masking (3 weeks)
□ A.8.18 - Use of privileged utility programs (2 weeks)
□ A.8.23 - Web filtering (2 weeks)
□ A.8.28 - Secure coding (8 weeks)
Effort: 200 hours
Cost: $25,000
Phase 4: Optimization (Months 10-12)
Priority: Continuous improvement
□ Automation and self-healing
□ Advanced monitoring and SIEM
□ Security orchestration (SOAR)
□ Threat hunting capabilities
Effort: 160 hours
Cost: $40,000
Total Implementation:
Timeline: 12 months
Effort: 920 hours
Cost: $150,000
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CERTIFICATION AUDIT PREPARATION
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Pre-Audit Checklist (A.8 Technological Controls):
Documentation:
□ All policies approved and current (<12 months)
□ Procedures documented and accessible
□ Configuration baselines documented
□ Network diagrams current
□ Data flow diagrams current
Technical Evidence:
□ Configuration exports (Terraform, AWS Config)
□ Log samples demonstrating required fields
□ Encryption status reports (S3, RDS, EBS)
□ Access control configurations (IAM policies)
□ Monitoring dashboards (CloudWatch, GuardDuty)
Operational Evidence:
□ Quarterly access reviews completed
□ Vulnerability scan results (monthly)
□ Patch compliance reports
□ Backup test results (quarterly)
□ Incident response drill results
Common Audit Questions:
1. "Show me how you enforce MFA for all users"
→ Okta policy + enrollment report (100%)
2. "How do you detect configuration drift?"
→ AWS Config rules + drift detection alerts
3. "Demonstrate log retention of 1 year"
→ S3 lifecycle policy + oldest log files
4. "How do you manage privileged access?"
→ IAM policies + monthly review reports
5. "Show encryption is enabled for all data at rest"
→ S3/RDS/EBS encryption reports
Tips for Stage 2 Audit:
- Organize evidence by control number (A.8.1, A.8.2, etc.)
- Have screenshots ready (don't navigate live during audit)
- Practice explaining controls (elevator pitch)
- Know your compensating controls (if any gaps)
- Be honest about gaps (better than auditor finding them)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
COST SUMMARY (A.8 Technological Controls)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Technology Costs (Annual):
Identity & Access (Okta): $7,000 ($50/user/month × 142 users × 1 year / 12)
Endpoint Protection (CrowdStrike): $7,100 ($50/endpoint/month)
Configuration Management: $2,400 (AWS Config)
Logging & Monitoring: $6,000 (CloudWatch, Storage)
Encryption (KMS): $120 (10 keys × $1/month)
Backup & DR: $12,000 (cross-region replication)
Vulnerability Scanning: $2,400 (Inspector)
Total Technology: $37,020/year
Implementation Costs (One-Time):
Phase 1 (Critical): $50,000
Phase 2 (High): $35,000
Phase 3 (Medium): $25,000
Phase 4 (Optimize): $40,000
Total Implementation: $150,000
Ongoing Operational Costs (Annual):
Access reviews: $12,000 (10 hours/month × $100/hour)
Config management: $6,000 (5 hours/month)
Log review: $6,000 (5 hours/month)
Vulnerability remediation: $12,000 (10 hours/month)
Incident response: $6,000 (5 hours/month avg)
Total Operational: $42,000/year
Grand Total: $150,000 (one-time) + $79,020/year (ongoing)
Related Commands
/iso:soa-generator- Generate Statement of Applicability/iso:risk-treatment-plan- Create risk treatment plan/iso:certification-roadmap- Plan certification process/iso:isms-documentation-pack- Generate ISMS documents/grc-engineer:generate-implementation- Generate IaC for controls
ISO 27001 Assessment
Evaluates ISMS compliance against ISO 27001:2022 requirements.
Arguments
$1- Assessment scope (optional: isms, annexa, specific-control)$2- Control domain (optional, for Annex A assessment)
Assessment Areas
ISMS Clauses (4-10)
- Clause 4: Context of the Organization
- Clause 5: Leadership
- Clause 6: Planning
- Clause 7: Support
- Clause 8: Operation
- Clause 9: Performance Evaluation
- Clause 10: Improvement
Annex A Control Domains (2022)
- A.5: Organizational Controls (37 controls)
- A.6: People Controls (8 controls)
- A.7: Physical Controls (14 controls)
- A.8: Technological Controls (34 controls)
Output
- Compliance status by clause/control
- Gap analysis
- Statement of Applicability guidance
- Certification readiness assessment
Example
/iso:assess annexa A.8
ISO 27001 Certification Roadmap
Generates a comprehensive roadmap for achieving and maintaining ISO 27001:2022 certification, including gap remediation, ISMS documentation, Stage 1 and Stage 2 audits, and ongoing surveillance requirements.
Usage
/iso:certification-roadmap [target-date] [options]
Arguments
$1- Target certification date (optional): "2025-12-31" or "12-months" (default: "12-months")$2- Options (optional):--current-maturity=low|medium|high,--scope=cloud-only|hybrid,--fast-track
Examples
# Standard 12-month roadmap
/iso:certification-roadmap 12-months
# Aggressive 6-month fast-track
/iso:certification-roadmap 6-months --fast-track
# Specific target date with current state
/iso:certification-roadmap 2025-09-30 --current-maturity=medium
# Cloud-only scope (simpler)
/iso:certification-roadmap 12-months --scope=cloud-only
Output
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ISO 27001:2022 CERTIFICATION ROADMAP
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Organization: Your Company, Inc.
Start Date: February 2025
Target Certification: January 2026 (12 months)
Scope: Cloud infrastructure and SaaS application
Current Maturity: Medium (some controls implemented)
Certification Body: TBD (select by Month 3)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CERTIFICATION PROCESS OVERVIEW
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Timeline: 12 months total
- Months 1-3: Gap analysis and planning (Readiness)
- Months 4-9: Implementation and ISMS operation (Build & Operate)
- Month 10: Stage 1 audit (Document review)
- Month 11: Stage 2 audit (On-site assessment)
- Month 12: Certification issuance
- Ongoing: Annual surveillance audits
Total Estimated Cost: $95,000 - $145,000
- Internal effort: $55,000 - $85,000 (550-850 hours @ $100/hour)
- External costs: $40,000 - $60,000 (certification body, consultants)
Key Milestones:
✓ Month 3: Gap remediation complete, ISMS documented
✓ Month 6: 3 months of ISMS operation (minimum required)
✓ Month 9: 6 months operation, evidence collected
✓ Month 10: Stage 1 audit passed
✓ Month 11: Stage 2 audit passed
✓ Month 12: Certificate received
Success Factors:
- Executive management commitment and sponsorship
- Dedicated ISMS owner (30-50% time commitment)
- Cross-functional team involvement
- Budget approved ($95k-$145k)
- Realistic timeline (12+ months for first-time certification)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
MONTH 1-2: GAP ANALYSIS & PLANNING (Readiness Assessment)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Objectives:
- Understand current state vs. ISO 27001 requirements
- Identify gaps in controls, policies, and procedures
- Develop remediation plan with priorities
- Secure budget and resources
Week 1-2: Initial Assessment
□ Conduct ISO 27001 readiness assessment
Command: /iso:assess full --output=detailed
Output: Gap analysis report with 93 Annex A controls
□ Define ISMS scope
Questions to answer:
- What systems and processes are in scope?
- What data do we protect (customer data, IP, etc.)?
- What locations (cloud regions, offices)?
- What organizational boundaries?
Example Scope Statement:
"The ISMS covers all systems and processes used to provide the
[Product Name] SaaS application to customers, including AWS
infrastructure in us-east-1 and us-west-2 regions, application
development, and customer support operations. Excluded from scope:
marketing website (separate infrastructure), mobile app (separate
audit), corporate office IT (no customer data)."
□ Identify key stakeholders
- ISMS Owner: CISO (overall responsibility)
- Implementation Team: Security, IT, DevOps, Legal, HR
- Management Rep: CFO or COO (executive sponsor)
- Internal Auditor: Internal audit or external consultant
Week 3-4: Planning & Prioritization
□ Analyze gap assessment results
- Categorize gaps: Critical, High, Medium, Low
- Estimate effort and cost per gap
- Identify dependencies
□ Create implementation roadmap
Command: Generate remediation plan from gaps
Output: Prioritized list of controls to implement
□ Define success criteria
- 100% of applicable Annex A controls implemented
- All mandatory ISMS documentation complete
- 3+ months of evidence collection
- Zero critical findings in Stage 1 audit
□ Select certification body (start RFP process)
Top Certification Bodies:
- BSI Group (British Standards Institution)
- NQA (National Quality Assurance)
- LRQA (Lloyd's Register Quality Assurance)
- DQS Inc
- SGS
Selection Criteria:
- Accreditation (ANAB, UKAS, etc.)
- Experience with cloud/SaaS companies
- Geographic coverage
- Cost ($25k-$40k for initial certification)
- Timeline (can they meet your target date?)
RFP Questions:
- What is your audit process and timeline?
- How many audit days required? (Typically 3-5 days Stage 2)
- Do you charge for travel/expenses?
- What is included in surveillance audits?
- References from similar clients?
Deliverables:
✓ Gap analysis report (detailed findings)
✓ ISMS scope statement (approved by management)
✓ Implementation roadmap (12-month plan)
✓ Budget approval ($95k-$145k)
✓ Certification body RFP (responses due Month 3)
Effort: 120 hours (2-3 people full-time for 1 month)
Cost: $12,000 internal + $5,000 external (optional consultant)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
MONTH 3-4: POLICY DEVELOPMENT & DOCUMENTATION
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Objectives:
- Create all mandatory ISMS documentation
- Develop policies and procedures
- Obtain management approval
Required ISMS Documentation (Clause 7.5):
1. ISMS Scope Statement
Status: ✓ Completed in Month 1
Owner: CISO
Approval: Executive management
2. Information Security Policy (Clause 5.2)
Content:
- Management commitment to ISMS
- Information security objectives
- Roles and responsibilities
- Approach to risk management
- Commitment to continual improvement
Template: Use /iso:isms-documentation-pack to generate
Approval Required: CEO or Board of Directors
Review Frequency: Annually
3. Risk Assessment Methodology (Clause 6.1.2)
Content:
- Risk identification process
- Risk analysis method (qualitative/quantitative)
- Risk evaluation criteria (5x5 matrix)
- Risk acceptance criteria
Tool: ISO 27005 risk assessment framework
Output: Risk assessment methodology document
4. Statement of Applicability (SOA) (Clause 6.1.3d)
Command: /iso:soa-generator full --include-evidence
Content:
- All 93 Annex A controls
- Applicability decision (applicable vs. not applicable)
- Justification for each decision
- Implementation status
- Control owners
Approval: CISO + Management
5. Risk Treatment Plan (Clause 6.1.3e, 6.2)
Command: /iso:risk-treatment-plan all --include-costs
Content:
- All identified risks
- Treatment option (mitigate, accept, transfer, avoid)
- Planned controls
- Responsibility and timeline
- Residual risk acceptance
Approval: CISO + CEO (for risk acceptance)
6. Risk Assessment Report (Clause 8.2)
Content:
- Assets identified
- Threats and vulnerabilities
- Inherent risk scores
- Existing controls
- Residual risk scores
- Decisions (accept or treat)
Frequency: Annually (initial + annual reviews)
Supporting Policies and Procedures (40-50 documents typical):
Access Control:
□ Access Control Policy
□ Password Policy
□ Privileged Access Management Procedure
□ User Provisioning/Deprovisioning Procedure
□ Access Review Procedure
Asset Management:
□ Asset Management Policy
□ Asset Inventory Procedure
□ Acceptable Use Policy
Cryptography:
□ Cryptography Policy
□ Key Management Procedure
Operations Security:
□ Change Management Policy
□ Backup and Recovery Procedure
□ Capacity Management Procedure
□ Malware Protection Procedure
Communications Security:
□ Network Security Policy
□ Remote Access Policy
System Acquisition, Development, Maintenance:
□ Secure Development Policy
□ Testing Procedure
Supplier Relationships:
□ Vendor Risk Management Policy
□ Vendor Security Assessment Procedure
Incident Management:
□ Incident Response Policy
□ Incident Response Procedure/Runbook
Business Continuity:
□ Business Continuity Policy
□ Disaster Recovery Plan
□ Crisis Communication Plan
Compliance:
□ Compliance Monitoring Procedure
□ Internal Audit Procedure
Policy Development Tips:
- Use templates (save time, ensure completeness)
- Tailor to your organization (don't copy-paste)
- Keep policies high-level, procedures detailed
- Version control all documents
- Require management approval for policies
- Set review frequency (annually minimum)
Deliverables:
✓ All mandatory ISMS documents (6 core documents)
✓ 40-50 supporting policies and procedures
✓ Management approval for all policies
✓ Document control system (version control, approval workflow)
Effort: 200 hours (CISO 50%, Security team 50%, Legal review)
Cost: $20,000 internal + $8,000 external (legal review, templates)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
MONTH 5-6: CONTROL IMPLEMENTATION (Build Phase)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Objectives:
- Implement missing controls (highest priority first)
- Configure technical controls
- Train personnel
- Begin evidence collection
Priority 1: Critical Controls (Must implement first)
□ Access Control (A.5.15, A.5.16, A.5.17, A.8.2, A.8.3, A.8.5)
- MFA for all users (100% enrollment)
- Privileged access management
- Quarterly access reviews
Effort: 60 hours
Cost: $10,000 (Okta licenses, implementation)
□ Cryptography (A.8.24)
- Encrypt all data at rest (S3, RDS, EBS)
- TLS 1.2+ for all data in transit
- KMS key management
Effort: 24 hours
Cost: $2,000 (KMS, implementation)
□ Logging and Monitoring (A.8.15, A.8.16)
- CloudTrail multi-region enabled
- 1-year log retention
- GuardDuty threat detection
Effort: 32 hours
Cost: $6,000/year (storage, GuardDuty)
□ Configuration Management (A.8.9)
- Infrastructure as Code (Terraform)
- AWS Config compliance monitoring
- Change management process
Effort: 80 hours
Cost: $8,000 (Config, implementation)
□ Backup and Recovery (A.8.13)
- Automated backups (RDS, S3 versioning)
- Cross-region replication
- Quarterly recovery testing
Effort: 40 hours
Cost: $12,000/year (DR infrastructure)
Priority 2: High-Priority Controls
□ Vulnerability Management (A.8.8)
- Weekly vulnerability scans (Amazon Inspector)
- 30-day patching SLA
- Automated patch management
Effort: 40 hours
Cost: $3,000/year
□ Incident Management (A.5.24, A.5.25, A.5.26)
- Incident response procedure
- PagerDuty alerting
- Quarterly incident response drills
Effort: 32 hours
Cost: $3,000/year (PagerDuty)
□ Endpoint Security (A.8.1)
- MDM (Jamf Pro)
- Endpoint protection (CrowdStrike)
- Full disk encryption (100%)
Effort: 24 hours
Cost: $8,000/year
Training and Awareness:
□ Security awareness training (A.6.3)
- All employees complete training
- Quarterly refresher training
- Phishing simulation testing
Platform: KnowBe4 or similar
Cost: $12,000/year
□ Role-specific training
- Developers: Secure coding training
- IT/DevOps: Incident response training
- Managers: ISMS awareness
Deliverables:
✓ All Priority 1 controls implemented and operating
✓ All Priority 2 controls implemented
✓ Staff training completion (100%)
✓ Evidence collection process established
Effort: 350 hours (multiple teams in parallel)
Cost: $35,000 internal + $64,000/year (tools and services)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
MONTH 7-9: ISMS OPERATION & EVIDENCE COLLECTION
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Objectives:
- Operate ISMS for minimum 3 months (ISO requirement)
- Collect evidence of control effectiveness
- Conduct internal audit
- Perform management review
ISO Requirement:
The ISMS must be operating for a minimum period before certification.
Most certification bodies require 3-6 months of operation, with
evidence demonstrating controls are working effectively over time.
Month 7-9 Activities:
Ongoing Operations:
□ Quarterly access review (complete by end of Month 7)
- Review all user access
- Remove unnecessary access
- Document review results
Evidence: Access review report, approval sign-off
□ Monthly vulnerability scans
- Run scans 1st of each month
- Remediate critical/high findings within 30 days
- Document exceptions and risk acceptance
Evidence: Scan reports (Months 7, 8, 9)
□ Security awareness training ongoing
- Track completion rates (target: 100%)
- Run monthly phishing simulations
- Document results and remedial training
Evidence: Training completion reports, phishing results
□ Incident management
- Log all security incidents (even minor)
- Conduct post-incident reviews
- Update incident response procedure as needed
Evidence: Incident log, post-incident review reports
□ Change management
- Document all infrastructure changes
- Obtain approvals before changes
- Test changes in dev/staging first
Evidence: Change tickets, approval records, Terraform logs
□ Continuous monitoring
- GuardDuty findings reviewed daily
- CloudWatch alarms configured and tested
- Security Hub compliance dashboard
Evidence: Monitoring dashboards, alert response logs
Internal Audit (Month 8 - Critical for Stage 1):
ISO requires at least one internal audit before certification.
Scope: All ISMS processes and controls
Method: ISO 19011 audit methodology
Auditor: Independent (external consultant or trained internal)
Audit Process:
Week 1: Audit planning
- Develop audit checklist (93 Annex A controls)
- Schedule interviews
- Request evidence from control owners
Week 2-3: Audit execution
- Interview control owners
- Review evidence
- Test control effectiveness (sample testing)
- Identify findings (non-conformities, observations)
Week 4: Audit reporting
- Audit report with findings
- Present to management
- Create corrective action plan
- Set remediation deadlines
Expected Findings:
- 0-5 minor non-conformities (acceptable)
- 0 major non-conformities (must be fixed before certification)
Deliverable: Internal audit report with findings and corrective actions
Management Review (Month 9 - Mandatory):
ISO requires management to review the ISMS at planned intervals.
Agenda:
1. Status of actions from previous management reviews
2. Changes in external/internal issues relevant to ISMS
3. Feedback on information security performance:
- Non-conformities and corrective actions
- Monitoring and measurement results
- Audit results (internal and external)
- Fulfillment of information security objectives
4. Feedback from interested parties
5. Results of risk assessment and status of risk treatment plan
6. Opportunities for continual improvement
Attendees:
- CEO (or designated management representative)
- CISO (ISMS owner)
- IT/Security leadership
- Legal/Compliance
- Internal auditor
Output:
- Management review meeting minutes
- Decisions on continual improvement
- Decisions on resource needs
- Approval to proceed with certification audit
Deliverable: Management review minutes (signed by CEO)
Evidence Collection Checklist:
□ Policies and procedures (all current, approved)
□ Risk assessment and treatment plan (current)
□ Statement of Applicability (current)
□ Access reviews (at least 1 completed)
□ Vulnerability scans (at least 3 months)
□ Security training records (100% completion)
□ Incident log (all incidents, even if zero)
□ Change records (sample of approved changes)
□ Internal audit report (with corrective actions)
□ Management review minutes
□ System configuration exports (CloudTrail, AWS Config)
□ Log samples (demonstrating 1-year retention)
Deliverables:
✓ 3+ months of ISMS operation
✓ Evidence collected for all applicable controls
✓ Internal audit completed (findings remediated)
✓ Management review completed
✓ Corrective actions from internal audit closed
Effort: 120 hours (ongoing operations + internal audit)
Cost: $12,000 internal + $10,000 (external internal auditor)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
MONTH 10: STAGE 1 AUDIT (Documentation Review)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Purpose:
Stage 1 audit is a document review to verify that ISMS documentation is
complete and meets ISO 27001 requirements. No on-site inspection of
controls; focus is on readiness for Stage 2.
Duration: 1-2 days (remote or on-site)
Participants: CISO, ISMS team, control owners
Auditor Will Review:
✓ ISMS Scope Statement
✓ Information Security Policy
✓ Risk Assessment Methodology and Report
✓ Risk Treatment Plan
✓ Statement of Applicability
✓ Mandatory procedures (incident management, internal audit, management review)
✓ Supporting policies and procedures (40-50 documents)
✓ Internal audit report
✓ Management review minutes
Auditor Will Check:
- Is documentation complete? (all required documents present)
- Is documentation current? (approved within last 12 months)
- Is documentation consistent? (no contradictions)
- Is ISMS operating? (evidence of at least 3 months operation)
- Is organization ready for Stage 2? (controls implemented)
Common Stage 1 Findings:
⚠ Policy not approved by management (missing signatures)
⚠ Risk assessment incomplete (not all assets identified)
⚠ SOA missing justifications (why controls not applicable)
⚠ Internal audit not completed
⚠ Management review not conducted
⚠ Insufficient evidence of ISMS operation (<3 months)
Preparation Checklist:
□ All documents uploaded to secure file share
□ Documents organized by ISO clause (easy navigation)
□ Version control evident (version numbers, dates)
□ Approvals documented (signatures or email approvals)
□ Evidence index created (control → evidence mapping)
□ Presentation prepared (ISMS overview for auditor)
Stage 1 Outcome:
✓ PASS: Minor findings, cleared for Stage 2 (typical)
⚠ CONDITIONAL PASS: Findings must be addressed before Stage 2
✗ FAIL: Major gaps, not ready for Stage 2 (rare if well-prepared)
Post-Stage 1 Actions:
1. Review auditor findings
2. Address all findings (2-4 weeks)
3. Provide evidence of corrective actions
4. Schedule Stage 2 audit (1-2 months after Stage 1)
Deliverable: Stage 1 audit report (from certification body)
Effort: 40 hours (preparation + audit participation)
Cost: Included in certification body fee ($25k-$40k total)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
MONTH 11: STAGE 2 AUDIT (On-Site Assessment)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Purpose:
Stage 2 audit is a comprehensive on-site assessment to verify that controls
are implemented and operating effectively. Auditor will interview staff,
observe processes, and test controls.
Duration: 3-5 days (depends on organization size and complexity)
Location: On-site or remote (many done remotely post-COVID)
Team Size: 1-2 lead auditors + technical experts (if needed)
Audit Methodology:
- Interviews with control owners (planned in advance)
- Process observation (watch controls in action)
- Document review (policies, procedures, evidence)
- Technical testing (sample testing of controls)
- System inspection (view configurations, logs, access controls)
Day-by-Day Schedule (Example):
Day 1 - Opening Meeting & Management Systems
- 9:00 AM: Opening meeting (audit plan, logistics)
- 10:00 AM: Management interview (CISO, CEO)
- 11:00 AM: ISMS documentation review (scope, policies)
- 1:00 PM: Risk management (risk assessment, treatment plan)
- 3:00 PM: Internal audit and management review
- 5:00 PM: Day 1 wrap-up
Day 2 - Organizational & People Controls
- 9:00 AM: Information security roles (HR, Security team)
- 10:30 AM: Security awareness training
- 1:00 PM: Screening and termination procedures
- 3:00 PM: Supplier management
- 5:00 PM: Day 2 wrap-up
Day 3 - Technological Controls (Part 1)
- 9:00 AM: Access control (IAM, MFA)
- 11:00 AM: Cryptography (encryption at rest/transit)
- 1:00 PM: Configuration management (IaC, AWS Config)
- 3:00 PM: Logging and monitoring
- 5:00 PM: Day 3 wrap-up
Day 4 - Technological Controls (Part 2)
- 9:00 AM: Vulnerability management (patching, scanning)
- 11:00 AM: Backup and recovery (DR testing)
- 1:00 PM: Incident management (process, drills)
- 3:00 PM: Change management (approval process)
- 5:00 PM: Day 4 wrap-up
Day 5 - Final Testing & Closing Meeting
- 9:00 AM: Sample testing (access requests, changes, incidents)
- 11:00 AM: Technical inspection (AWS console, CloudTrail)
- 1:00 PM: Auditor deliberation (findings discussion)
- 3:00 PM: Closing meeting (present findings)
Sample Testing Examples:
- Select 10 access requests → verify approval before access granted
- Select 5 terminations → verify access removed within 24 hours
- Select 10 changes → verify change approval and testing
- Review 3 incidents → verify followed incident response procedure
- Inspect CloudTrail logs → verify 1-year retention
- Check encryption status → verify all S3 buckets encrypted
Interview Questions (Examples):
"How do you ensure that access is approved before being granted?"
"What is the process for responding to a security incident?"
"How often do you review user access rights?"
"How do you ensure backups can be restored?"
"What happens if a vulnerability is discovered?"
Findings Types:
- Major Non-Conformity: Serious gap, control not implemented
→ Must be fixed before certification issued
- Minor Non-Conformity: Control implemented but evidence of occasional lapse
→ Must be fixed within defined timeframe (typically 90 days)
- Observation: Opportunity for improvement, not a failure
→ Optional to address
Typical Findings (Even in Well-Prepared Organizations):
⚠ Minor: One quarterly access review missed due to scheduling
⚠ Minor: Backup restoration not tested in Q4 (only tested Q1-Q3)
⚠ Observation: Consider implementing SIEM for enhanced monitoring
Stage 2 Outcome:
✓ RECOMMENDED FOR CERTIFICATION: Zero major findings, minors acceptable
⚠ CONDITIONAL: Major finding(s) must be remediated
✗ NOT RECOMMENDED: Multiple major findings (rare)
Post-Stage 2 Actions:
1. Review Stage 2 audit report
2. Address all findings (typically 30-90 days)
3. Provide evidence of corrective actions to auditor
4. Auditor reviews corrective actions
5. Certification decision made
Deliverable: Stage 2 audit report with recommendation
Effort: 100 hours (preparation + audit participation + corrective actions)
Cost: Included in certification body fee
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
MONTH 12: CERTIFICATION ISSUANCE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Actions:
□ Close all findings from Stage 2 audit
□ Submit evidence of corrective actions
□ Auditor verifies corrective actions (desk review)
□ Certification body makes certification decision
□ Certificate issued!
Certificate Details:
- Valid for: 3 years
- Scope: [Your ISMS scope statement]
- Standards: ISO/IEC 27001:2022
- Certification body accreditation mark
Certificate Usage:
✓ Display on website
✓ Include in sales proposals
✓ Reference in contracts
✓ Marketing materials
✓ Customer questionnaires (RFPs)
Announcement:
- Press release (optional)
- LinkedIn announcement
- Customer notification
- Internal celebration!
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ONGOING: SURVEILLANCE AUDITS (Years 2-3)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ISO 27001 certification requires annual surveillance audits to maintain
certification for the 3-year certificate validity period.
Schedule:
- Year 1: Certification audit (Stage 1 + Stage 2)
- Year 2: Surveillance audit (1-2 days)
- Year 3: Surveillance audit (1-2 days)
- Year 4: Recertification audit (full audit, similar to initial)
Surveillance Audit Scope:
- Review of management system changes
- Sample testing of controls (not all controls)
- Review of internal audit and management review
- Investigation of complaints or incidents
- Verification of previous findings corrected
Typical Duration: 1-2 days (less than Stage 2)
Cost: $8,000 - $15,000 per year
Annual ISMS Activities:
□ Quarterly access reviews (4 per year)
□ Monthly vulnerability scans (12 per year)
□ Quarterly management reviews (4 per year)
□ Annual internal audit (1 per year)
□ Annual risk assessment review
□ Annual policy review (all policies)
□ Security awareness training (all employees)
□ Incident response drills (at least 1 per year)
□ DR testing (at least 1 per year)
Ongoing Effort: 200-300 hours/year
Ongoing Cost: $20,000 - $30,000/year (internal) + $8,000-$15,000 (surveillance)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
TOTAL COST SUMMARY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Year 1 (Certification):
Internal Effort:
Gap analysis & planning: $12,000 (120 hours)
Policy development: $20,000 (200 hours)
Control implementation: $35,000 (350 hours)
ISMS operation & evidence: $12,000 (120 hours)
Internal audit: $10,000 (external auditor)
Stage 1 & 2 preparation: $14,000 (140 hours)
Corrective actions: $8,000 (80 hours)
──────────────────────────────────────────────
Total Internal: $111,000
External Costs:
Certification body fee: $32,000 (BSI, average)
Consultant (optional): $8,000 (policy review, gap analysis)
──────────────────────────────────────────────
Total External: $40,000
Technology Costs (Annual):
Okta (MFA, SSO): $7,000
Endpoint protection: $7,100
AWS Config: $2,400
Logging & monitoring: $6,000
Encryption (KMS): $120
Backup & DR: $12,000
Vulnerability scanning: $2,400
Security training: $12,000
Other tools: $5,000
──────────────────────────────────────────────
Total Technology: $54,020
Year 1 Total: $205,020
Year 2-3 (Maintenance):
Internal Effort: $25,000/year (250 hours)
Surveillance Audit: $12,000/year
Technology Costs: $54,020/year
──────────────────────────────────────────────
Annual Total: $91,020/year
3-Year Total Cost of Ownership: $387,060
ROI Justification:
- Customer requirements (enables $2M+ in contracts)
- Competitive differentiation
- Reduced security risk
- Operational efficiency (mature processes)
- Compliance with regulations (GDPR, etc.)
Related Commands
/iso:assess- Initial gap analysis/iso:soa-generator- Generate Statement of Applicability/iso:risk-treatment-plan- Create risk treatment plan/iso:annex-a-deep-dive- Deep dive on controls/iso:isms-documentation-pack- Generate ISMS documents/grc-engineer:generate-implementation- Generate IaC for controls
ISO 27001 Evidence Checklist
Generates an evidence collection checklist for ISO/IEC 27001:2022 Annex A controls, tailored to the organization's ISMS scope and Statement of Applicability (SoA).
Never commit evidence artifacts to source control. The outputs below include real usernames, credential reports, MFA device states, and privileged-account inventories. For GDPR workflows, raw exports may carry personal data subject to Art. 5 minimization and storage-limitation rules. Keep only what you need and delete on a retention schedule.
.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
/iso27001:evidence-checklist <control-id|domain> [--export <markdown|json|csv>]
Arguments
<control-id|domain>: A 2022 Annex A control ID (for example,A.5.15orA.8.24) or category name or ID:Organizational/A.5,People/A.6,Physical/A.7,Technological/A.8.--export:markdown,json, orcsv; defaultmarkdown.
Checklist generation
- Resolve the requested control against the ISO/IEC 27001:2022 Annex A catalog, not the 2013 catalog: A.5 contains 37 controls, A.6 contains 8, A.7 contains 14, and A.8 contains 34. For a category, enumerate its controls and generate evidence items for each; do not silently omit controls. Reject an unknown ID or category and ask for a valid selection instead of inventing a mapping. Consult the user's licensed standard and SoA when the catalog or applicability is uncertain.
- Ask for the ISMS boundary, assessment period, SoA and relevant systems if not provided; mark unknowns explicitly. Distinguish controls excluded in the SoA and request their documented rationale rather than asserting they are applicable.
- For each applicable control propose specific documentation, operational records and where feasible technical configuration or test results. Tag every item with its 2022 control ID, suggested owner, collection frequency, and what the reviewer should verify. Treat frequencies as suggestions, not universal ISO mandates. Mark missing or unverified evidence as outstanding; do not claim certification or effectiveness based on a checklist alone.
- Explain that control intent is paraphrased; consult the licensed ISO standard for normative requirements. Avoid reproducing ISO text or inventing SCF crosswalks. Restrict collection to authorized users and minimize personal data and secrets.
Export formats
Return the checklist in the requested format, not a description of the format. Markdown uses checkboxes and the same fields as the examples below. JSON is an array of objects; CSV has a header and one row per item. Both use control_id, item, owner, frequency, verification, and status fields. Default status to outstanding unless the user supplies verified evidence. Excluded controls should have a separate rationale item marked excluded rather than implying implementation.
For spreadsheet-oriented CSV, treat every data cell as untrusted text, including generated and user-supplied values. Before CSV encoding, prefix every data-cell value with a literal ASCII apostrophe ('), even if it begins with whitespace, a tab, a carriage return, a newline, =, +, -, or @. Do not trim away the prefix. Then encode each field as CSV: quote fields containing commas, double quotes, CR or LF, and double any embedded double quotes. Quoting alone does not prevent formula execution. For example, the data value =1+1 becomes '=1+1; the data value =1+1, "check" becomes "'=1+1, ""check""" in the CSV. The fixed header need not be prefixed.
This prefix changes the raw CSV values and spreadsheet behavior varies: import all columns explicitly as text, verify the target spreadsheet treats the apostrophe-prefixed cells as literal text, and do not enable formula evaluation for untrusted data. Saving and reopening in a spreadsheet may remove protective characters; reapply protection before any subsequent export. If the target importer cannot guarantee literal-text handling, do not open the CSV there; use JSON for faithful machine-readable values instead.
Example 1 — Organizational: A.5.15
/iso27001:evidence-checklist A.5.15
Output:
ISO 27001:2022 Evidence Checklist
Control: A.5.15 (Organizational)
Scope: Example ISMS; confirm boundary and assessment period
Intent (paraphrased): Establish an approach to controlling access that reflects business and security needs.
- [ ] **Access-control policy** — A.5.15
- Owner: Security governance; suggested frequency: annual and after material change
- Verify: approved policy defines access principles, ownership and scope.
- Status: outstanding
- [ ] **Access requirements and role matrix** — A.5.15
- Owner: Application owners; suggested frequency: annual and after role changes
- Verify: business and security requirements are documented and mapped to roles for in-scope systems.
- Status: outstanding
- [ ] **Policy review and exception records** — A.5.15
- Owner: Risk owner; suggested frequency: quarterly
- Verify: sampled exceptions have approval, a rationale and an expiry or review date.
- Status: outstanding
Example 2 — Technological: A.8.24
/iso27001:evidence-checklist A.8.24
Output:
ISO 27001:2022 Evidence Checklist
Control: A.8.24 (Technological)
Scope: Example ISMS; confirm boundary and assessment period
Intent (paraphrased): Apply cryptography and manage keys in a manner suited to the information and risks.
- [ ] **Cryptography and key-management guidance** — A.8.24
- Owner: Security architecture; suggested frequency: annual and after material change
- Verify: approved guidance covers algorithm selection and key lifecycle responsibilities.
- Status: outstanding
- [ ] **Encryption configuration inventory** — A.8.24
- Owner: Platform team; suggested frequency: quarterly
- Verify: sampled systems align with the approved protection requirements for data at rest and in transit.
- Status: outstanding
- [ ] **Key lifecycle and access review records** — A.8.24
- Owner: Key custodian; suggested frequency: quarterly
- Verify: sampled keys have accountable owners, access restrictions and evidence of lifecycle review; do not export secret key material.
- Status: outstanding
A configuration export is a point-in-time observation, not proof that a control operated throughout the assessment period. Supplement it with approved records, interviews and appropriately scoped tests.
ISO 27001 Gap Analysis
Identifies gaps between current state and ISO 27001 requirements.
Arguments
$1- Current controls document (required)$2- Target (optional: certification, maintenance)
Analysis Scope
- ISMS documentation requirements
- Mandatory clauses compliance
- Annex A control implementation
- Risk assessment methodology
- Performance measurement
Output
- Gap summary by domain
- Prioritized remediation roadmap
- Resource estimates
- Quick wins identification
- Long-term initiatives
Example
/iso:gap-analysis ./current-controls.xlsx certification
ISO 27001 ISMS Documentation Pack Generator
Generates the complete set of ISO 27001:2022 Information Security Management System (ISMS) documentation, including all mandatory documents required by the standard and comprehensive supporting policies and procedures.
Usage
/iso:isms-documentation-pack [package-type] [options]
Arguments
$1- Package type (optional): "mandatory-only", "full", "policies-only" (default: "full")$2- Options (optional):--format=docx|markdown|pdf,--organization=name,--scope="cloud infrastructure"
Examples
# Generate full ISMS documentation pack
/iso:isms-documentation-pack full
# Mandatory documents only (6 core documents)
/iso:isms-documentation-pack mandatory-only
# Export as Word documents
/iso:isms-documentation-pack full --format=docx
# Customize for organization
/iso:isms-documentation-pack full --organization="Acme Corp" --scope="AWS cloud platform"
Output
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ISO 27001:2022 ISMS DOCUMENTATION PACK
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Organization: Your Company, Inc.
Generation Date: 2025-01-28
ISO Version: ISO/IEC 27001:2022
Package Type: Full (mandatory + supporting)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
PACKAGE CONTENTS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Mandatory Documents (6): Required by ISO 27001 standard
Supporting Policies (15): Core security policies
Supporting Procedures (25): Operational procedures
Total Documents: 46
Output Directory: ./isms-documentation/
Format: Markdown (convertible to Word/PDF)
Customization: Templates with [PLACEHOLDERS] to fill in
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
PART 1: MANDATORY ISMS DOCUMENTS (ISO Required)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
These 6 documents are explicitly required by ISO 27001:2022.
1. ISMS Scope Statement (Clause 4.3)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
File: 01-ISMS-Scope-Statement.md
Purpose: Define the boundaries and applicability of the ISMS
Required By: Clause 4.3 - Determining the scope of the ISMS
Content:
```markdown
# ISO 27001:2022 ISMS Scope Statement
Organization: [Your Company, Inc.]
Version: 1.0
Date: [2025-01-28]
Approved By: [CEO Name], Chief Executive Officer
## 1. Scope Definition
The Information Security Management System (ISMS) of [Your Company] covers:
### 1.1 Organizational Boundaries
- [Your Company, Inc.] (legal entity)
- Locations:
- Corporate Headquarters: [123 Main St, City, State, ZIP]
- AWS Cloud Infrastructure: us-east-1, us-west-2 regions
- Remote workforce (142 employees across [states/countries])
### 1.2 Systems and Processes In Scope
Information Systems:
- Production infrastructure (AWS)
- Application servers (ECS, EC2)
- Databases (RDS PostgreSQL)
- Object storage (S3)
- Networking (VPC, CloudFront, Route 53)
- Identity and access management (Okta, AWS IAM)
- Development infrastructure (GitHub, CI/CD)
- Monitoring and logging (CloudWatch, GuardDuty)
- Business applications (Jira, Slack, Office 365)
Business Processes:
- Software development (SDLC)
- Cloud infrastructure operations
- Customer onboarding and support
- Incident response
- Change management
- Vendor management
Data Types:
- Customer data (PII, business data)
- Application source code
- System configuration data
- Security logs and monitoring data
### 1.3 Out of Scope (Exclusions)
The following are explicitly excluded from the ISMS scope:
- Marketing website (hosted separately by [vendor name])
- Mobile application infrastructure (separate ISMS/audit)
- Corporate office IT infrastructure (no customer data processing)
- [Company] subsidiary operations (separate legal entity)
Justification for Exclusions:
- Marketing website: Separate infrastructure, no customer data, managed by external vendor
- Mobile app: Covered under separate security assessment
- Office IT: No processing of customer data, no sensitive systems
### 1.4 Services Provided to Customers
Within the scope of this ISMS:
- [Product Name] SaaS Application
- Cloud-based data processing and storage
- Application programming interfaces (APIs)
- 24/7 customer support (email, chat)
### 1.5 Geographic Coverage
- Primary data centers: AWS us-east-1 (Virginia), us-west-2 (Oregon)
- Service availability: Global (all countries except [embargoed countries])
- Data residency: United States only
### 1.6 Interested Parties
Internal:
- Employees (142 FTE)
- Contractors (5-10 on average)
- Board of Directors
- Shareholders
External:
- Customers (10,000+ active users)
- Regulatory authorities (FTC, state data protection authorities)
- Cloud service providers (AWS, Okta, GitHub)
- Certification body ([BSI, NQA, etc.])
## 2. External and Internal Issues
External Issues:
- Increasing cyber threats (ransomware, data breaches)
- Regulatory requirements (GDPR, CCPA, state privacy laws)
- Customer security expectations (ISO 27001, SOC 2)
- Cloud provider security (shared responsibility model)
Internal Issues:
- Remote workforce security (BYOD, home networks)
- Rapid growth (scaling security controls)
- Limited security staffing (3 FTE security team)
- Cloud-native architecture (traditional controls don't apply)
## 3. Information Security Requirements
Legal/Regulatory:
- GDPR (EU customers)
- CCPA (California customers)
- GLBA (if applicable)
- Contract obligations (customer DPAs)
Business:
- Protect customer data confidentiality, integrity, availability
- Maintain service availability (99.9% SLA)
- Respond to security incidents within defined timeframes
- Demonstrate compliance to customers
## 4. Scope Review
Review Frequency: Annually or upon significant changes
Next Review: [Date 1 year from approval]
Review Triggers:
- New services or products launched
- Significant infrastructure changes
- Regulatory changes
- Major organizational changes (M&A, restructuring)
## Approval
This ISMS scope statement has been reviewed and approved by:
Name: [CEO Name]
Title: Chief Executive Officer
Date: [Approval Date]
Signature: _________________________
Name: [CISO Name]
Title: Chief Information Security Officer
Date: [Approval Date]
Signature: _________________________
Customization Notes:
- Fill in [PLACEHOLDERS] with your organization details
- Adjust services, systems, and data types to match your environment
- Ensure exclusions are justified
- Update interested parties list
- Information Security Policy (Clause 5.2) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
File: 02-Information-Security-Policy.md Purpose: Top-level security policy demonstrating management commitment Required By: Clause 5.2 - Policy
Content:
# Information Security Policy
Organization: [Your Company, Inc.]
Version: 2.1
Effective Date: [2025-01-01]
Review Date: [2026-01-01]
Owner: CISO
Approved By: CEO
## 1. Purpose
This Information Security Policy establishes the framework for protecting
information assets of [Your Company] and demonstrates management's commitment
to information security.
## 2. Scope
This policy applies to:
- All employees, contractors, and third parties with access to [Company] systems
- All information systems within the ISMS scope
- All customer data and company confidential information
## 3. Management Commitment
[Your Company]'s executive management is committed to:
- Protecting the confidentiality, integrity, and availability of information
- Meeting customer, legal, and regulatory requirements
- Continual improvement of the ISMS
- Providing adequate resources for information security
- Holding individuals accountable for security responsibilities
## 4. Information Security Objectives
Our information security objectives are to:
a) Protect customer data from unauthorized access, disclosure, or loss
b) Maintain service availability of 99.9% or higher
c) Detect and respond to security incidents within 1 hour (critical)
d) Comply with all applicable laws and regulations (GDPR, CCPA, etc.)
e) Achieve and maintain ISO 27001 certification
f) Conduct annual security risk assessments
g) Train 100% of employees on security awareness annually
## 5. Information Security Framework
### 5.1 Information Security Management System (ISMS)
[Company] has established an ISMS based on ISO 27001:2022 to:
- Systematically manage information security risks
- Implement appropriate security controls
- Monitor and improve security performance
### 5.2 Roles and Responsibilities
Executive Management:
- Overall accountability for ISMS
- Approve security policies and significant security decisions
- Provide resources for ISMS implementation and maintenance
CISO (Chief Information Security Officer):
- Lead the ISMS program
- Manage security risk
- Report security performance to executive management
- Coordinate security incident response
All Employees:
- Follow security policies and procedures
- Protect information assets
- Report security incidents and concerns
- Complete mandatory security training
### 5.3 Risk Management
[Company] manages information security risks by:
- Conducting annual risk assessments (ISO 27005)
- Implementing controls to reduce risks to acceptable levels
- Monitoring control effectiveness
- Accepting residual risks with management approval
Risk Appetite: MEDIUM
- Critical risks: Must be mitigated (not accepted)
- High risks: Must be mitigated or transferred (insurance)
- Medium risks: May be accepted with CISO approval
- Low risks: May be accepted
## 6. Security Controls
[Company] implements security controls across:
- Access control (least privilege, MFA)
- Cryptography (encryption at rest and in transit)
- Physical security (inherited from cloud providers)
- Operations security (change management, patching)
- Communications security (network segmentation, firewalls)
- System development (secure coding, testing)
- Supplier relationships (vendor risk assessments)
- Incident management (detection, response, recovery)
- Business continuity (DR, backups)
Detailed controls are documented in the Statement of Applicability.
## 7. Compliance
[Company] is committed to compliance with:
- ISO 27001:2022 requirements
- Legal and regulatory requirements (GDPR, CCPA, etc.)
- Contractual obligations (customer DPAs, SLAs)
- Industry best practices (OWASP, CIS, NIST)
## 8. Continual Improvement
[Company] continually improves the ISMS through:
- Quarterly management reviews
- Annual internal audits
- Annual external audits (surveillance or recertification)
- Lessons learned from incidents
- Security metrics and trending
## 9. Non-Compliance
Violations of this policy may result in:
- Verbal or written warning
- Suspension of access to systems
- Termination of employment or contract
- Legal action (if criminal activity)
## 10. Policy Review
This policy is reviewed annually and updated as needed to reflect:
- Changes in business requirements
- Changes in the threat landscape
- Lessons learned from incidents
- Audit findings or regulatory changes
## 11. Related Documents
- ISMS Scope Statement
- Risk Assessment Methodology
- Statement of Applicability
- All supporting security policies and procedures
## Approval
This policy has been reviewed and approved by:
Name: [CEO Name]
Title: Chief Executive Officer
Date: [Approval Date]
Signature: _________________________
- Risk Assessment Methodology (Clause 6.1.2) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
File: 03-Risk-Assessment-Methodology.md Purpose: Document how information security risks are assessed Required By: Clause 6.1.2c - Risk assessment process
[Content template included - defines risk identification, analysis, evaluation methods, risk matrix 5x5, risk acceptance criteria, assessment frequency]
- Statement of Applicability (Clause 6.1.3d) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
File: 04-Statement-of-Applicability.md Purpose: Document all Annex A control decisions Required By: Clause 6.1.3d Note: Generate using /iso:soa-generator for complete, customized SOA
- Risk Treatment Plan (Clause 6.1.3e, 6.2) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
File: 05-Risk-Treatment-Plan.md Purpose: Document how identified risks will be treated Required By: Clause 6.1.3e, Clause 6.2 Note: Generate using /iso:risk-treatment-plan for comprehensive plan
- Risk Assessment Report (Clause 8.2) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
File: 06-Risk-Assessment-Report.md Purpose: Document results of risk assessment Required By: Clause 8.2 Note: Generated annually as output of risk assessment process
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ PART 2: SUPPORTING POLICIES (15 policies) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- Access Control Policy (Supports A.5.15-5.18, A.8.2-8.6)
- Acceptable Use Policy (Supports A.5.10)
- Asset Management Policy (Supports A.5.9, A.5.11)
- Cryptography Policy (Supports A.8.24)
- Change Management Policy (Supports A.8.32)
- Data Classification Policy (Supports A.5.12)
- Incident Response Policy (Supports A.5.24-5.27)
- Business Continuity Policy (Supports A.5.29-5.30)
- Network Security Policy (Supports A.8.20-8.23)
- Physical Security Policy (Supports A.7.1-7.14, if applicable)
- Remote Access Policy (Supports A.6.7)
- Secure Development Policy (Supports A.8.25-8.31)
- Vendor Risk Management Policy (Supports A.5.19-5.23)
- Password Policy (Supports A.8.5)
- Data Retention and Disposal Policy (Supports A.8.10)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ PART 3: SUPPORTING PROCEDURES (25 procedures) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- User Provisioning Procedure
- User Deprovisioning Procedure
- Access Review Procedure
- Privileged Access Management Procedure
- Backup and Recovery Procedure
- Disaster Recovery Procedure
- Incident Response Procedure/Runbook
- Vulnerability Management Procedure
- Patch Management Procedure
- Configuration Management Procedure
- Change Management Procedure
- Vendor Security Assessment Procedure
- Internal Audit Procedure
- Management Review Procedure
- Security Awareness Training Procedure
- Secure Code Review Procedure
- Security Testing Procedure
- Log Management Procedure
- Monitoring and Alerting Procedure
- Cryptographic Key Management Procedure
- Data Masking Procedure
- Capacity Management Procedure
- Media Handling Procedure
- Equipment Disposal Procedure
- Business Continuity Testing Procedure
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ DOCUMENT MANAGEMENT ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
All documents include: ✓ Document ID and version number ✓ Effective date and review date ✓ Document owner ✓ Approval signature block ✓ Revision history table
Document Control System:
- Version control: Git repository
- Approval workflow: Pull request + management sign-off
- Distribution: Confluence/SharePoint (all employees)
- Review frequency: Annually (or upon significant changes)
File Naming Convention: [ID]-[Document-Name]-v[Version].md Example: 01-ISMS-Scope-Statement-v1.0.md
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ CUSTOMIZATION GUIDE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Step 1: Global Find and Replace Search: [Your Company] Replace: Acme Corporation
Search: [CISO Name] Replace: Jane Doe
Search: [CEO Name] Replace: John Smith
Step 2: Update Organization-Specific Details
- ISMS scope (systems, locations, services)
- Organizational structure (roles, reporting)
- Risk appetite and tolerance levels
- Specific technologies and tools used
- Compliance requirements (industry-specific)
Step 3: Technical Implementation Details
- Cloud providers (AWS, Azure, GCP)
- Identity provider (Okta, Azure AD)
- Monitoring tools (CloudWatch, Datadog, Splunk)
- Endpoint protection (CrowdStrike, Carbon Black)
- Backup solutions and retention periods
Step 4: Review and Approval
- Legal review (data protection, contracts)
- Technical review (architecture, controls)
- Management review (objectives, resources)
- Approval signatures
Step 5: Distribution and Training
- Publish to document management system
- Notify all employees
- Conduct training on key policies
- Track acknowledgment
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ COMPLETION CHECKLIST ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Mandatory Documents: □ ISMS Scope Statement (customized and approved) □ Information Security Policy (customized and approved) □ Risk Assessment Methodology (customized) □ Statement of Applicability (generated via /iso:soa-generator) □ Risk Treatment Plan (generated via /iso:risk-treatment-plan) □ Risk Assessment Report (conducted and documented)
Supporting Policies (Minimum Required): □ Access Control Policy □ Acceptable Use Policy □ Incident Response Policy □ Business Continuity Policy □ Vendor Risk Management Policy
Supporting Procedures (Minimum Required): □ Internal Audit Procedure □ Management Review Procedure □ Incident Response Procedure □ Change Management Procedure □ Access Review Procedure
Document Management: □ Version control system established □ Approval workflow defined □ Distribution mechanism in place □ Annual review schedule set □ Document ownership assigned
Audit Readiness: □ All documents current (<12 months old) □ All documents approved (signatures/emails) □ No contradictions between documents □ Evidence of document distribution □ Employees trained on applicable policies
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ NEXT STEPS ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- Customize all templates with your organization details
- Review with legal, technical, and management stakeholders
- Obtain management approval (signatures)
- Publish to document management system
- Conduct training for employees
- Begin ISMS operation (collect evidence)
- Schedule internal audit (after 3+ months operation)
- Schedule Stage 1 audit with certification body
## Additional Documentation Templates
The full package includes detailed templates for all 46 documents. Access via:
```bash
# Generate individual policy template
/iso:isms-documentation-pack policies-only --policy="Access Control Policy"
# Generate all procedures
/iso:isms-documentation-pack procedures-only
# Export to Word format for easy editing
/iso:isms-documentation-pack full --format=docx
Related Commands
/iso:soa-generator- Generate Statement of Applicability/iso:risk-treatment-plan- Create risk treatment plan/iso:annex-a-deep-dive- Control implementation guidance/iso:certification-roadmap- Certification process timeline/iso:assess- Gap analysis
ISO 27001 Risk Treatment Plan Generator
Generates a comprehensive Risk Treatment Plan for identified information security risks, including risk assessment results, treatment options, implementation timelines, ownership assignments, and residual risk acceptance criteria.
Usage
/iso:risk-treatment-plan [risk-level] [options]
Arguments
$1- Risk level filter (optional): "critical", "high", "medium", "low", or "all" (default: "all")$2- Options (optional):--format=docx|xlsx|markdown,--include-costs,--show-residual-only
Examples
# Generate full risk treatment plan
/iso:risk-treatment-plan all
# High and critical risks only
/iso:risk-treatment-plan high
# Export as Excel with cost estimates
/iso:risk-treatment-plan all --format=xlsx --include-costs
# Show residual risks requiring acceptance
/iso:risk-treatment-plan all --show-residual-only
Output
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ISO 27001:2022 RISK TREATMENT PLAN
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Organization: Your Company, Inc.
ISMS Scope: Cloud infrastructure and SaaS application
Risk Assessment Date: 2024-12-15
Plan Version: 2.1
Approved By: CISO, CEO
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
EXECUTIVE SUMMARY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Total Risks Identified: 47
🔴 Critical: 2 risks (4%)
🟠 High: 8 risks (17%)
🟡 Medium: 22 risks (47%)
🟢 Low: 15 risks (32%)
Treatment Strategy Distribution:
✓ Mitigate: 35 risks (75%)
⚠ Accept: 8 risks (17%)
→ Transfer: 3 risks (6%)
○ Avoid: 1 risk (2%)
Implementation Status:
✓ Completed: 28 risks (80% of mitigation)
⏳ In Progress: 5 risks (14%)
⏸ Planned: 2 risks (6%)
Total Treatment Cost: $127,000 (initial) + $48,000/year (ongoing)
Risk Reduction: 78% (inherent risk → residual risk)
Residual Risk Level: MEDIUM (acceptable per risk appetite)
Management Approval Required: 8 risks (accepted residual risk)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
RISK TREATMENT METHODOLOGY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Risk Assessment Methodology: ISO 27005:2022
Risk Matrix: 5x5 (Likelihood × Impact)
Risk Appetite: MEDIUM (willing to accept medium residual risks)
Risk Tolerance: No critical or high residual risks accepted
Treatment Options:
1. MITIGATE: Implement controls to reduce likelihood or impact
2. ACCEPT: Accept risk if within tolerance (management approval required)
3. TRANSFER: Transfer risk via insurance, outsourcing, or contracts
4. AVOID: Eliminate risk by discontinuing risky activity
Review Frequency:
- Risk Treatment Plan: Quarterly
- Risk Assessment: Annually or upon significant changes
- Residual Risk Acceptance: Annually
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CRITICAL RISKS (Immediate Action Required)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
RISK-001: Insufficient Disaster Recovery Capabilities
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Inherent Risk Level: 🔴 CRITICAL (Likelihood: 3, Impact: 5) = Risk Score 15
Threat:
Natural disaster, cyber attack, or infrastructure failure affecting AWS
us-east-1 region could cause extended service outage.
Vulnerability:
- Single-region deployment (no cross-region failover)
- Recovery Time Objective (RTO): 8 hours (target: 4 hours)
- Recovery Point Objective (RPO): 4 hours (target: 1 hour)
- No automated failover mechanism
Impact if Realized:
- Extended service outage (>8 hours)
- Customer data loss (up to 4 hours)
- Revenue loss: $50,000/day
- Reputation damage
- SLA breach penalties
- Regulatory reporting requirements (if >72 hours)
Assets Affected:
- Production RDS databases
- Application servers (EC2, ECS)
- Customer-facing web application
- 10,000+ active customers
Treatment Option: ✓ MITIGATE
Planned Controls:
1. Multi-Region Architecture (Primary: us-east-1, DR: us-west-2)
- RDS cross-region read replicas (real-time replication)
- S3 cross-region replication
- Route 53 health checks and automatic failover
- Infrastructure as Code (Terraform) for DR region
2. Automated Disaster Recovery Procedures
- Automated failover scripts (tested quarterly)
- DR runbook documentation
- Quarterly DR testing (full failover test)
3. Enhanced Backup Strategy
- Continuous backup to DR region
- 30-day backup retention
- Automated backup validation
Implementation Timeline:
Phase 1 (Weeks 1-4): DR region infrastructure deployment
Phase 2 (Weeks 5-8): Data replication setup and testing
Phase 3 (Weeks 9-12): Automated failover implementation
Phase 4 (Week 13): First DR test
Target Completion: March 31, 2025
Responsibility:
Owner: VP Engineering
Implementer: DevOps Team
Reviewer: CISO
Budget:
Initial: $35,000 (DR infrastructure setup, testing)
Ongoing: $12,000/year (DR region running costs)
Expected Residual Risk:
Level: 🟡 MEDIUM (Likelihood: 2, Impact: 3) = Risk Score 6
Justification: Multi-region architecture reduces likelihood and limits impact
Acceptance: Residual risk within tolerance (no further action required)
Evidence:
- DR architecture diagram (to be created)
- Terraform DR configuration (to be created)
- DR test results (quarterly, starting Q2 2025)
- RTO/RPO metrics (monitored post-implementation)
Related ISO 27001 Controls:
- A.5.29: Information security during disruption
- A.5.30: ICT readiness for business continuity
- A.8.13: Information backup
- A.8.14: Redundancy of information processing facilities
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
RISK-002: Inadequate Vendor Risk Management
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Inherent Risk Level: 🔴 CRITICAL (Likelihood: 4, Impact: 4) = Risk Score 16
Threat:
Third-party vendor security breach leads to compromise of customer data
or service disruption. Recent supply chain attacks (SolarWinds, MOVEit)
demonstrate this threat is actively exploited.
Vulnerability:
- 47 third-party vendors with access to systems/data
- Only 12/47 vendors have completed security assessments (26%)
- No continuous monitoring of vendor security posture
- No vendor incident response integration
- Vendor offboarding process incomplete (orphaned access)
Impact if Realized:
- Customer data breach via vendor compromise
- Regulatory fines (GDPR: up to 4% of revenue)
- Customer notification requirements
- Reputational damage
- Loss of customer trust
Assets Affected:
- Customer data (PII, payment information)
- Internal systems accessed by vendors
- Shared infrastructure (Okta, AWS, GitHub)
Treatment Option: ✓ MITIGATE
Planned Controls:
1. Vendor Risk Assessment Program
- Risk assessment for all vendors (prioritize by data access)
- Annual reassessment (high-risk vendors: quarterly)
- Security questionnaire (SOC 2, ISO 27001, insurance)
- Risk scoring (critical/high/medium/low)
2. Vendor Contract Requirements
- Data protection clauses (GDPR Article 28 compliant)
- Right to audit clause
- Breach notification requirements (24 hours)
- Cyber insurance requirements ($5M minimum for high-risk vendors)
3. Continuous Vendor Monitoring
- SecurityScorecard or BitSight ratings (automated)
- Breach monitoring (have vendors been compromised?)
- SOC 2 report review (annually)
4. Vendor Access Management
- Least privilege access (minimum necessary)
- Quarterly vendor access reviews
- Automated offboarding when contract ends
Implementation Timeline:
Phase 1 (Weeks 1-2): Vendor inventory and categorization
Phase 2 (Weeks 3-6): Risk assessments (prioritize high-risk first)
Phase 3 (Weeks 7-10): Contract reviews and amendments
Phase 4 (Weeks 11-12): Continuous monitoring setup
Target Completion: April 30, 2025
Responsibility:
Owner: CISO
Implementers: Security Team, Legal, Procurement
Reviewer: Risk Committee
Budget:
Initial: $18,000 (SecurityScorecard subscription, assessments)
Ongoing: $15,000/year (monitoring platform, annual reassessments)
Expected Residual Risk:
Level: 🟡 MEDIUM (Likelihood: 2, Impact: 3) = Risk Score 6
Justification: Vendor assessments and monitoring reduce likelihood;
contracts limit impact via insurance and liability
Acceptance: Residual risk within tolerance
Evidence:
- Vendor Risk Management Policy v1.0 (to be created)
- Vendor risk assessment reports (47 vendors)
- Vendor contracts with security clauses (all new/renewed contracts)
- SecurityScorecard dashboards
- Quarterly vendor access review results
Related ISO 27001 Controls:
- A.5.19: Information security in supplier relationships
- A.5.20: Addressing information security within supplier agreements
- A.5.21: Managing information security in the ICT supply chain
- A.5.22: Monitoring, review and change management of supplier services
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
HIGH RISKS (Priority Action Required)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
RISK-008: Insufficient Security Awareness Training
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Inherent Risk Level: 🟠 HIGH (Likelihood: 4, Impact: 3) = Risk Score 12
Threat:
Employees fall victim to phishing attacks, leading to credential compromise,
malware infection, or unauthorized data access.
Vulnerability:
- Annual security training only (not frequent enough)
- No phishing simulation testing
- Training completion: 98% (2 employees overdue)
- Training is generic (not role-specific)
Impact if Realized:
- Credential compromise leading to unauthorized access
- Malware infection (ransomware, data exfiltration)
- Business email compromise (BEC) financial fraud
- Customer data breach
Assets Affected:
- Employee credentials (142 users)
- Email system (Office 365)
- Internal systems (AWS, GitHub, Jira)
Treatment Option: ✓ MITIGATE
Planned Controls:
1. Enhanced Security Awareness Program
- Quarterly security training (instead of annual)
- Role-based training (developers, IT, general staff)
- Microlearning modules (5-10 minutes monthly)
2. Phishing Simulation Testing
- Monthly simulated phishing campaigns
- Immediate training for users who click
- Tracking and metrics (click rate, reporting rate)
- Target: <5% click rate, >50% reporting rate
3. Security Champions Program
- Designate security champions in each team
- Monthly security updates and discussions
- Incident response training
Implementation Timeline:
Immediate: Q1 2025
Ongoing: Monthly phishing tests, quarterly training
Responsibility:
Owner: CISO
Implementer: Security Team
Training Provider: KnowBe4 or similar
Budget:
Initial: $8,000 (platform setup, initial content)
Ongoing: $12,000/year ($7/user/month for 142 users)
Expected Residual Risk:
Level: 🟢 LOW (Likelihood: 2, Impact: 2) = Risk Score 4
Justification: Training reduces likelihood; other controls (MFA, email
filtering) limit impact
Acceptance: Residual risk acceptable
Evidence:
- Security Awareness Training Policy v1.1
- Training completion reports (quarterly)
- Phishing simulation results (monthly)
- Click rate trends (target: improving)
Related ISO 27001 Controls:
- A.6.3: Information security awareness, education, and training
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
MEDIUM RISKS (Managed Risk)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
RISK-014: Inadequate Patch Management
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Inherent Risk Level: 🟡 MEDIUM (Likelihood: 3, Impact: 3) = Risk Score 9
Threat:
Unpatched systems exploited by attackers using known vulnerabilities.
Vulnerability:
- Patch deployment average: 45 days (target: 30 days)
- No automated patching for production systems
- Testing before patching causes delays
Treatment Option: ✓ MITIGATE
Planned Controls:
1. Automated Patch Management
- AWS Systems Manager Patch Manager
- Automated testing in dev environment
- Automated deployment to staging (7 days after release)
- Automated deployment to production (14 days after release)
- Emergency patch process (critical CVEs within 7 days)
2. Vulnerability Scanning
- Weekly vulnerability scans (Amazon Inspector)
- Prioritization based on CVSS score and exploitability
Implementation Timeline: Q1 2025 (12 weeks)
Responsibility:
Owner: VP Engineering
Implementer: DevOps Team
Budget:
Initial: $5,000 (SSM setup, testing automation)
Ongoing: $2,000/year (Inspector costs)
Expected Residual Risk:
Level: 🟢 LOW (Likelihood: 1, Impact: 3) = Risk Score 3
Evidence:
- Patch Management Policy v1.3
- SSM Patch Manager configuration
- Weekly vulnerability scan results
- Patch compliance reports (target: >95%)
Related ISO 27001 Controls:
- A.8.8: Management of technical vulnerabilities
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
RISKS ACCEPTED (Management Approval Required)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
RISK-023: Limited Threat Intelligence Capabilities
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Inherent Risk Level: 🟡 MEDIUM (Likelihood: 3, Impact: 2) = Risk Score 6
Threat:
Inability to proactively identify emerging threats relevant to our industry
and technology stack.
Vulnerability:
- No formal threat intelligence platform
- Limited industry threat sharing
- Reactive security posture
Treatment Option: ⚠ ACCEPT (for now)
Justification for Acceptance:
- Cost of threat intelligence platform ($15,000/year) outweighs immediate
benefit given current threat landscape
- Compensating controls provide adequate protection:
* AWS GuardDuty for anomaly detection
* Regular review of CISA alerts
* GitHub security advisories for dependencies
- Risk level (MEDIUM) is within risk tolerance
- Will revisit decision if threat landscape changes or organization grows
Residual Risk: 🟡 MEDIUM (Likelihood: 3, Impact: 2) = Risk Score 6
Compensating Controls:
✓ AWS GuardDuty enabled (threat detection)
✓ Monthly CISA alert review
✓ GitHub Dependabot (dependency vulnerabilities)
✓ Security news monitoring (manual)
Review Date: Q3 2025 (or upon significant threat landscape change)
Approved By:
Name: John Doe, CISO
Date: 2025-01-15
Signature: _________________________
Name: Sarah Johnson, CEO
Date: 2025-01-15
Signature: _________________________
Evidence:
- Risk acceptance form (signed)
- Cost-benefit analysis
- Compensating controls verification
Related ISO 27001 Controls:
- A.5.7: Threat intelligence
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
RISKS TRANSFERRED (Insurance/Contracts)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
RISK-029: Third-Party Data Breach
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Inherent Risk Level: 🟠 HIGH (Likelihood: 3, Impact: 4) = Risk Score 12
Threat:
Critical vendor (Okta, AWS, GitHub) suffers data breach affecting our data.
Treatment Option: → TRANSFER (via insurance and contracts)
Transfer Mechanisms:
1. Cyber Insurance Policy
- Coverage: $5M per incident, $10M aggregate
- Deductible: $100,000
- Covers: Data breach response, notification, legal fees, fines
- Premium: $25,000/year
- Carrier: Marsh (A-rated)
2. Vendor Contracts
- Indemnification clauses in vendor agreements
- Vendor cyber insurance requirements ($5M minimum)
- Liability caps negotiated
3. Mitigation Controls (to reduce insurance premium):
- Multi-factor authentication
- Encryption at rest and in transit
- Regular security assessments
- Incident response plan
Residual Risk: 🟡 MEDIUM (Likelihood: 2, Impact: 2) = Risk Score 4
(Financial impact transferred; operational impact remains)
Cost:
Cyber Insurance: $25,000/year
Legal review of vendor contracts: $10,000 (one-time)
Evidence:
- Cyber insurance policy document
- Vendor contracts with indemnification clauses
- Insurance coverage certificate
Approved By: CFO + CISO
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
RISK TREATMENT IMPLEMENTATION ROADMAP
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Q1 2025 (Jan-Mar):
🔴 RISK-001: Multi-region DR architecture
🔴 RISK-002: Vendor risk assessment program
🟠 RISK-008: Enhanced security training + phishing tests
🟡 RISK-014: Automated patch management
Q2 2025 (Apr-Jun):
🟠 RISK-011: Implement SIEM (Splunk Cloud)
🟡 RISK-018: Enhanced logging and monitoring
🟡 RISK-022: Improved change management
Q3 2025 (Jul-Sep):
🟡 RISK-024: Network segmentation improvements
🟡 RISK-027: Enhanced backup verification
⚠ Review accepted risks (quarterly review)
Q4 2025 (Oct-Dec):
🟡 RISK-033: Improved incident response capabilities
📊 Annual risk assessment
📊 Risk treatment plan review
Ongoing:
- Quarterly risk review meetings
- Monthly risk dashboard updates
- Continuous monitoring of control effectiveness
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
METRICS AND MONITORING
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Risk Treatment KPIs:
- Mitigation on schedule: 80% (target: >90%)
- Average risk score reduction: 78%
- Critical/High residual risks: 0 (target: 0)
- Budget variance: +8% over plan (acceptable)
Risk Metrics Dashboard:
- Total risk exposure (inherent vs residual)
- Risks by treatment option (pie chart)
- Implementation progress (Gantt chart)
- Risk score trend (30-day rolling)
Monthly Risk Committee Report:
- New risks identified
- Treatment progress updates
- Budget/timeline variances
- Residual risk changes
- Upcoming risk reviews
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
APPROVAL SIGNATURES
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Risk Treatment Plan Approved:
CISO:
Name: John Doe
Date: 2025-01-28
Signature: _________________________
CEO:
Name: Sarah Johnson
Date: 2025-01-28
Signature: _________________________
CFO (Budget Approval):
Name: Michael Chen
Date: 2025-01-28
Signature: _________________________
Risk Committee Chair:
Name: David Williams
Date: 2025-01-28
Signature: _________________________
Next Review: April 2025 (Quarterly)
Related Commands
/iso:assess- Conduct risk assessment to identify risks/iso:soa-generator- Generate Statement of Applicability/iso:annex-a-deep-dive- Deep dive on controls/iso:certification-roadmap- Plan certification process/grc-engineer:generate-implementation- Generate IaC for mitigations
ISO 27001 Statement of Applicability Generator
Generates a comprehensive Statement of Applicability (SOA) for ISO 27001 Annex A controls, including applicability decisions, implementation status, justifications, and evidence references required for certification audit.
Usage
/iso:soa-generator [scope] [options]
Arguments
$1- Scope (optional): "cloud-only", "hybrid", "on-premise", or "full" (default: "full")$2- Options (optional):--format=docx|xlsx|markdown,--include-evidence,--show-gaps-only
Examples
# Generate full SOA for all 93 Annex A controls
/iso:soa-generator full
# Cloud-only SOA (excludes physical controls)
/iso:soa-generator cloud-only
# Export as Excel spreadsheet
/iso:soa-generator full --format=xlsx
# Show only gaps (controls not implemented)
/iso:soa-generator full --show-gaps-only
# Include evidence references
/iso:soa-generator full --include-evidence
Output
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ISO 27001:2022 STATEMENT OF APPLICABILITY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Organization: Your Company, Inc.
ISMS Scope: Cloud infrastructure and SaaS application platform
Date: 2025-01-28
Version: 1.0
Prepared By: Information Security Team
Approved By: CISO
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
EXECUTIVE SUMMARY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Total Annex A Controls: 93
Applicable: 78 (84%)
Not Applicable: 15 (16%)
Implementation Status:
✓ Implemented: 62 (79% of applicable)
⚠ Partially Implemented: 11 (14% of applicable)
✗ Not Implemented: 5 (6% of applicable)
○ Not Applicable: 15 (16% of total)
Certification Readiness: 79% (Target: 100% before Stage 2 audit)
Risk Summary:
- 5 controls not implemented represent MEDIUM risk
- 11 partially implemented controls under remediation
- Target completion date: Q2 2025
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
A.5 ORGANIZATIONAL CONTROLS (37 controls)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
A.5.1 - Policies for information security
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Status: ✓ APPLICABLE - IMPLEMENTED
Implementation Date: January 2024
Last Review: December 2024
Control Objective:
To provide management direction and support for information security in
accordance with business requirements and relevant laws and regulations.
Justification for Applicability:
As a SaaS provider handling customer data, we require comprehensive
information security policies to govern our operations, meet regulatory
requirements (SOC 2, GDPR), and demonstrate commitment to security.
Implementation Description:
Your Company maintains a comprehensive Information Security Policy (v2.1)
approved by executive management and reviewed annually. The policy covers:
- Information security objectives and strategy
- Roles and responsibilities
- Risk management approach
- Asset classification and handling
- Access control principles
- Incident management
- Business continuity
Policy is communicated to all employees during onboarding and annually
thereafter through mandatory security awareness training.
Evidence:
- Information Security Policy v2.1 (approved 2024-01-15)
- Executive management approval memo
- Policy acknowledgment records (98% employee completion)
- Annual policy review meeting minutes (2024-12-10)
- Security awareness training completion records
Control Owner: CISO
Implementation Cost: $8,000 (initial policy development)
Annual Review: December (annually)
Cross-Reference:
- NIST 800-53: PL-1, PM-1
- SOC 2: CC1.1, CC1.2
- GDPR: Article 24 (Security measures)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
A.5.2 - Information security roles and responsibilities
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Status: ✓ APPLICABLE - IMPLEMENTED
Implementation Date: January 2024
Control Objective:
To ensure that information security responsibilities are defined and assigned.
Justification for Applicability:
Clear definition of security roles ensures accountability and effective
security management across the organization.
Implementation Description:
Security roles and responsibilities are documented in:
1. Organizational chart showing security reporting structure
2. Job descriptions including security responsibilities
3. RACI matrix for security processes
Key Roles:
- CISO: Overall security strategy and program management
- Security Engineers: Technical security implementation and monitoring
- IT Operations: Day-to-day security operations
- Development Teams: Secure coding practices, security testing
- All Employees: Following security policies, reporting incidents
Responsibilities are reviewed during annual performance reviews and updated
when organizational changes occur.
Evidence:
- Organizational chart (updated 2024-11-01)
- Job descriptions with security responsibilities
- RACI matrix for ISMS processes
- Performance review templates including security criteria
- Security team charter (approved 2024-01-20)
Control Owner: CISO
Cross-Reference: NIST 800-53: PM-2; SOC 2: CC1.3
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
A.5.7 - Threat intelligence
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Status: ✓ APPLICABLE - PARTIALLY IMPLEMENTED
Implementation Date: March 2024 (in progress)
Target Completion: February 2025
Control Objective:
To ensure that information related to information security threats is
collected and analyzed to produce threat intelligence.
Justification for Applicability:
As a cloud service provider, understanding the threat landscape is critical
for proactive security measures and risk management.
Implementation Description:
Current Implementation:
✓ AWS GuardDuty enabled (threat detection for AWS environment)
✓ Subscription to AWS Security Bulletins
✓ Monthly review of CISA alerts
✓ GitHub security advisories for dependencies
Gaps:
✗ No formal threat intelligence platform
✗ Limited industry-specific threat intelligence
✗ No automated threat feed integration
Planned Remediation:
1. Implement threat intelligence platform (Q1 2025)
- Evaluate: Recorded Future, ThreatConnect, or CrowdStrike Threat Graph
- Budget: $15,000/year
2. Subscribe to FS-ISAC (Financial Services threat intelligence)
3. Integrate threat feeds with SIEM
Evidence:
- GuardDuty configuration and findings
- CISA alert review log (monthly)
- GitHub Dependabot alerts and remediation
- Threat intelligence platform RFP (in progress)
Control Owner: Security Team
Risk Level (current gap): MEDIUM
Compensating Control: Enhanced monitoring via GuardDuty + manual review
Cross-Reference: NIST 800-53: PM-16; SOC 2: CC7.1
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
A.5.10 - Acceptable use of information and other associated assets
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Status: ✓ APPLICABLE - IMPLEMENTED
Implementation Date: January 2024
Control Objective:
To ensure that personnel and other interested parties use information and
other associated assets in accordance with acceptable use policies.
Implementation Description:
Acceptable Use Policy (AUP) v1.6 defines permitted and prohibited uses of:
- IT systems and networks
- Email and communication tools
- Cloud resources (AWS, GitHub, etc.)
- Customer data
- Company devices (laptops, mobile devices)
Key provisions:
- No personal use of customer data
- No sharing of access credentials
- No installation of unauthorized software
- No use of personal cloud storage for company data
- Monitoring and logging of system usage
Policy enforced through:
- Annual acknowledgment required (100% compliance)
- Technical controls (DLP, endpoint protection)
- Monitoring and auditing
- Disciplinary action for violations
Evidence:
- Acceptable Use Policy v1.6
- Annual AUP acknowledgment (142/142 employees)
- DLP policies blocking unauthorized cloud storage
- USB device restrictions (enforced via MDM)
- Policy violation incidents (2 in 2024, both resolved)
Control Owner: IT Operations
Cross-Reference: NIST 800-53: AC-20, PS-6; SOC 2: CC6.1
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
A.5.23 - Information security for use of cloud services
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Status: ✓ APPLICABLE - IMPLEMENTED
Implementation Date: January 2024
Control Objective:
To establish processes for the acquisition, use, management, and exit from
cloud services in accordance with the organization's information security
requirements.
Implementation Description:
Cloud Service Management Process covers:
Acquisition:
- Vendor risk assessment required (all new cloud services)
- Security review of cloud provider's certifications (SOC 2, ISO 27001)
- Contract review including data protection clauses
- Budget approval process
Use:
- Configuration standards (CIS benchmarks)
- Security baselines (encryption, logging, access control)
- Monitoring and alerting
- Regular security assessments
Management:
- Asset inventory (AWS Config, Terraform state)
- Configuration management (Infrastructure as Code)
- Quarterly vendor reviews
- Annual risk reassessment
Exit:
- Data extraction procedures
- Secure data deletion requirements
- Service transition plan
- Post-exit verification
Primary Cloud Providers:
✓ AWS (production infrastructure) - SOC 2, ISO 27001, FedRAMP
✓ Okta (identity management) - SOC 2, ISO 27001
✓ GitHub (source code) - SOC 2
✓ Datadog (monitoring) - SOC 2
Evidence:
- Cloud Service Management Procedure v1.2
- Vendor risk assessments (4 primary vendors)
- Vendor SOC 2 reports (reviewed annually)
- Cloud configuration standards documentation
- Terraform IaC for AWS infrastructure
- Quarterly vendor review meeting minutes
Control Owner: CISO
Cross-Reference: NIST 800-53: SA-9; SOC 2: CC9.1
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
A.6 PEOPLE CONTROLS (8 controls)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
A.6.1 - Screening
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Status: ✓ APPLICABLE - IMPLEMENTED
Implementation Date: January 2024
Control Objective:
To ensure that personnel are suitable for their roles and understand their
responsibilities.
Implementation Description:
Background screening process for all new hires:
Standard Positions:
- Identity verification
- Employment history verification (7 years)
- Education verification
- Criminal background check (county, state, federal)
- Reference checks (minimum 2 professional references)
Privileged Positions (Security, IT, DevOps):
- All standard checks plus:
- Credit check (for financial access roles)
- Drug screening
- Enhanced background check (10 years)
Contractors and Vendors:
- Background screening required for onsite access
- NDA signed before access to systems/data
- Access limited to minimum necessary
Process:
- Screening initiated by HR upon offer acceptance
- Results reviewed before start date
- Adverse findings reviewed by HR + hiring manager
- Re-screening every 3 years for privileged positions
Evidence:
- Background Screening Policy v1.1
- Screening results (stored securely in BambooHR)
- Vendor screening records (for contractors)
- Re-screening schedule and completion log
Control Owner: Human Resources
Cost: $150/employee (standard), $300 (privileged)
Cross-Reference: NIST 800-53: PS-3; SOC 2: CC1.4
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
A.6.5 - Responsibilities after termination or change of employment
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Status: ✓ APPLICABLE - IMPLEMENTED
Implementation Date: January 2024
Control Objective:
To protect the organization's interests as part of the process of changing
or terminating employment.
Implementation Description:
Termination/Transfer Procedure:
Immediate Actions (within 4 hours):
✓ Disable all system accounts (Okta, AWS, GitHub, etc.)
✓ Revoke VPN access
✓ Deactivate physical access badges
✓ Remote wipe company devices (if not returned)
✓ Revoke access keys and API tokens
Within 24 Hours:
✓ Collect company property (laptop, phone, badge)
✓ Conduct exit interview (security reminders)
✓ NDA and confidentiality reminder
✓ Return of company data verification
Post-Termination:
✓ Email forwarding (30 days to manager)
✓ Knowledge transfer (if planned departure)
✓ Final access review (verify all access removed)
✓ Update asset inventory
Automation:
- HR termination in BambooHR triggers webhook
- Lambda function disables Okta account
- AWS SSO access auto-revoked (SCIM sync)
- Slack notification to IT/Security teams
Evidence:
- Termination Procedure v1.3
- Termination checklist (all 12 terminations in 2024)
- Automated deprovisioning logs
- Exit interview documentation
- Property return receipts
Control Owner: HR + IT Operations
Average Deprovisioning Time: 2.3 hours
Cross-Reference: NIST 800-53: PS-4; SOC 2: CC6.1, CC6.4
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
A.7 PHYSICAL CONTROLS (14 controls)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
A.7.1 - Physical security perimeters
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Status: ○ NOT APPLICABLE
Justification Date: January 2024
Control Objective:
To prevent unauthorized physical access, damage, and interference to the
organization's information and other associated assets.
Justification for Non-Applicability:
Your Company operates a cloud-only infrastructure with no owned or leased
data centers. All production infrastructure is hosted on AWS, which maintains
physical security controls and provides ISO 27001 and SOC 2 attestations.
Office Locations:
- Corporate office (50 employees): Shared office space with landlord-
managed physical security (badge access, security cameras, reception)
- Remote workforce (92 employees): Home offices, no company-controlled
physical security
Physical security for AWS infrastructure is inherited from AWS. Evidence:
- AWS ISO 27001 certificate (Annex A.7.1 covered)
- AWS SOC 2 Type II report (physical security controls tested)
- Shared Responsibility Matrix documents customer vs AWS responsibilities
Corporate office physical security managed by building management, not in
scope for ISMS (no customer data processed or stored in office).
Alternative Controls:
- All customer data encrypted at rest (AWS infrastructure)
- No local data storage policies (data must remain in cloud)
- Device encryption required (corporate laptops)
- Remote wipe capability (all company devices)
Evidence:
- AWS compliance documents (ISO 27001, SOC 2)
- Cloud-only architecture documentation
- No Local Data Storage policy
- Device encryption enforcement (MDM reports)
Risk Assessment:
- Risk of physical breach: LOW (no data centers, cloud-only)
- Residual risk from AWS: ACCEPTED (AWS maintains physical controls)
Approved By: CISO
Review Frequency: Annually (or if infrastructure changes)
Cross-Reference:
- AWS responsibility: Physical and environmental security
- Customer responsibility: Data encryption, access management
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
A.8 TECHNOLOGICAL CONTROLS (34 controls)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
A.8.1 - User endpoint devices
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Status: ✓ APPLICABLE - IMPLEMENTED
Implementation Date: February 2024
Control Objective:
To ensure security of user endpoint devices.
Implementation Description:
Endpoint Device Security Program:
Corporate Laptops (MacBook Pro, standard issue):
✓ Full disk encryption (FileVault) - enforced
✓ Automatic updates enabled
✓ Endpoint protection (CrowdStrike Falcon)
✓ MDM enrollment required (Jamf Pro)
✓ Screen lock after 5 minutes idle
✓ Password requirements (14+ chars, complexity)
✓ Remote wipe capability
Mobile Devices (BYOD policy):
✓ Okta Verify app required for MFA
✓ Conditional access (compliant devices only)
✓ Company data containerized (work profile)
✓ Remote wipe for work data
Technical Controls:
- Jamf Pro MDM manages laptop configuration
- CrowdStrike Falcon for endpoint protection
- AWS Systems Manager for cloud-based management
- Automated compliance checks (daily)
Non-Compliance Handling:
- Devices failing compliance checks blocked from network
- User notified with remediation steps
- IT support available for assistance
- Escalation to manager after 48 hours
Evidence:
- Endpoint Security Policy v1.4
- MDM enrollment report (142/142 devices enrolled)
- Encryption compliance report (100%)
- CrowdStrike deployment status (100% coverage)
- Compliance check results (daily)
Control Owner: IT Operations
Cost: $50/device/month (MDM + endpoint protection)
Cross-Reference: NIST 800-53: AC-19, MP-2; SOC 2: CC6.6, CC6.7
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
A.8.9 - Configuration management
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Status: ✓ APPLICABLE - IMPLEMENTED
Implementation Date: January 2024
Control Objective:
To establish and maintain configurations, including security configurations,
of hardware, software, services, and networks.
Implementation Description:
Configuration Management via Infrastructure as Code:
Infrastructure:
✓ All AWS infrastructure defined in Terraform
✓ Version controlled in GitHub (main branch protected)
✓ Configuration baselines (CIS AWS Foundations Benchmark)
✓ Automated compliance scanning (AWS Config)
Process:
1. All changes via pull request (Terraform)
2. Automated terraform plan in CI/CD
3. Security team review required for approval
4. Changes applied via Terraform Cloud
5. AWS Config detects drift from baseline
6. Manual changes trigger alerts → auto-remediation
Security Baselines:
- EC2: Amazon Linux 2023, SSM agent, encrypted EBS
- S3: Default encryption, versioning, public access blocked
- RDS: Encryption at rest, automated backups, Multi-AZ
- VPC: Private subnets, NAT gateway, VPC endpoints
- IAM: MFA required, password policy, no root usage
Configuration Documentation:
- Terraform modules (version controlled)
- Architecture diagrams (updated quarterly)
- Configuration baseline documentation
- Change log (Git history + Terraform Cloud)
Evidence:
- Terraform configuration files (GitHub repository)
- CIS AWS Foundations Benchmark compliance report
- AWS Config compliance dashboard
- Terraform Cloud run logs (all changes)
- Manual change detection alerts and remediation
Control Owner: DevOps Team
Cross-Reference: NIST 800-53: CM-2, CM-3, CM-6; SOC 2: CC8.1
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
A.8.24 - Use of cryptography
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Status: ✓ APPLICABLE - IMPLEMENTED
Implementation Date: January 2024
Control Objective:
To ensure proper and effective use of cryptography to protect the
confidentiality, authenticity and/or integrity of information.
Implementation Description:
Cryptography Policy and Standards:
Data at Rest:
✓ S3 buckets: AES-256 encryption (default enabled)
✓ RDS databases: AES-256 encryption
✓ EBS volumes: AES-256 encryption
✓ Secrets Manager: Encrypted with KMS
✓ Backups: Encrypted
Data in Transit:
✓ TLS 1.2+ only (TLS 1.0/1.1 disabled)
✓ Strong cipher suites (AES-GCM preferred)
✓ HSTS enforced (max-age=31536000)
✓ Certificate management via ACM (auto-renewal)
Key Management:
✓ AWS KMS for encryption keys
✓ Customer-managed keys (CMK) for sensitive data
✓ Automatic key rotation (annually)
✓ Key access logged in CloudTrail
✓ Key policies enforce least privilege
Cryptographic Standards:
- Encryption: AES-256 (symmetric), RSA-2048+ (asymmetric)
- Hashing: SHA-256 or stronger
- TLS: Version 1.2 or 1.3 only
- Certificates: 2048-bit RSA minimum, 1-year validity
Prohibited:
✗ DES, 3DES, RC4 (weak algorithms)
✗ MD5, SHA-1 (weak hashing)
✗ Self-signed certificates in production
✗ Hardcoded encryption keys
Evidence:
- Encryption Policy v1.5
- KMS key configuration and rotation schedule
- S3 encryption configuration (all buckets)
- TLS configuration (ALB, CloudFront)
- SSL Labs scan results (A+ rating)
- Certificate inventory (ACM)
Control Owner: Security Team
Cross-Reference: NIST 800-53: SC-12, SC-13, SC-28; SOC 2: CC6.7, CC6.8
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CONTROLS NOT IMPLEMENTED (RISK ACCEPTED)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
A.5.7 - Threat Intelligence (Partially Implemented)
Status: Under implementation (Q1 2025)
Risk Level: MEDIUM
Gap: No formal threat intelligence platform
Compensating Control: Enhanced monitoring via GuardDuty
Remediation Plan: Implement threat intelligence platform by Q1 2025
Budget Allocated: $15,000/year
Approval: CISO (accepted residual risk until implementation)
A.8.16 - Monitoring activities (Partially Implemented)
Status: Under implementation (Q1 2025)
Risk Level: MEDIUM
Gap: No centralized SIEM for log correlation
Compensating Control: CloudWatch Logs + GuardDuty + manual analysis
Remediation Plan: Implement Splunk Cloud or similar SIEM by Q2 2025
Budget Allocated: $100,000/year
Approval: CFO + CISO (cost-benefit analysis in progress)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
APPROVAL AND REVIEW
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Prepared By:
Name: Jane Smith, Security Engineer
Date: 2025-01-28
Signature: _________________________
Reviewed By:
Name: John Doe, CISO
Date: 2025-01-28
Signature: _________________________
Approved By:
Name: Sarah Johnson, CEO
Date: 2025-01-28
Signature: _________________________
Next Review Date: January 2026 (or upon significant ISMS changes)
Changes Since Last Version:
- v1.0 (2025-01-28): Initial SOA for ISO 27001:2022 certification
Excel Export Format
Column A: Control ID
Column B: Control Name
Column C: Applicability (Applicable/Not Applicable)
Column D: Implementation Status (Implemented/Partial/Not Implemented)
Column E: Justification
Column F: Evidence Reference
Column G: Control Owner
Column H: Implementation Date
Column I: Next Review Date
Column J: Cross-References (NIST, SOC 2, etc.)
Example rows:
A.5.1 | Policies for information security | Applicable | Implemented | Required for business operations | InfoSec Policy v2.1 | CISO | 2024-01-15 | 2025-01-15 | NIST PL-1, SOC2 CC1.1
A.7.1 | Physical security perimeters | Not Applicable | N/A | Cloud-only, no data centers | AWS compliance docs | CISO | 2024-01-15 | 2025-01-15 | Inherited from AWS
Related Commands
/iso:assess- Gap analysis to identify controls needing work/iso:risk-treatment-plan- Create risk treatment plan for gaps/iso:annex-a-deep-dive- Deep dive on specific Annex A domain/iso:certification-roadmap- Plan certification process/iso:isms-documentation-pack- Generate all required ISMS documents
Sponsors
Details
- Marketplace
- GRCEngClub/claude-grc-engineering
- Source
- plugins/frameworks/iso27001
- Category
- Community
More from GRCEngClub/claude-grc-engineering
All 70- jp-appiv0.1.0
- nist-800-53v0.1.0
- nist-ai-600-1v0.1.0
- nist-ai-rmfv0.1.0
- nist-csf-20v0.1.0
- nydfsv0.1.0
- okta-inspectorv0.1.0
- onepassword-connectorv0.1.0
- oscalv0.1.0
- pbmmv0.1.0
- pci-dssv0.1.0
- poam-automationv0.1.0
- sg-mas-trmv0.1.0
- singapore-pdpav0.1.0
- slack-inspectorv0.1.0
- snowflake-inspectorv0.1.0
- soc2v0.1.0
- splunk-inspectorv0.1.0
- staterampv0.1.0
- teach-mev0.1.0
- tenable-inspectorv0.1.0
- testssl-inspectorv0.1.0
- trust-centerv0.1.0
- us-ccpav0.1.0
