Why MCM
Accounts & Supported Providers
How MCM connects to cloud and infrastructure providers, and which providers are supported.
An account in MCM is a credential-backed connection to a cloud provider, source control system, container registry, or host. Connecting an account is a one-time step — every MCM module (Discovery, FinOps, Governance, SecOps, and Orchestration) then uses that connection without any per-module credential setup.
MCM provides a guided onboarding wizard for each provider type, with permission templates and step-by-step validation. Each connected account shows a live connection status — Active, Warning, or Failed — so credential issues are visible before they cause module outages. Accounts can be labelled with environment tags (Production, Staging, Development) that carry through to all modules.
| Provider | Credential Type | Modules Unlocked |
|---|
 AWS | IAM Role (cross-account assumed role) | Discovery, FinOps, Governance, SecOps, Orchestration |
 Azure | Service Principal (App Registration + client secret) | Discovery, FinOps, Governance, SecOps, Orchestration |
| Provider | Credential Type | Modules Unlocked |
|---|
 GitHub | Personal Access Token or GitHub App | Discovery (repos, orgs), SecOps (code scanning) |
| Provider | Credential Type | Modules Unlocked |
|---|
 Docker Hub | Username + Access Token | Discovery (images), SecOps (container scanning) |
| Docker (self-hosted) | Docker socket or daemon API | Discovery (containers), SecOps (container scanning) |
| Provider | Credential Type | Modules Unlocked |
|---|
 Ubuntu | SSH key or agent-based (Wazuh agent) | Discovery (hosts), Governance (host policies), SecOps (host scanning) |
