FedRAMP Moderate 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

What else in your programme already covers this

This control maps to 40 controls across 20 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 Data flow diagram of account data
1.4.4 Account data not stored on internet-accessible systems
12.5.2 PCI DSS scope documented and confirmed annually
3.3.1.1 Full track data not stored after authorization
3.3.3 SAD storage by issuers limited
3.2.1 Account data storage is kept to a minimum through implementation of data retention and disposal policies, procedures, and processes that include at least the following: • Coverage for all locations of stored account data.
7.2.4 All user accounts and related access privileges, including third-party/vendor accounts, are reviewed as follows: • At least once every six months. • To ensure user accounts and access remain appropriate based on job function.

NIST Cybersecurity Framework 2.0 · 5 controls

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

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 3 controls

CCM-DSP-03 Data Inventory
CCM-DSP-06 Data Ownership and Stewardship
CCM-DSP-19 Data Location

SOC 2 · 3 controls

SOC2-C1.1 Confidential information is identified and protected during receipt, processing, storage
SOC2-CC6.1 Implements logical access security software, infrastructure and architectures over protected information assets
SOC2-CC6.3 Role-based access and least privilege are enforced

AWS Well-Architected Security Pillar · 2 controls

SEC07-BP01 Understand your data classification scheme
SEC07-BP03 Automate identification and classification

Australia Consumer Data Right - Banking (CDR) · 2 controls

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

GDPR-Art.30 Records of processing activities
GDPR-Art.44 General principle for transfers

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 Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

ANSSI-HYG-04 Identify the Most Sensitive Information and Servers and Maintain a Network Diagram

Australia My Health Records Act 2012 · 1 control

MYHR-CUD-4 Records not held or taken outside Australia

Azure Security Benchmark · 1 control

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

DORA-Art.8 Identification

NIST SP 800-161 Rev 1 · 1 control

161R1-CM-12 Information Location

NIST SP 800-171 Rev 3 · 1 control

03.04.11 Information Location

NIST SP 800-172 · 1 control

3.14.5e Review Persistent Storage and Remove CUI No Longer Needed

NIST SP 800-53 Rev 5 · 1 control

NIST800-CM-12 Information Location. Identify and document the location of [organization-defined] and the specific system components on which the information is processed and stored; Identify and document the users who have access to the system and

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.

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

FedRAMP Moderate CM-12 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP Moderate your existing evidence covers. Hold ISO 27002:2022 and 182 of 323 FedRAMP Moderate controls already carry evidence.

If you hold ISO 27002:202256.3% covered · 141 gaps If you hold PCI DSS 4.051.1% covered · 158 gaps If you hold ISO 27001:202249.8% covered · 162 gaps If you hold NIST SP 800-171 Rev 345.5% covered · 176 gaps If you hold C5 (Germany)37.2% covered · 203 gaps If you hold CMMC 2.035% covered · 210 gaps

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. 348 were rejected on the ISO 27002:2022 pair alone.

See the released pairs, $299 each Browse the graph free