cm-12-information-location

name	CM-12_information-location
description	Identify and document the location of [organization-defined] and the specific system components on which the information is processed and stored;
category	configuration
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","cm-12","cm"]
tech_stack	["aws","azure","gcp","linux","windows"]
cwe_ids	["CWE-16"]
chains_with	["AC-2","AC-3","AC-4","AC-6","AC-23","CM-8","PM-5","RA-2","SA-4","SA-8"]
prerequisites	[]
severity_boost	{"AC-2":"Chain with AC-2 for comprehensive security coverage","AC-3":"Chain with AC-3 for comprehensive security coverage","AC-4":"Chain with AC-4 for comprehensive security coverage"}

CM-12 Information Location

High-Level Description

Family: Configuration Management (CM) Framework: NIST SP 800-53 Rev 5

Information location addresses the need to understand where information is being processed and stored. Information location includes identifying where specific information types and information reside in system components and how information is being processed so that information flow can be understood and adequate protection and policy management provided for such information and system components. The security category of the information is also a factor in determining the controls necessary to protect the information and the system component where the information resides (see FIPS 199 ). The location of the information and system components is also a factor in the architecture and design of the system (see SA-4, SA-8, SA-17).

What to Check

• Verify CM-12 Information Location is documented in SSP
• Validate all 3 control requirements are implemented
• Confirm control is operating effectively
• Review evidence of continuous monitoring for CM-12

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for CM-12 implementation details. Verify the organization has documented how this control is satisfied.

Step 2: Validate Implementation

# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly

# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null

Step 3: Test Operating Effectiveness

Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.

Tools

Tool	Purpose	Usage
cloud-audit-mcp	Check configuration baselines	cloud_audit_config
AWS CLI	Review Config rules	aws configservice describe-config-rules

Remediation Guide

Control Statement