Skip to content
Development
Command

/posture-review

Cloud security posture review with compliance gap analysis

From plugin
msp-claude-plugins
39200 skills141 agents200 commands
Install
$ npx -y skills add wyre-technology/msp-claude-plugins --agent claude-code

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/posture-review

Context preview

What this command does when you run it.

Cloud security posture review with compliance gap analysis

Command definition

posture-review.md
description: Cloud security posture review with compliance gap analysis
argument-hint: "[severity] [view_type] [limit]"
arguments: [severity, view_type, limit]

SentinelOne Cloud Security Posture Review

Review cloud security posture across managed client environments. Lists misconfigurations grouped by severity, identifies compliance gaps against industry standards (CIS, SOC 2, PCI DSS, HIPAA), and provides remediation guidance for the most critical findings. Useful for compliance audits, QBR security reporting, and cloud hardening initiatives.

Prerequisites

  • SentinelOne Purple MCP server connected with a valid Service User token
  • MCP tools `list_misconfigurations`, `search_misconfigurations`, and `get_misconfiguration` available
  • Token must be Account or Site level (NOT Global)

Steps

1. **Fetch misconfigurations**

Call `list_misconfigurations` with the specified `severity` filter, `viewType`, and `limit`. Sort by severity descending.

2. **Count by severity**

Aggregate results to show counts of CRITICAL, HIGH, MEDIUM, LOW misconfigurations.

3. **Identify compliance gaps**

Group misconfigurations by compliance standard to show which standards have the most open findings.

4. **Break down by client**

Group by site (client) to show which clients have the worst posture.

5. **Highlight critical findings with remediation**

For CRITICAL and HIGH findings, include the remediation steps and evidence details.

6. **Provide posture improvement recommendations**

Prioritize remediation based on severity, compliance impact, and exploit potential.

Parameters

| Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| | severity | string | No | all | Filter by severity (CRITICAL, HIGH, MEDIUM, LOW) | | view_type | string | No | CLOUD | Domain filter (CLOUD, KUBERNETES, IDENTITY, INFRASTRUCTURE_AS_CODE, SECRET_SCANNING) | | limit | integer | No | 50 | Maximum number of misconfigurations to return |

Examples

Cloud Posture Review

/posture-review

Critical Cloud Findings Only

/posture-review --severity CRITICAL

Kubernetes Posture Review

/posture-review --view_type KUBERNETES

Identity Posture Review

/posture-review --view_type IDENTITY

IaC Security Review

/posture-review --view_type INFRASTRUCTURE_AS_CODE

Exposed Secrets Review

/posture-review --view_type SECRET_SCANNING

Output

Cloud Posture Report

SentinelOne Cloud Security Posture Review
================================================================
Generated: 2026-02-24
Domain:    CLOUD
Total Misconfigurations: 156

Severity Breakdown:
+----------+-------+
| Severity | Count |
+----------+-------+
| CRITICAL | 5     |
| HIGH     | 18    |
| MEDIUM   | 67    |
| LOW      | 66    |
+----------+-------+

Compliance Impact:
+----------------------------+----------+------+--------+------+
| Standard                   | CRITICAL | HIGH | MEDIUM | LOW  |
+----------------------------+----------+------+--------+------+
| CIS AWS 1.5               | 3        | 8    | 25     | 20   |
| CIS Azure 2.0             | 1        | 5    | 18     | 15   |
| SOC 2                     | 4        | 12   | 35     | 30   |
| PCI DSS 3.2.1             | 2        | 6    | 15     | 10   |
| HIPAA                     | 1        | 4    | 12     | 8    |
+----------------------------+----------+------+--------+------+

Clients by Posture Risk:
+----------------------------+----------+------+--------+------+
| Client                     | CRITICAL | HIGH | MEDIUM | LOW  |
+----------------------------+----------+------+--------+------+
| Acme Corporation           | 2        | 5    | 15     | 12   |
| TechStart Inc              | 1        | 4    | 12     | 10   |
| Global Services LLC        | 1        | 3    | 18     | 15   |
| Metro Industries           | 1        | 3    | 10     | 12   |
| Summit Financial           | 0        | 3    | 12     | 17   |
+----------------------------+----------+------+--------+------+

CRITICAL Findings (Immediate Remediation Required):
================================================================

1. S3 Bucket Public Access Enabled
   Client:     Acme Corporation
   Resource:   arn:aws:s3:::acme-backup-2026 (AWS us-east-1)
   Compliance: CIS AWS 1.5, SOC 2, PCI DSS
   MITRE:      T1530 - Data from Cloud Storage
   Remediation:
     1. Navigate to S3 > acme-backup-2026 > Permissions
     2. Enable "Block all public access"
     3. Verify no bucket policies grant public access
     4. Enable S3 access logging

2. Security Group Allows SSH from 0.0.0.0/0
   Client:     Acme Corporation
   Resource:   sg-0abc1234 (AWS us-east-1)
   Compliance: CIS AWS 1.5, SOC 2, PCI DSS
   MITRE:      T1133 - External Remote Services
   Remediation:
     1. Restrict SSH (port 22) to specific IP ranges
     2. Use a bastion host or VPN for remote access
     3. Enable VPC Flow Logs for monitoring

3. Azure Storage Account Without Encryption at Rest
   Client:     TechStart Inc
   Resource:   techstart-files (Azure eastus)
   Compliance: CIS Azure 2.0, HIPAA, PCI DSS
   MITRE:      T1565 - Data Manipulation
   Remediation:
     1. Enable Azure Storage Service Encryption (SSE)
     2. Use customer-managed keys for HIPAA compliance
     3. Enable soft delete and versioning

4. IAM Root Account Without MFA
   Client:     Global Services LLC
   Resource:   AWS Account 123456789012
   Compliance: CIS AWS 1.5, SOC 2, PCI DSS, HIPAA
   MITRE:      T1078 - Valid Accounts
   Remediation:
     1. Enable MFA on the root account immediately
     2. Use hardware MFA token for root (not virtual)
     3. Restrict root account usage to emergencies only

5. Kubernetes Dashboard Exposed to Internet
   Client:     Metro Industries
   Resource:   k8s-dashboard (AKS cluster metro-prod)
   Compliance: CIS Kubernetes 1.6, SOC 2
   MITRE:      T1133 - External Remote Services
   Remedia
Read more
Ships withmsp-claude-plugins

One command to supercharge Claude Code for MSP workflows. Then restart Claude Code. That's it. Documentation: mcp.wyre.ai

Get the whole plugin, auto-invoked
Stats
39
Stars
0
Views
17
Forks
Active
Maintenance
Astro
Language
Apache-2.0
License
1d ago
Last commit
6mo ago
Created

Repo: wyre-technology/msp-claude-plugins