Microsoft Defender for Cloud

Connection methods

• Cloud provider API with read-only security roles
• CSPM platform REST API
• Scheduled compliance report exports
• Webhook alerts for critical misconfigurations

Documentation topics

Review the following areas in Microsoft Defender for Cloud admin and product documentation before connecting to ComplAI:

• Admin console setup and service account creation
• API authentication, scopes, and rate limits
• Audit log export and retention settings
• Security hardening and least-privilege configuration

ComplAI integration overview

Microsoft Defender for Cloud integrates with ComplAI to support Propel Ready Solutions's GRC program. Azure-native CSPM with secure score, regulatory compliance, and hybrid coverage. This guide covers product context, the recommended connection process, prerequisites, and verification steps for audit-ready evidence collection.

Last updated: 2026-06-24

GRC evidence available

• Misconfiguration counts by severity
• Compliance benchmark pass/fail rates
• Cloud asset inventory
• Mean time to remediate cloud findings
• Secure score metrics and configuration evidence
• Regulatory compliance metrics and configuration evidence

Prerequisites

• Named integration owner and backup contact at Propel Ready Solutions
• Change request approved per Propel Ready Solutions change management policy
• Network egress allowlisting completed if required by vendor
• ComplAI organization administrator access
• Admin or integration-builder role in Microsoft Defender for Cloud
• Microsoft Defender for Cloud product documentation reviewed (see Documentation topics below)

Integration process

1. Step 1

   Plan Microsoft Defender for Cloud integration scope

   Confirm which Secure score and Regulatory compliance capabilities will be connected first. Start with read-only ingestion before enabling write actions.

2. Step 2

   Connect cloud accounts and subscriptions

   Onboard AWS, Azure, GCP, or Kubernetes clusters to the CSPM platform with read-only security audit roles.

3. Step 3

   Enable compliance benchmarks

   Activate CIS, PCI DSS, ISO 27001, or custom frameworks and baseline current posture scores.

4. Step 4

   Integrate ComplAI via API or exports

   Pull misconfiguration counts, compliance pass rates, and critical findings into ComplAI Assurance and risk dashboards.

5. Step 5

   Define remediation ownership

   Assign cloud account owners and map CSPM alerts to change management and vulnerability SLAs.

6. Step 6

   Mark integration complete in ComplAI

   Update integration status to Connected, attach configuration evidence, and link mapped controls in the Controls library.

GRC benefits

• Cloud misconfiguration evidence for ISO A.8.9 and SOC 2 CC6.6/CC7.1
• Multi-cloud compliance posture for leadership and audit dashboards
• Automated drift detection aligned to change management controls

Related controls

Verification checklist

• ☐Integration credentials stored securely and rotation scheduled
• ☐Test sync completed successfully with sample records
• ☐Error alerting configured for failed sync or API rate limits
• ☐Control mappings documented in ComplAI
• ☐Evidence sample exported and reviewed by control owner
• ☐Runbook link attached to related controls

Troubleshooting