[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HC6BXBP49MVMK3A3AF3GY8":3,"skill-same:01M6HC6BXBP49MVMK3A3AF3GY8":107},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":68,"commitSha":69,"skillDirectory":70,"forksCount":71,"repositoryHtmlUrl":72,"repositoryHomepageUrl":6,"ownerHtmlUrl":73,"ownerBlogUrl":6,"ownerDescription":74,"updatedAt":75,"install":76,"resources":89},"01M6HC6BXBP49MVMK3A3AF3GY8","auditing-cloud-with-cis-benchmarks",null,"This skill details how to conduct cloud security audits using Center for Internet Security benchmarks for AWS, Azure, and GCP. It covers interpreting CIS Foundations Benchmark controls, running automated assessments with tools like Prowler and...","HenriqueMC17\u002Fagente-core","HenriqueMC17","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206460478?v=4","01M6HB63HBBF18AC4H09XTB549","Henrique Monteiro Cardoso","01M6HB63NGSQXWKWCFWW2B20W0",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fauditing-cloud-with-cis-benchmarks\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"cis benchmarks","cloud","with","auditing cloud with cis benchmarks","benchmarks","cis","t1098","internet","foundations","how to","map","cm","cybersecurity","gcp","security-hardening","prowler","compliance-assessment","cloud-audit","cis-benchmarks","assessment","2026-11-10 10:12:30",false,"---\nname: auditing-cloud-with-cis-benchmarks\ndescription: This skill details how to conduct cloud security audits using Center for Internet Security benchmarks for AWS, Azure, and GCP. It covers interpreting CIS Foundations Benchmark controls, running automated assessments with tools like Prowler and...\ndomain: cybersecurity\nsubdomain: cloud-security\ntags:\n- cis-benchmarks\n- cloud-audit\n- compliance-assessment\n- prowler\n- security-hardening\nversion: 1.0.0\nauthor: mahipal\nlicense: Apache-2.0\nnist_ai_rmf:\n- GOVERN-1.1\n- GOVERN-4.2\n- MAP-2.3\nnist_csf:\n- PR.IR-01\n- ID.AM-08\n- GV.SC-06\n- DE.CM-01\nmitre_attack:\n- T1078.004\n- T1530\n- T1098.003\n- T1685.002\n- T1580\ncategory: auditing-cloud-with-cis-benchmarks\n---\n# Auditing-Cloud-With-Cis-Benchmarks\n\n## Overview\nThis skill details how to conduct cloud security audits using Center for Internet Security benchmarks for AWS, Azure, and GCP. It covers interpreting CIS Foundations Benchmark controls, running automated assessments with tools like Prowler and ScoutSuite, remediating failed controls, and maintaining continuous compliance monitoring against CIS v5 for AWS, v4 for Azure, and v4 for GCP.\n\n\n\n# Auditing Cloud with CIS Benchmarks\n\n## When to Use\n\n- When performing initial security audits of cloud environments against industry-standard benchmarks\n- When preparing for SOC 2, ISO 27001, or regulatory audits that reference CIS controls\n- When establishing a measurable security baseline for new cloud accounts or subscriptions\n- When tracking compliance improvement over time with periodic reassessment\n- When evaluating the security posture of acquired or inherited cloud environments\n\n**Do not use** for runtime threat detection (see detecting-cloud-threats-with-guardduty), for application-level security testing (see conducting-cloud-penetration-testing), or for compliance frameworks not based on CIS (refer to specific regulatory skill files).\n\n## Prerequisites\n\n- Read-only access to target cloud accounts (AWS SecurityAudit policy, Azure Reader role, GCP Viewer role)\n- Prowler, ScoutSuite, or cloud-native CSPM tools installed and configured\n- Understanding of CIS benchmark structure: sections, controls, profiles (Level 1 and Level 2)\n- Remediation access for implementing fixes (separate from audit credentials)\n\n## Workflow\n\n### Step 1: Select Appropriate CIS Benchmark Version\n\nChoose the correct benchmark version for each cloud provider. Current versions as of 2025 include CIS AWS Foundations Benchmark v5.0, CIS Azure Foundations Benchmark v4.0, and CIS GCP Foundations Benchmark v4.0.\n\n```\nCIS Benchmark Coverage Areas:\n+-------------------+-------------------------+------------------------+\n| Section           | AWS v5.0                | Azure v4.0             |\n+-------------------+-------------------------+------------------------+\n| Identity & Access | IAM policies, MFA, root | Azure AD, RBAC, PIM    |\n| Logging           | CloudTrail, Config      | Activity Log, Diag     |\n| Monitoring        | CloudWatch alarms       | Defender, Sentinel     |\n| Networking        | VPC, SG, NACLs         | NSG, ASG, Firewall     |\n| Storage           | S3 encryption, access   | Storage encryption     |\n| Database          | RDS encryption          | SQL TDE, auditing      |\n+-------------------+-------------------------+------------------------+\n\nCIS Profile Levels:\n  Level 1: Practical security settings that can be implemented without significant\n           performance impact or reduced functionality\n  Level 2: Defense-in-depth settings that may reduce functionality or require\n           additional planning for implementation\n```\n\n### Step 2: Run Automated Assessment with Prowler\n\nExecute comprehensive CIS benchmark scans using Prowler for automated control evaluation across AWS, Azure, and GCP.\n\n```bash\n# AWS CIS v5.0 assessment\nprowler aws \\\n  --compliance cis_5.0_aws \\\n  --profile audit-account \\\n  --output-formats json-ocsf,html,csv \\\n  --output-directory .\u002Fcis-audit-$(date +%Y%m%d)\n\n# Azure CIS v4.0 assessment\nprowler azure \\\n  --compliance cis_4.0_azure \\\n  --subscription-ids \"sub-id-1,sub-id-2\" \\\n  --output-formats json-ocsf,html,csv \\\n  --output-directory .\u002Fcis-audit-azure-$(date +%Y%m%d)\n\n# GCP CIS v4.0 assessment\nprowler gcp \\\n  --compliance cis_4.0_gcp \\\n  --project-ids \"project-1,project-2\" \\\n  --output-formats json-ocsf,html,csv \\\n  --output-directory .\u002Fcis-audit-gcp-$(date +%Y%m%d)\n\n# Multi-account AWS scan using ScoutSuite\nscout suite aws \\\n  --profile audit-account \\\n  --report-dir .\u002Fscout-report \\\n  --ruleset cis-5.0 \\\n  --force\n```\n\n### Step 3: Interpret Results and Prioritize Remediation\n\nAnalyze audit results by section and severity. Prioritize Level 1 controls first as they represent fundamental security hygiene, then address Level 2 controls for defense in depth.\n\n```bash\n# Parse Prowler results for failed controls\ncat .\u002Fcis-audit-*\u002Fprowler-output-*.json | \\\n  jq '[.[] | select(.StatusExtended == \"FAIL\")] | group_by(.CheckID) |\n  map({control: .[0].CheckID, description: .[0].CheckTitle,\n  failed_resources: length, severity: .[0].Severity}) |\n  sort_by(-.failed_resources)'\n\n# Generate compliance score by section\ncat .\u002Fcis-audit-*\u002Fprowler-output-*.json | \\\n  jq 'group_by(.Section) | map({\n    section: .[0].Section,\n    total: length,\n    passed: [.[] | select(.StatusExtended == \"PASS\")] | length,\n    failed: [.[] | select(.StatusExtended == \"FAIL\")] | length,\n    score: (([.[] | select(.StatusExtended == \"PASS\")] | length) \u002F length * 100 | round)\n  })'\n```\n\n### Step 4: Remediate Critical and High Controls\n\nAddress failed controls starting with the highest impact items. Use AWS Config remediation, Azure Policy, or Terraform to apply fixes systematically.\n\n```bash\n# CIS 1.4: Ensure no root account access key exists\naws iam list-access-keys --user-name root\n# If keys exist, delete them\naws iam delete-access-key --user-name root --access-key-id AKIAEXAMPLE\n\n# CIS 2.1.1: Ensure S3 bucket default encryption is enabled\nfor bucket in $(aws s3api list-buckets --query 'Buckets[*].Name' --output text); do\n  aws s3api put-bucket-encryption --bucket \"$bucket\" \\\n    --server-side-encryption-configuration '{\n      \"Rules\": [{\"ApplyServerSideEncryptionByDefault\": {\"SSEAlgorithm\": \"AES256\"}}]\n    }' 2>\u002Fdev\u002Fnull && echo \"Encrypted: $bucket\" || echo \"FAILED: $bucket\"\ndone\n\n# CIS 3.1: Ensure CloudTrail is enabled in all regions\naws cloudtrail create-trail \\\n  --name organization-trail \\\n  --s3-bucket-name cloudtrail-logs-bucket \\\n  --is-multi-region-trail \\\n  --enable-log-file-validation \\\n  --kms-key-id arn:aws:kms:us-east-1:123456789012:key\u002Fkey-id\n\naws cloudtrail start-logging --name organization-trail\n\n# CIS 4.x: Configure CloudWatch metric filters and alarms\naws logs put-metric-filter \\\n  --log-group-name CloudTrail\u002FDefaultLogGroup \\\n  --filter-name UnauthorizedAPICalls \\\n  --filter-pattern '{ ($.errorCode = \"*UnauthorizedAccess*\") || ($.errorCode = \"AccessDenied*\") }' \\\n  --metric-transformations metricName=UnauthorizedAPICalls,metricNamespace=CISBenchmark,metricValue=1\n```\n\n### Step 5: Establish Continuous Compliance Monitoring\n\nDeploy automated compliance monitoring to detect configuration drift between periodic audits. Use AWS Security Hub, Azure Policy, or GCP Security Command Center.\n\n```bash\n# AWS: Enable CIS v5.0 in Security Hub\naws securityhub batch-enable-standards \\\n  --standards-subscription-requests '[\n    {\"StandardsArn\": \"arn:aws:securityhub:::ruleset\u002Fcis-aws-foundations-benchmark\u002Fv\u002F5.0.0\"}\n  ]'\n\n# Azure: Assign CIS benchmark policy initiative\naz policy assignment create \\\n  --name cis-azure-benchmark \\\n  --scope \"\u002Fsubscriptions\u002F\u003Csub-id>\" \\\n  --policy-set-definition \"1a5bb27d-173f-493e-9568-eb56638dbd0e\" \\\n  --params '{\"effect\": {\"value\": \"AuditIfNotExists\"}}'\n\n# Schedule periodic Prowler assessments\n# Run weekly via cron or CI\u002FCD pipeline\n0 2 * * 1 prowler aws --compliance cis_5.0_aws --output-formats csv --output-directory \u002Fopt\u002Faudits\u002Fweekly-$(date +\\%Y\\%m\\%d)\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| CIS Benchmark | Prescriptive security configuration guidelines developed by the Center for Internet Security through community consensus |\n| Level 1 Profile | Practical security controls implementable without significant performance or functionality impact, representing security hygiene |\n| Level 2 Profile | Defense-in-depth controls that may restrict functionality and require careful planning before implementation |\n| Foundations Benchmark | CIS benchmark specifically for cloud providers covering IAM, logging, monitoring, networking, and storage security |\n| Control ID | Unique numerical identifier for each CIS recommendation (e.g., 1.4 for root access key checks, 2.1.1 for S3 encryption) |\n| Compliance Score | Percentage of CIS controls in a passing state, tracked over time to measure security posture improvement |\n| Automated Assessment | Tool-driven evaluation of CIS controls using cloud provider APIs to check resource configurations against benchmark requirements |\n| Remediation Runbook | Documented step-by-step procedure for fixing a specific failed CIS control, including pre-checks and validation |\n\n## Tools & Systems\n\n- **Prowler**: Open-source cloud security tool performing 300+ checks including CIS benchmark assessments for AWS, Azure, and GCP\n- **ScoutSuite**: Multi-cloud security auditing tool with CIS benchmark rule sets generating HTML reports\n- **AWS Security Hub**: Native AWS service supporting CIS AWS Foundations Benchmark as a security standard\n- **Azure Policy**: Governance service with built-in CIS benchmark policy initiatives for automated compliance monitoring\n- **GCP Security Command Center**: Native GCP service evaluating configurations against CIS GCP Foundations Benchmark\n\n## Common Scenarios\n\n### Scenario: Pre-Audit CIS Assessment for SOC 2 Certification\n\n**Context**: A SaaS company pursuing SOC 2 Type II certification needs to demonstrate cloud security controls aligned to CIS benchmarks. The auditor requires evidence of continuous compliance monitoring across 45 AWS accounts.\n\n**Approach**:\n1. Run Prowler CIS v5.0 assessment across all 45 accounts to establish the baseline compliance score\n2. Export results to CSV and categorize failures by section (IAM, Logging, Monitoring, Networking)\n3. Map each CIS control to the relevant SOC 2 Trust Services Criteria (CC6.1, CC6.6, CC7.1, etc.)\n4. Remediate all Level 1 control failures within 30 days and Level 2 within 60 days\n5. Enable CIS v5.0 in AWS Security Hub for continuous monitoring and automated drift detection\n6. Generate weekly compliance reports showing improvement trajectory for the auditor\n7. Document exceptions for controls intentionally not implemented with risk acceptance justification\n\n**Pitfalls**: Remediating controls without testing in a staging environment first can break production workloads. Ignoring Level 2 controls entirely weakens the audit narrative even if they are not strictly required.\n\n## Output Format\n\n```\nCIS Benchmark Audit Report\n============================\nCloud Provider: AWS\nBenchmark Version: CIS AWS Foundations Benchmark v5.0\nAccounts Assessed: 45\nAssessment Date: 2025-02-23\nTool: Prowler v4.3.0\n\nOVERALL COMPLIANCE SCORE: 74%\n\nCOMPLIANCE BY SECTION:\n  1. Identity and Access Management:  68% (41\u002F60 controls passed)\n  2. Storage:                         82% (28\u002F34 controls passed)\n  3. Logging:                         91% (20\u002F22 controls passed)\n  4. Monitoring:                      55% (18\u002F33 controls passed)\n  5. Networking:                      78% (32\u002F41 controls passed)\n\nTOP FAILED CONTROLS (by affected accounts):\n  [1.4]   Root account has active access keys           - 3\u002F45 accounts\n  [1.5]   MFA not enabled for root account              - 2\u002F45 accounts\n  [2.1.1] S3 default encryption not enabled             - 12\u002F45 accounts\n  [3.1]   CloudTrail not multi-region                   - 8\u002F45 accounts\n  [4.3]   No alarm for root account usage               - 28\u002F45 accounts\n  [5.1]   VPC flow logs not enabled                     - 15\u002F45 accounts\n  [5.4]   Security groups allow 0.0.0.0\u002F0 ingress      - 22\u002F45 accounts\n\nREMEDIATION PRIORITY:\n  Critical (Fix within 7 days):  Root access keys, missing root MFA\n  High (Fix within 30 days):     S3 encryption, CloudTrail, VPC flow logs\n  Medium (Fix within 60 days):   CloudWatch alarms, security group restrictions\n  Low (Fix within 90 days):      Level 2 controls, informational items\n```\n","# Auditing-Cloud-With-Cis-Benchmarks\n\n## Overview\nThis skill details how to conduct cloud security audits using Center for Internet Security benchmarks for AWS, Azure, and GCP. It covers interpreting CIS Foundations Benchmark controls, running automated assessments with tools like Prowler and ScoutSuite, remediating failed controls, and maintaining continuous compliance monitoring against CIS v5 for AWS, v4 for Azure, and v4 for GCP.\n\n\n\n# Auditing Cloud with CIS Benchmarks\n\n## When to Use\n\n- When performing initial security audits of cloud environments against industry-standard benchmarks\n- When preparing for SOC 2, ISO 27001, or regulatory audits that reference CIS controls\n- When establishing a measurable security baseline for new cloud accounts or subscriptions\n- When tracking compliance improvement over time with periodic reassessment\n- When evaluating the security posture of acquired or inherited cloud environments\n\n**Do not use** for runtime threat detection (see detecting-cloud-threats-with-guardduty), for application-level security testing (see conducting-cloud-penetration-testing), or for compliance frameworks not based on CIS (refer to specific regulatory skill files).\n\n## Prerequisites\n\n- Read-only access to target cloud accounts (AWS SecurityAudit policy, Azure Reader role, GCP Viewer role)\n- Prowler, ScoutSuite, or cloud-native CSPM tools installed and configured\n- Understanding of CIS benchmark structure: sections, controls, profiles (Level 1 and Level 2)\n- Remediation access for implementing fixes (separate from audit credentials)\n\n## Workflow\n\n### Step 1: Select Appropriate CIS Benchmark Version\n\nChoose the correct benchmark version for each cloud provider. Current versions as of 2025 include CIS AWS Foundations Benchmark v5.0, CIS Azure Foundations Benchmark v4.0, and CIS GCP Foundations Benchmark v4.0.\n\n```\nCIS Benchmark Coverage Areas:\n+-------------------+-------------------------+------------------------+\n| Section           | AWS v5.0                | Azure v4.0             |\n+-------------------+-------------------------+------------------------+\n| Identity & Access | IAM policies, MFA, root | Azure AD, RBAC, PIM    |\n| Logging           | CloudTrail, Config      | Activity Log, Diag     |\n| Monitoring        | CloudWatch alarms       | Defender, Sentinel     |\n| Networking        | VPC, SG, NACLs         | NSG, ASG, Firewall     |\n| Storage           | S3 encryption, access   | Storage encryption     |\n| Database          | RDS encryption          | SQL TDE, auditing      |\n+-------------------+-------------------------+------------------------+\n\nCIS Profile Levels:\n  Level 1: Practical security settings that can be implemented without significant\n           performance impact or reduced functionality\n  Level 2: Defense-in-depth settings that may reduce functionality or require\n           additional planning for implementation\n```\n\n### Step 2: Run Automated Assessment with Prowler\n\nExecute comprehensive CIS benchmark scans using Prowler for automated control evaluation across AWS, Azure, and GCP.\n\n```bash\n# AWS CIS v5.0 assessment\nprowler aws \\\n  --compliance cis_5.0_aws \\\n  --profile audit-account \\\n  --output-formats json-ocsf,html,csv \\\n  --output-directory .\u002Fcis-audit-$(date +%Y%m%d)\n\n# Azure CIS v4.0 assessment\nprowler azure \\\n  --compliance cis_4.0_azure \\\n  --subscription-ids \"sub-id-1,sub-id-2\" \\\n  --output-formats json-ocsf,html,csv \\\n  --output-directory .\u002Fcis-audit-azure-$(date +%Y%m%d)\n\n# GCP CIS v4.0 assessment\nprowler gcp \\\n  --compliance cis_4.0_gcp \\\n  --project-ids \"project-1,project-2\" \\\n  --output-formats json-ocsf,html,csv \\\n  --output-directory .\u002Fcis-audit-gcp-$(date +%Y%m%d)\n\n# Multi-account AWS scan using ScoutSuite\nscout suite aws \\\n  --profile audit-account \\\n  --report-dir .\u002Fscout-report \\\n  --ruleset cis-5.0 \\\n  --force\n```\n\n### Step 3: Interpret Results and Prioritize Remediation\n\nAnalyze audit results by section and severity. Prioritize Level 1 controls first as they represent fundamental security hygiene, then address Level 2 controls for defense in depth.\n\n```bash\n# Parse Prowler results for failed controls\ncat .\u002Fcis-audit-*\u002Fprowler-output-*.json | \\\n  jq '[.[] | select(.StatusExtended == \"FAIL\")] | group_by(.CheckID) |\n  map({control: .[0].CheckID, description: .[0].CheckTitle,\n  failed_resources: length, severity: .[0].Severity}) |\n  sort_by(-.failed_resources)'\n\n# Generate compliance score by section\ncat .\u002Fcis-audit-*\u002Fprowler-output-*.json | \\\n  jq 'group_by(.Section) | map({\n    section: .[0].Section,\n    total: length,\n    passed: [.[] | select(.StatusExtended == \"PASS\")] | length,\n    failed: [.[] | select(.StatusExtended == \"FAIL\")] | length,\n    score: (([.[] | select(.StatusExtended == \"PASS\")] | length) \u002F length * 100 | round)\n  })'\n```\n\n### Step 4: Remediate Critical and High Controls\n\nAddress failed controls starting with the highest impact items. Use AWS Config remediation, Azure Policy, or Terraform to apply fixes systematically.\n\n```bash\n# CIS 1.4: Ensure no root account access key exists\naws iam list-access-keys --user-name root\n# If keys exist, delete them\naws iam delete-access-key --user-name root --access-key-id AKIAEXAMPLE\n\n# CIS 2.1.1: Ensure S3 bucket default encryption is enabled\nfor bucket in $(aws s3api list-buckets --query 'Buckets[*].Name' --output text); do\n  aws s3api put-bucket-encryption --bucket \"$bucket\" \\\n    --server-side-encryption-configuration '{\n      \"Rules\": [{\"ApplyServerSideEncryptionByDefault\": {\"SSEAlgorithm\": \"AES256\"}}]\n    }' 2>\u002Fdev\u002Fnull && echo \"Encrypted: $bucket\" || echo \"FAILED: $bucket\"\ndone\n\n# CIS 3.1: Ensure CloudTrail is enabled in all regions\naws cloudtrail create-trail \\\n  --name organization-trail \\\n  --s3-bucket-name cloudtrail-logs-bucket \\\n  --is-multi-region-trail \\\n  --enable-log-file-validation \\\n  --kms-key-id arn:aws:kms:us-east-1:123456789012:key\u002Fkey-id\n\naws cloudtrail start-logging --name organization-trail\n\n# CIS 4.x: Configure CloudWatch metric filters and alarms\naws logs put-metric-filter \\\n  --log-group-name CloudTrail\u002FDefaultLogGroup \\\n  --filter-name UnauthorizedAPICalls \\\n  --filter-pattern '{ ($.errorCode = \"*UnauthorizedAccess*\") || ($.errorCode = \"AccessDenied*\") }' \\\n  --metric-transformations metricName=UnauthorizedAPICalls,metricNamespace=CISBenchmark,metricValue=1\n```\n\n### Step 5: Establish Continuous Compliance Monitoring\n\nDeploy automated compliance monitoring to detect configuration drift between periodic audits. Use AWS Security Hub, Azure Policy, or GCP Security Command Center.\n\n```bash\n# AWS: Enable CIS v5.0 in Security Hub\naws securityhub batch-enable-standards \\\n  --standards-subscription-requests '[\n    {\"StandardsArn\": \"arn:aws:securityhub:::ruleset\u002Fcis-aws-foundations-benchmark\u002Fv\u002F5.0.0\"}\n  ]'\n\n# Azure: Assign CIS benchmark policy initiative\naz policy assignment create \\\n  --name cis-azure-benchmark \\\n  --scope \"\u002Fsubscriptions\u002F\u003Csub-id>\" \\\n  --policy-set-definition \"1a5bb27d-173f-493e-9568-eb56638dbd0e\" \\\n  --params '{\"effect\": {\"value\": \"AuditIfNotExists\"}}'\n\n# Schedule periodic Prowler assessments\n# Run weekly via cron or CI\u002FCD pipeline\n0 2 * * 1 prowler aws --compliance cis_5.0_aws --output-formats csv --output-directory \u002Fopt\u002Faudits\u002Fweekly-$(date +\\%Y\\%m\\%d)\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| CIS Benchmark | Prescriptive security configuration guidelines developed by the Center for Internet Security through community consensus |\n| Level 1 Profile | Practical security controls implementable without significant performance or functionality impact, representing security hygiene |\n| Level 2 Profile | Defense-in-depth controls that may restrict functionality and require careful planning before implementation |\n| Foundations Benchmark | CIS benchmark specifically for cloud providers covering IAM, logging, monitoring, networking, and storage security |\n| Control ID | Unique numerical identifier for each CIS recommendation (e.g., 1.4 for root access key checks, 2.1.1 for S3 encryption) |\n| Compliance Score | Percentage of CIS controls in a passing state, tracked over time to measure security posture improvement |\n| Automated Assessment | Tool-driven evaluation of CIS controls using cloud provider APIs to check resource configurations against benchmark requirements |\n| Remediation Runbook | Documented step-by-step procedure for fixing a specific failed CIS control, including pre-checks and validation |\n\n## Tools & Systems\n\n- **Prowler**: Open-source cloud security tool performing 300+ checks including CIS benchmark assessments for AWS, Azure, and GCP\n- **ScoutSuite**: Multi-cloud security auditing tool with CIS benchmark rule sets generating HTML reports\n- **AWS Security Hub**: Native AWS service supporting CIS AWS Foundations Benchmark as a security standard\n- **Azure Policy**: Governance service with built-in CIS benchmark policy initiatives for automated compliance monitoring\n- **GCP Security Command Center**: Native GCP service evaluating configurations against CIS GCP Foundations Benchmark\n\n## Common Scenarios\n\n### Scenario: Pre-Audit CIS Assessment for SOC 2 Certification\n\n**Context**: A SaaS company pursuing SOC 2 Type II certification needs to demonstrate cloud security controls aligned to CIS benchmarks. The auditor requires evidence of continuous compliance monitoring across 45 AWS accounts.\n\n**Approach**:\n1. Run Prowler CIS v5.0 assessment across all 45 accounts to establish the baseline compliance score\n2. Export results to CSV and categorize failures by section (IAM, Logging, Monitoring, Networking)\n3. Map each CIS control to the relevant SOC 2 Trust Services Criteria (CC6.1, CC6.6, CC7.1, etc.)\n4. Remediate all Level 1 control failures within 30 days and Level 2 within 60 days\n5. Enable CIS v5.0 in AWS Security Hub for continuous monitoring and automated drift detection\n6. Generate weekly compliance reports showing improvement trajectory for the auditor\n7. Document exceptions for controls intentionally not implemented with risk acceptance justification\n\n**Pitfalls**: Remediating controls without testing in a staging environment first can break production workloads. Ignoring Level 2 controls entirely weakens the audit narrative even if they are not strictly required.\n\n## Output Format\n\n```\nCIS Benchmark Audit Report\n============================\nCloud Provider: AWS\nBenchmark Version: CIS AWS Foundations Benchmark v5.0\nAccounts Assessed: 45\nAssessment Date: 2025-02-23\nTool: Prowler v4.3.0\n\nOVERALL COMPLIANCE SCORE: 74%\n\nCOMPLIANCE BY SECTION:\n  1. Identity and Access Management:  68% (41\u002F60 controls passed)\n  2. Storage:                         82% (28\u002F34 controls passed)\n  3. Logging:                         91% (20\u002F22 controls passed)\n  4. Monitoring:                      55% (18\u002F33 controls passed)\n  5. Networking:                      78% (32\u002F41 controls passed)\n\nTOP FAILED CONTROLS (by affected accounts):\n  [1.4]   Root account has active access keys           - 3\u002F45 accounts\n  [1.5]   MFA not enabled for root account              - 2\u002F45 accounts\n  [2.1.1] S3 default encryption not enabled             - 12\u002F45 accounts\n  [3.1]   CloudTrail not multi-region                   - 8\u002F45 accounts\n  [4.3]   No alarm for root account usage               - 28\u002F45 accounts\n  [5.1]   VPC flow logs not enabled                     - 15\u002F45 accounts\n  [5.4]   Security groups allow 0.0.0.0\u002F0 ingress      - 22\u002F45 accounts\n\nREMEDIATION PRIORITY:\n  Critical (Fix within 7 days):  Root access keys, missing root MFA\n  High (Fix within 30 days):     S3 encryption, CloudTrail, VPC flow logs\n  Medium (Fix within 60 days):   CloudWatch alarms, security group restrictions\n  Low (Fix within 90 days):      Level 2 controls, informational items\n```\n",{"name":5,"tags":49,"author":50,"domain":36,"license":15,"version":51,"category":5,"nist_csf":52,"subdomain":57,"description":7,"nist_ai_rmf":58,"mitre_attack":62},[42,41,40,39,38],"mahipal","1.0.0",[53,54,55,56],"PR.IR-01","ID.AM-08","GV.SC-06","DE.CM-01","cloud-security",[59,60,61],"GOVERN-1.1","GOVERN-4.2","MAP-2.3",[63,64,65,66,67],"T1078.004","T1530","T1098.003","T1685.002","T1580","main","5eea5b3296f4673b5f481e8bcc1ba76281149f16","modules\u002Fauditing-cloud-with-cis-benchmarks",0,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core","https:\u002F\u002Fgithub.com\u002FHenriqueMC17","Qualquer tecnologia suficientemente avançada é indistinguível da mágica.","2026-09-28 22:40:38",{"source":8,"skillName":5,"commands":77,"prompt":87,"zipAvailable":88},[78,81,84],{"tool":79,"command":80},"npx","npx skills add HenriqueMC17\u002Fagente-core --skill auditing-cloud-with-cis-benchmarks",{"tool":82,"command":83},"bunx","bunx skills add HenriqueMC17\u002Fagente-core --skill auditing-cloud-with-cis-benchmarks",{"tool":85,"command":86},"pnpm","pnpm dlx skills add HenriqueMC17\u002Fagente-core --skill auditing-cloud-with-cis-benchmarks","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fauditing-cloud-with-cis-benchmarks\u002FSKILL.md",true,[90,95,101],{"path":91,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fauditing-cloud-with-cis-benchmarks\u002FLICENSE",{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fapi-reference.md","REFERENCE","参考文档",1956,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fauditing-cloud-with-cis-benchmarks\u002Freferences\u002Fapi-reference.md",{"path":102,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":105,"sourceHtmlUrl":106},"scripts\u002Fagent.py","SCRIPT","脚本",6392,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fauditing-cloud-with-cis-benchmarks\u002Fscripts\u002Fagent.py",[108,139,164,187,203,223],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":119,"publishedAt":44},"01M6HPFF0RCN0X6WT5EBSV71GY","validating-backup-integrity-for-recovery","Validate backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to ensure backups are reliable for disaster recovery and ransomware response scenarios.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[114],{"categoryNo":115,"categoryName":116,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[120,121,122,123,124,125,36,126,127,128,129,130,131,132,133,134,135,136,137,138],"integrity","backup","recovery","validating backup integrity for recovery","for","testing","validate","verification","hash-verification","incident-response","ransomware","detection","t1078","t1490","disaster-recovery","restore","incident","disaster recovery","ransomware response",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":44},"01M6HPFAWJVFK25Q33K3T7WQ8G","triaging-vulnerabilities-with-ssvc-framework","Triage and prioritize vulnerabilities using CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree framework to produce actionable remediation priorities.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[],[146,147,148,149,26,36,150,151,152,153,154,155,156,157,158,159,160,161,162,163],"vulnerabilities","framework","ssvc","triaging vulnerabilities with ssvc framework","triage and prioritize","CISA","vulnerability-management","risk-management","cvss","remediation","vulnerability","prioritization","decision-tree","prioritize","decision","priorities","actionable","tree",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":44},"01M6HPF6JS9X72WP59094H3ASQ","triaging-security-incident","Performs initial triage of security incidents to determine severity, scope, and required response actions using the NIST SP 800-61r3 and SANS PICERL frameworks. Classifies incidents by type, assigns priority based on business impact, and routes...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident\u002FSKILL.md",[],[171,172,136,36,173,174,175,132,133,176,177,178,179,180,181,182,183,184,185,186],"security","triaging security incident","actions","soc","NIST","analysis","severity-classification","incident-triage","SANS-PICERL","SOC-operations","picerl","conversion","isolation","scope","impact","consistency",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":193,"publishedAt":44},"01M6HPF2EX6ZYNYYHKBRJN7GEF","triaging-security-incident-with-ir-playbook","Classify and prioritize security incidents using structured IR playbooks to determine severity, assign response teams, and initiate appropriate response procedures.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident-with-ir-playbook\u002FSKILL.md",[],[171,194,195,172,136,26,36,196,174,129,197,198,132,133,199,177,159,200,201,202],"playbook","triaging security incident with ir playbook","teams","IR-playbook","severity","classification","classify","incidents","initiate",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":209,"publishedAt":44},"01M6HPEY9XPGE7X95AG4XJFQAW","triaging-security-alerts-in-splunk","Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL queries and the Incident Review dashboard. Use when...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-alerts-in-splunk\u002FSKILL.md",[],[171,210,211,212,213,214,36,215,216,217,174,218,132,219,220,221,180,35,136,222],"security alerts","splunk","triaging security alerts in splunk","alerts","review","siem","dashboard","search","correlation-search","t1566","notable-events","incident-review","de",{"skillNo":224,"name":225,"nameZh":6,"description":226,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":227,"categories":228,"keywords":229,"publishedAt":44},"01M6HPET6XGEPEJPN7V032JGZ0","tracking-threat-actor-infrastructure","Threat actor infrastructure tracking involves monitoring and mapping adversary-controlled assets including command-and-control (C2) servers, phishing domains, exploit kit hosts, bulletproof hosting, a","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftracking-threat-actor-infrastructure\u002FSKILL.md",[],[230,231,232,233,36,234,235,236,237,238,239,219,240,241,35,242,222,243,244,245],"infrastructure","tracking threat actor infrastructure","tracking","threat","monitoring","mitre-attack","threat-actor","threat-intelligence","command-and-control","dns","command","exploit","intelligence","domains","kit","hosts"]