Skip to content
System hardening
ASD ISMISM-1830

ASD ISM 1830 Central logging of security events for Microsoft AD infrastructure servers

What it says

Security-relevant events for Microsoft AD DS domain controllers, Microsoft AD CS servers, Microsoft AD FS servers and Microsoft Entra Connect servers are centrally logged.

Quoted as published. Everything else on this page is written by Control Stack.

In plain English

Send security-relevant events from AD DS domain controllers and AD CS, AD FS and Entra Connect servers to the central logging facility, not only to local logs.

Security-relevant events from Microsoft AD DS domain controllers, AD CS servers, AD FS servers and Entra Connect servers must be centrally logged, meaning sent to the organisation's central event logging facility rather than kept only on each server. Security-relevant events are those that help detect or investigate misuse, such as logons, account and group changes, configuration changes and each role's own activity, like certificate requests. The control does not list them, so the organisation decides. Every server of these types is covered, including standby and offline ones.

Why it matters

Attacks on these servers, such as a certificate request for another user's identity or directory replication from a computer that is not a domain controller, can leave traces in their logs. An intruder can clear local logs; central copies remain for detection and investigation.

How to implement

  1. Decide which events are security-relevant for each role.

    The control sets no list, so choose what would reveal misuse: logons, privilege use, account, group and configuration changes, plus directory replication requests on domain controllers, certificate requests on AD CS servers (ISM-2132), token issuance on AD FS and synchronisation events on Entra Connect.

  2. Turn on the auditing that generates those events.

    Set advanced audit policy through Group Policy for each server type, add audit entries to directory objects so changes are recorded, and turn on certification authority and AD FS auditing, which each need their own setting besides the audit policy. Size local logs so events survive until forwarded.

  3. Forward events to the central facility from every server.

    Send them through a logging agent or built-in event forwarding to the facility ISM-1405 requires, as soon as possible (ISM-1983) and encrypted (ISM-1984). Include Entra Connect staging servers. For an offline root certification authority, export its logs each time it is used and import them into the facility.

  4. Alert when a server stops sending.

    Compare the facility's log sources with the list of these servers, and raise an alert when any goes quiet. Where a provider runs domain controllers for you, use its log export and confirm it includes security events.

Keep it running

Add each new server of these types as a log source before it goes live, and investigate any source that stops sending. Revisit the event list after upgrades and when new attack techniques against these services are published. ISM-1986 covers analysing the logs.

Evidence and audit

  1. Check 1 of 3What an auditor asks for

    Ask for

    A directory list of domain controllers and enterprise certification authorities, the AD FS farm and Entra Connect server lists, and the log sources registered in the central facility.

    Look at

    Whether every server, including staging and offline ones, is a log source, and whether a sampled server's newest local event has reached the facility.

    Good evidence

    Every server is a log source, an offline certification authority's logs are imported after each use, and each sampled server's newest local security event is present in the facility.

  2. Check 2 of 3What an auditor asks for

    Ask for

    The organisation's list of security-relevant events for each role, and the audit settings applied on a sampled server of each type.

    Look at

    Whether the list covers logons, privilege use, account, group and configuration changes and each role's own activity, and whether the applied settings generate those events.

    Good evidence

    The list covers each of those for every role, and the resultant audit policy and role-level auditing on each sampled server generate every listed event.

  3. Check 3 of 3What an auditor asks for

    Ask for

    Harmless test actions on a sampled server of each type, such as a failed logon, adding a test account to a group and changing a test certificate template or a minor AD FS setting, traced in the central facility.

    Look at

    Whether each action arrives in the facility with its time, account and server.

    Good evidence

    Every test action appears in the central facility with the correct time, account and server.

Mappings

Closest match in ASD Essential Eight: E8-RA-ML2.6, Privileged access events are centrally logged, which this control covers in full and more.

ISO 27001

ISO/IEC 27001: 2 mappings

  • A.8.15LoggingPartially meets
  • A.8.16Monitoring activitiesSupports
Essential Eight

ASD Essential Eight: 5 mappings

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.