test.mysmartlogon.com - Healthcheck analysis

Date: 2020-01-18 - Engine version: 2.8.0.0

This report has been generated with the Basic Edition of PingCastle.
Being part of a commercial package is forbidden (selling the information contained in the report).
If you are an auditor, you MUST purchase an Auditor license to share the development effort.

This section focuses on the core security indicators.
Locate the sub-process determining the score and fix some rules in that area to get a score improvement.

Indicators

050100

Domain Risk Level: 100 / 100

It is the maximum score of the 4 indicators and one score cannot be higher than 100. The lower the better

050100

Stale Object : 80 /100

It is about operations related to user or computer objects

6 rules matched

050100

Trusts : 100 /100

It is about links between two Active Directories

4 rules matched

050100

Privileged Accounts : 100 /100

It is about administrators of the Active Directory

14 rules matched

050100

Anomalies : 100 /100

It is about specific security control points

18 rules matched

Stale ObjectsPrivileged accountsTrustsAnomalies
Inactive user or computer
Account take over
Old trust protocol
Audit
Network topography
ACL Check
SID Filtering
Backup
Object configuration
Admin control
SIDHistory
Certificate take over
Obsolete OS
Irreversible change
Trust impermeability
Golden ticket
Old authentication protocols
Privilege control
Trust inactive
Local group vulnerability
Provisioning
Network sniffing
Replication
Pass-the-credential
Vulnerability management
Password retrieval
Reconnaissance
Temporary admins
Weak password
Legend:
  score is 0 - no risk identified but some improvements detected
  score between 1 and 10 - a few actions have been identified
  score between 10 and 30 - rules should be looked with attention
  score higher than 30 - major risks identified
050100

Stale Objects : 80 /100

It is about operations related to user or computer objects

+ 15 Point(s)

Domain Controller Update

Description:

The purpose is to ensure that all the Domain Controllers are updated regularly. This is done by checking if a DC has been rebooted in the past 6 months. If not, it means it has not be patched as well in these 6 monthes

Technical explanation:

Domain Controller needs to be updated regularly because threats to the AD evolve all the time, so assets in the AD should evolve accordingly. The date of last update is computed by getting the StatisticsStartTime from [net statistics workstation]. If not available, the PingCastle solution will use the lastLogonTimestamp attribute which is refreshed based on the LastLogon attribute. Do note that there is a maximum delay for refresh: 14 days.

Advised solution:

Frequently updating the DC should be part of the AD policies, as there should be a dedicated time-slot for the servers to reboot and apply security patches

Points:

15 points if present

Documentation:

BSI M 4.315 Aufrechterhaltung der Betriebssicherheit von Active Directory

Details:

The detail can be found in Domain controllers

Domain controllerReason
ADIANT-A7B9AAC6 LastComputerLogonDate=11/9/2018 7:29:04 AM
+ 15 Point(s)

Check for hidden group membership for computer accounts

Description:

The purpose is to check for unusual value in the primarygroupid attribute used to store group membership

Technical explanation:

In Active Directory, group membership is stored on the "members" attribute and on the "primarygroupid" attribute.
The default primary group value is "Domain Users" for the users, "Domain Computers" for the computers and "Domain Controllers" for the domain controllers.
The primarygroupid contains the RID (last digits of a SID) of the group targeted. It can be used to store hidden membership as this attribute is not often analyzed.
This rule can also be triggered if one domain controller is not in the default container (named "Domain Controllers" and located at the root) which is not a recommended practice.

Advised solution:

Unless strongly justified, change the primary group id to its default. 513 or 514 for users, 516 or 521 for domain controllers, 514 or 515 for computers. The primary group can be edited in a friendly manner by editing the account with the "Active Directory Users and Computers" and after selecting the "Member Of" tab, "set primary group".

Points:

15 points if present

Documentation:

https://support.microsoft.com/en-us/help/297951/how-to-use-the-primarygroupid-attribute-to-find-the-primary-group-for

Details:

The detail can be found in User information and Computer information

+ 15 Point(s)

Check that every account requires a password

Description:

The purpose is to ensure that every account requires a password

Technical explanation:

An account can be set without a password if it has the flag "PASSWD_NOTREQD" set as "True" in the "useraccountcontrol" attribute. This represents a high security risk as the account is not protected at all without a password

Advised solution:

The best solution to solve the problem is to change the "useraccountcontrol" attribute of all the accounts that have it and that are not used in trusts. If the flag is removed while there is no password set, you will have an error. You can use this to detect accounts without any passwords. Do note that you can manually check all the accounts that need to be worked on using the following PowerShell command: get-adobject -ldapfilter "(&(objectCategory=person)(objectClass=user)(userAccountControl:1.2.840.113556.1.4.803:=32))" -properties useraccountcontrol

Points:

15 points if present

Documentation:

https://support.microsoft.com/en-us/kb/305144
ANSSI - Recommandations de sécurité relatives à Active Directory - R36 [subsection.3.6]

Details:

The detail can be found in User information and Computer information

+ 15 Point(s)

SIDHistory check

Description:

The purpose is to ensure that a migration has been completed correctly and that the SIDHistory attribute has been cleared out from user and computer accounts. This attribute is indeed set when migrating a user or a computer from one domain to another

Technical explanation:

The SIDHistory attribute is useful when doing a migration because it allows to keep the reference to the former account. On the other hand, once the migration is over, it is mandatory that this attribute is removed to evaluate the permissions in regards with the new account and not the former one.

Advised solution:

To solve the security issue, you should remove all the SIDHistory attributes. To do so, you can list the objects having an SIDHistory attribute using the command: get-ADObject -ldapfilter "(sidhistory=*)" -properties sidhistory.
Each security descriptor of the domain (including file shares for example) should be reviewed to be rewritten with the new SID of the account. Then, the attribute can be removed of these accounts using the migration tool or a PowerShell snippet Remove-SIDHistory once the migration is completed. Please note that once the SID History has been removed, it cannot be added back again without doing a real migration. Hopefully hacking tools such as mimikatz can be used to undo a deletion with for example the lsadump::dcshadow attack.

Points:

5 points per discovery with a minimal of 15 points

Documentation:

ANSSI - Recommandations de sécurité relatives à Active Directory - R15 [paragraph.3.3.1.5]

Details:

The SIDHistory detail can be found in User information and Computer information and a quick summary in SID History

SIDObject(s)
S-1-5-18 1
+ 10 Point(s)

Check the process of registration of computers to the domain

Description:

The purpose is to ensure that basic users cannot register extra computers in the domain

Technical explanation:

By default, a basic user can register up to 10 computers within the domain. This default configuration represents a security issue as basic users shouldn't be able to create such accounts and this task should be handled by administrators.

Advised solution:

To solve the issue limit the number of extra computers that can be registered by a basic user. It can be reduced by modifying the value of ms-DS-MachineAccountQuota to zero (0). Another solution can be to remove altogether the authenticated users group in the domain controllers policy. Do note that if you need to set delegation to an account so it can add computers to the domain, it can be done through 2 methods: Delegation in the OU or by assigning the SeMachineAccountPrivilege to a special group

Points:

10 points if present

Documentation:

http://support.microsoft.com/?id=243327
http://prajwaldesai.com/allow-domain-user-to-add-computer-to-domain/
http://blog.backslasher.net/preventing-users-from-adding-computers-to-a-domain.html

+ 10 Point(s)

DC Vulnerability (SMB v1)

Description:

The purpose is to verify if Domain Controller(s) are vulnerable to the SMB v1 vulnerability

Technical explanation:

The SMB downgrade attack is used to obtain credentials or executing commands on behalf of a user by using SMB v1 as protocol. Indeed, because SMB v1 supports old authentication protocol, the integrity can be bypassed

Advised solution:

It is highly recommended by Microsoft to disable SMB v1 whenever it is possible on both client and server side. Do note that if you are still not following best practices regarding the usage of deprecated OS (Windows 2000, 2003, XP, CE), regarding Network printer using SMBv1 scan2shares functionalities, or regarding software accessing Windows share with a custom implementation relying on SMB v1, you should consider fixing this issues before disabling SMB v1, as it will generates additional errors.

Points:

10 points if present

Documentation:

https://github.com/lgandx/Responder-Windows
https://blogs.technet.microsoft.com/josebda/2015/04/21/the-deprecation-of-smb1-you-should-be-planning-to-get-rid-of-this-old-smb-dialect
ttps://support.microsoft.com/en-us/help/2696547/how-to-enable-and-disable-smbv1,-smbv2,-and-smbv3-in-windows-vista,-windows-server-2008,-windows-7,-windows-server-2008-r2,-windows-8,-and-windows-server-2012
BSI M 2.412 Schutz der Authentisierung beim Einsatz von Active Directory
ANSSI CERTFR-2017-ACT-019
ANSSI CERTFR-2016-ACT-039

Details:

The detail can be found in Domain controllers

Domain controller
WIN-PGAHI2ECI8E
050100

Privileged Accounts : 100 /100

It is about administrators of the Active Directory

+ 60 Point(s)

Ensure that dangerous privileges are not granted to everyone by GPO

Description:

The purpose is to ensure that standard users are not granted dangerous privileges

Technical explanation:

To perform special operations, the operating system relies on privileges. They can be displayed by running the command: whoami /all.
SeLoadDriverPrivilege can be used to take control of the system by loading a specifically designed driver. This procedure can be performed by low privileged users as the driver can be defined in HKCU.
SeTcbPrivilege is the privilege used to "Act on behalf the operating system". This is the privilege reserved to the SYSTEM user. This procedure allow any users to act as SYSTEM.
SeDebugPrivilege is the privilege used to debug program and to access any program's memory. It can be used to create a new process and set the parent process to a privileged one.
SeRestorePrivilege can be used to modify a service running as local system and startable by all users to a chosen one.
SeBackupPrivilege can be used to backup Windows registry and use third party tools for extracting local NTLM hashes.
SeTakeOwnershipPrivilege can be used to take ownership of any secureable object in the system including a service registry key. Then to change its ACL to define its own service running as LocalSystem.
SeCreateTokenPrivilege can be used to create a custom token with all privileges and thus be abused like SeTcbPrivilege
SeImpersonatePrivilege and SeAssignPrimaryTokenPrivilege can be abused to impersonate privileged tokens. These tokens can be retrieved by establishing security context such as Local DCOM DCE/RPC reflexion.
SeSecurityPrivilege can be use to clear the security event log and shrink it to make events flushed soon. Also read security log and view events where the user inverted the login and its password.

Advised solution:

Locate the GPO specified in Details and remove the privilege.
Most of the settings are located in :
Computer configuration -> Policies -> Windows Settings ->Security Settings -> Local Policies -> User Rights Assignment.
As an alternative, the file GptTmpl.inf can be manually edited.

Points:

15 points per discovery

Documentation:

https://www.romhack.io/slides/RomHack%202018%20-%20Andrea%20Pierini%20-%20whoami%20priv%20-%20show%20me%20your%20Windows%20privileges%20and%20I%20will%20lead%20you%20to%20SYSTEM.pdf
https://www.tarlogic.com/en/blog/abusing-seloaddriverprivilege-for-privilege-escalation/
https://github.com/decoder-it/psgetsystem
ANSSI - Recommandations de sécurité relatives à Active Directory - R18 [subsubsection.3.3.2]

Details:

The detail can be found in Privileges

GPOAccountPrivilege
Default Domain Policy Everyone SeDebugPrivilege
Default Domain Policy Everyone SeLoadDriverPrivilege
test nfc 2 Everyone SeDebugPrivilege
test nfc 2 Everyone SeLoadDriverPrivilege
+ 45 Point(s)

Ensure that GPO items cannot be modified by any user

Description:

The purpose is to ensure that standard users cannot modify GPO

Technical explanation:

When the group Authenticated Users, Everyone or any similar groups have permission to modify a GPO, it can be abused to take control of the accounts where this GPO applies. It can potentially lead to the compromise of the domain

Advised solution:

Edit the Access Control List (ACL) of the GPO object or the directory where the items is located. Then remove any write permission given to the group.

Points:

15 points per discovery

Documentation:

ANSSI - Recommandations de sécurité relatives à Active Directory - R18 [subsubsection.3.3.2]
STIG V-2370 - The access control permissions for the directory service site group policy must be configured to use the required access permissions.

Details:
GPOItemAccountRight
Test GPO site \\WIN-PGAHI2ECI8E.test.mysmartlogon.com\sysvol\test.mysmartlogon.com\Policies\{59C59FC3-6DCA-4659-9842-E9C490088449} Everyone FullControl
Default Domain Controllers Policy \\WIN-PGAHI2ECI8E.test.mysmartlogon.com\sysvol\test.mysmartlogon.com\Policies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\GPT.INI Authenticated Users FullControl
Default Domain Controllers Policy \\WIN-PGAHI2ECI8E.test.mysmartlogon.com\sysvol\test.mysmartlogon.com\Policies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\MACHINE\Registry.pol Authenticated Users FullControl
+ 45 Point(s)

Ensure that the privilege to log on Domain Controllers are not granted to everyone by GPO

Description:

The purpose is to ensure that standard users cannot login to Domain Controllers

Technical explanation:

Domain Controllers are critical components of the Active Directory. If an attacker is able to open a session, he will be able to discover unsecure backup media or perform a local privilege escalation to become the DC admin and thus the AD admin.
Local logon requires usually physical interaction, which explains why network seggregation is a best practice, but this can be bypassed. Indeed VNC or remote server management software is a way to perform local logon remotely.
In addition, remote server management software have been the subject of many vulnerabilites, some of them can be exploited even if this software is disabled.

Advised solution:

Locate the GPO specified in Details and remove the privilege "Allow log on locally" or "Allow log on through Remote Desktop Services" to "Everyone", "Authenticated Users", "Domain Users" or "Domain Computers".
The settings are located in :
Computer configuration -> Policies -> Windows Settings ->Security Settings -> Local Policies -> User Rights Assignment.
As an alternative, the file GptTmpl.inf can be manually edited.

Points:

15 points per discovery

Documentation:

https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/allow-log-on-locally
https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/allow-log-on-through-remote-desktop-services
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04197764-1
ANSSI - Recommandations de sécurité relatives à Active Directory - R18 [subsubsection.3.3.2]

Details:

The detail can be found in Privileges

GPOAccountPrivilege
Default Domain Controllers Policy Everyone SeInteractiveLogonRight
Default Domain Controllers Policy Authenticated Users SeInteractiveLogonRight
Default Domain Controllers Policy Authenticated Users SeRemoteInteractiveLogonRight
+ 30 Point(s)

Ensure that all login scripts cannot be modified by any user

Description:

The purpose is to ensure that standard users cannot modify login scripts

Technical explanation:

When the group Authenticated Users, Everyone or any similar groups have permission to modify a login script, it can be abused to take control of the accounts using this script. It can potentially lead to the compromise of the domain

Advised solution:

Edit the Access Control List (ACL) of the script object or the directory where the file is located. Then remove any write permission given to the group.

Points:

15 points per discovery

Documentation:

ANSSI - Recommandations de sécurité relatives à Active Directory - R18 [subsubsection.3.3.2]
STIG V-2370 - The access control permissions for the directory service site group policy must be configured to use the required access permissions.

Details:

The detail can be found in GPO Login script

ScriptAccountRight
test.ps1 Authenticated Users Modify, Synchronize
\\test.mysmartlogon.com\sysvol\test.mysmartlogon.com\bin\test.ps1 Authenticated Users Modify, Synchronize
+ 25 Point(s)

Check if there is a control path involving everyone-like groups.

Description:

The purpose is to ensure that there is no control path involving everyone.

Technical explanation:


If you have access to a key server and the helpdesk can reset your password, then the helpdesk has access to the key server.
This is the kind of logic used by hackers to take control of the domain using key infrastructure objects (domain root, ...) or groups (domain administrators, ...).
Permissions are collected and analyzed to produce a control paths analysis.
Only write permissions (and specific ones) are used for this analysis.
Then the program identifies which users or computers, that are not members of known groups, can take control of this object.
To be fast, some tradeoffs have been selected. For example, logged on users on servers are ignored.
The program may also select paths which are not exploitable and ignore paths if it cannot read every permissions.
[Everyone] includes the anonymous, everyone, authenticated users, domain users, domain computers and builtin-users groups.

Advised solution:

You should analyze the chart and determine which underlying object is involved and grants write permissions to everyone.
Then edit the permissions and locate the write permission involved.
Then delete it or replace it according to your delegation model.

Points:

25 points if present

Documentation:

https://github.com/BloodHoundAD/BloodHound
https://github.com/ANSSI-FR/AD-control-paths

Details:

The detail can be found in Control Paths Analysis

Group
Certificate Publishers
Domain Controllers
Domain Root
+ 20 Point(s)

At least one Administrator Account can be delegated

Description:

The purpose is to ensure that all Administrator Accounts have the configuration flag "this account is sensitive and cannot be delegated"

Technical explanation:

Without the flag "This account is sensitive and cannot be delegated" any account can be impersonated by some service account. It is a best practice to enforce this flag on administrators accounts.

Advised solution:

To correct the situation, you should make sure that all your Administrator Accounts has the check-box "This account is sensitive and cannot be delegated" active. Please not that there is a section bellow in this report named "Admin Groups" which give more information.

Points:

20 points if present

Documentation:

STIG V-36435 - Delegation of privileged accounts must be prohibited.

Details:

The detail can be found in Admin Groups

+ 15 Point(s)

Check delegations for the recipient's existence

Description:

The purpose is to verify that each delegation are linked to an account which exists

Technical explanation:

In the case where a delegation has been created where the account can't be translated to a NT account, it means that the delegation is actually from another domain or that the user has been deleted.

Advised solution:

To reduce the risk, the easiest way is essentially to remove the delegation

Points:

15 points if present

Documentation:

STIG V-2370 - The access control permissions for the directory service site group policy must be configured to use the required access permissions.

Details:

The detail can be found in Delegations

DNdelegationright
CN=Users,DC=test,DC=mysmartlogon,DC=com S-1-5-21-4005144719-3948538632-2546531719-1115 WRITE_PROP_MEMBER, VAL_WRITE_SELF_MEMBERSHIP, EXT_RIGHT_FORCE_CHANGE_PWD
+ 15 Point(s)

Ensure that file deployed by a GPO cannot be modified by everyone.

Description:

The purpose is to check that files deployed to computers cannot be changed by everyone.

Technical explanation:

Application provided in a msi form or general files can be deployed by a GPO. If an attacker can modify one of this file, it can take control of the user account.

Advised solution:

Locate the file mentionned by the GPO specified in Details and change its permissions.

Points:

5 points per discovery

Documentation:

ANSSI - Recommandations de sécurité relatives à Active Directory - R18 [subsubsection.3.3.2]
STIG V-2370 - The access control permissions for the directory service site group policy must be configured to use the required access permissions.

Details:

The detail can be found in GPO Deployed Files

GPOTypeFileNameAccountRight
WEF test Files (User section) \\test.mysmartlogon.com\sysvol\test.mysmartlogon.com\bin\test.txt Authenticated Users Modify, Synchronize
WEF test Application (Computer section) \\test.mysmartlogon.com\SYSVOL\test.mysmartlogon.com\bin\7z1900.msi Authenticated Users Modify, Synchronize
WEF test Application (Computer section) \\test.mysmartlogon.com\SYSVOL\test.mysmartlogon.com\bin\7z1900.msi Authenticated Users Modify, Synchronize
+ 15 Point(s)

A Delegation is granted to Everyone

Description:

The purpose is to verify that there is no delegation granted to "Everyone" and to "Authenticated Users"

Technical explanation:

To delegate control to a OU, access checks can be modified. In case of a misconfiguration, access can be granted to the group "Everyone" or "Authenticated Users".

Advised solution:

Review the delegation to remove this permission and if needed, set a more targeted group as recipient of the delegation.

Points:

15 points per discovery

Documentation:

ANSSI - Recommandations de sécurité relatives à Active Directory - R18 [subsubsection.3.3.2]
STIG V-2370 - The access control permissions for the directory service site group policy must be configured to use the required access permissions.

Details:

The detail can be found in Delegations

DNdelegationright
DC=test,DC=mysmartlogon,DC=com Everyone GenericAll, GenericWrite, WriteDacl, WriteOwner, All extended right, DSSelf, Write all prop
+ 15 Point(s)

Ensure the "automatic administrative logon" feature of the recovery mode is not enabled

Description:

The purpose is to check that it is not possible to go into recovery mode without the administrator password

Technical explanation:

The recovery mode is a special mode allowing an admin to fix an issue preventing the computer to boot. By pressing F8 in the short time span allowed, the computer boots with just a simple command line.
Usually, the administrator password is requested to avoid that people having physical access get control of it. It can typically be done by creating a new user account and add this account as member of the administrators group. This rule checks if there are any GPO which disable this password prompt.

Advised solution:

Locate the GPO specified in Details and turn off the setting "Recovery console: Allow automatic administrative logon"
The setting is located in :
Computer configuration -> Policies -> Windows Settings ->Security Settings -> Local Policies -> Security Options.
As an alternative, the file GptTmpl.inf can be manually edited.

Points:

15 points if present

Documentation:

https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/recovery-console-allow-automatic-administrative-logon
STIG V-1159 - The Recovery Console option is set to permit automatic logon to the system.

Details:

The detail can be found in Security settings

GPO
Default Domain Policy
+ 10 Point(s)

At least one Domain controller is not owned correctly

Description:

The purpose is to perform a review of which accounts have ownership rights on a domain controller and can then modify their permissions

Technical explanation:

By default, the "Domain Administrators" group or the "Enterprise Administrators" group are set as owners for "Domain Controllers". Nonetheless, in some cases (for instance when the server has been promoted from an existing server), the owner can be a non-admin person which joined the server to the domain. If this person has still rights over this account, it can be used to take ownership over the whole domain. A chain of compromising events can be designed to take control of the domain by including this account.

Advised solution:

To solve this security issue, you should change the ownership of the domain controller to match the "Domain Administrators" group.
To control the ownership of domain controller objects, you can use the following PowerShell command:
Get-ADComputer -server my.domain.to.check -LDAPFilter "(&(objectCategory=computer)(|(primarygroupid=521)(primarygroupid=516)))" -properties name, ntsecuritydescriptor | select name,{$_.ntsecuritydescriptor.Owner}.
To change it you can edit the owner of an object using adexplorer.exe. First, locate the DC object then right click to select properties. Open the security tab and press the advanced button. You then have a new dialog with an owner tab. Select the owner and change it for the domain administrators group. You’re done (no reboot needed)

Points:

10 points if present

Details:

The detail can be found in Domain controllers

Domain controllerOwner
CN=ADIANT-A7B9AAC6,CN=Computers,DC=test,DC=mysmartlogon,DC=com TEST\administrator
+ 5 Point(s)

Check if admin accounts are vulnerable to the kerberoast attack.

Description:

The purpose is to ensure that the password of admin accounts cannot be retrieved using the kerberoast attack.

Technical explanation:

To access a service using kerberos, a user does request a ticket (named TGS) to the DC specific to the service.
However this ticket is encrypted using a derivative of the service password. This ticket can then be brute-forced to retrieve the original password.
Any account having the attribute SPN populated is considered as a service account.
Given the fact that any user can request a ticket for service account, these accounts can have their password retrieved.
In addition, services are known to have their password not changed at a regular basis and to use well-known words.

Please note that this program skips service accounts having their password changed for less than 40 days ago to allow a mitigation using a password change process.

Advised solution:

If the account is a service account, the service should be removed from the privileged group or have a process to change it at a regular basis.
If the user is a person, the SPN attribute of the account should be removed.

Points:

5 points per discovery

Documentation:

https://adsecurity.org/?p=3466

Details:

The detail can be found in Admin Groups

GroupUser
Administrators Adiant
+ 5 Point(s)

Check if there is an explicit delegation on DNS which is not using the DnsAdmins group.

Description:

The purpose is to ensure that no specific delegation has been setup to manage the Microsoft DNS.

Technical explanation:

Administrators of the DNS Service have the possibility to inject a DLL in this service.
However this service is hosted most of the time in the domain controller and is running as system.
That means that DNS Admins are potentially domain admins.

The security descriptor used to grant admin rights is located on the nTSecurityDescriptor attribute of the object CN=MicrosoftDNS,CN=System.

In this case, an explicit delegation has been setup and this delegation is not using the existing DnsAdmins group.

Advised solution:

You should remove the explicit delegation located in the CN=MicrosoftDNS,CN=System container and make the user or group member of the DnsAdmins group.

Points:

5 points if present

Documentation:

https://medium.com/@esnesenon/feature-not-bug-dnsadmin-to-dc-compromise-in-one-line-a0f779b8dc83
https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-dnsp/007efcd2-2955-46dd-a59e-f83ae88f4678

Details:

The detail can be found in Delegations

AccountRight
TEST\wrongaccount3 GenericWrite, DSSelf, Write all prop
Informative rule

Check that operators group are empty

Description:

The purpose is to ensure that the operator groups, which can have indirect control to the domain, are empty

Technical explanation:

Operator groups (account operators, server operators, ...) can take indirect control of the domain. Indeed these groups have write access to critical resources of the domain.

Advised solution:

It is recommended to have these groups empty. Assign administrators into administrators group. Other accounts should have proper delegation rights in an OU or in the scope they are managing.

Points:

Informative rule (0 point)

Documentation:

ANSSI - Recommandations de sécurité relatives à Active Directory - R27 [subsection.3.5]

Details:

The detail can be found in Admin Groups

GroupMembers
Account Operators 1
050100

Trusts : 100 /100

It is about operations related to user or computer objects

+ 50 Point(s)

Check for local backdoor stored in SID History

Description:

The purpose is to ensure that accounts are not linked for more privileged accounts in the same domain

Technical explanation:

SID History is an attribute used in migration to link with a former account. It is not possible to have an account linked with an account belonging to the same domain. This can be analyzed by comparing the domain part of the SID History with the domain SID.

Advised solution:

It is not possible to have this occurrence except if a user from domain A has been migrated to domain B and then migrated again to domain A. This should be strongly investigated as it may be linked to a compromise of the domain.

Points:

50 points if present

Documentation:

ANSSI - Recommandations de sécurité relatives à Active Directory - R15 [paragraph.3.3.1.5]

+ 50 Point(s)

Check for Trusts whose security is not maximum

Description:

The purpose is to check if all trusts are protected using the functionality named SID Filtering

Technical explanation:

SID Filtering is a mechanism used to block account presenting a SID History property. SID History is used to link an existing account to another account and can be use to propagate a compromise through trusts. SID Filtering for domain to domain trust is called a quarantine and is disabled by default. SID Filtering to a forest is enabled by default and disabling it is called "enabling SID History".

The algorithm to compute the SID Filtering is:
get the attribute trustDirection and TrustAttributes of the trust object.
if the direction is 0 or 1 or if the trust is intra forest (trustattributes & 32 != 0) then SID Filtering is not applicable.
Then, if the trust is a forest trust (trusattributes & 8 != 0) then
check if /enablesidhistory has been enabled - trustattributes & 64 != 0.
If enabled: SID Filtering is deactivated.
Else if not a forest trust (trustattributes & 8 == 0) then check for the quarantined attribute (trustattributes & 4 != 0).
If the quarantine flag is set, SID Filtering is enabled.

You can use the PowerShell command to get its status:
[System.DirectoryServices.ActiveDirectory.Domain]::GetCurrentDomain().GetSidFilteringStatus('my.domain.to.test.local')

Advised solution:

A trust without SID Filtering means either that a migration is in progress or that the domain can be compromised instantly via the trust.
The solution is to complete existing migration ASAP and enable the SID Filtering feature

If the trust is a domain trust, you should use netdom /quarantine and set it to yes
If the trust is a forest trust, you should use netdom /enablesidhistory and set it to no
Do not apply /quarantine on a forest trust: you will break the transitivity of the trust.

Points:

100 points if the occurence is greater or equals than 4
then 80 points if the occurence is greater or equals than 2
then 50 points if present

Documentation:

https://msdn.microsoft.com/en-us/library/cc237940.aspx
ANSSI - Recommandations de sécurité relatives à Active Directory - R16 [paragraph.3.3.1.6]
STIG V-8538 - Security identifiers (SIDs) must be configured to use only authentication data of directly trusted external or forest trust.
BSI M 4.314 Sichere Richtlinieneinstellungen für Domänen und Domänen-Controller

Details:

The detail can be found in Trusts section

Trust
mil
+ 20 Point(s)

Check for inactive trusts

Description:

The purpose is to verify that every trust has a remote domain which is active.

Technical explanation:

When a trust is active, it is using a shared secret to communicate to a domain. This secret is hold in a special account whose name is the remote domain name. This password is changed every month and as consequence the whenChanged attribute of this account is changed. When there is no modification of the whenChanged attribute, it can be guessed that the secret has not being changed and that there was either a problem with the remote domain or that the remote domain does not exist anymore.

Advised solution:

Check for network connectivity issues from the remote domain or if the remote domain still exists. If it doesn't exist anymore, the trust should be removed. Indeed the secret used by the trust can be used to issue fake kerberos tickets and be used as a backdoor.

Points:

20 points if present

Documentation:

https://msdn.microsoft.com/fr-fr/library/ms680921(v=vs.85).aspx

Details:

The detail can be found in Trusts section

Trust
mil
test4.mysmartlogon.com
+ 5 Point(s)

Check if a migration is in progress

Description:

The purpose is to ensure that the SID History creation is not enabled

Technical explanation:

To migrate accounts to another domain, the attribute SID History should be added to the new account. Despite the fact that numerous hacking tools such as mimikatz allows the creation of the SID History attribute, its official creation requires the presence of a special auditing group named DOMAIN-$$$ such as TEST-$$$ for the TEST domain.

Advised solution:

If a migration is in progress, declare it in PingCastle so this rule won't be triggered. Else, remove this auditing group. You can locate it by using the LDAP query (sAMAccountName=*$$$)

Points:

5 points if present

Documentation:

ANSSI - Recommandations de sécurité relatives à Active Directory - R15 [paragraph.3.3.1.5]

050100

Anomalies : 100 /100

It is about specific security control points

+ 80 Point(s)

Find Password GPO

Description:

The purpose is to alert when a clear text password has been identified in the GPO. Regardless of whether the password is present or not, both the account and password should be considered compromised

Technical explanation:

A check is performed to identify passwords in the GPO. If a password is identified through the PingCastle solution, it means that it can be identified through many other means by attackers, and that the account should be considered compromised.
Do note that the AES key used to encrypt passwords in GPOs has been made public for interoperability reasons, which is why even an encrypted password is compromised. It has been revealed in this page

Advised solution:

In order to solve this issue, you should manually change the password to a new one. If this password is shared on many systems, each system should have a different password. If the GPO was used to define the native local administrator account, it is recommended to install a password solution manager such as the LAPS solution.

Points:

20 points per discovery

Documentation:

https://msdn.microsoft.com/en-us/library/cc422924.aspx
ANSSI CERTFR-2015-ACT-046

Details:

The detail can be found in the Obfuscated Passwords

GPOloginpassword
test nfc 2 administrator vletoux
test nfc 2 adiant vletoux
test nfc 2 test test
WEF test ssss dddd
+ 30 Point(s)

Mitigate golden ticket attack via a regular change of the krbtgt password

Description:

The purpose is to alert when the password for the krbtgt account can be used to compromise the whole domain. This password can be used to sign every kerberos ticket. Monitoring it closely often mitigates the risk of golden ticket attacks greatly.

Technical explanation:

Kerberos is an authentication protocol. It is using to sign its tickets a secret stored as the password of the krbtgt account. If the hash of the password of the krbtgt account is retrieved, it can be use to generate authentication tickets at will.
To mitigate this attack, it is recommended to change the krbtgt password every 40 days. If it not the case, every backup done until the last password change of the krbtgt account can be used to emit Golden tickets, compromising the entire domain.
Retrieval of this secret is one of the highest priority in an attack, as this password is rarely changed and offer a long term backdoor.
Also this attack can be performed using the former password of the krbtgt account. That's why the krbtgt password should be changed twice to invalidate its leak.

Advised solution:

The password of the krbtgt account should be changed twice to invalidate the golden ticket attack.
Beware: two changes of the krbtgt password not replicated to domain controllers can break these domain controllers You should wait at least 8 hours between each krbtgt password change.

There are several possibilities to change the krbtgt password.
First, a Microsoft script can be run in order to guarantee the correct replication of these secrets. Unfortunately this script supports only English operating systems.
Second, a more manual way is to essentially reset the password manually once, then to wait 3 days, then to reset it again. This is the safest way as it ensures the password is no longer usable by the Golden ticket attack.

Points:

50 points if the occurence is greater or equals than 732
then 40 points if the occurence is greater or equals than 366
then 30 points if the occurence is greater or equals than 180
then 20 points if the occurence is greater or equals than 70

Documentation:

https://gallery.technet.microsoft.com/Reset-the-krbtgt-account-581a9e51
ANSSI CERTFR-2014-ACT-032

Details:

The detail can be found in Krbtgt

+ 30 Point(s)

Check for Accounts using Smart Card with unchanged password for a long time

Description:

The purpose is to make sure the requirement of Smart Cards doesn't degrade password rotation

Technical explanation:

Using Smart Card to protected sensitive account is a good thing. Nevertheless, when the "Smart Card required" flag is set, the password of the account is not changed anymore by default. Internally the hash of this password is used to sign the user's kerberos tickets, making this account vulnerable to Silver ticket attacks. The rule is triggered 90 days after the last change of the attribute unicodePwd. This value is collected using the replication metadata of the attribute 589914

Advised solution:

There are 3 solutions to fix this issue, the most obvious being to change the user password on a regular basis. The fastest way is to check if the domain has the attribute msDS-ExpirePasswordsOnSmartCardOnlyAccounts, which is available for Windows 2016 and later versions and handle periodically hash change. Another possibility instead of changing the password is to disable the flag "this account requires a smart card" then re-enable it which will trigger internally a password hash change.

Points:

30 points if present

Documentation:

https://blogs.technet.microsoft.com/positivesecurity/2017/05/17/smartcard-and-pass-the-hash/
ANSSI - Recommandations de sécurité relatives à Active Directory - R38 [paragraph.3.6.2.2]
STIG V-72821 - All accounts, privileged and unprivileged, that require smart cards must have the underlying NT hash rotated at least every 60 days.

Details:

The detail can be found in Smart Card and Password

+ 15 Point(s)

Check for the last backup date according to Microsoft standard

Description:

The purpose is check if the backups are actually up to date in case they are needed. The alert can be triggered when a domain is backed up using non-recommended methods

Technical explanation:

A verification is done on the backups, ensuring that the backup is performed according to Microsoft standards. Indeed at each backup the DIT Database Partition Backup Signature is updated.  If for any reasons, backups are needed to perform a rollback (rebuild a domain) or to track past changes, the backups will actually be up to date. This check is equivalent to a REPADMIN /showbackup *.

Advised solution:

Plan AD backups based on Microsoft standards. These standards depend on the Operating System. For example with the wbadmin utility: wbadmin start systemstatebackup -backuptarget:d:

Points:

15 points if the occurence is greater or equals than 7

Documentation:

https://technet.microsoft.com/en-us/library/jj130668(v=ws.10).aspx
STIG V-25385 - Active Directory data must be backed up daily for systems with a Risk Management Framework categorization for Availability of moderate or high. Systems with a categorization of low must be backed up weekly.

Details:

The detail can be found in Backup

+ 15 Point(s)

Check for suspicious account(s) used in administrator activities

Description:

The purpose is to ensure that there is no rogue admin accounts in the Active Directory

Technical explanation:

A check is performed on non-admin accounts in order to identify if they have an attribute admincount set. If they have this attribute, it means that this account, which is not supposed to be admin, has been granted administrator rights in the past. This typically happens when an administrator gives temporary rights to a normal account, off process.

Advised solution:

These accounts should be reviewed, especially in regards with their past activities and have the admincount attribute removed. In order to identify which accounts are detected by this rule, we advise to run a PowerShell command that will show you all users having this flag set: get-adobject -ldapfilter "(admincount=1)"
Do not forget to look at the section AdminSDHolder below.

Points:

50 points if the occurence is greater or equals than 50
then 45 points if the occurence is greater or equals than 45
then 40 points if the occurence is greater or equals than 40
then 35 points if the occurence is greater or equals than 35
then 30 points if the occurence is greater or equals than 30
then 25 points if the occurence is greater or equals than 25
then 20 points if the occurence is greater or equals than 20
then 15 points if present

Documentation:

https://msdn.microsoft.com/en-us/library/ms675212(v=vs.85).aspx
ANSSI - Recommandations de sécurité relatives à Active Directory - R40 [paragraph.3.6.3.1]

Details:

The detail can be found in the AdminSDHolder User List

+ 10 Point(s)

Check for Short password length in password policy

Description:

The purpose is to verify if the password policy of the domain enforces users to have at least 8 characters in their password

Technical explanation:

A check is performed to identify if the GPO regarding password policy allows less than 8 characters password. Short passwords represents a high risk because they can fairly easily be brute-forced. Most CERT and agencies advises for at least 8 characters (and often this number goes up to 12)

Advised solution:

To solve the issue, the best way is to either remove the GPO enabling short password, or to modify it in order to increase the password length to at least 8 characters

Points:

10 points if present

Documentation:

https://www.microsoft.com/en-us/research/publication/password-guidance/
BSI M 4.314 Sichere Richtlinieneinstellungen für Domänen und Domänen-Controller

Details:

The detail can be found in Password policies

GPO
Default Domain Controllers Policy
Default Domain Policy
test nfc 2
PSO:test
+ 10 Point(s)

Check if there is the expected audit policy on domain controllers.

Description:

The purpose is to ensure that the audit policy on domain controllers collect the right set of events.

Technical explanation:

To detect and mitigate an attack, the right set of events need to be collected.
The audit policy is a compromise between too much and too few events to collect.
To solve this problem, the suggested audit policy from adsecurity.org is checked against the audit policy in place.

Advised solution:

Identitfy the Audit settings to apply and fix them.
Beware that there is two places for audit settings:
a) in Computer Configuration -> Policies -> Windows Settings -> Security Settings -> Local Policies -> Audit Policies
b) in Computer Configuration -> Policies -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration

Points:

10 points if present

Documentation:

https://adsecurity.org/?p=3299

Details:

The detail can be found in Audit settings

AuditProblemRationale
Audit Policy Change No GPO check for audit success Collect event 4908, to track special groups such as "administrators"
Audit object access No GPO check for audit success Collect event 4698, 4699, 4702 to track schedule tasks lifecycle
Detailled Tracking / DPAPI Activity No GPO check for audit success Collect event 4692 to track the export of DPAPI backup key
Detailled Tracking / Process Creation No GPO check for audit success Collect event 4688 to get the history of executed programs
Privilege Use / Sensitive Privilege Use No GPO check for audit success Collect events 4672, 4673, 4674 for privileges tracking such as the debug one
+ 10 Point(s)

Retrieve data from the domain without any account

Description:

The purpose is to access without any account, aka NULL Sessions, within the Active Directory. A NULL Session is a session opened anonymously to access the AD, often used by attackers to perform a recon operation on the AD, to identify weaknesses

Technical explanation:

Unless other rules which check for known cause of anonymous access, this rule tries to enumerate accounts from the domain without any account. The program use two methods: MS-SAMR with a NULL connection and MS-LSAT which forces SID resolution with well known SID.
NULL sessions are deactivated by default since Windows 2003 and Windows XP. For compatibility reasons a setting enabling them may be still active years after.
It is possible to verify the results provided by the PingCastle solution by using a Kali distribution. You should run [rpcclient -U " target_ip_address] and press enter at the password prompt to finally type [enumdomusers].

Advised solution:

Locate other PingCastle rules such as A-PreWin2000Anonymous or A-DsHeuristicsAnonymous which triggered and apply the solutions. You can use the PingCastle scanner mode to do a manual check and prove the extraction of the data.

Points:

10 points if present

Documentation:

https://www.sans.org/reading-room/whitepapers/windows/null-sessions-nt-2000-286
BSI M 2.412 Schutz der Authentisierung beim Einsatz von Active Directory
STIG V-14798 - Directory data (outside the root DSE) of a non-public directory must be configured to prevent anonymous access.

Details:

The detail can be found in Domain controllers and Null Session

Domain controller
WIN-PGAHI2ECI8E
+ 10 Point(s)

Check if LDAPS is used with weak SSL protocol.

Description:

The purpose is to ensure that all DC don't use weak SSL protocols when acting as server.

Technical explanation:

SSL version 2 and SSL version 3 are considered weak and it is strongly advised to disable them.
The SSL protocols in Windows is provided by the Schannel component.
The Schannel component needs to be tuned in order to not propose these weak protocols. Many guidelines to handle this problem issued by Microsoft do not talk about Schannel but rather IIS. These guidlines are quoted in the documentation section below.

PingCastle is able to check the SSL version if LDAPS is exposed. LDAPS is automatically exposed once a certificate is available for the DC and the service restarted.
Please note that PingCastle is using the native .Net SSL stack to perform this test. .Net begins to ignore these weak protocols starting the version 4.7 of the framework and as a consequence, PingCasle may miss some weak protocol detection.

To test these protocol, you can use openssl with the following commands:
openssl s_client -connect dc.domain.local:636 -ssl2
openssl s_client -connect dc.domain.local:636 -ssl3

Advised solution:

Apply Windows updates and registry tweaks described in the documentation section to disable the weak SSL protocols.

Points:

10 points if present

Documentation:

https://social.technet.microsoft.com/wiki/contents/articles/2249.windows-server-20082008r2-how-to-disable-sslv2-on-domain-controller-dsforum2wiki.aspx
https://support.microsoft.com/en-us/help/187498/how-to-disable-pct-1-0-ssl-2-0-ssl-3-0-or-tls-1-0-in-internet-informat
https://adsecurity.org/?p=376

Details:

The detail can be found in Domain controllers

DCProtocol
WIN-PGAHI2ECI8E Ssl2
WIN-PGAHI2ECI8E Ssl3
+ 5 Point(s)

Check for GPO enabling the unsafe algorithm LM hash

Description:

The authentication protocol NTLM v1 can use the LM password hash algorithm which is weak if enabled by a GPO.

Technical explanation:

LM hash, or LAN Manager hash is a hash algorithm developed by Microsoft since Windows 3.1. Due to flaw design, hashes retrieved from the network can be reverted to the clear text password in a matter of seconds.

Advised solution:

A GPO explicitly disabled the default security policy LmCompatibilityLevel or NoLMHash. Using the information provided, identify the setting modified in the GPO and fix it.
All security settings should be modified in the Domain GPO Editor and are located in Computer Configuration / Policies / Windows Settings / Security Settings / Local Policies / Security Options
For NoLMHash the setting is located in: Network security: Do not store LAN Manager hash value on next password change
For LmCompatibilityLevel the setting is located in: Network security: LAN Manager authentication level

Points:

5 points if present

Documentation:

BSI M 2.412 Schutz der Authentisierung beim Einsatz von Active Directory
STIG V-3379 - The system is configured to store the LAN Manager hash of the password in the SAM.
ANSSI - Recommandations de sécurité relatives à Active Directory - R37 [paragraph.3.6.2.1]

Details:

The detail can be found in Security settings

GPOSetting
Default Domain Policy NoLMHash
+ 5 Point(s)

Ensure LDAP signing requirements is not set to None

Description:

The purpose is to check that the integrity of the network protocol LDAP as not been explicitly disabled.

Technical explanation:

The LDAP signature feature enables the integrity of the network communication between the computer and the domain controller.
Hackers aim at intercepting the communication at the network layer and modify the network dialog to grant themselves admin privileges.
The goal of this feature is to defeat these attacks.
Unfortunately, not all devices support LDAP signature. That's why the best practice is to Require Signature if possible or to, at least, try to negotiate it.
In this case, the LDAP signature feature is configured to None (no negotiation), which can enable hackers to perform their attacks.

Advised solution:

Locate the GPO specified in Details and change the setting in "Network security: LDAP client signing requirements".
Disable this setting, or set it to "Negotiate signing" or "Require Signature".
The setting is located in :
Computer configuration -> Policies -> Windows Settings ->Security Settings -> Local Policies -> Security Options.
As an alternative, the file GptTmpl.inf can be manually edited.

Points:

5 points if present

Documentation:

https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/network-security-ldap-client-signing-requirements
BSI M 2.412 Schutz der Authentisierung beim Einsatz von Active Directory
ANSSI CERTFR-2015-ACT-021
STIG V-3381 - The Recovery Console option is set to permit automatic logon to the system.

Details:

The detail can be found in Security settings

GPO
Default Domain Policy
+ 5 Point(s)

Check for Windows 2000 compatibility which allows access to the domain without any account

Description:

The purpose is to identify domains which allow access without any account because of a Pre-Windows 2000 compatibility.

Technical explanation:

When a Windows 2003 DC is promoted, a pre-Windows 2000 compatibility setting can be enabled through the wizard. If it is enabled, the wizard will add "Everyone" and "Anonymous" to the pre-Windows 2000 compatible access group, and by doing so, it will authorize the domain to be queried without an account (null session)
It is possible to verify the results provided by the PingCastle solution by using a Kali distribution. You should run [rpcclient -U " target_ip_address] and press enter at the password prompt to finally type [enumdomusers].

Advised solution:

Remove the "EveryOne" and "Anonymous" from the PreWin2000 group while making sure that the group "Authenticated Users" is present. Then reboot each DC

Points:

5 points if present

Documentation:

https://msdn.microsoft.com/en-us/library/cc223672.aspx
STIG V-8547 - The Anonymous Logon and Everyone groups must not be members of the Pre-Windows 2000 Compatible Access group.
BSI M 2.412 Schutz der Authentisierung beim Einsatz von Active Directory

+ 1 Point(s)

Check for Intermediate Certificates using unsafe hashing algorithm (SHA1)

Description:

The purpose is to ensure that there is no use of the SHA1 hashing algorithm in Intermediate Certificate

Technical explanation:

The SHA1 hashing algorithm is not considered as safe. There are design flaws inherent to the algorithm that allow an attacker to generate a hash collision in less than a brute-force time

Advised solution:

To solve the matter, the certificate should be removed from the GPO and if needed, certificates depending on it should be reissued.

Points:

1 points if present

Documentation:

https://tools.ietf.org/html/rfc6194
STIG V-14820 - PKI certificates (server and clients) must be issued by the DoD PKI or an approved External Certificate Authority (ECA).

Details:

The detail can be found in Certificates

GPOSubject
GPO:Default Domain Policy;Machine SERIALNUMBER=200804, CN=Foreigner CA, C=BE
GPO:Default Domain Policy;Machine CN=UTN-USERFirst-Object, OU=http://www.usertrust.com, O=The USERTRUST Network, L=Salt Lake City, S=UT, C=US
GPO:Default Domain Policy;Machine CN=COMODO Code Signing CA 2, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GB
NTLMStore CN=COMODO Code Signing CA 2, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GB
NTLMStore CN=UTN-USERFirst-Object, OU=http://www.usertrust.com, O=The USERTRUST Network, L=Salt Lake City, S=UT, C=US
NTLMStore CN=COMODO Code Signing CA, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GB
Informative rule

Check if LLMNR can be used to steal credentials

Description:

The purpose is to ensure that local name resolution protocol (LLMNR) cannot be used to collect credentials by performing a network attack

Technical explanation:

LLMNR is a protocol which translates names such as foo.bar.com into an ip address. LLMNR has been designed to translate name locally in case the default protocol DNS is not available.
Regarding Active Directory, DNS is mandatory which makes LLMNR useless.
LLMNR exploits typo mistakes or faster response time to redirect users to a specially designed share, server or website.
Being trusted, this service will trigger the single sign on procedure which can be abused to retrieve the user credentials.

LLMNR is enabled by default on all OS except starting from Windows 10 v1903 and Windows Server v1903 where it is disabled.

Advised solution:

Enable the GPO Turn off multicast name resolution and check that no GPO override this setting.
(if it is the case, the policy involved will be displayed below)

Points:

Informative rule (0 point)

Documentation:

https://youtu.be/Fg2gvk0qgjM

Details:

The detail can be found in Security settings

GPO
Default Domain Policy
Informative rule

Check the Password Policy for Service Accounts (Information)

Description:

The purpose is to give information regarding a best practice for the Service Account password policy. Indeed, having a 20+ characters password for this account greatly helps reducing the risk behind Kerberoast attack (offline crack of the TGS tickets)

Technical explanation:

The rule is purely informative, as it gives insights regarding a best practice. It verifies if there is a GPO or PSO enforcing a 20+ characters password for the Service Account.

Advised solution:

The recommended way to handle service accounts is to use "Managed service accounts" introduced since Windows 2008 R2 (search for "msDS-ManagedServiceAccount").
To solve the anomaly, you should implement a PSO or GPO password guarantying a 20+ length password.

Points:

Informative rule (0 point)

Documentation:

https://www.microsoft.com/en-us/research/publication/password-guidance/

Details:

The detail can be found in Password Policies

Informative rule

Check if there is powershell logging enabled.

Description:

The purpose is to ensure that Powershell logging is enabled.

Technical explanation:

Powershell is a powerful language, also used by hackers because of this quality. Hackers are able to run programs such as mimikatz in memory using obfuscated commands such as Invoke-Mimikatz.
Because there is no artefact on the disk, the incident response task is difficult for the forensic analysts.
For this reason, we recommend to enable Powershell logging via a group policy, despite the fact that these security settings may be part of the workstation or server images.

Advised solution:

Go to Computer Configuration -> Administrative Templates -> Windows Components -> Windows PowerShell
And enable "Turn on Module logging" and "Turn on Powershell Script Block logging"
We recommend to set "*" as the module list.

Points:

Informative rule (0 point)

Documentation:

https://adsecurity.org/?p=2604
https://docs.microsoft.com/en-us/powershell/scripting/wmf/whats-new/script-logging?view=powershell-6
STIG V-68819 - PowerShell script block logging must be enabled

Details:

The detail can be found in Security settings

Informative rule

Check for presence of the Protected users group

Description:

The purpose is to ensure that the schema has been updated for the creation of Protected Users group.

Technical explanation:

The Protected Users group is a special group which is a very effective mitigation solution to counter attacks using Credential theft starting with Windows 8.1. Older Operating System must be updated to take this protection in account such as the Windows 7 KB2871997 patch.

Advised solution:

The Protected Users group is automatically created when a Windows 2012 R2 domain controller is installed and upgraded to a PDC (primary DC). The group is then be automatically created and replicated.
Warning: Do not add service account into this group as this will result in "authentication failure" messages. Use "protected accounts" instead

Points:

Informative rule (0 point)

Documentation:

https://docs.microsoft.com/en-us/windows-server/security/credentials-protection-and-management/protected-users-security-group
ANSSI CERTFR-2017-ALE-012
STIG V-78131 - Accounts with domain level administrative privileges must be members of the Protected Users group in domains with a domain functional level of Windows 2012 R2 or higher.

Details:

The schema version is indicated in Domain Information

Informative rule

Check for Root Certificates using unsafe hashing algorithm (SHA1)

Description:

The purpose is to ensure that there is no use of the SHA1 hashing algorithm in Root Certificate

Technical explanation:

The SHA1 hashing algorithm is not considered as safe. There are design flaws inherent to the algorithm that allow an attacker to generate a hash collision in less than a brute-force time

Advised solution:

To solve the matter, the certificate should be removed from the GPO and if needed, certificates depending on it should be reissued.

Points:

Informative rule (0 point)

Documentation:

https://tools.ietf.org/html/rfc6194
STIG V-14820 - PKI certificates (server and clients) must be issued by the DoD PKI or an approved External Certificate Authority (ECA).

Details:

The detail can be found in Certificates

GPOSubject
GPO:Default Domain Policy;Machine CN=AddTrust External CA Root, OU=AddTrust External TTP Network, O=AddTrust AB, C=SE
GPO:Default Domain Policy;Machine CN=Belgium Root CA2, C=BE
GPO:Default Domain Policy;Machine CN=MaskTech CSCA, OU=Test Division, O=MaskTech GmbH, C=DE
GPO:Default Domain Policy;Machine CN=CA, DC=test, DC=mysmartlogon, DC=com
GPO:Default Domain Policy;Machine CN=DOD EMAIL CA-29, C=US, O=U.S. Government, OU=DoD, OU=PKI
NTLMStore CN=CA, DC=test, DC=mysmartlogon, DC=com
NTLMStore CN=MaskTech CSCA, OU=Test Division, O=MaskTech GmbH, C=DE
NTLMStore CN=Belgium Root CA2, C=BE
NTLMStore CN=DOD EMAIL CA-29, C=US, O=U.S. Government, OU=DoD, OU=PKI
NTLMStore CN=AddTrust External CA Root, OU=AddTrust External TTP Network, O=AddTrust AB, C=SE
NTLMStore CN=CA, DC=test, DC=mysmartlogon, DC=com

This section shows the main technical characteristics of the domain.

DomainNetbios NameDomain Functional LevelForest Functional LevelCreation dateDC countSchema versionRecycle Bin enabled
test.mysmartlogon.comTESTWindows Server 2008 R2Windows Server 2008 R22012-03-03 18:12:40Z2Windows Server 2008 R2TRUE

This section gives information about the user accounts stored in the Active Directory

Honey Pot

A honey pot has been configured. It is used to generate fake security issues that are heavily monitored and that a hacker will spot using security tools like PingCastle. By enabling this feature, all the accounts listed below will not be evaluated with PingCastle rules.

[2]
NameCreationLast logonDistinguished name
HoneyPot2020-01-18 10:07:42ZNeverCN=Honey Pot,CN=Users,DC=test,DC=mysmartlogon,DC=com
HoneyPotInexistantAccess DeniedNever

Account analysis

Nb User AccountsNb Enabled ?Nb Disabled ?Nb Active ?Nb Inactive ?Nb Locked ?Nb pwd never Expire ?Nb SidHistory ?Nb Bad PrimaryGroup ?Nb Password not Req. ?Nb Des enabled. ?Nb unconstrained delegations ?Nb Reversible password ?
2420451506301000
[15]
NameCreationLast logonDistinguished name
1234567892017-11-15 13:47:44ZNeverCN=tata yoyo.123456789,CN=Users,DC=test,DC=mysmartlogon,DC=com
ADHealthCheck$2016-12-03 10:22:26ZNeverCN=ADHealthCheck,CN=Managed Service Accounts,DC=test,DC=mysmartlogon,DC=com
BlueHat2018-01-19 15:23:37ZNeverCN=BlueHat,CN=Users,DC=test,DC=mysmartlogon,DC=com
HINSON2014-11-30 16:02:50ZNeverCN=Kimberly Hinson,CN=Users,DC=test,DC=mysmartlogon,DC=com
min2014-06-21 21:19:29Z2014-07-03 21:24:07ZCN=min,CN=Users,DC=test,DC=mysmartlogon,DC=com
testitb12019-04-06 11:31:38Z2019-04-06 13:33:30ZCN=testitb,CN=Builtin,DC=test,DC=mysmartlogon,DC=com
wrongAccount12015-06-26 10:20:33ZNeverCN=wrongAccount1,CN=Users,DC=test,DC=mysmartlogon,DC=com
wrongaccount102018-08-20 14:22:43ZNeverCN=wrongaccount10,OU=TestOU,DC=test,DC=mysmartlogon,DC=com
wrongAccount22015-06-26 10:20:48ZNeverCN=wrongAccount2,CN=Users,DC=test,DC=mysmartlogon,DC=com
wrongaccount32015-06-26 11:13:15ZNeverCN=wrongaccount3,CN=Users,DC=test,DC=mysmartlogon,DC=com
wrongAccount52015-06-26 15:47:18ZNeverCN=wrongAccount5,OU=TestOU,DC=test,DC=mysmartlogon,DC=com
wrongAccount62015-06-26 15:47:35ZNeverCN=wrongAccount6,OU=TestOU,DC=test,DC=mysmartlogon,DC=com
wrongAccount72015-06-27 07:26:05Z2015-06-27 09:27:23ZCN=wrongAccount7,OU=TestOU,DC=test,DC=mysmartlogon,DC=com
wrongaccount82016-03-28 10:40:52ZNeverCN=wrongaccount8,CN=Users,DC=test,DC=mysmartlogon,DC=com
wrongaccount92016-03-30 13:02:35ZNeverCN=wrongaccount9,OU=TestOU,DC=test,DC=mysmartlogon,DC=com
[6]
NameCreationLast logonDistinguished name
Administrator2012-03-03 18:13:00Z2019-08-26 13:56:05ZCN=Administrator,CN=Users,DC=test,DC=mysmartlogon,DC=com
HINSON2014-11-30 16:02:50ZNeverCN=Kimberly Hinson,CN=Users,DC=test,DC=mysmartlogon,DC=com
min2014-06-21 21:19:29Z2014-07-03 21:24:07ZCN=min,CN=Users,DC=test,DC=mysmartlogon,DC=com
test2013-03-31 11:33:16Z2019-11-11 11:52:36ZCN=test,CN=Users,DC=test,DC=mysmartlogon,DC=com
test22019-03-23 07:19:15Z2020-01-12 14:26:14ZCN=test2,CN=Users,DC=test,DC=mysmartlogon,DC=com
testitb12019-04-06 11:31:38Z2019-04-06 13:33:30ZCN=testitb,CN=Builtin,DC=test,DC=mysmartlogon,DC=com
[3]
NameCreationLast logonDistinguished name
BlueHat2018-01-19 15:23:37ZNeverCN=BlueHat,CN=Users,DC=test,DC=mysmartlogon,DC=com
test2013-03-31 11:33:16Z2019-11-11 11:52:36ZCN=test,CN=Users,DC=test,DC=mysmartlogon,DC=com
wrongaccount82016-03-28 10:40:52ZNeverCN=wrongaccount8,CN=Users,DC=test,DC=mysmartlogon,DC=com
[1]
NameCreationLast logonDistinguished name
BlueHat2018-01-19 15:23:37ZNeverCN=BlueHat,CN=Users,DC=test,DC=mysmartlogon,DC=com

SID History

SID History from domainFirst date seen ?Last date seen ?Count
S-1-5-182013-03-31 11:33:16Z2013-03-31 11:33:16Z1
test.mysmartlogon.com2016-03-28 10:40:52Z2018-01-19 15:23:37Z2

Account analysis

This section gives information about the computer accounts stored in the Active Directory

Nb Computer AccountsNb Enabled ?Nb Disabled ?Nb Active ?Nb Inactive ?Nb SidHistory ?Nb Bad PrimaryGroup ?Nb unconstrained delegations ?Nb Reversible password ?
990360110
[6]
NameCreationLast logonDistinguished name
ADIANT-2CC70D66$2013-04-01 09:32:22Z2013-04-01 11:32:26ZCN=ADIANT-2CC70D66,CN=Computers,DC=test,DC=mysmartlogon,DC=com
ADIANT-A7B9AAC6$2013-04-01 10:10:33Z2018-11-09 07:29:04ZCN=ADIANT-A7B9AAC6,CN=Computers,DC=test,DC=mysmartlogon,DC=com
ADIANT-VIRTUAL-$2019-01-27 12:57:02Z2019-01-27 13:57:02ZCN=ADIANT-VIRTUAL-,CN=Computers,DC=test,DC=mysmartlogon,DC=com
TEST$2019-01-27 09:40:38Z2019-01-27 10:40:41ZCN=TEST,CN=Computers,DC=test,DC=mysmartlogon,DC=com
WIN-1MLHM2RAF4U$2012-03-03 18:24:33Z2019-03-09 18:00:28ZCN=WIN-1MLHM2RAF4U,CN=Computers,DC=test,DC=mysmartlogon,DC=com
WINDOWS7X86$2012-03-03 22:07:05Z2016-09-15 23:54:27ZCN=WINDOWS7X86,CN=Computers,DC=test,DC=mysmartlogon,DC=com
[2]
NameCreationLast logonDistinguished name
ADIANT-VIRTUAL-$2019-01-27 12:57:02Z2019-01-27 13:57:02ZCN=ADIANT-VIRTUAL-,CN=Computers,DC=test,DC=mysmartlogon,DC=com
TEST$2019-01-27 09:40:38Z2019-01-27 10:40:41ZCN=TEST,CN=Computers,DC=test,DC=mysmartlogon,DC=com
[1]
NameCreationLast logonDistinguished name
ADIANT-A7B9AAC6$2013-04-01 10:10:33Z2018-11-09 07:29:04ZCN=ADIANT-A7B9AAC6,CN=Computers,DC=test,DC=mysmartlogon,DC=com
[1]
NameCreationLast logonDistinguished name
WIN-PGAHI2ECI8E$2012-03-03 18:17:15Z2020-01-12 14:24:39ZCN=WIN-PGAHI2ECI8E,OU=Domain Controllers,DC=test,DC=mysmartlogon,DC=com

Operating Systems

Operating SystemNb OSNb Enabled ?Nb Disabled ?Nb Active ?Nb Inactive ?Nb SidHistory ?Nb Bad PrimaryGroup ?Nb unconstrained delegations ?Nb Reversible password ?
Windows XP220020100
Windows 7330120000
Windows 10110100000
Windows 2008110100010
OperatingSystem not set110010000
Ubuntu Desktop Linux110010000

Domain controllers

Here is a specific zoom related to the Active Directory servers: the domain controllers.

[2]
Domain controllerOperating SystemCreation Date ?Startup TimeUptimeOwner ?Null sessions ?SMB v1 ?Remote spooler ?FSMO role ?
WIN-PGAHI2ECI8EWindows 20082012-03-03 18:17:15Z2019-09-03 17:41:16Z136 daysTEST\Domain AdminsYESYESNOPDC,
RID pool manager,
Infrastructure master,
Schema master,
Domain naming Master
ADIANT-A7B9AAC6Windows XP2013-04-01 10:10:33ZInactive?TEST\administratorNONONO

Groups

This section is focused on the groups which are critical for admin activities. If the report has been saved which the full details, each group can be zoomed with its members. If it is not the case, for privacy reasons, only general statictics are available.

Group NameNb Admins ?Nb Enabled ?Nb Disabled ?Nb Inactive ?Nb PWd never expire ?Nb Smart Card required ?Nb Service accounts ?Nb can be delegated ?Nb external users ?
Account Operators110100010
Administrators651311140
Backup Operators000000000
Certificate Operators000000000
Certificate Publishers000000000
Domain Administrators541211130
Enterprise Administrators110010000
Print Operators220120020
Schema Administrators220010110
Server Operators000000000
[9]
SamAccountName ?Enabled ?Active ?Pwd never Expired ?Locked ?Smart Card required ?Service account ?Flag Cannot be delegated present ?Distinguished name ?
AdiantYESYESNONONOYESNOCN=Adiant,CN=Users,DC=test,DC=mysmartlogon,DC=com
AdministratorYESYESYESNONONOYESCN=Administrator,CN=Users,DC=test,DC=mysmartlogon,DC=com
test2YESYESYESNONONONOCN=test2,CN=Users,DC=test,DC=mysmartlogon,DC=com
teste (NONONONONONOYESCN=New Object with (dsg,CN=Users,DC=test,DC=mysmartlogon,DC=com
testitb1YESNOYESNONONONOCN=testitb,CN=Builtin,DC=test,DC=mysmartlogon,DC=com
tset ☺☻♥♦♣♠•◘○◙♂♀♪♫☼YESNONONONONONOCN=test ☺☻♥♦♣♠•◘○◙♂♀♪♫☼►◄↕‼¶§▬↨↑↓→←∟↔▲▼,CN=Users,DC=test,DC=mysmartlogon,DC=com
wrongAccount1YESNONONONONONOCN=wrongAccount1,CN=Users,DC=test,DC=mysmartlogon,DC=com
wrongAccount5YESNONONOYESNONOCN=wrongAccount5,OU=TestOU,DC=test,DC=mysmartlogon,DC=com
wrongaccount8YESNONONONONONOCN=wrongaccount8,CN=Users,DC=test,DC=mysmartlogon,DC=com

Delegations

Each specific rights defined for Organizational Unit (OU) are listed below.

[13]
DistinguishedNameAccountRight
DC=testEveryoneGenericAll, GenericWrite, WriteDacl, WriteOwner, All extended right, DSSelf, Write all prop
DC=testTEST\Domain ControllersEXT_RIGHT_REPLICATION_GET_CHANGES_ALL
CN=MicrosoftDNS,CN=SystemNT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERSGenericWrite, WriteDacl, WriteOwner, All extended right, DSSelf, Write all prop
CN=MicrosoftDNS,CN=SystemTEST\DnsAdminsGenericWrite, WriteDacl, WriteOwner, All extended right, DSSelf, Write all prop
CN=MicrosoftDNS,CN=SystemTEST\wrongaccount3GenericWrite, DSSelf, Write all prop
CN=RAS and IAS Servers Access Check,CN=SystemTEST\RAS and IAS ServersGenericWrite, WriteDacl, WriteOwner, All extended right, DSSelf, Write all prop
CN=WMIPolicy,CN=SystemTEST\Group Policy Creator OwnersGenericWrite, DSSelf, Write all prop
CN=SOM,CN=WMIPolicy,CN=SystemTEST\Group Policy Creator OwnersGenericWrite, DSSelf, Write all prop
CN=UsersS-1-5-21-4005144719-3948538632-2546531719-1115WRITE_PROP_MEMBER, VAL_WRITE_SELF_MEMBERSHIP, EXT_RIGHT_FORCE_CHANGE_PWD
OU=TestOUTEST\AdiantGenericAll, GenericWrite, WriteDacl, WriteOwner, All extended right, DSSelf, Write all prop
OU=TestOUTEST\wrongAccount6GenericAll, GenericWrite, WriteDacl, WriteOwner, WRITE_PROP_MEMBER, VAL_WRITE_SELF_MEMBERSHIP
OU=TestOUTEST\wrongAccount7EXT_RIGHT_FORCE_CHANGE_PWD
OU=TestOUTEST\wrongaccount9EXT_RIGHT_FORCE_CHANGE_PWD

This section focuses on permissions issues that can be exploited to take control of the domain.
This is an advanced section that should be examined after having looked at the Admin Groups section.

Foreign domain involved

This analysis focuses on accounts found in control path and located in other domains.

No operative link with other domains has been found.

Indirect links

This part try to summarize in a single table if major issues have been found.
Focus on finding critical objects such as the Everyone group then try to decrease the number of objects having indirect access.
The detail is displayed below.

Priority to remediate ?Critical Object Found ?Number of objects with Indirect ?Max number of indirect numbers ?Max ratio ?
CriticalYES5480
HighNO000
MediumYES110
OtherYES110

Admin groups

If the report has been saved which the full details, each object can be zoomed with its full detail. If it is not the case, for privacy reasons, only general statictics are available.

Group or user account ?Priority ?Number of users member of the group ?Number of computer member of the group ?Number of object having indirect control ?Number of unresolved members (removed?) ?Link with other domainsDetail
Account OperatorsHigh1 (Details)000NoneAnalysis
AdministratorCritical1 (Details)0NoneAnalysis
AdministratorsCritical6 (Details)01 (Details)0NoneAnalysis
Backup OperatorsHigh0000NoneAnalysis
Certificate OperatorsMedium0000NoneAnalysis
Certificate PublishersOther01 (Details)1 including EVERYONE (Details)0NoneAnalysis
Domain AdministratorsCritical5 (Details)04 (Details)0NoneAnalysis
Enterprise AdministratorsCritical1 (Details)000NoneAnalysis
Print OperatorsMedium2 (Details)000NoneAnalysis
Schema AdministratorsCritical2 (Details)01 (Details)0NoneAnalysis
Server OperatorsHigh0000NoneAnalysis

Critical Infrastructure

If the report has been saved which the full details, each object can be zoomed with its full detail. If it is not the case, for privacy reasons, only general statictics are available.

Group or user account ?Priority ?Number of users member of the group ?Number of computer member of the group ?Number of object having indirect control ?Number of unresolved members (removed?) ?Link with other domainsDetail
Builtin OUMedium00NoneAnalysis
Certificate storeMedium00NoneAnalysis
Computers containerMedium00NoneAnalysis
Domain ControllersCritical02 (Details)2 including EVERYONE (Details)0NoneAnalysis
Domain RootMedium1 including EVERYONE (Details)0NoneAnalysis
Enterprise Read Only Domain ControllersOther0000NoneAnalysis
Group Policy Creator OwnersMedium1 (Details)000NoneAnalysis
Krbtgt accountMedium00NoneAnalysis
Read Only Domain ControllersMedium0000NoneAnalysis
Users containerMedium01 (Details)NoneAnalysis

This section focuses on the relations that this domain has with other domains

Discovered Domains

This part displays the direct links that this domain has with other domains.

Trust PartnerTypeAttributDirection ?SID Filtering active ?TGT Delegation ?Creation ?Is Active ? ?
mil ?MITNon-TransitiveOutboundNoNot applicable2014-06-09 12:49:20ZFALSE
test4.mysmartlogon.com ?UplevelForest TrustInboundNot applicableNo2019-04-06 21:53:36ZFALSE

Reachable Domains

These are the domains that PingCastle was able to detect but which is not releated to direct trusts. It may be children of a forest or bastions.

Reachable domainViaNetbiosCreation date

This section focuses on security checks specific to the Active Directory environment.

Backup

The program checks the last date of the AD backup. This date is computed using the replication metadata of the attribute dsaSignature (reference).

Last backup date: Never

LAPS

LAPS is used to have a unique local administrator password on all workstations / servers of the domain. Then this password is changed at a fixed interval. The risk is when a local administrator hash is retrieved and used on other workstation in a pass-the-hash attack.

Mitigation: having a process when a new workstation is created or install LAPS and apply it through a GPO

LAPS installation date: 2019-03-22 21:12:37Z

Windows Event Forwarding (WEF)

Windows Event Forwarding is a native mechanism used to collect logs on all workstations / servers of the domain. Microsoft recommends to Use Windows Event Forwarding to help with intrusion detection Here is the list of servers configured for WEF found in GPO

Number of WEF configuration found: 3

[3]
GPO NameOrderServer
WEF test1Server=http://192.168.0.25:5985/wsman/SubscriptionManager/WEC
WEF test2test
WEF test3teset2

krbtgt (Used for Golden ticket attacks)

The password of the krbtgt account should be changed twice every 40 days using this script

You can use the version gathered using replication metadata from two reports to guess the frequency of the password change or if the two consecutive resets has been done. Version starts at 1.

Kerberos password last changed: 2019-03-10 18:21:24Z version: 3

AdminSDHolder (detect temporary elevated accounts)

This control detects accounts which are former 'unofficial' admins. Indeed when an account belongs to a privileged group, the attribute admincount is set. If the attribute is set without being an official member, this is suspicious. To suppress this warning, the attribute admincount of these accounts should be removed after review.

Number of accounts to review: 1

[1]
NameCreationLast logonDistinguished name
wrongaccount92016-03-30 13:02:35ZNeverCN=wrongaccount9,OU=TestOU,DC=test,DC=mysmartlogon,DC=com

NULL SESSION (anonymous access)

This control detects domain controllers which can be accessed without authentication. Hackers can then perform a reconnaissance of the environement with only a network connectivity and no account at all.

Domain controllers vulnerable: 1

[1]
Domain Controller
WIN-PGAHI2ECI8E

Smart Card and Password

This control detects users which use only smart card and whose password hash has not been changed for at least 40 days. Indeed, once the smart card required check is activated in the user account properties, a random password hash is set. But this hash is not changed anymore like for users having a password whose change is controlled by password policies. As a consequence, a capture of the hash using a memory attack tool can lead to a compromission of this account unlimited in time. The best practice is to reset these passwords on a regular basis or to uncheck and check again the "require smart card" property to force a hash change.

Users with smart card and having their password unchanged since at least 40 days: 3

[3]
NameCreationLast logonDistinguished name
BlueHat2018-01-19 15:23:37ZNeverCN=BlueHat,CN=Users,DC=test,DC=mysmartlogon,DC=com
wrongaccount102018-08-20 14:22:43ZNeverCN=wrongaccount10,OU=TestOU,DC=test,DC=mysmartlogon,DC=com
wrongAccount52015-06-26 15:47:18ZNeverCN=wrongAccount5,OU=TestOU,DC=test,DC=mysmartlogon,DC=com

Logon scripts

You can check here backdoors or typo error in the scriptPath attribute

Script NameCount
None21

Certificates

This detects trusted certificate which can be used in man in the middle attacks or which can issue smart card logon certificates

Number of trusted certificates: 17

[17]
SourceStoreSubjectIssuerNotBeforeNotAfterModule sizeSignature AlgSC Logon
GPO:Default Domain Policy;MachineRootCN=AddTrust External CA Root, OU=AddTrust External TTP Network, O=AddTrust AB, C=SECN=AddTrust External CA Root, OU=AddTrust External TTP Network, O=AddTrust AB, C=SE2000-05-30 12:48:38Z2020-05-30 12:48:38Z2048sha1RSAFalse
GPO:Default Domain Policy;MachineRootCN=Belgium Root CA2, C=BECN=Belgium Root CA2, C=BE2007-10-04 12:00:00Z2021-12-15 09:00:00Z2048sha1RSAFalse
GPO:Default Domain Policy;MachineRootCN=MaskTech CSCA, OU=Test Division, O=MaskTech GmbH, C=DECN=MaskTech CSCA, OU=Test Division, O=MaskTech GmbH, C=DE2014-02-13 15:30:41Z2019-01-16 15:30:41Z3072sha1RSAFalse
GPO:Default Domain Policy;MachineRootCN=CA, DC=test, DC=mysmartlogon, DC=comCN=CA, DC=test, DC=mysmartlogon, DC=com2015-10-03 09:34:06Z2030-10-02 09:44:04Z2048sha1RSAFalse
GPO:Default Domain Policy;MachineRootCN=DOD EMAIL CA-29, C=US, O=U.S. Government, OU=DoD, OU=PKICN=DOD EMAIL CA-29, C=US, O=U.S. Government, OU=DoD, OU=PKI2014-05-01 09:08:21Z2041-09-15 09:08:21Z2048sha1RSAFalse
GPO:Default Domain Policy;MachineCASERIALNUMBER=200804, CN=Foreigner CA, C=BECN=Belgium Root CA2, C=BE2007-10-04 14:00:00Z2014-06-04 14:00:00Z2048sha1RSAFalse
GPO:Default Domain Policy;MachineCACN=UTN-USERFirst-Object, OU=http://www.usertrust.com, O=The USERTRUST Network, L=Salt Lake City, S=UT, C=USCN=AddTrust External CA Root, OU=AddTrust External TTP Network, O=AddTrust AB, C=SE2005-06-07 10:09:10Z2020-05-30 12:48:38Z2048sha1RSAFalse
GPO:Default Domain Policy;MachineCACN=COMODO Code Signing CA 2, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GBCN=UTN-USERFirst-Object, OU=http://www.usertrust.com, O=The USERTRUST Network, L=Salt Lake City, S=UT, C=US2011-08-24 02:00:00Z2020-05-30 12:48:38Z2048sha1RSAFalse
Enterprise NTAuth ?NTLMStoreCN=CA, DC=test, DC=mysmartlogon, DC=comCN=CA, DC=test, DC=mysmartlogon, DC=com2015-10-03 09:34:06Z2030-10-02 09:44:04Z2048sha1RSAFalse
Enterprise NTAuth ?NTLMStoreCN=MaskTech CSCA, OU=Test Division, O=MaskTech GmbH, C=DECN=MaskTech CSCA, OU=Test Division, O=MaskTech GmbH, C=DE2014-02-13 15:30:41Z2019-01-16 15:30:41Z3072sha1RSAFalse
Enterprise NTAuth ?NTLMStoreCN=Belgium Root CA2, C=BECN=Belgium Root CA2, C=BE2007-10-04 12:00:00Z2021-12-15 09:00:00Z2048sha1RSAFalse
Enterprise NTAuth ?NTLMStoreCN=COMODO Code Signing CA 2, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GBCN=UTN-USERFirst-Object, OU=http://www.usertrust.com, O=The USERTRUST Network, L=Salt Lake City, S=UT, C=US2011-08-24 02:00:00Z2020-05-30 12:48:38Z2048sha1RSAFalse
Enterprise NTAuth ?NTLMStoreCN=DOD EMAIL CA-29, C=US, O=U.S. Government, OU=DoD, OU=PKICN=DOD EMAIL CA-29, C=US, O=U.S. Government, OU=DoD, OU=PKI2014-05-01 09:08:21Z2041-09-15 09:08:21Z2048sha1RSAFalse
Enterprise NTAuth ?NTLMStoreCN=AddTrust External CA Root, OU=AddTrust External TTP Network, O=AddTrust AB, C=SECN=AddTrust External CA Root, OU=AddTrust External TTP Network, O=AddTrust AB, C=SE2000-05-30 12:48:38Z2020-05-30 12:48:38Z2048sha1RSAFalse
Enterprise NTAuth ?NTLMStoreCN=UTN-USERFirst-Object, OU=http://www.usertrust.com, O=The USERTRUST Network, L=Salt Lake City, S=UT, C=USCN=AddTrust External CA Root, OU=AddTrust External TTP Network, O=AddTrust AB, C=SE2005-06-07 10:09:10Z2020-05-30 12:48:38Z2048sha1RSAFalse
Enterprise NTAuth ?NTLMStoreCN=COMODO Code Signing CA, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GBCN=UTN-USERFirst-Object, OU=http://www.usertrust.com, O=The USERTRUST Network, L=Salt Lake City, S=UT, C=US2011-04-27 02:00:00Z2020-05-30 12:48:38Z2048sha1RSAFalse
Enterprise NTAuth ?NTLMStoreCN=CA, DC=test, DC=mysmartlogon, DC=comCN=CA, DC=test, DC=mysmartlogon, DC=com2012-03-03 19:21:37Z2027-03-03 19:31:35Z2048sha1RSAFalse

Password policies

Note: PSO (Password Settings Objects) will be visible only if the user which collected the information has the permission to view it.
PSO shown in the report will be prefixed by "PSO:"

Policy NameComplexityMax Password AgeMin Password AgeMin Password LengthPassword HistoryReversible EncryptionLockout ThresholdLockout DurationReset account counter locker after
Default Domain Controllers Policy ?FalseNever expires0 day0Not SetNot SetNot SetNot SetNot Set
Default Domain Policy ?FalseNever expires0 day00False0Not SetNot Set
test nfc 2 [Not linked] ?FalseNever expires0 day1Not SetNot SetNot SetNot SetNot Set
PSO:testFalse90 day(s)0 day05False505 minute(s)1 minute(s)

Screensaver policies

This is the settings related to screensavers stored in Group Policies. Each non compliant setting is written in red.

Policy NameScreensaver enforcedPassword requestStart after (seconds)Grace Period (seconds)
test nfc 2 [Not linked] ?TrueTrue90000Not Set

GPO

This section focuses on security settings stored in the Active Directory technical security policies.

Obfuscated Passwords

The password in GPO are obfuscated, not encrypted. Consider any passwords listed here as compromised and change it immediatly.

GPO NamePassword originUserNamePasswordChangedOther
test nfc 2groups.xmladministratorvletoux2016-04-02 19:40:14ZNewName:adiant-admin
test nfc 2drives.xmladiantvletoux2016-04-02 19:39:33ZPath:test
test nfc 2groups.xmltesttest2016-04-02 20:21:02Z
WEF testregistry.xmlssssdddd2019-09-17 16:56:10ZAutologon info

Restricted Groups

Giving local group membership in a GPO is a way to become administrator.
The local admin of a domain controller can become domain administrator instantly.

Security settings

A GPO can be used to deploy security settings to workstations.
The best practice out of the default security baseline is reported in green.
The following settings in red are unsual and may need to be reviewed.
Each setting is accompagnied which its value and a link to the GPO explanation.

Policy NameSettingValue
Default Domain Controllers Policy ?Allow anonymous SID/Name translation (Technical details)Enabled
Default Domain Controllers Policy ?Microsoft network server: Digitally sign communications (if client agrees) (Technical details)Disabled
Default Domain Policy ?Recovery console: Allow automatic administrative logonEnabled
Default Domain Policy ?LDAP client signing requirements (Technical details)None (Do not request signature)
Default Domain Policy ?Do not store LAN Manager hash value on next password change (Technical details)Disabled
Default Domain Policy ?Turn off multicast name resolution (Technical details)LLMNR Enabled

Audit settings

Audit settings allow the system to generate logs which are useful to detect intrusions. Here are the settings found in GPO.

Simple audit events are described here and Advanced audit events are described here

You can get a list of all audit settings with the command line: auditpol.exe /get /category:* (source)

Policy NameCategorySettingValue
Audit_Varonis ?Account LogonKerberos Authentication ServiceSuccess and Failure
Audit_Varonis ?Account LogonKerberos Service Ticket OperationsSuccess and Failure
Audit_Varonis ?Account LogonOther Account Logon EventsSuccess
Audit_Varonis ?Account ManagementApplication Group ManagementSuccess and Failure
Audit_Varonis ?Account ManagementComputer Account ManagementSuccess and Failure
Audit_Varonis ?Account ManagementDistribution Group ManagementSuccess and Failure
Audit_Varonis ?Account ManagementOther Account Management EventsSuccess and Failure
Audit_Varonis ?Account ManagementSecurity Group ManagementSuccess and Failure
Audit_Varonis ?Account ManagementUser Account ManagementSuccess and Failure
Audit_Varonis ?DS AccessDetailed Directory Service ReplicationSuccess
Audit_Varonis ?DS AccessDirectory Service AccessSuccess
Audit_Varonis ?DS AccessDirectory Service ChangesSuccess
Audit_Varonis ?DS AccessDirectory Service ReplicationSuccess
Audit_Varonis ?Logon/LogoffAccount LockoutSuccess
Audit_Varonis ?SystemUser/Device ClaimsSuccess
Audit_Varonis ?Logon/LogoffIPsec Extended ModeSuccess
Audit_Varonis ?Logon/LogoffIPsec Main ModeSuccess
Audit_Varonis ?Logon/LogoffIPsec Quick ModeSuccess
Audit_Varonis ?Logon/LogoffLogoffSuccess
Audit_Varonis ?Logon/LogoffLogonSuccess
Audit_Varonis ?Logon/LogoffNetwork Policy ServerSuccess
Audit_Varonis ?Logon/LogoffOther Logon/LogoffSuccess
Audit_Varonis ?Logon/LogoffSpecial LogonSuccess
Audit_Varonis ?Object AccessCertification ServicesSuccess
Audit_Varonis ?Object AccessOther Object AccessSuccess
Audit_Varonis ?Policy ChangeAudit Policy ChangeSuccess
Audit_Varonis ?Policy ChangeAuthentication Policy ChangeSuccess
Audit_Varonis ?Policy ChangeAuthorization Policy ChangeSuccess
Audit_Varonis ?Policy ChangeFiltering Platform Policy ChangeSuccess
Audit_Varonis ?Policy ChangeMPSSVC Rule-Level Policy ChangeSuccess
Audit_Varonis ?Policy ChangeOther Policy Change EventsSuccess
Audit_Varonis ?SystemIPsec DriverSuccess
Audit_Varonis ?SystemOther System EventsSuccess and Failure
Audit_Varonis ?SystemSecurity State ChangeSuccess
Audit_Varonis ?SystemSecurity System ExtensionSuccess
Audit_Varonis ?SystemSystem IntegritySuccess and Failure

Privileges

Giving privileges in a GPO is a way to become administrator without being part of a group.
For example, SeTcbPriviledge give the right to act as SYSTEM, which has more privileges than the administrator account.

GPO NamePrivilegeMembers
Default Domain Controllers Policy ?SeAssignPrimaryTokenPrivilegeIIS APPPOOL\crl.eid.belgium.be
Default Domain Controllers Policy ?SeAssignPrimaryTokenPrivilegeIIS APPPOOL\SmartPolicy
Default Domain Controllers Policy ?SeAssignPrimaryTokenPrivilegeNT AUTHORITY\LOCAL SERVICE
Default Domain Controllers Policy ?SeAssignPrimaryTokenPrivilegeNT AUTHORITY\NETWORK SERVICE
Default Domain Controllers Policy ?SeAssignPrimaryTokenPrivilegeIIS APPPOOL\DefaultAppPool
Default Domain Controllers Policy ?SeAssignPrimaryTokenPrivilegeIIS APPPOOL\Classic .NET AppPool
Default Domain Controllers Policy ?SeBackupPrivilegeAdministrators
Default Domain Controllers Policy ?SeBackupPrivilegeBUILTIN\Backup Operators
Default Domain Controllers Policy ?SeBackupPrivilegeBUILTIN\Server Operators
Default Domain Controllers Policy ?SeDebugPrivilegeAdministrators
Default Domain Controllers Policy ?SeLoadDriverPrivilegeAdministrators
Default Domain Controllers Policy ?SeLoadDriverPrivilegeBUILTIN\Print Operators
Default Domain Controllers Policy ?SeMachineAccountPrivilegeAuthenticated Users
Default Domain Controllers Policy ?SeMachineAccountPrivilegeAuthenticated Users
Default Domain Controllers Policy ?SeRestorePrivilegeAdministrators
Default Domain Controllers Policy ?SeRestorePrivilegeBUILTIN\Backup Operators
Default Domain Controllers Policy ?SeRestorePrivilegeBUILTIN\Server Operators
Default Domain Controllers Policy ?SeSecurityPrivilegeAdministrators
Default Domain Controllers Policy ?SeTakeOwnershipPrivilegeAdministrators
Default Domain Controllers Policy ?SeEnableDelegationPrivilegeAdministrators
Default Domain Policy ?SeDebugPrivilegeEveryone
Default Domain Policy ?SeLoadDriverPrivilegeEveryone
test nfc 2 [Not linked] ?SeDebugPrivilegeadiant-test
test nfc 2 [Not linked] ?SeDebugPrivilegeEveryone
test nfc 2 [Not linked] ?SeLoadDriverPrivilegeEveryone

Login

Login authorization and restriction can be set by GPO. Indeed, by default, everyone is allowed to login on every computer except domain controllers. Defining login restriction is a way to have different isolated tiers. Here are the settings found in GPO.

GPO NamePrivilegeMembers
Banned Login for admin ?Deny access to this computer from the network ?Domain Admins
Banned Login for admin ?Deny log on as a batch job ?Domain Admins
Banned Login for admin ?Deny log on as a service ?Domain Admins
Banned Login for admin ?Deny log on locally ?Domain Admins
Banned Login for admin ?Deny logon through Remote Desktop Services ?Domain Admins
Banned Login for admin ?Allow log on locally ?Domain Users
Banned Login for admin ?Allow log on locally ?Administrators
Banned Login for admin ?Allow logon through Remote Desktop Services ?Domain Users
Default Domain Controllers Policy ?Log on as a batch job ?Administrators
Default Domain Controllers Policy ?Log on as a batch job ?BUILTIN\Backup Operators
Default Domain Controllers Policy ?Log on as a batch job ?BUILTIN\IIS_IUSRS
Default Domain Controllers Policy ?Log on as a batch job ?BUILTIN\Performance Log Users
Default Domain Controllers Policy ?Log on as a batch job ?TEST\test
Default Domain Controllers Policy ?Allow log on locally ?BUILTIN\Server Operators
Default Domain Controllers Policy ?Allow log on locally ?BUILTIN\Print Operators
Default Domain Controllers Policy ?Allow log on locally ?Everyone
Default Domain Controllers Policy ?Allow log on locally ?BUILTIN\Backup Operators
Default Domain Controllers Policy ?Allow log on locally ?Authenticated Users
Default Domain Controllers Policy ?Allow log on locally ?Administrators
Default Domain Controllers Policy ?Allow log on locally ?BUILTIN\Account Operators
Default Domain Controllers Policy ?Access this computer from the network ?Everyone
Default Domain Controllers Policy ?Access this computer from the network ?Administrators
Default Domain Controllers Policy ?Access this computer from the network ?Authenticated Users
Default Domain Controllers Policy ?Access this computer from the network ?NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS
Default Domain Controllers Policy ?Access this computer from the network ?BUILTIN\Pre-Windows 2000 Compatible Access
Default Domain Controllers Policy ?Allow logon through Remote Desktop Services ?Authenticated Users

GPO Login script

A GPO login script is a way to force the execution of data on behalf of users. Only enabled users are analyzed.

GPO NameActionSourceCommand lineParameters
test nfc 2 [Not linked] ?Logonscripts.ini (User section)test.vbsmachin trust
test nfc 2 [Not linked] ?Logoffscripts.ini (User section)test123
test nfc 2 [Not linked] ?Logoffscripts.ini (User section)tatayoyo
test nfc 2 [Not linked] ?Logonpsscripts.ini (User section)test.ps1tsettte
test nfc 2 [Not linked] ?Logoffpsscripts.ini (User section)test456
Default Domain Controllers Policy ?LogonRegistry.pol (Computer section)\\test.mysmartlogon.com\sysvol\test.mysmartlogon.com\bin\test.ps1

GPO Deployed Files

A GPO can be used to deploy applications or copy files. These files may be controlled by a third party to control the execution of local programs.

GPO NameTypeFile
WEF test [Not linked] ?Files (User section)\\test.mysmartlogon.com\sysvol\test.mysmartlogon.com\bin\test.txt
WEF test [Not linked] ?Application (Computer section)\\test.mysmartlogon.com\SYSVOL\test.mysmartlogon.com\bin\7z1900.msi
WEF test [Not linked] ?Application (Computer section)\\test.mysmartlogon.com\SYSVOL\test.mysmartlogon.com\bin\7z1900.msi