[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B746GA22R65CEW948SN1K2":3,"skill-same:01M7B746GA22R65CEW948SN1K2":85},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":13,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M7B746GA22R65CEW948SN1K2","implementing-cloud-security-posture-management",null,"Continuously monitor multi-cloud environments (AWS, Azure, GCP) for misconfigurations, compliance violations, and security risks using Prowler, ScoutSuite, AWS Security Hub, Microsoft Defender for Cloud, and GCP Security Command Center. Use for cross-cloud posture monitoring, CIS\u002FSOC 2\u002FPCI DSS compliance, or drift-detection workflows; not for runtime workload protection or application security testing.","vikasvardhanv\u002Fjerry_skills","vikasvardhanv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99010657?v=4","01M7B2B0VN78W7529RQX5BR6DZ","01M7B2B0WDNTXJHRK3QNPNWRP6",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-cloud-security-posture-management\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-cloud-security-posture-management\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-cloud-security-posture-management\ndescription: 'Continuously monitor multi-cloud environments (AWS, Azure, GCP) for\n  misconfigurations, compliance violations, and security risks using Prowler, ScoutSuite,\n  AWS Security Hub, Microsoft Defender for Cloud, and GCP Security Command Center.\n  Use for cross-cloud posture monitoring, CIS\u002FSOC 2\u002FPCI DSS compliance, or drift-detection\n  workflows; not for runtime workload protection or application security testing.\n\n  '\ndomain: cybersecurity\nsubdomain: cloud-security\ntags:\n- cloud-security\n- cspm\n- multi-cloud\n- compliance\n- prowler\n- scoutsuite\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\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- T1537\n- T1580\n---\n\n# Implementing Cloud Security Posture Management\n\n## When to Use\n\n- When establishing continuous security monitoring across AWS, Azure, and GCP environments\n- When compliance requirements demand automated posture assessment against CIS, SOC 2, or PCI DSS\n- When security teams need visibility into cloud misconfigurations across multiple accounts and subscriptions\n- When building a security operations workflow that detects and remediates drift from security baselines\n- When migrating workloads to the cloud and need to enforce security guardrails\n\n**Do not use** for runtime workload protection (use CWPP tools like Falco or Aqua), for application security testing (use DAST\u002FSAST tools), or for network intrusion detection (use cloud-native IDS like GuardDuty or Network Watcher).\n\n## Prerequisites\n\n- Multi-cloud credentials with read-only security audit permissions across all target environments\n- Prowler v3+ installed (`pip install prowler`)\n- ScoutSuite installed (`pip install scoutsuite`)\n- AWS Config, Azure Policy, and GCP Organization Policy enabled in respective environments\n- Central logging destination (S3 bucket, Log Analytics Workspace, or Cloud Storage) for findings aggregation\n- Notification channels configured (Slack, PagerDuty, email) for critical finding alerts\n\n## Workflow\n\n### Step 1: Deploy Cloud-Native CSPM Services\n\nEnable the built-in CSPM capabilities in each cloud provider for baseline posture assessment.\n\n```bash\n# AWS: Enable Security Hub with FSBP and CIS standards\naws securityhub enable-security-hub --enable-default-standards\naws securityhub batch-enable-standards --standards-subscription-requests \\\n  '[{\"StandardsArn\":\"arn:aws:securityhub:::standards\u002Fcis-aws-foundations-benchmark\u002Fv\u002F1.4.0\"}]'\n\n# Azure: Enable Microsoft Defender for Cloud (CSPM tier)\naz security pricing create --name CloudPosture --tier standard\naz security auto-provisioning-setting update --name default --auto-provision on\n\n# GCP: Enable Security Command Center Premium\ngcloud services enable securitycenter.googleapis.com\ngcloud scc settings update --organization=ORG_ID \\\n  --enable-asset-discovery\n```\n\n### Step 2: Run Prowler for Multi-Cloud Assessment\n\nExecute Prowler to perform comprehensive security checks across all three cloud providers.\n\n```bash\n# AWS assessment with all CIS checks\nprowler aws \\\n  --profile production \\\n  -M json-ocsf csv html \\\n  -o .\u002Fprowler-results\u002Faws\u002F \\\n  --compliance cis_1.4_aws cis_1.5_aws\n\n# Azure assessment\nprowler azure \\\n  --subscription-ids SUB_ID_1 SUB_ID_2 \\\n  -M json-ocsf csv html \\\n  -o .\u002Fprowler-results\u002Fazure\u002F \\\n  --compliance cis_2.0_azure\n\n# GCP assessment\nprowler gcp \\\n  --project-ids project-1 project-2 \\\n  -M json-ocsf csv html \\\n  -o .\u002Fprowler-results\u002Fgcp\u002F \\\n  --compliance cis_2.0_gcp\n\n# View summary across all providers\nprowler aws --list-compliance\n```\n\n### Step 3: Run ScoutSuite for Cross-Cloud Comparison\n\nUse ScoutSuite for a unified multi-cloud security assessment with visual reporting.\n\n```bash\n# Scan AWS\npython3 -m ScoutSuite aws --profile production \\\n  --report-dir .\u002Fscoutsuite\u002Faws\u002F\n\n# Scan Azure\npython3 -m ScoutSuite azure --cli \\\n  --all-subscriptions \\\n  --report-dir .\u002Fscoutsuite\u002Fazure\u002F\n\n# Scan GCP\npython3 -m ScoutSuite gcp --user-account \\\n  --all-projects \\\n  --report-dir .\u002Fscoutsuite\u002Fgcp\u002F\n\n# Each produces an HTML report with risk-scored findings\n```\n\n### Step 4: Build Automated Compliance Monitoring Pipeline\n\nCreate a scheduled pipeline that runs CSPM checks daily and routes findings to appropriate channels.\n\n```bash\n# Create a daily Prowler scan with EventBridge + CodeBuild (AWS)\ncat > buildspec.yml \u003C\u003C 'EOF'\nversion: 0.2\nphases:\n  install:\n    commands:\n      - pip install prowler\n  build:\n    commands:\n      - prowler aws -M json-ocsf -o s3:\u002F\u002Fsecurity-findings-bucket\u002Fprowler\u002F$(date +%Y%m%d)\u002F\n      - prowler aws --compliance cis_1.5_aws -M csv -o s3:\u002F\u002Fsecurity-findings-bucket\u002Fprowler\u002Fcompliance\u002F\n  post_build:\n    commands:\n      - |\n        CRITICAL=$(cat output\u002F*.json | grep -c '\"CRITICAL\"')\n        if [ \"$CRITICAL\" -gt 0 ]; then\n          aws sns publish --topic-arn arn:aws:sns:us-east-1:ACCOUNT:security-alerts \\\n            --subject \"Prowler: $CRITICAL critical findings\" \\\n            --message \"Review at s3:\u002F\u002Fsecurity-findings-bucket\u002Fprowler\u002F$(date +%Y%m%d)\u002F\"\n        fi\nEOF\n\n# Schedule with EventBridge\naws events put-rule \\\n  --name daily-prowler-scan \\\n  --schedule-expression \"cron(0 6 * * ? *)\" \\\n  --state ENABLED\n```\n\n### Step 5: Configure Finding Aggregation and Deduplication\n\nAggregate findings from multiple CSPM tools and cloud providers into a unified view.\n\n```python\n# findings_aggregator.py - Normalize and deduplicate CSPM findings\nimport json\nimport hashlib\nfrom datetime import datetime\n\ndef normalize_finding(finding, source):\n    \"\"\"Normalize findings from different CSPM tools to a common format.\"\"\"\n    normalized = {\n        'id': hashlib.sha256(f\"{finding.get('ResourceId','')}{finding.get('CheckId','')}\".encode()).hexdigest()[:16],\n        'source': source,\n        'cloud': finding.get('Provider', 'unknown'),\n        'account': finding.get('AccountId', finding.get('SubscriptionId', '')),\n        'region': finding.get('Region', ''),\n        'resource_type': finding.get('ResourceType', ''),\n        'resource_id': finding.get('ResourceId', ''),\n        'severity': finding.get('Severity', 'INFO').upper(),\n        'status': finding.get('Status', 'FAIL'),\n        'title': finding.get('CheckTitle', finding.get('Title', '')),\n        'description': finding.get('StatusExtended', ''),\n        'compliance': finding.get('Compliance', {}),\n        'remediation': finding.get('Remediation', {}).get('Recommendation', {}).get('Text', ''),\n        'timestamp': datetime.utcnow().isoformat()\n    }\n    return normalized\n\ndef aggregate_findings(prowler_file, scoutsuite_file):\n    findings = {}\n    for file_path, source in [(prowler_file, 'prowler'), (scoutsuite_file, 'scoutsuite')]:\n        with open(file_path) as f:\n            for line in f:\n                raw = json.loads(line)\n                normalized = normalize_finding(raw, source)\n                if normalized['status'] == 'FAIL':\n                    findings[normalized['id']] = normalized\n    return sorted(findings.values(), key=lambda x: {'CRITICAL':0,'HIGH':1,'MEDIUM':2,'LOW':3}.get(x['severity'],4))\n```\n\n### Step 6: Implement Drift Detection and Auto-Remediation\n\nSet up automated responses to configuration drift that violates security baselines.\n\n```bash\n# AWS Config auto-remediation for non-compliant S3 buckets\naws configservice put-remediation-configurations --remediation-configurations '[{\n  \"ConfigRuleName\": \"s3-bucket-public-read-prohibited\",\n  \"TargetType\": \"SSM_DOCUMENT\",\n  \"TargetId\": \"AWS-DisableS3BucketPublicReadWrite\",\n  \"Parameters\": {\n    \"S3BucketName\": {\"ResourceValue\": {\"Value\": \"RESOURCE_ID\"}}\n  },\n  \"Automatic\": true,\n  \"MaximumAutomaticAttempts\": 3,\n  \"RetryAttemptSeconds\": 60\n}]'\n\n# Azure Policy for auto-remediation\naz policy assignment create \\\n  --name \"enforce-storage-encryption\" \\\n  --policy \"\u002Fproviders\u002FMicrosoft.Authorization\u002FpolicyDefinitions\u002F404c3081-a854-4457-ae30-26a93ef643f9\" \\\n  --scope \"\u002Fsubscriptions\u002FSUB_ID\" \\\n  --enforcement-mode Default\n\n# GCP Organization Policy constraint\ngcloud resource-manager org-policies set-policy policy.yaml --organization=ORG_ID\n# policy.yaml: constraint: constraints\u002Fstorage.publicAccessPrevention, enforcement: true\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| CSPM | Cloud Security Posture Management, the practice of continuously monitoring cloud infrastructure for misconfigurations and compliance violations |\n| Configuration Drift | Unintended changes to cloud resource configurations that deviate from the approved security baseline over time |\n| Security Baseline | A documented set of minimum security configuration requirements that all cloud resources must meet |\n| Compliance Framework | A structured set of security controls and requirements (CIS, SOC 2, PCI DSS, NIST) against which cloud configurations are evaluated |\n| Finding Severity | Risk classification of a misconfiguration based on exploitability and potential impact (Critical, High, Medium, Low, Informational) |\n| Auto-Remediation | Automated corrective action that restores a non-compliant resource to its required configuration without manual intervention |\n\n## Tools & Systems\n\n- **Prowler**: Open-source multi-cloud security assessment tool with 300+ checks aligned to CIS, PCI DSS, HIPAA, and NIST\n- **ScoutSuite**: Multi-cloud security auditing tool producing risk-scored HTML reports from API-collected configuration data\n- **AWS Security Hub**: AWS-native CSPM with aggregated findings and compliance standard evaluation\n- **Microsoft Defender for Cloud**: Azure-native CSPM with secure score, regulatory compliance, and workload protection\n- **GCP Security Command Center**: GCP-native security platform with asset inventory, vulnerability scanning, and compliance monitoring\n\n## Common Scenarios\n\n### Scenario: Establishing CSPM for a Multi-Cloud Enterprise\n\n**Context**: An enterprise runs production workloads across AWS (primary), Azure (identity and Microsoft services), and GCP (data analytics). The security team needs unified posture visibility.\n\n**Approach**:\n1. Enable cloud-native CSPM in each provider: Security Hub, Defender for Cloud, SCC\n2. Deploy Prowler scans as daily scheduled jobs in each environment via CI\u002FCD pipelines\n3. Normalize and aggregate findings into a central data lake using the aggregation script\n4. Build dashboards in Grafana or Kibana showing posture scores by cloud, account, and severity\n5. Configure auto-remediation for known-good fixes (public access blocks, encryption enablement)\n6. Route CRITICAL findings to PagerDuty for immediate response and HIGH findings to Jira tickets\n7. Produce weekly compliance reports for executive stakeholders showing trend data\n\n**Pitfalls**: Running CSPM tools with overly broad permissions creates a high-value target. Use dedicated service accounts with read-only permissions and rotate credentials regularly. Different CSPM tools may report the same misconfiguration differently, so deduplication logic must account for varying resource ID formats and finding titles across tools.\n\n## Output Format\n\n```\nCloud Security Posture Management Dashboard\n==============================================\nOrganization: Acme Corp\nAssessment Date: 2026-02-23\nEnvironments: AWS (12 accounts), Azure (8 subscriptions), GCP (5 projects)\n\nPOSTURE SCORES:\n  AWS:   82\u002F100  (+3 from last week)\n  Azure: 76\u002F100  (-1 from last week)\n  GCP:   79\u002F100  (+5 from last week)\n  Overall: 79\u002F100\n\nFINDINGS BY SEVERITY:\n  Critical:  18 (AWS: 7, Azure: 8, GCP: 3)\n  High:      67 (AWS: 28, Azure: 24, GCP: 15)\n  Medium:   234 (AWS: 98, Azure: 87, GCP: 49)\n  Low:      412 (AWS: 178, Azure: 134, GCP: 100)\n\nTOP FAILING CATEGORIES:\n  1. IAM overly permissive policies     (43 findings)\n  2. Encryption not enabled at rest      (38 findings)\n  3. Public network exposure             (29 findings)\n  4. Logging and monitoring gaps         (24 findings)\n  5. Unused credentials and keys         (19 findings)\n\nAUTO-REMEDIATION (Last 7 Days):\n  Findings auto-remediated:  34\n  Manual remediation pending: 51\n  Exceptions approved:        8\n```\n","# Implementing Cloud Security Posture Management\n\n## When to Use\n\n- When establishing continuous security monitoring across AWS, Azure, and GCP environments\n- When compliance requirements demand automated posture assessment against CIS, SOC 2, or PCI DSS\n- When security teams need visibility into cloud misconfigurations across multiple accounts and subscriptions\n- When building a security operations workflow that detects and remediates drift from security baselines\n- When migrating workloads to the cloud and need to enforce security guardrails\n\n**Do not use** for runtime workload protection (use CWPP tools like Falco or Aqua), for application security testing (use DAST\u002FSAST tools), or for network intrusion detection (use cloud-native IDS like GuardDuty or Network Watcher).\n\n## Prerequisites\n\n- Multi-cloud credentials with read-only security audit permissions across all target environments\n- Prowler v3+ installed (`pip install prowler`)\n- ScoutSuite installed (`pip install scoutsuite`)\n- AWS Config, Azure Policy, and GCP Organization Policy enabled in respective environments\n- Central logging destination (S3 bucket, Log Analytics Workspace, or Cloud Storage) for findings aggregation\n- Notification channels configured (Slack, PagerDuty, email) for critical finding alerts\n\n## Workflow\n\n### Step 1: Deploy Cloud-Native CSPM Services\n\nEnable the built-in CSPM capabilities in each cloud provider for baseline posture assessment.\n\n```bash\n# AWS: Enable Security Hub with FSBP and CIS standards\naws securityhub enable-security-hub --enable-default-standards\naws securityhub batch-enable-standards --standards-subscription-requests \\\n  '[{\"StandardsArn\":\"arn:aws:securityhub:::standards\u002Fcis-aws-foundations-benchmark\u002Fv\u002F1.4.0\"}]'\n\n# Azure: Enable Microsoft Defender for Cloud (CSPM tier)\naz security pricing create --name CloudPosture --tier standard\naz security auto-provisioning-setting update --name default --auto-provision on\n\n# GCP: Enable Security Command Center Premium\ngcloud services enable securitycenter.googleapis.com\ngcloud scc settings update --organization=ORG_ID \\\n  --enable-asset-discovery\n```\n\n### Step 2: Run Prowler for Multi-Cloud Assessment\n\nExecute Prowler to perform comprehensive security checks across all three cloud providers.\n\n```bash\n# AWS assessment with all CIS checks\nprowler aws \\\n  --profile production \\\n  -M json-ocsf csv html \\\n  -o .\u002Fprowler-results\u002Faws\u002F \\\n  --compliance cis_1.4_aws cis_1.5_aws\n\n# Azure assessment\nprowler azure \\\n  --subscription-ids SUB_ID_1 SUB_ID_2 \\\n  -M json-ocsf csv html \\\n  -o .\u002Fprowler-results\u002Fazure\u002F \\\n  --compliance cis_2.0_azure\n\n# GCP assessment\nprowler gcp \\\n  --project-ids project-1 project-2 \\\n  -M json-ocsf csv html \\\n  -o .\u002Fprowler-results\u002Fgcp\u002F \\\n  --compliance cis_2.0_gcp\n\n# View summary across all providers\nprowler aws --list-compliance\n```\n\n### Step 3: Run ScoutSuite for Cross-Cloud Comparison\n\nUse ScoutSuite for a unified multi-cloud security assessment with visual reporting.\n\n```bash\n# Scan AWS\npython3 -m ScoutSuite aws --profile production \\\n  --report-dir .\u002Fscoutsuite\u002Faws\u002F\n\n# Scan Azure\npython3 -m ScoutSuite azure --cli \\\n  --all-subscriptions \\\n  --report-dir .\u002Fscoutsuite\u002Fazure\u002F\n\n# Scan GCP\npython3 -m ScoutSuite gcp --user-account \\\n  --all-projects \\\n  --report-dir .\u002Fscoutsuite\u002Fgcp\u002F\n\n# Each produces an HTML report with risk-scored findings\n```\n\n### Step 4: Build Automated Compliance Monitoring Pipeline\n\nCreate a scheduled pipeline that runs CSPM checks daily and routes findings to appropriate channels.\n\n```bash\n# Create a daily Prowler scan with EventBridge + CodeBuild (AWS)\ncat > buildspec.yml \u003C\u003C 'EOF'\nversion: 0.2\nphases:\n  install:\n    commands:\n      - pip install prowler\n  build:\n    commands:\n      - prowler aws -M json-ocsf -o s3:\u002F\u002Fsecurity-findings-bucket\u002Fprowler\u002F$(date +%Y%m%d)\u002F\n      - prowler aws --compliance cis_1.5_aws -M csv -o s3:\u002F\u002Fsecurity-findings-bucket\u002Fprowler\u002Fcompliance\u002F\n  post_build:\n    commands:\n      - |\n        CRITICAL=$(cat output\u002F*.json | grep -c '\"CRITICAL\"')\n        if [ \"$CRITICAL\" -gt 0 ]; then\n          aws sns publish --topic-arn arn:aws:sns:us-east-1:ACCOUNT:security-alerts \\\n            --subject \"Prowler: $CRITICAL critical findings\" \\\n            --message \"Review at s3:\u002F\u002Fsecurity-findings-bucket\u002Fprowler\u002F$(date +%Y%m%d)\u002F\"\n        fi\nEOF\n\n# Schedule with EventBridge\naws events put-rule \\\n  --name daily-prowler-scan \\\n  --schedule-expression \"cron(0 6 * * ? *)\" \\\n  --state ENABLED\n```\n\n### Step 5: Configure Finding Aggregation and Deduplication\n\nAggregate findings from multiple CSPM tools and cloud providers into a unified view.\n\n```python\n# findings_aggregator.py - Normalize and deduplicate CSPM findings\nimport json\nimport hashlib\nfrom datetime import datetime\n\ndef normalize_finding(finding, source):\n    \"\"\"Normalize findings from different CSPM tools to a common format.\"\"\"\n    normalized = {\n        'id': hashlib.sha256(f\"{finding.get('ResourceId','')}{finding.get('CheckId','')}\".encode()).hexdigest()[:16],\n        'source': source,\n        'cloud': finding.get('Provider', 'unknown'),\n        'account': finding.get('AccountId', finding.get('SubscriptionId', '')),\n        'region': finding.get('Region', ''),\n        'resource_type': finding.get('ResourceType', ''),\n        'resource_id': finding.get('ResourceId', ''),\n        'severity': finding.get('Severity', 'INFO').upper(),\n        'status': finding.get('Status', 'FAIL'),\n        'title': finding.get('CheckTitle', finding.get('Title', '')),\n        'description': finding.get('StatusExtended', ''),\n        'compliance': finding.get('Compliance', {}),\n        'remediation': finding.get('Remediation', {}).get('Recommendation', {}).get('Text', ''),\n        'timestamp': datetime.utcnow().isoformat()\n    }\n    return normalized\n\ndef aggregate_findings(prowler_file, scoutsuite_file):\n    findings = {}\n    for file_path, source in [(prowler_file, 'prowler'), (scoutsuite_file, 'scoutsuite')]:\n        with open(file_path) as f:\n            for line in f:\n                raw = json.loads(line)\n                normalized = normalize_finding(raw, source)\n                if normalized['status'] == 'FAIL':\n                    findings[normalized['id']] = normalized\n    return sorted(findings.values(), key=lambda x: {'CRITICAL':0,'HIGH':1,'MEDIUM':2,'LOW':3}.get(x['severity'],4))\n```\n\n### Step 6: Implement Drift Detection and Auto-Remediation\n\nSet up automated responses to configuration drift that violates security baselines.\n\n```bash\n# AWS Config auto-remediation for non-compliant S3 buckets\naws configservice put-remediation-configurations --remediation-configurations '[{\n  \"ConfigRuleName\": \"s3-bucket-public-read-prohibited\",\n  \"TargetType\": \"SSM_DOCUMENT\",\n  \"TargetId\": \"AWS-DisableS3BucketPublicReadWrite\",\n  \"Parameters\": {\n    \"S3BucketName\": {\"ResourceValue\": {\"Value\": \"RESOURCE_ID\"}}\n  },\n  \"Automatic\": true,\n  \"MaximumAutomaticAttempts\": 3,\n  \"RetryAttemptSeconds\": 60\n}]'\n\n# Azure Policy for auto-remediation\naz policy assignment create \\\n  --name \"enforce-storage-encryption\" \\\n  --policy \"\u002Fproviders\u002FMicrosoft.Authorization\u002FpolicyDefinitions\u002F404c3081-a854-4457-ae30-26a93ef643f9\" \\\n  --scope \"\u002Fsubscriptions\u002FSUB_ID\" \\\n  --enforcement-mode Default\n\n# GCP Organization Policy constraint\ngcloud resource-manager org-policies set-policy policy.yaml --organization=ORG_ID\n# policy.yaml: constraint: constraints\u002Fstorage.publicAccessPrevention, enforcement: true\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| CSPM | Cloud Security Posture Management, the practice of continuously monitoring cloud infrastructure for misconfigurations and compliance violations |\n| Configuration Drift | Unintended changes to cloud resource configurations that deviate from the approved security baseline over time |\n| Security Baseline | A documented set of minimum security configuration requirements that all cloud resources must meet |\n| Compliance Framework | A structured set of security controls and requirements (CIS, SOC 2, PCI DSS, NIST) against which cloud configurations are evaluated |\n| Finding Severity | Risk classification of a misconfiguration based on exploitability and potential impact (Critical, High, Medium, Low, Informational) |\n| Auto-Remediation | Automated corrective action that restores a non-compliant resource to its required configuration without manual intervention |\n\n## Tools & Systems\n\n- **Prowler**: Open-source multi-cloud security assessment tool with 300+ checks aligned to CIS, PCI DSS, HIPAA, and NIST\n- **ScoutSuite**: Multi-cloud security auditing tool producing risk-scored HTML reports from API-collected configuration data\n- **AWS Security Hub**: AWS-native CSPM with aggregated findings and compliance standard evaluation\n- **Microsoft Defender for Cloud**: Azure-native CSPM with secure score, regulatory compliance, and workload protection\n- **GCP Security Command Center**: GCP-native security platform with asset inventory, vulnerability scanning, and compliance monitoring\n\n## Common Scenarios\n\n### Scenario: Establishing CSPM for a Multi-Cloud Enterprise\n\n**Context**: An enterprise runs production workloads across AWS (primary), Azure (identity and Microsoft services), and GCP (data analytics). The security team needs unified posture visibility.\n\n**Approach**:\n1. Enable cloud-native CSPM in each provider: Security Hub, Defender for Cloud, SCC\n2. Deploy Prowler scans as daily scheduled jobs in each environment via CI\u002FCD pipelines\n3. Normalize and aggregate findings into a central data lake using the aggregation script\n4. Build dashboards in Grafana or Kibana showing posture scores by cloud, account, and severity\n5. Configure auto-remediation for known-good fixes (public access blocks, encryption enablement)\n6. Route CRITICAL findings to PagerDuty for immediate response and HIGH findings to Jira tickets\n7. Produce weekly compliance reports for executive stakeholders showing trend data\n\n**Pitfalls**: Running CSPM tools with overly broad permissions creates a high-value target. Use dedicated service accounts with read-only permissions and rotate credentials regularly. Different CSPM tools may report the same misconfiguration differently, so deduplication logic must account for varying resource ID formats and finding titles across tools.\n\n## Output Format\n\n```\nCloud Security Posture Management Dashboard\n==============================================\nOrganization: Acme Corp\nAssessment Date: 2026-02-23\nEnvironments: AWS (12 accounts), Azure (8 subscriptions), GCP (5 projects)\n\nPOSTURE SCORES:\n  AWS:   82\u002F100  (+3 from last week)\n  Azure: 76\u002F100  (-1 from last week)\n  GCP:   79\u002F100  (+5 from last week)\n  Overall: 79\u002F100\n\nFINDINGS BY SEVERITY:\n  Critical:  18 (AWS: 7, Azure: 8, GCP: 3)\n  High:      67 (AWS: 28, Azure: 24, GCP: 15)\n  Medium:   234 (AWS: 98, Azure: 87, GCP: 49)\n  Low:      412 (AWS: 178, Azure: 134, GCP: 100)\n\nTOP FAILING CATEGORIES:\n  1. IAM overly permissive policies     (43 findings)\n  2. Encryption not enabled at rest      (38 findings)\n  3. Public network exposure             (29 findings)\n  4. Logging and monitoring gaps         (24 findings)\n  5. Unused credentials and keys         (19 findings)\n\nAUTO-REMEDIATION (Last 7 Days):\n  Findings auto-remediated:  34\n  Manual remediation pending: 51\n  Exceptions approved:        8\n```\n",{"name":5,"tags":24,"author":31,"domain":32,"license":14,"version":33,"nist_csf":34,"subdomain":25,"description":39,"mitre_attack":40},[25,26,27,28,29,30],"cloud-security","cspm","multi-cloud","compliance","prowler","scoutsuite","mahipal","cybersecurity","1.0",[35,36,37,38],"PR.IR-01","ID.AM-08","GV.SC-06","DE.CM-01","Continuously monitor multi-cloud environments (AWS, Azure, GCP) for misconfigurations, compliance violations, and security risks using Prowler, ScoutSuite, AWS Security Hub, Microsoft Defender for Cloud, and GCP Security Command Center. Use for cross-cloud posture monitoring, CIS\u002FSOC 2\u002FPCI DSS compliance, or drift-detection workflows; not for runtime workload protection or application security testing.\n",[41,42,43,44],"T1078.004","T1530","T1537","T1580","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-cloud-security-posture-management","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill implementing-cloud-security-posture-management",{"tool":57,"command":58},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill implementing-cloud-security-posture-management",{"tool":60,"command":61},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill implementing-cloud-security-posture-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-cloud-security-posture-management\u002FSKILL.md",true,[65,69,75,81],{"path":66,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fapi-reference.md","REFERENCE","参考文档",1946,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-cloud-security-posture-management\u002Freferences\u002Fapi-reference.md",{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"scripts\u002Fagent.py","SCRIPT","脚本",7831,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-cloud-security-posture-management\u002Fscripts\u002Fagent.py",{"path":82,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":83,"sourceHtmlUrl":84},"SKILL.es.md",12963,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-cloud-security-posture-management\u002FSKILL.es.md",[86,94,101,108,115,122],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":90,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7BESR1CJ3H5SP9XM8KYJZ9W","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","MIT","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":90,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7BES1YA6R97W7QPMFFM1PED","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":90,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7BERNHYGY035AR00VRT03KE","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":90,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M7BERCK1EAKTWW7R436WAR0J","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":90,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M7BEQZAZAQRTXFJRY7RHV3TY","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":90,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":19},"01M7BEQKJ45K31QK5VRAQSVJCJ","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]