← Back to blog

Active Directory Security Assessment Playbook for Admins: Standards to Fixes

September 24, 2026
Active Directory Security Assessment Playbook for Admins: Standards to Fixes

An Active Directory security assessment finds where a domain controller, a stale privilege, or a misconfigured trust could let an attacker move from a single compromised laptop to full domain control. It identifies attack paths, privileged exposure, configuration drift, and detection gaps, then delivers a prioritised remediation roadmap and technical evidence pack for the SOC and leadership. The best assessments map findings to Microsoft, NCSC, and CIS guidance, and firms like Solusec deliver that work hands-on rather than through an automated report alone.


TL;DR:

  • Privileged account discovery, including nested group memberships and service account privileges, is among the most critical checks often missed or misconfigured.
  • Remediation should prioritize patching critical vulnerabilities like Zerologon, deploying Windows LAPS, and enforcing MFA on administrative logons within days.
  • Structuring assessments around tiers and assets allows organizations to focus on high-impact findings and set realistic, owner-specific remediation timelines.
  • An expert-led assessment combines manual validation with automated mapping, providing actionable insights and prioritizations, unlike standalone scanner reports.
  • Ongoing assessment and continuous monitoring are essential, as Group Policy drift and privilege creep tend to recur steadily, diminishing the value of one-off audits.

Solusec
solusec.co.uk
Strengthen Your Active Directory Defences
Solusec provides expert-led penetration testing and practical cybersecurity guidance to help identify vulnerabilities before attackers can exploit them.
Get a penetration test quote

Table of Contents

What does an Active Directory security assessment cover?

Scope determines whether an assessment catches the finding that actually matters or misses it entirely. Get the boundaries wrong and you either drown the report in noise or leave a Tier 0 gap unchecked.

A properly scoped Active Directory security audit covers five interlocking areas:

  • Inventory: every user account, service principal, security group, domain controller, trust relationship, and device joined to the domain.
  • Privileged access review: mapping accounts against the Tier model, checking PIM/PAM readiness, and testing emergency break-glass account controls.
  • Configuration hygiene: Group Policy Objects, access control lists, Kerberos delegation settings, and Windows LAPS deployment state.
  • Detection coverage: which logs actually reach the SIEM, and where telemetry gaps leave lateral movement invisible.
  • Vulnerability posture: patch levels against known Active Directory CVEs, including legacy Netlogon exposure.

Securing the identity layer first is deliberate, not arbitrary. Microsoft's Zero Trust guidance treats the identity control plane as phase one of any hardening programme, because every other control (endpoint protection, network segmentation, conditional access) inherits its trust from AD. Harden the perimeter around a compromised domain and you have only slowed the inevitable.

How do you run the assessment phase by phase?

Most failed engagements collapse at the first stage, not the last. Vague scoping produces vague findings, and unauthorised "quick tests" on production domain controllers cause outages that get the whole exercise cancelled. A structured Active Directory penetration testing methodology runs in four phases.

  1. Preparation. Agree scope in writing: which domains, forests, and OUs are in play, who signs off before any exploit validation, and what permissions the assessment team needs (read-only AD access is the floor; some checks require a low-privileged domain account). Isolate collection hosts so tooling never touches production authentication paths directly.
  2. Data collection. Pull AD exports (objects, group memberships, ACLs), GPO backups, Kerberos and security event logs, and, where hybrid identity is in play, Entra ID and PIM configuration reports. Microsoft's own on-demand Active Directory Security Assessment automates much of this collection through the Services Hub, uploading configuration and event data to Log Analytics for scoring.
  3. Analysis. Run automated attack-path mapping to surface routes from low-privilege accounts to Domain Admin, then follow up with manual review, because tooling flags plausible paths, not exploitable ones. Where the engagement is authorised for it, validate select paths with safe, controlled exploitation to confirm real-world risk rather than theoretical exposure.
  4. Reporting. Produce an executive summary for leadership, a technical findings section with reproduction steps for engineers, a short list of tactical quick wins, and a remediation roadmap with named owners and realistic timelines.

Skipping the preparation phase to get to "results faster" is the single most common reason assessments produce findings nobody acts on.

Which technical checks surface the highest-impact findings?

Certain checks find critical risk disproportionately often, and skipping them is how assessments miss the finding that would have stopped a real breach.

  • Privileged discovery. Enumerate nested group memberships (a user three groups deep in Domain Admins is invisible to a flat permissions view), separate permanent privileges from PIM-eligible ones, and flag service accounts with far more access than their function requires.
  • GPO and ACL review. Search for writable ACLs on sensitive objects (a helpdesk group with write access to a Domain Admin's account is a live escalation path), and check GPO precedence for drift that silently reverts a hardening setting applied months earlier.
  • Kerberos and delegation. Unconstrained delegation on a server means any account authenticating to it can be impersonated domain-wide. Resource-based constrained delegation misconfigurations and pass-the-ticket indicators in event logs both point to active or attempted credential theft.
  • Trusts and forest relationships. Weak or legacy trusts, SIDHistory abuse, and shadow admin accounts (users with effective admin rights nobody documented) routinely surface in engagements that specifically test for them.
  • Patch and CVE checks. Zerologon (CVE-2020-1472) remains the reference case for what an unpatched domain controller costs an organisation, and NCSC's alert details both the exploitation artefacts to hunt for and the urgency of remediation.

Pro Tip: Nested group enumeration is the check most tools get wrong. Run it manually at least once per assessment, because flattening group membership by hand is often how you find the access nobody remembers granting.

Evidence collection ties the checks together: capture the specific Event IDs tied to privileged logons, flag anomalous authentication chains (a service account authenticating from a workstation it has never touched), and log lateral movement indicators, because NCSC guidance is explicit that monitoring, patching, and segmentation only work if you can actually see the movement happening.

How should you prioritise and sequence remediation?

Every assessment produces more findings than any team can fix in a week. The organisations that actually reduce risk triage ruthlessly, using one rule above all others: protect Tier 0 assets first, remove standing privileges second, and enforce multi-factor authentication on every admin logon third.

  1. Quick wins (days). Patch critical CVEs immediately, deploy Windows LAPS anywhere it's missing, restrict remote admin interfaces on domain controllers, and require MFA on all administrative logons.
  2. Medium term (weeks to months). Move standing admin rights to just-in-time, PIM-managed access, roll out Privileged Access Workstations for Tier 0 administration, and flatten unnecessary nested group inheritance.
  3. Long term (ongoing). Segment the network around identity boundaries, automate identity lifecycle management so leavers lose access on day one rather than month three, and set a recurring assessment cadence tied into SOC monitoring rather than a one-off audit.

Pro Tip: When presenting remediation to stakeholders, resist the urge to hand over the full findings list. Convert it into three or four workstreams with named owners and dates. A 40-item spreadsheet gets ignored; a four-line roadmap gets funded.

Why an expert-led assessment beats an automated scan alone

CREST accreditation and status as a certification body for Cyber Essentials give Solusec a structural reason to get this right: certifications are earned against independent standards, not marketing copy. Automated scanners are genuinely useful for AD security vulnerability assessment at scale, but they flag plausible attack paths without weighing which asset actually matters, which is why noisy output is the most common practitioner complaint about tool-only reviews. Expert-led assessment adds the context: which Tier 0 asset is genuinely exposed, which finding is theoretical, and what remediation sequence a specific organisation can realistically execute. Typical engagements end with a prioritised roadmap and hands-on remediation support, not just a PDF.

Where to verify this guidance

Every recommendation above maps to a published standard rather than opinion. Microsoft's AD DS tier model defines the privileged access architecture referenced throughout; NCSC's lateral movement guidance sets the detection and segmentation baseline; the Microsoft cloud security benchmark governs the JIT and PIM recommendations; and CIS benchmarks provide the configuration scoring used against domain controllers. These form the primary standards any credible assessment maps to.

Four standards mapped to assessment areas

The gap between checklist compliance and actual risk reduction

Most Active Directory security audit advice online reads like a checklist: patch this, enable that, review the other thing. It's not wrong, exactly, but it misses the harder judgement call, which is deciding what to fix first when you have 200 findings and a Monday deadline.

The gap between checklist compliance and actual risk reduction — overview diagram

The research is consistent on one point that conventional advice underweights: automated tooling generates noise, and the assessments that actually change an organisation's risk exposure are the ones that contextualise every finding by asset criticality before touching the remediation plan. A writable ACL on a marketing distribution list and a writable ACL on a Domain Admin object are the same finding type and wildly different risks. Treating them the same is how remediation budgets get spent on the wrong problem.

The other gap is cadence. A one-off assessment captures a snapshot, but Group Policy drift and privilege creep happen continuously, which means the value of any assessment starts decaying the day it's delivered. If you take one thing from this, prioritise Tier 0 containment and standing privilege removal before anything else on the list, and treat the assessment itself as recurring rather than annual.

— Solusec Admin

Get an expert-led Active Directory security assessment

Some cybersecurity firms run Active Directory security assessments the way this article describes them: preparation, structured collection, manual analysis on top of automated attack-path mapping, and a report split into an executive summary and a technical remediation plan with owners attached. That's the practical difference from a scanner output alone. Clients typically work directly with CREST-accredited testers, not a sales team, so the fixes you get back are proportionate to your environment rather than a generic vendor template.

Solusec

If your organisation needs to demonstrate compliance alongside the technical fix, Solusec's Cyber Essentials certification service (from £320 to £600, one-off, with urgent turnaround available for an additional £100) can run alongside remediation to close both gaps at once. For a full infrastructure or external test that goes beyond AD configuration into exploitable exposure, the penetration testing service covers external IP testing from £3,000 and CMS website testing from £2,500. Get in touch to scope an assessment against your domain and receive a fixed quote before any work begins.

Sources

Reproducibility separates an audit trail from a one-off opinion. If a finding cannot be recreated from the same data six months later, it will not survive a compliance review.

FAQ

What are the main steps of an Active Directory security assessment?

The standard sequence runs preparation and scoping, data collection (AD exports, GPO backups, event logs), analysis using automated attack-path mapping plus manual review, and reporting with an executive summary and technical remediation plan. Microsoft's on-demand assessment automates much of the collection stage, but manual validation is still needed to confirm which paths are genuinely exploitable.

What are the three main types of security assessments for Active Directory?

Most engagements fall into automated vulnerability scanning, configuration and compliance audits against benchmarks like CIS, and full penetration testing that includes authorised exploit validation of attack paths. Solusec's penetration testing service sits in the third category, combining manual attack-path validation with the configuration review covered in this guide.

What are the key security considerations for Active Directory?

The priorities are privileged access control using the Tier model, Kerberos delegation configuration, patch management for known domain controller vulnerabilities, and detection coverage across authentication logs. Microsoft's tier model guidance sets the architectural baseline, while NCSC's lateral movement controls cover monitoring and segmentation.

How much does an Active Directory security assessment cost?

Pricing depends on scope and whether the engagement includes full penetration testing or a configuration-focused audit. Solusec's external IP test starts at £3,000 one-off and its CMS website test at £2,500 one-off, both listed on the penetration testing page, with pricing varying based on scope and specifics of the engagement.

How often should organisations reassess Active Directory security?

Because Group Policy drift and privilege creep build up continuously, a single annual review is a minimum, not a target. Organisations handling sensitive data or under regulatory obligations such as HIPAA, SOX, or GDPR typically benefit from more frequent reviews tied to change management, with continuous monitoring through a SOC filling the gaps between formal assessments.

This article was created with assistance of AI. We never use AI with your data unless given explicit permission.