FedRAMP High
CM - Configuration Management

FedRAMP High CM-12: Information Location (CM-12)

Information Location. a. Identify and document the location of [Assignment: organization-defined information] and the specific system components on which the information is processed and stored; b. Identify and document the users who have access

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 42 controls across 22 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

PCI DSS 4.0 · 7 controls

  • 1.2.4 1.2.4 Accurate data-flow diagram for account data
  • 1.4.4 1.4.4 Cardholder data stores not reachable from untrusted networks
  • 12.5.2 12.5.2 Annual and change-driven scope confirmation
  • 3.3.1.1 3.3.1.1 Full track data not retained after authorization
  • 3.3.3 3.3.3 Issuer SAD storage limited, justified and encrypted
  • 3.2.1 3.2.1 Data retention and disposal minimise stored account data
  • 7.2.4 7.2.4 User accounts and privileges reviewed every six months
  • NIST-CSF-ID.AM-01 Inventories of hardware managed by the organization are maintained
  • NIST-CSF-ID.AM-02 Inventories of software, services, and systems managed by the organization are maintained
  • NIST-CSF-ID.AM-07 Inventories of data and corresponding metadata for designated data types are maintained
  • NIST-CSF-ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles
  • NIST-CSF-PR.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties

SOC 2 · 3 controls

  • SOC2-C1.1 C1.1 Identifying and maintaining confidential information
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties
  • SEC07-BP01 Understand your data classification scheme
  • SEC07-BP03 Automate identification and classification
  • AUCDR-IS-3 Securely manage information assets over their lifecycle
  • AUCDR-IS-STEP2 Step 2 - Define the boundaries of the CDR data environment

CIS Controls v8 · 2 controls

  • CIS-3.2 Establish and Maintain a Data Inventory
  • CIS-3.8 Document Data Flows

GDPR · 2 controls

ISO 27001:2022 · 2 controls

  • 5.9 Inventory of information and other associated assets
  • 8.3 Information access restriction

ISO 27002:2022 · 2 controls

  • 5.18 Access rights
  • 5.9 Inventory of information and other associated assets
  • ANSSI-HYG-04 Identify the Most Sensitive Information and Servers and Maintain a Network Diagram
  • MYHR-CUD-4 Records not held or taken outside Australia
  • ASBv3-DP-1 Discover, classify, and label sensitive data

C5 (Germany) · 1 control

  • C5-PSS-12 Locations of Data Processing and Storage

DORA · 1 control

ISO 27701:2019 · 1 control

  • 6.5.2 Information classification

NIST SP 800-172 · 1 control

  • 3.14.5e Review Persistent Storage and Remove CUI No Longer Needed
  • CM-12 CM-12 Information Location
  • CM-12 CM-12 Information Location

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in CM - Configuration Management

You are reading one control. How much of FedRAMP High have you already done?

FedRAMP High CM-12 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP High your existing evidence covers. Hold C5 (Germany) and 119 of 410 FedRAMP High controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 6 were rejected on the C5 (Germany) pair alone.

Query this from an agent

The graph holds this control, the 42 it maps to, and the evidence behind each claim, over MCP and REST.