FedRAMP High AC-2(3): Disable Accounts

What else in your programme already covers this

This control maps to 28 controls across 19 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 · 3 controls

2.2.2 Vendor default accounts are managed as follows: • If the vendor default account(s) will be used, the default password is changed per Requirement 8.3.6. • If the vendor default account(s) will not be used,
8.2.5 Access for terminated users is immediately revoked
8.2.6 Inactive user accounts are removed or disabled within 90 days of inactivity

SOC 2 · 3 controls

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-P4.2 Personal information is retained for only as long as needed

AWS Well-Architected Security Pillar · 2 controls

SEC02-BP05 Audit and rotate credentials periodically
SEC03-BP06 Manage access based on lifecycle

CIS Controls v8 · 2 controls

CIS-5.3 Disable Dormant Accounts
CIS-6.2 Establish an Access Revoking Process

CMMC 2.0 · 2 controls

AC.L2-3.1.1 Authorized Access Control
IA.L2-3.5.6 Identifier Handling

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

CCM-IAM-07 User Access Changes and Revocation
CCM-IAM-08 User Access Review

UK Cyber Essentials · 2 controls

CE-AC.3 Remove or Disable Accounts When No Longer Required
CE-SC.1 Remove or Disable Unused Software

ACSC Essential Eight · 1 control

E8-ADMIN-ML2 Restrict Administrative Privileges (ML2)

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

ANSSI-HYG-06 Organise Joiner, Leaver and Role Change Procedures

Australia My Health Records Act 2012 · 1 control

MYHR-SEC-2 Access controls and user account management

Azure Security Benchmark · 1 control

PA-3 Manage lifecycle of identities and entitlements

C5 (Germany) · 1 control

C5-IDM-03 Locking and withdrawal of user accounts in the event of inactivity or multiple failed logins

HIPAA Security Rule · 1 control

164.308(a)(3)(ii)(C) Termination Procedures (Addressable)

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization

NIST SP 800-171 Rev 3 · 1 control

03.01.01 Account Management

NIST SP 800-53 Rev 5 · 1 control

NIST800-AC-2 Account management

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(3)(ii)(C) Termination Procedures (Addressable)

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-2(3) 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