ASD Strategies to Mitigate Cyber Security Incidents
Limiting the Extent of Cyber Security Incidents

ASD Strategies to Mitigate Cyber Security Incidents ASD37-21: Disable local administrator accounts (Excellent)

Disable local administrator accounts or assign unique, complex, unpredictable passphrases to each, using a tool such as Microsoft LAPS.

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

What else in your programme already covers this

This control maps to 52 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.

  • ANSSI-HYG-05 Maintain an Exhaustive Inventory of Privileged Accounts
  • ANSSI-HYG-08 Identify Each Person by Name and Separate User and Administrator Roles
  • ANSSI-HYG-10 Define and Verify Password Selection and Sizing Rules
  • ANSSI-HYG-12 Change Default Authentication Elements on Equipment and Services

CMMC 2.0 · 4 controls

FedRAMP High · 4 controls

  • AC-2(9) Restrictions on Use of Shared and Group Accounts
  • AC-6 Least Privilege
  • IA-2 Identification and Authentication (Organizational Users)
  • IA-5 Authenticator Management

FedRAMP Moderate · 4 controls

  • AC-2(9) Restrictions on Use of Shared and Group Accounts
  • AC-6 Least Privilege
  • IA-2 Identification and Authentication (Organizational Users)
  • IA-5 Authenticator Management

UK Cyber Essentials · 4 controls

  • CE-FW.2 Change Default Firewall Passwords
  • CE-SC.1 Remove or Disable Unused Software
  • CE-SC.2 Change Default Passwords on Devices and Software
  • CE-SC.5 Password-Based Authentication Quality
  • IM-1 Use centralized identity and authentication system
  • PA-1 Separate and limit highly privileged/administrative users
  • PA-2 Avoid standing access for user accounts and permissions

NIST SP 800-171 Rev 3 · 3 controls

NIST SP 800-53 Rev 5 · 3 controls

PCI DSS 4.0 · 3 controls

  • 2.2.2 2.2.2 Vendor default accounts managed
  • 8.2.2 8.2.2 Shared and generic IDs only by exception
  • 8.6.2 8.6.2 No hard-coded passwords for interactive system accounts

C5 (Germany) · 2 controls

  • C5-IDM-03 Locking and withdrawal of user accounts in the event of inactivity or multiple failed logins
  • C5-IDM-06 Privileged access rights

CIS Controls v8 · 2 controls

  • CIS-4.7 Manage Default Accounts on Enterprise Assets and Software
  • CIS-5.2 Use Unique Passwords

HIPAA Security Rule · 2 controls

ISO 27001:2022 · 2 controls

  • 5.17 Authentication information
  • 8.2 Privileged access rights

ISO 27002:2022 · 2 controls

  • 5.17 Authentication information
  • 8.2 Privileged access rights
  • NIST-CSF-PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization
  • 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-66 Rev 2 · 2 controls

  • E8-ADMIN-ML2 Restrict Administrative Privileges (ML2)
  • SEC01-BP02 Secure account root user and properties

SOC 2 · 1 control

  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties

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 Limiting the Extent of Cyber Security Incidents

You are reading one control. How much of ASD Strategies to Mitigate Cyber Security Incidents have you already done?

ASD Strategies to Mitigate Cyber Security Incidents ASD37-21 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ASD Strategies to Mitigate Cyber Security Incidents your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 32 of 37 ASD Strategies to Mitigate Cyber Security Incidents 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. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

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