Security & Compliance

    Active Directory analysed and hardened, with findings and a plan of measures.

    We check your on-premises Active Directory for attack paths, harden domain controllers, admin accounts and policies and deliver a findings report and a plan of measures, as a one-off or as a monthly service.

    For IT leads who run an on-premises Active Directory alongside Entra ID, with file servers, business applications or group policies.

    • Active Directory
    • Windows Server 2025
    • Group Policy
    • Windows LAPS
    • Microsoft Defender for Identity
    • PingCastle
    In a vault of Chillon Castle a technician checks the Active Directory structure on a laptop, a coffee mug, a notebook with the CNEXT logo, a ticked list and a locked filing cabinet beside him
    01

    A service account with Domain Admin since 2014

    The analysis runs on Tuesday, the finding is in the report on Thursday: a backup service account has held Domain Admin rights since 2014, its password never expires, and the backup server it signs in to still allows NTLMv1. The plan of measures lists the case with its severity, the responsible person and the way out: a group managed service account, rights only on the backup servers, NTLMv1 switched off, re-test after two weeks. Four weeks later the re-test shows the path closed.

    02

    Check, harden, prove

    Attackers get ahead through identities: through accounts that may do too much, through paths from an ordinary user to Domain Admin and through settings left over from earlier years. We check your Active Directory the way an attacker sees it and implement every measure with your IT, first in a test group, then for everyone. What you deliberately keep as it is, we record as a justified exception.

    • Attack paths and rightsWe read groups, delegations, permissions and sign-ins and show every path from a user account to Domain Admin, with tools such as PingCastle, Purple Knight and BloodHound.Result: a list of paths ordered by the attacker's effort, with the step that closes each one.
    • Privileged accountsDomain Admins, service accounts with admin rights, accounts whose passwords never expire, Kerberos weaknesses such as unconstrained delegation and RC4.Result: a tier model with Tier 0, 1 and 2, one account per person and level, service accounts as group managed service accounts.
    • Domain controllersOperating system and patch level, LDAP signing and channel binding, SMB signing, NTLM restriction, time sync, system state backup and a rehearsed restart.Result: domain controllers on a hardened baseline, documented per setting.
    • Group policiesWe compare your policies with the Microsoft security baselines, remove orphaned and contradictory policies and introduce Windows LAPS for local admin passwords.Result: policies you can read, with one baseline per device type.
    • MonitoringMicrosoft Defender for Identity on the domain controllers, audit policies for account changes and sign-ins, alerts in the Defender portal to the people who respond.Result: attacks on the directory are reported before they reach Domain Admin.
    • Connection to the cloudWhich accounts are synchronised, where Microsoft Entra Connect runs and who is admin on it belongs in the same check.Result: the handover points between Active Directory and Entra ID are known and hardened.
    03

    What we need before the analysis

    Read access to the directory for the analysis and an admin account of your IT with which we implement the measures together; we work in your environment, and your data stays with you. An overview of domains, sites and service accounts as far as it exists, one person in your IT who approves changes and works on the measures with us, and one maintenance window per wave.

    04

    What you hold at the end

    A findings report with every finding, its severity, where it was found and the recommended way out, a plan of measures with owners and deadlines that is updated after every wave, and a re-test that shows which paths are closed. As a monthly service you also get: a check after every Patch Tuesday, maintained baselines, a monthly report with trend and open items and a person at CNEXT who advises your IT on changes to the directory.

    What you receive from us

    The documents we work with.

    Three documents accompany the work on the directory: the findings report after the analysis, the plan of measures for implementation and, in the monthly service, the monthly report. Shown here as samples with invented findings.

    Findings report

    Sample

    Active Directory findings report

    Customer
    Muster AG, Bern (fictional)
    Scope
    Forest muster.local, 2 domains, 4 domain controllers, 184 users
    Analysed on
    13 October 2026
    Tools
    PingCastle 3.3, Purple Knight 5, BloodHound CE, Microsoft security baselines
    • 3critical findings
    • 7high findings
    • 11medium findings
    • 4paths to Domain Admin

    Summary

    The directory is in good working order but carries decisions from 2014 to 2019 forward: service accounts with Domain Admin rights, NTLMv1 on two servers and one domain controller on Windows Server 2016. Four paths lead from an ordinary user account to Domain Admin; two of them can be closed with one change each.

    No.FindingSeverityLocationRecommendation
    AD-01Service account svc_backup is a member of Domain Admins, password without expiry since 2014CriticalOU Service Accounts, group Domain AdminsGroup managed service account, rights only on backup servers
    AD-02Unconstrained Kerberos delegation on SRV-FILE01CriticalComputer account SRV-FILE01Switch to resource-based constrained delegation
    AD-03Domain controller DC02 on Windows Server 2016, support ends 12 January 2027CriticalDC02, Bern siteReplace with Windows Server 2025 in wave 2
    AD-04NTLMv1 allowed on SRV-BACKUP01 and SRV-PRINT01HighPolicy LAN Manager authentication levelEnforce NTLMv2, audit for two weeks first
    AD-0523 accounts with password never expires outside the service account OUMediumVarious OUsReview, let expire or run as gMSA

    Attack paths

    • Path 1: users in the Helpdesk group may reset passwords of the Server Admins group; one Server Admin is local admin on DC02. Closed by AD-06.
    • Path 2: svc_backup signs in to SRV-BACKUP01, where NTLMv1 is allowed and another account holds local admin rights. Closed by AD-01 and AD-04.
    • Paths 3 and 4: through the delegation on SRV-FILE01. Closed by AD-02.

    Next steps

    Review of the report with IT lead and management on 20 October 2026; the plan of measures follows with the decisions taken there.

    Samples with invented details for a fictional Muster AG.

    Sound familiar? Tell us where you stand today.

    Contact

    What's new.

    As of: 30 October 2026

    • As of 28 October 2026

      Windows Server 2016 receives its last update on 12 January 2027.

      Extended support for Windows Server 2016 ends on 12 January 2027, for Windows Server 2019 on 9 January 2029. Domain controllers on either version belong in the plan of measures with a date.

      Source: Microsoft Learn: Windows Server release information
    • Since 1 November 2024

      Windows Server 2025 encrypts LDAP by default.

      New Active Directory deployments on Windows Server 2025 require LDAP signing for all client communication after a SASL bind, LDAP supports TLS 1.3, and Kerberos no longer issues tickets with RC4. Delegated managed service accounts (dMSA) replace classic service accounts with randomised, managed keys.

      Source: Microsoft Learn: What's new in Windows Server 2025
    • As of 30 October 2026

      NTLMv1 is removed from Windows Server 2025, NTLMv2 is deprecated.

      Microsoft lists NTLMv1 among the features removed from Windows Server 2025; LANMAN and NTLMv2 are no longer under development and are to be removed in a future release. Also deprecated: TLS 1.0 and 1.1, RC4 in Kerberos and WSUS. Applications should call Negotiate.

      Source: Microsoft Learn: Features removed or deprecated in Windows Server

    One-off or monthly.

    The same check, the same documents. You decide whether we clean up once and hand over or look after the directory continuously.

    • One-off

      Analysis and hardening as a project

      Analysis, findings report, plan of measures, implementation in waves with your IT and a re-test. Afterwards your IT continues with the plan. What the project covers is set out in the proposal.

      Analysis and hardening as a project
    • Monthly

      Active Directory as a managed service

      A check after every Patch Tuesday, maintained baselines and policies, re-tests after changes, a monthly report with trend and open items and a contact at CNEXT. Cancellable after the agreed notice period.

      Active Directory as a managed service

    What IT leads ask beforehand.

    Does the analysis change anything in our directory?

    The analysis reads. The tools query groups, permissions, policies and sign-ins and write nothing back. Changes happen only during implementation, with your approval, per wave and within a maintenance window. Every change is recorded in the plan of measures with its date and reason.

    We have Entra ID. Do we still need the on-premises Active Directory?

    As long as file servers, business applications, printers or group policies depend on it, yes. Many organisations run both for years, and the on-premises directory is then the place where an attacker picks up the cloud identities as well. Whether and how you can retire it is covered in the findings report, in the chapter on dependencies.

    Which tools do you use?

    PingCastle and Purple Knight for the overall state, BloodHound for attack paths, the Microsoft security baselines for policies and Microsoft Defender for Identity for monitoring. You receive the tools' own reports as well; our findings report puts them in order and says what comes first.

    How long does the implementation take?

    That depends on the number of paths and the size of your IT. We implement in waves: first the paths with the smallest effort for the attacker, then the baselines, then the monitoring. Every wave has a maintenance window and a re-test. The waves and their order are in the plan of measures before we start.

    What happens to exceptions we deliberately keep?

    They go into the report with a reason, a responsible person and a review date. In the re-test and in every monthly report they appear as a known deviation until you lift them. That way an auditor knows why a finding is open.

    Can we run the service ourselves after the project?

    Yes. The plan of measures, the documented baselines and the alerts stay with you. If you would rather hand over the check after every Patch Tuesday and the maintenance of the baselines, you book the monthly service; cancellable after the agreed notice period.

    Agree on a useful next step

    Tell us about your current workflow, the systems involved and the result you need. In our first conversation, we identify what else we need to know to plan a useful next step.