FedRAMP High AC-6(1): Authorize Access to Security Functions

What else in your programme already covers this

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

CIS Controls v8 · 4 controls

CIS-5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts
CIS-6.1 Establish an Access Granting Process
CIS-6.7 Centralize Access Control
CIS-6.8 Define and Maintain Role-Based Access Control

NIST SP 800-53 Rev 5 · 4 controls

NIST800-AC-2 Account management
NIST800-AC-3 Access enforcement
NIST800-AC-6 Least privilege
NIST800-IA-2 Identification and authentication of organizational users

PCI DSS 4.0 · 4 controls

7.2.3 Required privileges are approved by authorized personnel
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.
7.2.5 All application and system accounts and related access privileges are assigned and managed as follows: • Based on the least privileges necessary for the operability of the system or application. • Access is limited
7.3.1 An access control system(s) is in place that restricts access based on a user's need to know and covers all system components

SOC 2 · 4 controls

SOC2-CC5.1 COSO principle 10: Selects and develops control activities to mitigate risks
SOC2-CC6.2 Prior to granting access, registration and authorization processes are established
SOC2-CC6.3 Role-based access and least privilege are enforced
SOC2-CC6.4 Restricts physical access to facilities and protected information assets (for example, data center facilities, back-up media storage, and other sensitive locations) to authorized personnel to meet the entity's objectives

AWS Well-Architected Security Pillar · 3 controls

SEC02-BP06 Employ user groups and attributes
SEC03-BP01 Define access requirements
SEC03-BP02 Grant least privilege access

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

CCM-IAM-05 Least Privilege
CCM-IAM-10 Management of Privileged Access Roles
CCM-IAM-11 CSCs Approval for Agreed Privileged Access Roles

Azure Security Benchmark · 2 controls

ASBv3-AM-4 Limit access to asset management
ASBv3-PA-7 Follow just enough administration (least privilege) principle

C5 (Germany) · 1 control

C5-PSS-09 Authorisation Mechanisms

CMMC 2.0 · 1 control

AC.L2-3.1.5 Least Privilege

NIST Cybersecurity Framework 2.0 · 1 control

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

NIST SP 800-171 Rev 3 · 1 control

03.01.06 Least Privilege - Privileged Accounts

NIST SP 800-172 · 1 control

3.13.2e Introduce Unpredictability into System Operations

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 High have you already done?

FedRAMP High AC-6(1) 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.

If you hold C5 (Germany)29% covered · 291 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. 6 were rejected on the C5 (Germany) pair alone.

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