Azure Security Benchmark
Identity Management

Azure Security Benchmark ASBv3-IM-9: Secure user access to existing applications

Govern user access to legacy and non-native applications in hybrid environments using solutions such as an access security broker, application proxy or single sign-on.

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

What else in your programme already covers this

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

NIST SP 800-53 Rev 5 · 3 controls

FedRAMP High · 2 controls

  • AC-17(3) Managed Access Control Points
  • IA-8 Identification and Authentication (Non-Organizational Users)

FedRAMP Moderate · 2 controls

  • AC-17(3) Managed Access Control Points
  • IA-8 Identification and Authentication (Non-Organizational Users)

HIPAA Security Rule · 1 control

ISO 27002:2022 · 1 control

  • 8.3 Information access restriction
  • 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
  • 161R1-IA-8 Identification and Authentication (Non-Organizational Users)

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 Identity Management

You are reading one control. How much of Azure Security Benchmark have you already done?

Azure Security Benchmark ASBv3-IM-9 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Azure Security Benchmark your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 71 of 85 Azure Security Benchmark 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 13 it maps to, and the evidence behind each claim, over MCP and REST.