Sign in
Menu
Sign up
Docs

Azure subscriptions should not have guest accounts with read permissions

External accounts with read privileges should be removed from your subscription in order to prevent unmonitored access. The Azure Policy check is named "Guest accounts with read permissions on Azure resources should be removed".

External accounts with read privileges should be removed from your subscription in order to prevent unmonitored access.

What this control checks

Guest accounts with read permissions on Azure resources should be removed

Common pitfalls

Effect can be Disabled

The effect parameter has the allowed values AuditIfNotExists and Disabled. The effect parameter has the default value AuditIfNotExists.

Audit evidence

Evidence that deployed resources meet this control: Azure Policy compliance results for the built-in policy definition "Guest accounts with read permissions on Azure resources should be removed" (e9ac8f8e-ce22-4355-8f04-99b911d6be52); PowerPipe control azure_compliance.control.iam_external_user_with_read_permission.

Framework-specific interpretation

NIST SP 800-53 Rev 5: Mapped to AC-2 (Account Management).

NIST Cybersecurity Framework v2.0: Mapped to GV.OC-02 (Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk...) and PR.AA-01 (Identities and credentials for authorized users, services, and hardware are managed by the organization.).

FedRAMP Moderate Baseline Rev 4: Mapped to AC-2 (Account Management).

Framework mappings

The clauses this control is mapped to in each framework.

NIST SP 800-53 Rev 5

  • AC-2 Account Management

NIST Cybersecurity Framework v2.0

  • GV.OC-02: Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and considered.
  • PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization.

FedRAMP Moderate Baseline Rev 4

  • AC-2 (3): Disable Inactive Accounts

NIST SP 800-171 Rev 2

  • 3.1.1 Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems)
  • 3.1.2: Limit system access to the types of transactions and functions that authorized users are permitted to execute.

RBI IT Framework for NBFCs

  • 3.1.a Identification and Classification of Information Assets
  • 3.1.c Role based Access Control
  • 3.1.f Maker-checker

CMMC 2.0 Level 2

  • AC.L1-3.1.1 Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems)
  • AC.L1-3.1.2 Limit system access to the types of transactions and functions that authorized users are permitted to execute

FedRAMP High

  • AC-2 Account Management

PCI DSS v3.2.1

  • 7.2.1 Confirm that access control systems are in place on all system components
  • 8.1.2 Control addition, deletion, and modification of user IDs, credentials, and other identifier objects
  • 8.1.5: Manage IDs used by thid parties to access, support, or maintain system components via remote access. Remote access are as follows: - Enabled only during the time period needed and disabled when not in use. - Monitored when in use.
  • Do not store sensitive authentication data after authorization (even if encrypted)
  • Incorporate multi-factor authentication for all non-console access into the CDE for personnel with administrative access

Tool mappings

Use these identifiers to cross-reference this control across tools, reports, and evidence.

  • Compliance.tf Control: iam_external_user_with_read_permission
  • Powerpipe Control: azure_compliance.control.iam_external_user_with_read_permission
  • Azure Policy Definition: e9ac8f8e-ce22-4355-8f04-99b911d6be52

Last reviewed: 2026-10-13

View all Azure controls →

On this page

Ask AI about this

Help improve this page