🏛️NIST 800-53 CM-2Rule: NIST-CM-002high

Baseline Configuration

Description

Develop, document, and maintain a current baseline configuration of the system.

⚠️ Risk Impact

Without a documented baseline, there is no signal of drift. Configuration changes accumulate; the team forgets what 'normal' looks like. Auditors test whether you can produce the baseline; staff often can't.

🔍 How EchelonGraph Detects This

NIST-CM-002Automated scanner rule

EchelonGraph's Tier 1 Cloud Scanner automatically checks for this condition across all connected cloud accounts. Violations are flagged as high-severity findings with remediation guidance.

🔧 Remediation

Maintain Infrastructure-as-Code (Terraform/CloudFormation/Pulumi) as the baseline. Treat console mutations as drift. Use AWS Config / GCP Asset Inventory / Azure Resource Graph to detect deviation. Reconcile + remediate.

💀 Real-World Attack Scenario

An engineer manually modified a security group 'for debugging' but forgot to revert. Three months later, a security audit asked 'what does normal look like?'. The team referenced Terraform — which didn't reflect actual state. They spent 2 weeks reconciling drift before they could even begin the audit response.

💰 Cost of Non-Compliance

Drift-related breaches: 38% of cloud incidents (Mandiant M-Trends 2024). FedRAMP CM-2 deficiencies: avg $480K remediation + delayed ATO.

📋 Audit Questions

  • 1.Show the baseline configuration document (or IaC).
  • 2.What percentage of cloud resources are managed by IaC?
  • 3.How is drift detected? Show recent drift remediation.
  • 4.When was the baseline last updated?

🎯 MITRE ATT&CK Mapping

T1078 — Valid AccountsT1562 — Impair Defenses

⚡ Common Pitfalls

  • IaC for new resources but legacy resources unmanaged ('we'll Terraform-import them eventually')
  • Drift detection in audit mode but no remediation routing
  • Updating IaC without re-applying — repository diverges from live state

📈 Business Value

Baseline configuration is the foundation of every Configuration Management activity. Without it, every other CM control operates on assumption rather than evidence.

⏱️ Effort Estimate

Manual

80-200 hours for cluster-wide IaC migration + ongoing maintenance

With EchelonGraph

EchelonGraph detects console mutations + IaC drift in real-time; flags untracked resources

🔗 Cross-Framework References

SOC2-CC8.1ISO27001-A.8.9

Automate NIST 800-53 CM-2 compliance

EchelonGraph continuously monitors this control across all your cloud accounts.

Start Free →