Azure Security Benchmark IM-7: Restrict resource access based on conditions

What else in your programme already covers this

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

FedRAMP High · 6 controls

AC-17 Remote Access
AC-17(1) Monitoring and Control
AC-2(12) Account Monitoring for Atypical Usage
AC-3 Access Enforcement
IA-11 Re-Authentication
IA-3 Device Identification and Authentication

FedRAMP Moderate · 6 controls

AC-17 Remote Access
AC-17(1) Monitoring and Control
AC-2(12) Account Monitoring for Atypical Usage
AC-3 Access Enforcement
IA-11 Re-Authentication
IA-3 Device Identification and Authentication

NIST SP 800-53 Rev 5 · 6 controls

NIST800-AC-17 AC-17 Remote Access
NIST800-AC-24 AC-24 Access Control Decisions
NIST800-AC-3 AC-3 Access Enforcement
NIST800-IA-10 IA-10 Adaptive Authentication
NIST800-IA-11 IA-11 Re-authentication
NIST800-IA-3 IA-3 Device Identification and Authentication

ISO 27002:2022 · 4 controls

5.15 Access control
6.7 Remote working
8.3 Information access restriction
8.5 Secure authentication

PCI DSS 4.0 · 4 controls

7.2.1 7.2.1 Access control model defined
7.3.2 7.3.2 Access control system enforces role-based permissions
8.4.3 8.4.3 MFA for remote access that could reach CDE
7.3.1 7.3.1 Need-to-know access control system covers all components

CIS Controls v8 · 3 controls

CIS-13.5 Manage Access Control for Remote Assets
CIS-3.3 Configure Data Access Control Lists
CIS-6.4 Require MFA for Remote Network Access

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

CCM-HRS-04 Remote and Home Working Policy and Procedures
CCM-IAM-16 Authorization Mechanisms
CCM-UEM-14 Third-Party Endpoint Security Posture

ISO 27001:2022 · 3 controls

5.15 Access control
6.7 Remote working
8.3 Information access restriction

NIST SP 800-171 Rev 3 · 3 controls

03.01.02 Access Enforcement
03.01.12 Remote Access
03.05.02 Device Identification and Authentication

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 2 controls

ANSSI-HYG-07 Authorise Network Connection Only for Managed Equipment
ANSSI-HYG-13 Prefer Strong Authentication Where Possible

C5 (Germany) · 2 controls

C5-PSS-06 Session Management
C5-PSS-09 Authorisation Mechanisms

CMMC 2.0 · 2 controls

AC.L2-3.1.1 Authorized Access Control
AC.L2-3.1.12 Control Remote Access

HIPAA Security Rule · 2 controls

164.308(a)(4)(ii)(B) Access Authorization (Addressable)
164.312(a)(1) Access Control (Standard)

NIST SP 800-161 Rev 1 · 2 controls

161R1-AC-19 Access Control for Mobile Devices
161R1-AC-24 Access Control Decisions

NIST SP 800-172 · 2 controls

3.1.2e Restrict Access to Organization-Owned, Provisioned, or Issued Information Resources
3.5.3e Prohibit Connection of Unknown or Unverified System Components

NIST SP 800-66 Rev 2 · 2 controls

164.308(a)(4)(ii)(B) Access Authorization (Addressable)
164.312(a)(1) Access Control (Standard)

ACSC Essential Eight · 1 control

E8-MFA-ML1 Multi-Factor Authentication - Maturity Level 1

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

ASD37-20 Multi-factor authentication (Essential)

AWS Well-Architected Security Pillar · 1 control

SEC03-BP02 Grant least privilege access

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

SOC 2 · 1 control

SOC2-CC6.1 CC6.1 Logical access security over protected information assets

UK Cyber Essentials · 1 control

CE-SC.6 Multi-Factor Authentication for Cloud Services

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 Azure Security Benchmark have you already done?

Azure Security Benchmark IM-7 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.

If you hold NIST SP 800-53 Rev 583.5% covered · 14 gaps If you hold FedRAMP Moderate78.8% covered · 18 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.172.9% covered · 23 gaps If you hold ISO 27002:202269.4% covered · 26 gaps If you hold C5 (Germany)65.9% covered · 29 gaps If you hold ISO 27001:202261.2% covered · 33 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. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

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