azure_compliance

Azure Compliance

Multi-Factor Authentication (MFA) should be enabled for all subscription accounts with owner permissions to prevent a breach of accounts or resources.

iam_user_with_owner_permission_on_subscription_mfa_enabled

hipaa_hitrust_v92_11109_01q1organizational

11109.01q1Organizational.57-01.q 01.05 Operating System Access Control

hipaa_hitrust_v92_1116_01j1organizational

1116.01j1Organizational.145-01.j 01.04 Network Access Control

hipaa_hitrust_v92_1121_01j3organizational

1121.01j3Organizational.2-01.j 01.04 Network Access Control

nist_sp_800_53_rev_5_ac_3

Access Enforcement (AC-3)

nist_sp_800_53_rev_5_ia_2

Identification and Authentication (organizational Users) (IA-2)

nist_sp_800_53_rev_5_ia_2_1

Multi-factor Authentication to Privileged Accounts IA-2(1)

pci_dss_v321_requirement_3_2

PCI DSS requirement 3.2

pci_dss_v321_requirement_7_2_1

PCI DSS requirement 7.2.1

pci_dss_v321_requirement_8_3_1

PCI DSS requirement 8.3.1

hipaa_hitrust_v92_1176_01j2organizational

The organization requires a callback capability with re-authentication to verify dial-up connections from authorized locations

Accounts with owner permissions on Azure resources should be MFA enabled

azure

azuread

Run individual configuration, compliance and security controls or full compliance benchmarks for CIS, HIPAA HITRUST, NIST, PCI DSS across all your Azure subscriptions using Powerpipe and Steampipe.

Apache License 2.0

steampipe-mod-azure-compliance

Control: Accounts with owner permissions on Azure resources should be MFA enabled

Description

Usage

SQL

Tags