Skip to content

Active Directory Domain Configuration

OU and group structure, shared folder permissions, replication and patch compliance

Active Directory is the oldest thing in most environments and the least often reviewed. It accretes. Departments reorganise and the organisational units do not, people change roles and keep their old group memberships, and leavers stay enabled because disabling an account felt risky at the time.

The library also covers the part most people forget is Active Directory at all: shared folders, the permissions on them, and whether anyone has checked those permissions against what the business agreed to.

What this library checks

  • Organisational unit and security group structure, measured against how the business is organised today
  • Group and departmental membership signed off by the business
  • Domain functional level, and whether it supports the controls layered on top of it
  • Domain controller redundancy, with directory and DNS replication proven
  • DNS forwarders answering queries
  • Stale and unused accounts, reviewed and disabled
  • Shared folder structure by department, the permissions on each, and an audit of real access against the documented intent
  • Departmental drives and printers mapped by policy, not by hand at each desk
  • Patch compliance against a stated minimum for workstations and servers, with every Windows machine inside the patching policy

Evidence you will be asked for

Every check in Spectra Core carries its own evidence. These are the artefacts an auditor, insurer or board most often wants to see for this area.

  • Approved list of users against their groups and departmental units, signed off by the business
  • Documented share structure with the permissions applied to each folder
  • Patch compliance percentages for workstations and servers against the stated minimum

Where this usually goes wrong

Share permissions are the control IT cannot sign off alone. Only the business can say who should see the HR folder, that conversation happens once at setup, and people move departments around the answer for years afterwards.

Run this library against your environment

Every check comes with a risk level, a review frequency, an assignee and a plain-language rationale, so the output reads for leadership as well as for engineers. See the full workflow, or read how internal IT teams and managed service providers use it.

Related libraries

Last updated