ACSC recommended prioritised mitigations
Where a security update cannot be immediately applied, the ACSC recommends organisations implement additional mitigations to prevent immediate exploitation. The ACSC recommends organisations ensure servers have completely applied the update, through a system reboot.
Where organisations cannot implement patching and hotfixes in a timely manner (such as in certain Critical Infrastructure environments), organisations should ensure logging is enabled for events documented below.
Organisations should ensure logging is enabled for the following events:
- Event ID 4624; 4742– An account was successfully logged on, or A computer account was changed;
- Events that contain the following fields should be assessed, and where possible diagnosed. Note that legitimate, legacy devices may utilise this functionality.
- Security ID: ANONYMOUS LOGON
- Account Name: ANONYMOUS LOGON
- Account Domain: NT AUTHORITY
Note: A computer account change is not needed for the exploit to be successful – It is possible for multiple exploits to be chained together to trigger this vulnerability without requiring Domain Controller password modification.
If a system is patched, monitor:
- Event ID 5827, 5828, and 5829 – Events related to insecure connection attempts that are denied;
- Event ID 5830, and 5831 – Events related to insecure connection attempts that are successful.
More details of specific post-patch Event IDs are available in Microsoft’s Mitigation Guidance.
ACSC recommended additional mitigations
Beyond the key mitigations above, the ACSC strongly recommends implementing the remainder of the ACSC Essential Eight Mitigation Strategies. Organisations that follow the ACSC’s Essential 8 Mitigation Strategies and implement immediate system patching are protected from exploitation of this vulnerability. The ACSC recommends organisations verify that mitigations are applied. Microsoft has published specific security update details related to this vulnerability.
Due to the nature of this vulnerability, the ACSC recommends organisations at greater risk of exploit implement additional Defence-in-depth measures to ensure robust protection against exploitation. This vulnerability may allow adversaries to leverage external access for administrative domain credential compromise. Where external access is not possible, adversaries can utilise this vulnerability to trivially pivot throughout the target organisation’s network once a device is compromised through other means, or introduced to the network.
- Implement robust defence and detection measures at network boundaries, including:
- Ensuring all administrative access protocols, ports, and Domain Controller access is not available externally, and where possible, not available via an organisations DMZ;
- Most recent firewall products will be able to perform Deep Packet Inspection to detect network traffic that is attempting to exploit this vulnerability.
- Implement additional protection mechanisms between domain controllers and user devices:
- Domain controllers should be actively defended from untrusted devices;
- Domain controller logs demonstrating documented activity should be immediately assessed for vulnerability or compromise.
- Enable “Enforcement Mode” immediately:
- Microsoft’s Change Management Guidance provides details for organisations to implement “Enforcement Mode” immediately;
- All legacy or non-compliant devices should be assessed, and eliminated from the network where possible.
If you have questions about this advice or have indications that your environment has been compromised, contact the ACSC or calling 1300 CYBER1 (1300 292 371).
Becoming an ACSC Partner
The ACSC encourages all eligible organisations to become an ACSC Partner. As a partner, you will automatically receive threat intelligence, consisting of context-rich, actionable and timely information in a variety of formats, including advisories and automated indicator sharing.