๐ŸขActive Directoryโ˜๏ธAzure Entra IDComplianceConfigMonitoring

AD and Azure Compliance: Mapping NIS2, ISO 27001 and CIS to Real Controls

NIS2, ISO 27001, CIS Controls โ€” compliance requirements map to specific AD and Azure controls. Learn how to assess your environment and close compliance gaps efficiently.

ES
EtcSec Security Team
6 min read
AD and Azure Compliance: Mapping NIS2, ISO 27001 and CIS to Real Controls

What Is AD Security Compliance?

Security compliance frameworks โ€” NIS2, ISO 27001, SOC 2, CIS Controls, ANSSI โ€” define baseline security requirements for identity infrastructure. For organizations running Active Directory or Azure Entra ID, these frameworks translate into concrete technical controls: password policies, privileged access management, audit logging, MFA enforcement, and vulnerability management.

The challenge is that compliance requirements are often vague while the technical controls needed to meet them are specific. "Implement strong authentication" in a NIS2 requirement maps to a concrete list of AD and Azure settings. This article bridges that gap โ€” mapping the most common compliance requirements to the specific Active Directory and Azure controls that satisfy them.

โ„น๏ธ Note: Compliance is not the same as security. A compliant environment can still be compromised. But the controls required for compliance โ€” when properly implemented โ€” significantly reduce the attack surface covered throughout this blog.


How It Works

Compliance audits evaluate your environment against a defined control set. For identity infrastructure, auditors typically examine:

  • Password and authentication policies โ€” minimum length, complexity, MFA enforcement
  • Privileged access controls โ€” who has admin rights, how access is granted and reviewed
  • Audit and monitoring โ€” what events are logged, how long they are retained, who reviews them
  • Vulnerability management โ€” how quickly known vulnerabilities are remediated
  • Access lifecycle management โ€” how user access is provisioned, reviewed, and revoked

Each control maps to specific AD and Azure settings โ€” and each setting is something EtcSec audits automatically.


Compliance Framework Mapping

NIS2 Directive (EU, 2024)

NIS2 requires essential and important entities to implement appropriate technical measures for identity security. Key requirements:

NIS2 RequirementAD/Azure ControlEtcSec Check
Multi-factor authenticationMFA for all privileged accountsCA_NO_MFA_REQUIREMENT, PA_GLOBAL_ADMIN_NOT_MFA
Access control policiesLeast privilege, privileged access managementEXCESSIVE_PRIVILEGED_ACCOUNTS, PA_PIM_NOT_ENABLED
Password policiesMinimum length, complexity, rotationPASSWORD_POLICY_WEAK, PASSWORD_NEVER_EXPIRES
Incident detectionAudit logging, SIEM integrationMonitoring category checks
Supply chain securityThird-party and guest access controlsGUEST_INVITATION_UNRESTRICTED, B2B_CROSS_TENANT_OPEN

CIS Controls v8

The CIS Controls provide prioritized security actions. Identity-related controls:

CIS ControlRequirementAD Implementation
CIS 5Account ManagementDisable stale accounts, enforce account lifecycle
CIS 6Access Control ManagementLeast privilege, privileged access workstations
CIS 12Network Infrastructure ManagementKerberos encryption, NTLM restrictions
CIS 17Incident Response ManagementAudit policy, log retention, SIEM

ISO 27001:2022

ISO 27001 Annex A controls relevant to AD:

ControlDescriptionAD Mapping
A.5.15Access controlRBAC implementation, group membership governance
A.5.16Identity managementAccount lifecycle, offboarding procedures
A.5.17Authentication informationPassword policy, MFA
A.5.18Access rightsPrivileged access review, least privilege
A.8.2Privileged access rightsPAW, PIM, DA account governance
A.8.5Secure authenticationMFA, Kerberos AES, NTLMv2 only

ANSSI Recommendations (France)

ANSSI's AD hardening guide defines specific technical requirements:

# ANSSI recommends: AES-only Kerberos encryption
Set-ADDefaultDomainPasswordPolicy -Identity corp.local -KerberosEncryptionType AES128,AES256

# ANSSI recommends: Disable RC4 fallback
Set-ADUser krbtgt -Replace @{msDS-SupportedEncryptionTypes=24}

# ANSSI recommends: Enable Protected Users for all admins
Add-ADGroupMember -Identity "Protected Users" -Members (Get-ADGroupMember "Domain Admins")

The Compliance Gap Assessment

Step 1 - Baseline Your Current State

# Quick compliance baseline โ€” password policy
Get-ADDefaultDomainPasswordPolicy | Select-Object MinPasswordLength, ComplexityEnabled, MaxPasswordAge

# MFA status (Azure โ€” requires Graph API)
Connect-MgGraph -Scopes "Policy.Read.All"
Get-MgIdentityConditionalAccessPolicy | Where-Object {$_.State -eq "enabled"} |
    Select-Object DisplayName, State

# Audit policy status
auditpol /get /category:"Account Logon","DS Access","Account Management" | Select-String "Success|Failure"

Step 2 - Map Gaps to Framework Controls

# Generate a compliance gap report
$checks = @{
    "Min password length >= 12"     = (Get-ADDefaultDomainPasswordPolicy).MinPasswordLength -ge 12
    "Password complexity enabled"   = (Get-ADDefaultDomainPasswordPolicy).ComplexityEnabled
    "Max password age <= 90 days"   = (Get-ADDefaultDomainPasswordPolicy).MaxPasswordAge.Days -le 90
    "DS Changes audit enabled"      = (auditpol /get /subcategory:"Directory Service Changes") -match "Success"
    "Kerberos audit enabled"        = (auditpol /get /subcategory:"Kerberos Authentication Service") -match "Success"
}

$checks.GetEnumerator() | ForEach-Object {
    [PSCustomObject]@{
        Control = $_.Key
        Status  = if ($_.Value) { "PASS" } else { "FAIL" }
    }
} | Format-Table -AutoSize

Step 3 - Prioritize and Remediate

Prioritize by risk impact, not by compliance checkbox:

  1. Critical: MFA not enforced, DCSync capable accounts, unconstrained delegation
  2. High: Weak password policy, no audit logging, excessive privileged accounts
  3. Medium: Stale accounts, missing LAPS, no fine-grained password policies
  4. Low: Administrative naming conventions, documentation gaps

Detection

Compliance monitoring requires continuous assessment, not point-in-time audits.

Continuous Compliance Checks

# Schedule weekly: check for new DA members added without approval
$cutoff = (Get-Date).AddDays(-7)
Get-ADGroup "Domain Admins" -Properties Members, whenChanged |
    Where-Object {$_.whenChanged -gt $cutoff} |
    Select-Object Name, whenChanged

# Monthly: accounts with no activity in 90 days
Get-ADUser -Filter {Enabled -eq $true -and LastLogonDate -lt (Get-Date).AddDays(-90)} |
    Select-Object SamAccountName, LastLogonDate | Measure-Object | Select-Object Count

Remediation

๐Ÿ’ก Quick Win: Run a CIS benchmark self-assessment using the free CIS-CAT Lite tool against your Domain Controllers. It produces a scored report with specific remediation steps.

Priority Remediation Sequence

  1. Enable MFA for all privileged accounts (Azure: Conditional Access; AD: use smart cards or FIDO2)
  2. Enable audit logging โ€” Advanced Audit Policy on all DCs
  3. Fix password policy โ€” minimum 14 chars, complexity, 90-day max age
  4. Remove excessive DA members โ€” audit and reduce to minimum
  5. Deploy LAPS โ€” eliminate shared local admin passwords
  6. Disable stale accounts โ€” automate with a weekly scheduled task
  7. Enable AES-only Kerberos โ€” disable RC4 fallback

How EtcSec Detects This

EtcSec maps its 426 vulnerability checks directly to compliance framework requirements. Every finding in an EtcSec report includes:

  • The specific misconfiguration detected
  • The risk level (Critical/High/Medium/Low)
  • The compliance frameworks affected (NIS2, CIS, ISO 27001, ANSSI)
  • Step-by-step remediation guidance

The Compliance category in EtcSec reports aggregates findings by framework, allowing you to generate a compliance gap report directly from your AD audit โ€” without a separate assessment tool.

โ„น๏ธ Note: EtcSec maps all findings to compliance frameworks automatically. Run a free audit to see your compliance posture across NIS2, CIS Controls, and ISO 27001.

Related articles: AD Security Monitoring | Active Directory Password Security

EtcSec

ยฉ 2026 EtcSec. All rights reserved.

AD & Azure Compliance: NIS2, ISO 27001, CIS Controls | EtcSec โ€” EtcSec Blog | EtcSec