This model regroup all rules per category. It summarize what checks are performed. Click on a cell to show all rules associated to a category.
| Stale Objects | Privileged accounts | Trusts | Anomalies | |
|---|---|---|---|---|
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 | Control paths | Trust impermeability | Golden ticket | |
Old authentication protocols | Delegation Check | Trust inactive | Local group vulnerability | |
Provisioning | Irreversible change | Trust with Azure | Network sniffing | |
Replication | Privilege control | Pass-the-credential | ||
Vulnerability management | Read-Only Domain Controllers | Password retrieval | ||
Reconnaissance | ||||
Temporary admins | ||||
Weak password |
Each line represents a rule. Click on a rule to expand it and show the details of it.
By reusing existing objects, whose credentials may be the same among all objects or stored on configuration files or in memory, a third party can take them over.
S-PwdLastSet-45
Description:The purpose is to ensure that the regular change of computer account is active
Technical explanation:By default, each computers change automatically its password every 30 days.
Changing regularly secrets like passwords ensures that they are not used in side channel attacks.
Also with the default possibility to create up to 10 computers accounts, these accounts may be seen as a backdoor.
This audit program considers this as an anomaly between 45 days and 90 days.
Also this rule is the companion for the rule S-PwdLastSet-90
Some security agencies report the absence of password change as an indicator of compromise.
If it is not the case, check the following registry keys:
* HKLM\System\CurrentControlSet\Services\Netlogon\Parameters\DisablePasswordChange: must be set to 0 or inexistent;
* HKLM\System\CurrentControlSet\Services\Netlogon\Parameters\MaximumPasswordAge: must be set to 30.
2.9.0.0
Points:5 points if present
Documentation:https://support.microsoft.com/en-us/help/154501/how-to-disable-automatic-machine-account-password-changes
[FR]ANSSI - Servers with passwords unchanged for more than 45 days (vuln3_password_change_server_no_change_45)3
[US]STIG V-63653 - The computer account password must not be prevented from being reset.
[US]STIG V-3373 - The maximum age for machine account passwords is not set to requirements.
S-PwdLastSet-90
Description:The purpose is to ensure that all computer accounts have their password changed in the last 3 months
Technical explanation:By default, each computers change automatically its password every 30 days.
Changing regularly secrets like passwords ensures that they are not used in side channel attacks.
Also with the default possibility to create up to 10 computers accounts, these accounts may be seen as a backdoor.
This audit program considers this as an anomaly starting with 90 days.
Also this rule is the companion for the rule S-PwdLastSet-45 which does the same between 45 and 90 days
Some security agencies report the absence of password change as an indicator of compromise.
If it is not the case, check the following registry keys:
* HKLM\System\CurrentControlSet\Services\Netlogon\Parameters\DisablePasswordChange: must be set to 0 or inexistent;
* HKLM\System\CurrentControlSet\Services\Netlogon\Parameters\MaximumPasswordAge: must be set to 30.
2.9.0.0
Points:15 points if present
Documentation:https://support.microsoft.com/en-us/help/154501/how-to-disable-automatic-machine-account-password-changes
[FR]ANSSI - Servers with passwords unchanged for more than 90 days (vuln2_password_change_server_no_change_90)2
[US]STIG V-63653 - The computer account password must not be prevented from being reset.
[US]STIG V-3373 - The maximum age for machine account passwords is not set to requirements.
S-DC-Inactive
Description:The purpose is to ensure that every DC is active.
Technical explanation:Domain Controllers are user accounts with powerfull privileges.
While an active Domain Controller change its password every 30 days, an inactive account can be involved in a domain compromise.
Indeed, another account, which have rights over this object, may reset the password of this account without being noticed.
You have to demote the DC object using the procedure referenced in the documentation section.
2.9.0.0
Points:5 points per discovery
Documentation:https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/demoting-domain-controllers-and-domains--level-200-
[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R45 [paragraph.3.6.6.2]
[FR]ANSSI - Inactive domain controllers (vuln1_password_change_inactive_dc)1
S-PwdLastSet-DC
Description:The purpose is to ensure that the regular change of computer account is active on Domain Controllers.
Technical explanation:By default, each computers change automatically its password every 30 days. This is the same case for domain controllers.
Changing regularly secrets like passwords ensures that they are not used in side channel attacks.
For exemple, using DCSync to export the hash of a domain controller password, then reusing it in a silver attack to create kerberos tickets.
This audit program considers this as an anomaly after 45 days.
Some security agencies report the absence of password change as an indicator of compromise.
If it is not the case, check the following registry keys:
* HKLM\System\CurrentControlSet\Services\Netlogon\Parameters\DisablePasswordChange: must be set to 0 or inexistent;
* HKLM\System\CurrentControlSet\Services\Netlogon\Parameters\MaximumPasswordAge: must be set to 30.
2.9.0.0
Points:5 points per discovery
Documentation:https://support.microsoft.com/en-us/help/154501/how-to-disable-automatic-machine-account-password-changes
[FR]ANSSI - Domain controllers with passwords unchanged for more than 45 days (vuln1_password_change_dc_no_change)1
[US]STIG V-63653 - The computer account password must not be prevented from being reset.
[US]STIG V-3373 - The maximum age for machine account passwords is not set to requirements.
S-Inactive
Description:The purpose is to ensure that there are as few inactive accounts as possible within the domain
Technical explanation:Inactive accounts often stay in the network because of weaknesses in the decommissioning process. These stale computer accounts can be used as backdoors and therefore represents a possible security breach.
Advised solution:To mitigate the risk, you should monitor the number of inactive accounts and reduce it as much as possible. A list of all inactive accounts is obtainable through the command: Search-ADaccount -UsersOnly -AccountInactive -Timespan (New-TimeSpan -Days 180).
Points:10 points if the occurence is greater than or equals than 25
Documentation:[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R45 [paragraph.3.6.6.2]
[FR]ANSSI - Dormant accounts (vuln1_user_accounts_dormant)1
S-C-Inactive
Description:The purpose is to ensure that there are as few inactive computers as possible within the domain
Technical explanation:Inactive computers often stay in the network because of weaknesses in the decommissioning process. These stale computer accounts can be used as backdoors and therefore represents a possible security breach.
Advised solution:To mitigate the risk, you should monitor the number of inactive accounts and reduce it as much as possible. A list of all inactive accounts is obtainable through the command: Search-ADaccount -ComputersOnly -AccountInactive -Timespan (New-TimeSpan -Days 180).
Points:30 points if the occurence is greater than or equals than 30
then 10 points if the occurence is greater than or equals than 20
then 5 points if the occurence is greater than or equals than 15
[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R45 [paragraph.3.6.6.2]
[FR]ANSSI - Inactive servers (vuln3_password_change_inactive_servers)3
It is important to have a database of all the assets and control the physical security of the server. If one server is compromised physically, all the secrets of the domain can be exposed.
S-DC-SubnetMissing
Description:The purpose is to ensure that the minimum set of subnet(s) has been configured in the domain
Technical explanation:When multiple sites are created in a domain, networks should be declared in the domain in order to optimize processes such as DC attribution. In addition, PingCastle can collect the information to be able to build a network map. This rule has been triggered because at least one domain controller has an IP address which was not found in subnet declaration. These IP addresses have been collected by querying the DC FQDN IP address in both IPv6 and IPv4 format.
Advised solution:Locate the IP address which was found as not being part of declared subnet then add this subnet to the "Active Directory Sites" tool. If you have found IPv6 addresses and it was not expected, you should disable the IPv6 protocol on the network card.
Introduced in:2.5.0.0
Points:5 points if present
By abusing a misconfiguration, an attacker can gain the control of the domain.
S-C-PrimaryGroup
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.
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:[FR]ANSSI - Accounts with modified PrimaryGroupID (vuln3_primary_group_id_nochange)3
S-PrimaryGroup
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.
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:[FR]ANSSI - Accounts with modified PrimaryGroupID (vuln3_primary_group_id_nochange)3
S-C-Reversible
Description:The purpose is to verify if there are accounts currently running with a reversible password
Technical explanation:It is possible that domains have accounts with an encryption that can be reversed. In this case, it means that the password is actually stored in clear text in the supplementalCredential attribute of the account and that it can be retrieved using DCSync attack
Advised solution:To remove this risk, there should be no account(s) with reversible encryption. You should remove them by removing the flag "Store password using reversible encryption" on all accounts, so that the cleartext password is removed at the next password change. You can get a list of all the possibly compromised accounts running the following PowerShell command: get-adobject -ldapfilter "(userAccountControl:1.2.840.113556.1.4.803:=128)" -properties useraccountcontrol
Points:5 points if present
Documentation:[FR]ANSSI - Accounts with passwords stored using reversible encryption (vuln3_reversible_password)3
S-Reversible
Description:The purpose is to verify if there are user accounts currently running with a reversible password
Technical explanation:It is possible that domains have accounts with an encryption that can be reversed. In this case, it means that the password is actually stored in clear text in the supplementalCredential attribute of the account and that it can be retrieved using DCSync attack
Advised solution:To remove this risk, there should be no account(s) with reversible encryption. You should remove them by removing the flag "Store password using reversible encryption" on all accounts, so that the cleartext password is removed at the next password change. You can get a list of all the possibly compromised accounts running the following PowerShell command: get-adobject -ldapfilter "(userAccountControl:1.2.840.113556.1.4.803:=128)" -properties useraccountcontrol
Points:5 points if present
Documentation:[FR]ANSSI - Accounts with passwords stored using reversible encryption (vuln3_reversible_password)3
S-NoPreAuth
Description:The purpose is to ensure that all accounts do support kerberos pre-authentication
Technical explanation:Without kerberos pre-authentication, an attacker can request kerberos data from the domain controller and use this data to brute-force the account password. You can search accounts using the ldap query (userAccountControl:1.2.840.113556.1.4.803:=4194304)
Advised solution:Edit the property of the involved accounts and select the Account tab. Uncheck "Do not require Kerberos preauthentication". For computers which doesn't have the Account tab, you have to manually edit the attribute useraccountcontrol. Subtract from the attribute the value 4194304.
Points:5 points if present
Documentation:http://www.harmj0y.net/blog/activedirectory/roasting-as-reps/
[FR]ANSSI - Kerberos pre-authentication disabled (vuln2_kerberos_properties_preauth)2
S-NoPreAuthAdmin
Description:The purpose is to ensure that all admin accounts do support kerberos pre-authentication
Technical explanation:Without kerberos pre-authentication, an attacker can request kerberos data from the domain controller and use this data to brute-force the account password. You can search accounts using the ldap query (userAccountControl:1.2.840.113556.1.4.803:=4194304)
Advised solution:Edit the property of the involved accounts and select the Account tab. Uncheck "Do not require Kerberos preauthentication". For computers which doesn't have the Account tab, you have to manually edit the attribute useraccountcontrol. Subtract from the attribute the value 4194304.
Introduced in:2.9.0.0
Points:5 points per discovery
Documentation:http://www.harmj0y.net/blog/activedirectory/roasting-as-reps/
[FR]ANSSI - Kerberos pre-authentication disabled for privileged accounts (vuln1_kerberos_properties_preauth_priv)1
S-PwdNotRequired
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://docs.microsoft.com/troubleshoot/windows-server/identity/useraccountcontrol-manipulate-account-properties
[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R36 [subsection.3.6]
S-PwdNeverExpires
Description:The purpose is to ensure that every account has a password which is compliant with password expiration policies
Technical explanation:Some accounts have passwords which never expire. Should an attacker compromise one of these accounts, he would be able to maintain long-term access to the Active Directory domain.
We have noted that some Linux servers, domain joined, are configured with a password which never expires.
This is a misconfiguration because a password change can be configured. It was however not the default on some plateform.
See one of the link below for more information.
In order to make Active Directory enforce periodic password change, accounts must not have the "Password never expires" flag set in the "Account" tab of the user properties. Their passwords should then be rolled immediately.
For services accounts, Windows provide the "managed service accounts" and "group managed service accounts" features to facilite the automatic change of passwords.
Please note that there is a document in the section below which references solutions for service accounts of well known products.
Also Linux servers should be configured with automatic machine account change.
2.9.0.0
Points:1 points if present
Documentation:https://adsecurity.org/?p=4115
https://access.redhat.com/discussions/1283873
[FR]ANSSI - Accounts with never-expiring passwords (vuln2_dont_expire)2
S-SIDHistory
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.
5 points per discovery with a minimal of 15 points
Documentation:[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R15 [paragraph.3.3.1.5]
Operating systems have a lifecycle where its manufacturer provides patches. If the operating system is not supported anymore, vulnerabilities are not fixed anymore.
S-DC-2000
Description:The purpose is to ensure that there is no use of the obsolete and vulnerable OS Windows 2000 as Domain Controller within the domain
Technical explanation:The OS Windows 2000 as a DC is vulnerable to many publicly known exploits such as MS17-010 or MS14-068 and it can no longer be patched. A domain running this OS version should be considered compromised
Advised solution:To resolve this security risk, the only way is to decommission DC running Windows 2000 OS, in order to use new versions that are more secured and that are still being patched regarding new security threats
Points:40 points if present
Documentation:[US]STIG V-8551 - The domain functional level must be at a Windows Server version still supported by Microsoft.
[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R12 [subsection.3.1]
S-DC-2003
Description:The purpose is to ensure that there is no use of the obsolete and vulnerable OS Windows 2003 as Domain Controller within the domain
Technical explanation:The OS Windows 2003 as a DC is vulnerable to many publicly known exploits such as MS14-068 and it is very complicated to patch it at this date. A domain running this OS version should be considered compromised
Advised solution:To resolve this security risk, the only way is to decommission DC running Windows 2003 OS, in order to use new versions that are more secured and that are still being patched regarding new security threats
Points:20 points if present
Documentation:[US]STIG V-8551 - The domain functional level must be at a Windows Server version still supported by Microsoft.
[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R12 [subsection.3.1]
S-DC-2008
Description:The purpose is to ensure that there is no use of the obsolete and vulnerable OS Windows 2008 as Domain Controller within the domain
Technical explanation:The OS Windows 2008 is not supported anymore by Microsoft (except when migrated to Azure) and any vulnerability found will not be patched unless an expensive support contrat has been purchased.
Advised solution:To resolve this security risk, the only way is to decommission DC running Windows 2008 OS, in order to use new versions that are more secured and that are still being patched regarding new security threats
Points:5 points if present
Documentation:https://support.microsoft.com/en-us/help/4456235/end-of-support-for-windows-server-2008-and-windows-server-2008-r2
[US]STIG V-8551 - The domain functional level must be at a Windows Server version still supported by Microsoft.
[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R12 [subsection.3.1]
S-OS-2000
Description:The purpose is to ensure that there is no use of the obsolete and vulnerable OS Windows 2000 for the workstations within the domain
Technical explanation:The Windows 2000 OS is not supported any longer, as it is vulnerable to many publicly known exploits: Administrator's credentials can be captured, security protocols are weak, etc.
Advised solution:In order to solve this security issue, you should upgrade all the workstations to a more recent version of Windows, starting from Windows 7. Do note that you can get the full details regarding the OS used with the following PowerShell command: Get-ADComputer -Filter * -Property * | Format-Table Name,OperatingSystem,OperatingSystemServicePack,OperatingSystemVersion -Wrap -Auto You can replace [-Filter *] by [-Filter {OperatingSystem -Like "Windows Server*"}
Points:40 points if present
Documentation:S-OS-2003
Description:The purpose is to ensure that there is no use of the obsolete and vulnerable OS Windows 2003 for the workstations within the domain
Technical explanation:The Windows 2003 OS is not supported any longer, as it is vulnerable to many publicly known exploits: Administrator's credentials can be captured, security protocols are weak, etc.
Advised solution:In order to solve this security issue, you should upgrade all the workstations to a more recent version of Windows, starting from Windows 7. Do note that you can get the full details regarding the OS used with the following PowerShell command: Get-ADComputer -Filter * -Property * | Format-Table Name,OperatingSystem,OperatingSystemServicePack,OperatingSystemVersion -Wrap -Auto You can replace [-Filter *] by [-Filter {OperatingSystem -Like "Windows Server*"}
Points:30 points if the occurence is greater than or equals than 15
then 25 points if the occurence is greater than or equals than 6
then 20 points if present
S-OS-2008
Description:The purpose is to ensure that there is no use of the obsolete and vulnerable OS Windows 2008 for the workstations within the domain
Technical explanation:The Windows 2008 OS is not supported any longer, as it is vulnerable to many publicly known exploits: Administrator's credentials can be captured, security protocols are weak, etc.
Advised solution:In order to solve this security issue, you should upgrade all the servers to a more recent version of Windows, starting from Windows 2012. Do note that you can get the full details regarding the OS used with the following PowerShell command: Get-ADComputer -Filter * -Property * | Format-Table Name,OperatingSystem,OperatingSystemServicePack,OperatingSystemVersion -Wrap -Auto You can replace [-Filter *] by [-Filter {OperatingSystem -Like "Windows Server*"}
Points:15 points if the occurence is greater than or equals than 15
then 10 points if the occurence is greater than or equals than 6
then 5 points if present
https://support.microsoft.com/en-us/help/4456235/end-of-support-for-windows-server-2008-and-windows-server-2008-r2
[FR]ANSSI CERTFR-2005-INF-003
S-OS-Win7
Description:The purpose is to ensure that there is no use of the obsolete and vulnerable OS Windows 7 for the workstations within the domain
Technical explanation:The Windows 7 OS is not supported any longer, as it is vulnerable to many publicly known exploits: Administrator's credentials can be captured, security protocols are weak, etc.
PingCastle is trying to guess if support has been purchased from Microsoft. Based on the documentation referenced below, the program checks if the script Activate-ProductOnline.ps1 is present.
If the script is detected, Windows 7 is considered as supported and this rule is not triggered.
In order to solve this security issue, you should upgrade all the workstations to a more recent version of Windows, starting from Windows 10. Do note that you can get the full details regarding the OS used with the following PowerShell command: Get-ADComputer -Filter * -Property * | Format-Table Name,OperatingSystem,OperatingSystemServicePack,OperatingSystemVersion -Wrap -Auto You can replace [-Filter *] by [-Filter {OperatingSystem -Like "Windows Server*"}
Introduced in:2.9.0.0
Points:5 points if the occurence is greater than or equals than 15
then 2 points if the occurence is greater than or equals than 6
then 1 points if present
https://techcommunity.microsoft.com/t5/windows-it-pro-blog/activate-windows-7-esus-on-multiple-devices-with-a-mak/ba-p/1167196
[FR]ANSSI CERTFR-2005-INF-003
S-OS-NT
Description:The purpose is to ensure that there is no use of the obsolete and vulnerable OS Windows NT for the workstations within the domain
Technical explanation:The Windows NT OS is not supported any longer, as it is vulnerable to many publicly known exploits: Administrator's credentials can be captured, security protocols are weak, etc.
In order to solve this security issue, you should upgrade all the workstations to a more recent version of Windows, starting from Windows 7. Do note that you can get the full details regarding the OS used with the following PowerShell command: Get-ADComputer -Filter * -Property * | Format-Table Name,OperatingSystem,OperatingSystemServicePack,OperatingSystemVersion -Wrap -Auto You can replace [-Filter *] by [-Filter {OperatingSystem -Like "Windows Server*"}
Points:60 points if present
Documentation:S-OS-Vista
Description:The purpose is to ensure that there is no use of the obsolete and vulnerable OS Windows Vista for the workstations within the domain
Technical explanation:The Windows Vista OS is not supported any longer, as it is vulnerable to many publicly known exploits: Administrator's credentials can be captured, security protocols are weak, etc.
Advised solution:In order to solve this security issue, you should upgrade all the workstations to a more recent version of Windows, starting from Windows 10. Do note that you can get the full details regarding the OS used with the following PowerShell command: Get-ADComputer -Filter * -Property * | Format-Table Name,OperatingSystem,OperatingSystemServicePack,OperatingSystemVersion -Wrap -Auto You can replace [-Filter *] by [-Filter {OperatingSystem -Like "Windows Server*"}
Introduced in:2.8.0.0
Points:20 points if the occurence is greater than or equals than 15
then 15 points if the occurence is greater than or equals than 6
then 10 points if present
S-OS-XP
Description:The purpose is to ensure that there is no use of the obsolete and vulnerable OS Windows XP for the workstations within the domain
Technical explanation:The Windows XP OS is not supported any longer, as it is vulnerable to many publicly known exploits: Administrator's credentials can be captured, security protocols are weak, etc.
Advised solution:In order to solve this security issue, you should upgrade all the workstations to a more recent version of Windows, starting from Windows 7. Do note that you can get the full details regarding the OS used with the following PowerShell command: Get-ADComputer -Filter * -Property * | Format-Table Name,OperatingSystem,OperatingSystemServicePack,OperatingSystemVersion -Wrap -Auto You can replace [-Filter *] by [-Filter {OperatingSystem -Like "Windows Server*"}
Points:20 points if the occurence is greater than or equals than 15
then 15 points if the occurence is greater than or equals than 6
then 10 points if present
Cryptography and computer power have evolved during the time and the oldest protocols do not provide the same level of security anymore. They can be broken and used to gain control of the domain.
S-DesEnabled
Description:The purpose is to verify that no weak encryption algorithm such as DES is used as crypto algorithm.
Technical explanation:DES is very weak algorithm and once assigned to an account, it can be used in Kerberos ticket requests, even though it is easily breakable. It represents a security risk for the kerberos ticket, therefore for the whole AD.
Advised solution:It is recommended to disable DES as an encyrption algorithm in the user configuration dialog or in the "msDSSupportedEncryptionTypes" attribute at LDAP level. It has to be disabled in the property of an account by unchecking the box "Use Kerberos DES encryption for this account"
Points:15 points if present
Documentation:https://docs.microsoft.com/en-us/archive/blogs/openspecification/msds-supportedencryptiontypes-episode-1-computer-accounts
[FR]ANSSI - Use of Kerberos with weak encryption (vuln2_kerberos_properties_deskey)2
S-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
https://docs.microsoft.com/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3
[FR]ANSSI CERTFR-2017-ACT-019
[FR]ANSSI CERTFR-2016-ACT-039
It is important to control who can create new objects in the Active Directory. Indeed, its owner may introduced an object in which it has a strong control.
S-DCRegistration
Description:The purpose is to ensure that DC are well registered.
Technical explanation:To be registered as a domain controller, a computer must be a member of the domain controller group, but also has some specific settings.
The settings are a change of the userAccountControl attribute and a couple of objects in the configuration partition.
This rule is triggered when an inconsistency has been detected between the expected values and the real values.
The user account control value for Read/Write DC is:
SERVER_TRUST_ACCOUNT (0x00002000) | TRUSTED_FOR_DELEGATION (0x00080000) = 0x00082000
The user account control value for Read Only DC is:
PARTIAL_SECRETS_ACCOUNT (0x04000000) | TRUSTED_TO_AUTHENTICATE_FOR_DELEGATION (0x01000000) | WORKSTATION_TRUST_ACCOUNT (0x00001000) = 0x05001000
This rule result is either the result of a manual or software based misconfiguration. It can also be the sign of a compromise.
Depending on the anonamly reported, you have to perform the following actions:
- for InvalidUserAccount:
you have to check that the userAccountControl attribute of the AD object is either 0x00082000 for RW DC or 0x05001000 for RODC
- for NoConfiguration:
the DC registration in the Configuration partition is mising. The DC should not be active and need to be demoted.
- for NoNTDS:
the NTDS part of the DC Configuration is missing. Most probably the replication is not working. The DC should be demoted.
2.9.0.0
Points:10 points if present
Documentation:https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-adts/9164e4e8-f892-4ca2-8067-059f6f9387a4
https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-adts/8ebf2419-1169-4413-88e2-12a5ad499cf5
[FR]ANSSI - Domain controllers in inconsistent state (vuln1_dc_inconsistent_uac)1
S-ADRegistration
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:https://docs.microsoft.com/troubleshoot/windows-server/identity/default-workstation-numbers-join-domain
http://prajwaldesai.com/allow-domain-user-to-add-computer-to-domain/
http://blog.backslasher.net/preventing-users-from-adding-computers-to-a-domain.html
Active Directory uses a distributed architecture to have a high level of availability. This architecture replicates each change at a regular interval. Collision of changes can create unexpected objects which can be used later.
S-Duplicate
Description:The purpose is to verify if there currently are duplicate accounts within the domain. A duplicate account is essentially a duplicate of two objects having the same attributes.
Technical explanation:In order to identify a duplicate account, a check is performed on the "DN" and the "sAMAccountName". Indeed, when a DC detects a conflict, there is a replacement performed on the second object
Advised solution:Duplicate accounts often means there are weaknesses in term of processes, that is why they should be monitored and removed. To identify all duplicate accounts, you should use the following PowerShell commands: get-adobject -ldapfilter "(cn=*cnf:*)" ; get-adobject -ldapfilter "(sAMAccountName=$duplicate)"
Points:5 points if present
Patching computers is part of the security process. Unpatched vulnerability is a way to gain control of a computer.
S-Vuln-MS14-068
Description:The purpose is to verify if Domain Controller(s) are vulnerable to the MS14-068 vulnerability
Technical explanation:MS14-068 is a critical vulnerability that was published on November, 18th 2014. It can be used to very quickly compromise an entire domain, which is why having DC still vulnerable to this publicly known vulnerability represents a high security risk.
Advised solution:To fix the security breach, you should pacth the DC as soon as it has been established it was vulnerable. You can verify that using a program in the links: this program will check remotely the last startup time of the DC and evaluate the risk
Points:100 points if present
Documentation:https://technet.microsoft.com/en-us/library/security/ms14-068.aspx
[FR]ANSSI CERTFR-2014-ALE-011
S-Vuln-MS17_010
Description:The purpose is to verify if Domain Controller(s) are vulnerable to the MS17-010 vulnerability
Technical explanation:MS17-010 is a critical vulnerability that was published on March, 14th 2017. It can be used to compromise an entire domain via DC compromise. This exploit has been revealed by the Shadow brokers (EternalBlue, EternalRomance, EternalSinergy) and it uses the SMB v1 vulnerability
Advised solution:To fix the security breach, you should pacth the DC as soon as it has been established it was vulnerable. Another good remediation is to disable SMB v1 (see "DC Vulnerability (SMB v1)). You can verify that using the github program in the links: this program will check remotely the last startup time of the DC and evaluate the risk
Points:100 points if present
Documentation:https://blogs.technet.microsoft.com/msrc/2017/04/14/protecting-customers-and-evaluating-risk/
https://github.com/misterch0c/shadowbroker/tree/master/windows/exploits
[FR]ANSSI CERTFR-2017-ALE-010
S-DC-NotUpdated
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
Each line represents a rule. Click on a rule to expand it and show the details of it.
Members of administrators' groups are a priority target. By misconfiguring their protection, the password of the account can be retrieved by an attacker or it can leverage internal mechanisms of the AD such authentication to act on its behalf.
P-Delegated
Description:The purpose is to ensure that all Administrator Accounts have the configuration flag "this account is sensitive and cannot be delegated" (and are not member of the built-in group "Protected Users" when your domain functional level is at least Windows Server 2012 R2).
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 or add your Administrator Accounts to the built-in group "Protected Users" if your domain functional level is at least Windows Server 2012 R2 (some functionalities may not work properly afterwards, you should check the official documentation). Please note that there is a section bellow in this report named "Admin Groups" which give more information.
Points:20 points if present
Documentation:[US]STIG V-36435 - Delegation of privileged accounts must be prohibited.
P-Kerberoasting
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.
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.
2.7.0.0
Points:5 points per discovery
Documentation:https://adsecurity.org/?p=3466
[FR]ANSSI - Privileged accounts with SPN (vuln1_spn_priv)1
P-AdminPwdTooOld
Description:The purpose is to ensure that all admins are changing their passwords at least every 3 years
Technical explanation:This rule ensure that passwords of administrator are well managed.
Advised solution:We advised to read the ANSSI guidelines about this, which is quoted in the documentation section below.
2.9.0.0
Points:10 points if present
Documentation:[FR]ANSSI - Privileged account passwords age too old (vuln1_password_change_priv)1
P-ProtectedUsers
Description:The purpose is to ensure that all privileged accounts are in the special group Protected Users
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.
For admins, it:
- disable NTLM authentication
- reduce Kerberos ticket lifetime
- enforce usage of strong encryption algorthms such as AES
- prevent caching of passwords on workstations
- prevent any type of Kerberos delegation
Please also note that a few links (see below) recommends that at least one account is kept outside of the group Protected Users in case there is a permission problem.
That's why this rule is not triggered if only one account is not protected.
After having reviewed the potential impact on adding users to this group, add the missing privileged accounts to this group.
Introduced in:2.9.0.0
Points:10 points if the occurence is greater than or equals than 2
Documentation:https://docs.microsoft.com/en-us/windows-server/security/credentials-protection-and-management/protected-users-security-group
https://blog.netwrix.com/2015/02/20/add-sensitive-user-accounts-to-active-directory-protected-users-group/
https://dirteam.com/sander/2014/11/25/ten-things-you-need-to-be-aware-of-before-using-the-protected-users-group/
https://blog.andreas-schreiner.de/2018/09/07/active-directory-sicherheit-teil-1-privilegierte-benutzer/
[US]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.
[FR]ANSSI CERTFR-2017-ALE-012
[FR]ANSSI - Privileged accounts outside of the Protected Users group (vuln3_protected_users)3
P-LogonDenied
Description:The purpose is to ensure that there is a tier isolation.
Technical explanation:A way to collect an administrator credential is to take control of a workstation in the unsecure tiers and expect that an administrator will connect to it.
An attack such as credential theft or kerberos delegation is then performed.
To reduce the impact of such compromise, the best practice is to isolate components (such as admins, DC) in tiers.
Typically, a domain admin should not be allowed to connect to any workstation but login only to perform highly privileged operations.
To check for this policy, PingCastle looks at all GPO and check if there is a GPO denying logon (SeDenyRemoteInteractiveLogonRight, SeDenyInteractiveLogonRight) of admins (Domain Admins or Administrators) to a specific scope.
False positives can occurs for this rule:
* if the expected GPO is hidden due to ACL checks
* if the targeted group is not "checked" when saving the GPO. Indeed the group will be saved as is without a convertion to its technical name and it will prohibit a match if there are groups internationalized, aka renamed given a specific language.
As a consequence, only one deny policy on one group will fulfill this requirements. The program also do not check if the GPO is applied on an Organizational Unit or a Container.
Also this rule is enforced only if there is more than 200 users and 200 computers.
You should add a GPO prohibing the logon for the specific group: Domain Admins and Administrators.
The setting is located in Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment.
Then Deny log on locally and Deny logon through Remote Desktop Services.
2.8.0.0
Points:1 points if present
Documentation:Delegation is used to perform day to day activities. It is important to control it.
P-DCOwner
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)
10 points if present
Documentation:P-DangerousExtendedRight
Description:The purpose is to verify the presence of dangerous rights when a part of the domain is delegated to a third party
Technical explanation:The right "REANIMATE_TOMBSTONE" used to undelete objects, "UNEXPIRE_PASSWORD" used to undo the expiration of a password, or "SID_HISTORY" used to create an alternate identity is considered dangerous. Indeed this rights can be used to trigger a backdoor.
Advised solution:Unless there is a strong justification of their presence, these delegations should be removed. In addition, if the origin of this delegation cannot be found, their creation should be investigated as it can be related to a compromise of the domain
Points:5 points per discovery
Documentation:https://technet.microsoft.com/en-us/library/ff405676.aspx
[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R18 [subsubsection.3.3.2]
P-DsHeuristicsDoListObject
Description:The purpose is to check if the DoListObject feature has been enabled
Technical explanation:The DoListObject is a feature to probihit account located in an OU to look at another OU. It proceed by checking an special ACL named RIGHT_DS_LIST_OBJECT.
This is an informative rule.
If you want to reverse this behavior to its default value, find the dsHeuristics configuration which is located in CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration,DC=ad,DC=contoso,DC=com.
Then edit the 3rd character and set it to zero.
2.7.0.0
Points:Informative rule (0 point)
Documentation:https://dirteam.com/sander/2008/12/09/active-directory-visibility-modes/
https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-adts/e5899be4-862e-496f-9a38-33950617d2c5
https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-adts/990fb975-ab31-4bc1-8b75-5da132cd4584
P-DNSAdmin
Description:The purpose is to ensure that the Dns Admin group is not used
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.
The "Write All Prop" access right induces the vulnerability.
In this case, the DnsAdmins group is not empty and grant to its user, the possibility to interact with the DNS Service.
You should remove the members of the DNS admin group and do a proper delegation to the specific DNS Zones.
First, grant only "Read Property", "List", "List object" and "Read permssions" to CN=MicrosoftDNS,CN=System to enable access to the RPC service.
Then on each zone (the object in the tree below with the class dnsZone), grant "Read Property", "List", "List object", "Read permissions", "Create Child", "Delete Child", "Delete", "Delete Tree".
2.9.0.0
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
[FR]ANSSI - DnsAdmins group members (vuln1_dnsadmins)1
P-DNSDelegation
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.
The "Write All Prop" access right induces the vulnerability.
In this case, an explicit delegation has been setup and this delegation is not using the existing DnsAdmins group.
You should remove the explicit write delegation located in the CN=MicrosoftDNS,CN=System container and do a proper delegation.
First, grant only "Read Property", "List", "List object" and "Read permssions" to CN=MicrosoftDNS,CN=System to enable access to the RPC service.
Then on each zone (the object in the tree below with the class dnsZone), grant "Read Property", "List", "List object", "Read permissions", "Create Child", "Delete Child", "Delete", "Delete Tree".
2.8.0.0
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
P-DelegationLoginScript
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.
Introduced in:2.5.0.0
Points:15 points per discovery
Documentation:[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R18 [subsubsection.3.3.2]
[US]STIG V-2370 - The access control permissions for the directory service site group policy must be configured to use the required access permissions.
P-DelegationKeyAdmin
Description:The purpose is to ensure that no weaknesses have been introduced following a Windows 2016 installation.
Technical explanation:After performing adprep /domainprep from Windows Server 2016 sources there may be an unwanted AccessControlEntry (ACE) in the DiscretionaryACL (DACL) of the targeted domain-naming-context's SecurityDescriptor (SD) that grants FullControl permission to the Enterprise Key Admins group ( SID = ending with -527 ).
This is s a bug in ADPREP that was fixed in Windows Server 2016 RS3/1709. No official fix for those who used pre-1709.
Note: The SID will only be resolvable after the PDC emulator role is transferred to a Windows Server 2016 domain controller.
After having carefully studied the possible impact of the following change, apply the script made by MSRC and referenced in the documentation below to alter the permission.
Introduced in:2.6.0.0
Points:5 points if present
Documentation:https://gallery.technet.microsoft.com/scriptcenter/Enterprise-Key-Admins-720eb270
https://secureidentity.se/adprep-bug-in-windows-server-2016/
[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R18 [subsubsection.3.3.2]
[FR]ANSSI - Bad Active Directory versions (vuln2_adupdate_bad)2
P-ExchangePrivEsc
Description:The purpose is to ensure that Exchange Installation did not introduce privilege escalation vulnerabilites by modifying domain permissions
Technical explanation:When Exchange is installed, a set of permissions is modified to allow a deep Windows integration. A dependancy analysis has shown that the permissions that Exchange set introduce privilege escalation.
The most basic exploitation is that a member of the group Exchange Windows Permissions can modified the security permission of the domain, granting itself the right Ds-Replication-Get-Changes-All.
This right allows the account to perform an attack named DCSync which retrieve the hash of the krbtgt account. With this hash, the attacker can then create a golden ticket and impersonate silently any user of the domain.
Edit the root domain security descriptor. Identify the ACE giving the right ModifyDACL to the principal Exchange Windows Permissions. Go to the advanced settings and set the inheritance to Inherit Only.
Or run the powershell script Fix-DomainObjectDACL.ps1 referenced below.
2.7.0.0
Points:15 points per discovery
Documentation:https://github.com/gdedrouas/Exchange-AD-Privesc/blob/master/DomainObject/Fix-DomainObjectDACL.ps1
https://blogs.technet.microsoft.com/exchange/2019/02/12/released-february-2019-quarterly-exchange-updates/
https://support.microsoft.com/en-us/help/4490059/using-shared-permissions-model-to-run-exchange-server
[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R18 [subsubsection.3.3.2]
P-ExchangeAdminSDHolder
Description:The purpose is to ensure that no weakness has been introduced at Exchange installation.
Technical explanation:At install time, the Exchange Windows Permissions universal security group (USG) was granted the ability to modify the members attribute, the ability to change and reset passwords, and the ability to modify the permissions of any object protected by the AdminSDHolder role.
This security group includes all the Exchange servers.
As a consequence, a malicious administrator could elevate their privileges on one of the servers and thus gain control of the Active Directory forest.
Newest versions of Exchange do not introduce this security vulnerability.
After having carefully studied the possible impact of the following change, alter the AdminSDHolder permissions to remove the Exchange objects.
Introduced in:2.6.0.0
Points:5 points if present
Documentation:https://blogs.technet.microsoft.com/exchange/2009/09/23/exchange-2010-and-resolution-of-the-adminsdholder-elevation-issue/
[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R18 [subsubsection.3.3.2]
P-DelegationFileDeployed
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.
Introduced in:2.7.0.0
Points:5 points per discovery
Documentation:[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R18 [subsubsection.3.3.2]
[US]STIG V-2370 - The access control permissions for the directory service site group policy must be configured to use the required access permissions.
P-DelegationGPOData
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.
Introduced in:2.6.0.0
Points:15 points per discovery
Documentation:[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R18 [subsubsection.3.3.2]
[US]STIG V-2370 - The access control permissions for the directory service site group policy must be configured to use the required access permissions.
P-DsHeuristicsAdminSDExMask
Description:The purpose is to ensure that the AdminSDHolder mechanism has not been altered
Technical explanation:The AdminSDHolder service is a protection which prohibits an admin to loose control of the domain after a permission change or to introduce a weakness in the permissions.
It proceed by rewriting every 60 minutes the security descriptor of critical objects.
By modifying the dsHeuristics attribute, this protection can be disabled for one or more critical group.
Each critical group is associated with a value:
Account Operators: 1,
Server Operators: 2,
Print Operators:4,
Backup Operators: 8.
The 16th character of dsHeuristics represents the sum of the values associated to the groups where the AdminSDHolder has been disabled.
To disable it for the 'Backup Operators' and the 'Server Operators', the value is 8 + 2 = 0x0A = 'a'.
Find the dsHeuristics configuration which is located in CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration,DC=ad,DC=contoso,DC=com.
Then edit the 16th character and set it to zero.
2.7.0.0
Points:5 points if present
Documentation:https://www.petri.com/active-directory-security-understanding-adminsdholder-object
https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-adts/e5899be4-862e-496f-9a38-33950617d2c5
[FR]ANSSI - Dangerous dsHeuristics settings (vuln1_dsheuristics_bad)1
P-LoginDCEveryone
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.
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.
2.7.0.0
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
[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R18 [subsubsection.3.3.2]
P-RecoveryModeUnprotected
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.
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.
2.7.0.0
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
[US]STIG V-1159 - The Recovery Console option is set to permit automatic logon to the system.
It is important to know how much administrators are in place and to track the use of emergency accounts
P-Inactive
Description:The purpose is to ensure that the Administrator Accounts in the AD are all necessary and used
Technical explanation:Accounts within the AD have attributes indicating the creation date of the account and the last login of this account. Accounts which haven't have a login since 6 months or created more than 6 months ago without any login are considered inactive. If an Administrator Account is set as inactive, the reason for having Administrator rights should be strongly justified.
Advised solution:To correct the situation, you should make sure that all your Administrator Account(s) are "Active", meaning that you should remove Administrator rights if an account is set as not "Active"
Points:30 points if the occurence is greater than or equals than 30
then 20 points if the occurence is greater than or equals than 15
[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R36 [subsection.3.6]
P-AdminLogin
Description:The purpose is to verify if the Native Administrator account is used.
Technical explanation:The Native Administrator account is the main administrator account, and it is sharing its password with Directory Services Restore Mode password. Since it is the same password, it can be used to take control of the domain even if the account is disabled, notably through a DSync attack. The last login date is retrieved through the LastLogonTimestamp LDAP attribute retrieved from the Active Directory. There is an exception for 35 days to avoid this rule to be triggered at the domain creation.
Advised solution:To mitigate the security risk, a good practice is to use the Native Administrator account only for emergency, while the daily work is performed through other accounts.
It is indeed strongly recommended to not use this account but to use nominative account for administrators and dedicated account for services.
Do note that the anomaly will be removed 35 days after the last native administrator login.
To track where the administrator account has been used for the last time, we recommend to extract the attribute LastLogon of the administrator account on ALL domain controllers.
It can be done with tools such as ADSIEdit or ADExplorer.
Then, for each domain controller, extract the events 4624 at the date matching the LastLogon date. You will identify the computer and the process at the origin of the logon event.
Please note that PingCastle relies on the attribute LastLogonTimestamp to perform this check. The LastLogonTimestamp attribute is replicated but has a latency of a maximum of 14 days, while LastLogon is updated at each logon and is more accurate but not replicated.
20 points if the occurence is strictly lower than 35
Documentation:P-AdminNum
Description:The purpose is to verify if the number of administrator accounts is not disproportionate. Very few users should have domain admin accounts
Technical explanation:Every domain administrator represents a possible security breach, this is why it is strongly advised to have as few domain administrator accounts as possible
Advised solution:It is strongly advised to perform a review of which users have domain administrator rights, and to ensure that these rights are actually needed. Indeed, the end goal is to remove as much domain administrator as possible, as very few users actually need these high level rights.
The rule is trigger is the number of cumulated privileged members are 50 accounts or if it represents more than 10 percent of the user accounts.
The rule enabled only if the domain has more than 100 active users.
10 points if present
Documentation:https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/plan/security-best-practices/implementing-least-privilege-administrative-models
[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R26 [subsection.3.5]
[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R30 [subsubsection.3.5.7]
[FR]ANSSI - Large privileged group member count (vuln1_privileged_members)1
P-OperatorsEmpty
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:[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R27 [subsection.3.5]
Permissions granted to someone can be difficult to analyze. Hackers use this fact to chain multiple permission leaks in order to gain control of the domain.
P-ControlPathIndirectEveryone
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.
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.
2.8.0.0
Points:25 points if present
Documentation:https://github.com/BloodHoundAD/BloodHound
https://github.com/ANSSI-FR/AD-control-paths
P-ControlPathIndirectMany
Description:The purpose is to ensure that there is no control path involving a large number of users.
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.
You should analyze the chart and determine which underlying object is involved and grants too much write permissions.
Then edit the permissions and locate the write permission involved.
Then delete it or replace it according to your delegation model.
2.8.0.0
Points:25 points if the occurence is greater than or equals than 200
then 15 points if the occurence is greater than or equals than 100
then 10 points if the occurence is greater than or equals than 50
then 5 points if the occurence is greater than or equals than 20
https://github.com/BloodHoundAD/BloodHound
https://github.com/ANSSI-FR/AD-control-paths
P-DelegationEveryone
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:[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R18 [subsubsection.3.3.2]
[US]STIG V-2370 - The access control permissions for the directory service site group policy must be configured to use the required access permissions.
P-UnkownDelegation
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:P-DelegationDCt2a4d
Description:The purpose is to ensure that no contrained delegations with protocol transition are applied to DC
Technical explanation:A constrained delegation with protocol transition is a delegation with some limitation.
In this case, it is a limitation of the technical service a delegate can call (SPN).
But in practice, the specific service name is not checked and the delegate can impersonate anyone on all services of a computer.
For the case of a domain controller, that means that the delegate can take the control of the domain by impersonating a domain admin and doing modifications with the LDAP service.
This delegation is set via the attribute msDS-AllowedToDelegateTo.
The protocol transition is a special feature set in the userAccountControl which does not limit the delegation to the kerberos protocol.
Note: this rule is a companion of the rule P-DelegationDCa2d2
You should edit the msDS-AllowedToDelegateTo attribute of the accounts listed below to remove the SPN of the domain controllers involved.
2.9.0.0
Points:25 points per discovery
Documentation:P-DelegationDCa2d2
Description:The purpose is to ensure that no contrained delegations are applied to DC
Technical explanation:A constrained delegation is a delegation with some limitation.
In this case, it is a limitation of the technical service a delegate can call (SPN).
But in practice, the specific service name is not checked and the delegate can impersonate anyone on all services of a computer.
For the case of a domain controller, that means that the delegate can take the control of the domain by impersonating a domain admin and doing modifications with the LDAP service.
This delegation is set via the attribute msDS-AllowedToDelegateTo and is limited to kerberos
Note: this rule is a companion of the rule P-DelegationDCt2a4d
You should edit the msDS-AllowedToDelegateTo attribute of the accounts listed below to remove the SPN of the domain controllers involved.
2.9.0.0
Points:25 points per discovery
Documentation:P-DelegationDCsourcedeleg
Description:The purpose is to ensure that no resource based constrained delegations are applied to DC
Technical explanation:Resource based contrained delegation are a new feature of Windows 2012 which tries to handle the limitation of Constrained delegations.
This delegation is defined by setting the msDS-AllowedToDelegateToattribute attribute either using the GUI or a powershell command.
You should edit the msDS-AllowedToDelegateToattribute attribute of the domain controllers and remove the account involved.
You can do this with the powershell command:
Set-ADComputer COMPUTER -PrincipalsAllowedToDelegateToAccount $Null
2.9.0.0
Points:25 points per discovery
Documentation:https://blog.stealthbits.com/resource-based-constrained-delegation-abuse/
[FR]ANSSI - Resource-based constrained delegation on domain controlers (vuln1_delegation_sourcedeleg)1
P-UnconstrainedDelegation
Description:The purpose is to ensure no account can impersonate any account.
Technical explanation:When an unconstrained delegation is configured, the kerberos ticket TGT can be captured. This TGT grant then access to any service the user has access. If the user is an administrator or a domain controller (a connection can be forced using the spooler service), the domain can be compromised.
Advised solution:Replace unconstrained delegation by constrained delegation. In practice, on the account object, tab "delegation", replace "trust this computer for delegation to any service" by "trust this computer for delegation to specified services only".
Introduced in:2.6.0.0
Points:5 points per discovery
Documentation:https://blogs.technet.microsoft.com/389thoughts/2017/04/18/get-rid-of-accounts-that-use-kerberos-unconstrained-delegation/
https://adsecurity.org/?p=1667
[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R18 [subsubsection.3.3.2]
[FR]ANSSI - Unconstrained authentication delegation (vuln2_delegation_t4d)2
Most of the changes can be reversed. Some not, and it can broke the domain.
P-SchemaAdmin
Description:The purpose is to ensure that no account can make unexpected modifications to the schema
Technical explanation:The group "Schema Admins" is used to give permissions to alter the schema. Once a modification is performed on the schema such as new objects, it cannot be undone. This can result in a rebuild of the domain. The best practice is to have this group empty and to add an administrator when a schema update is required then to remove this group membership.
Advised solution:Remove the accounts or groups belonging to the "schema administrators" group.
Points:10 points if present
Documentation:[US]STIG V-72835 - Membership to the Schema Admins group must be limited
[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R13 [subsection.3.2]
P-RecycleBin
Description:The purpose is to ensure that the Recycle Bin feature is enabled
Technical explanation:The Recycle Bin avoids immediate deletion of objects (which can still be partially recovered by its tombstone). This lowers the administration work needed to restore. It also extends the period where traces are available when an investigation is needed.
Advised solution:First, be sure that the forest level is at least Windows 2008 R2.
You can check it with Get-ADForest or in the Domain Information section.
Then you can enable it using the powershell command:
Enable-ADOptionalFeature -identity 'CN=Recycle Bin Feature,CN=Optional Features,CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration,DC=test,DC=mysmartlogon,DC=com' -Scope ForestOrConfigurationSet -Target 'test.mysmartlogon.com'
2.7.0.0
Points:10 points if present
Documentation:https://enterinit.com/powershell-enable-active-directory-recycle-bin
Privileges are granted to special groups to perform their duty. Sometimes, these privileges can be used to take control of the domain.
P-ServiceDomainAdmin
Description:The purpose is to check for "Service Accounts" in the "Domain Administrator" group
Technical explanation:"Service Accounts" can imply a high security risk as their password are stored in clear text in the LSA database, which can then be easily exploited using Mimikatz or Cain&Abel for instance. In addition, their passwords don't change and can be used in kerberoast attacks.
Advised solution:To mitigate the security risk, it is strongly advised to lower the privileges of the "Service Accounts", meaning that they should be removed from the "Domain Administrator" group, while ensuring that the password of each and every "Service Account" is higher than 20 characters
Points:15 points if the occurence is greater than or equals than 2
Documentation:[US]STIG V-36432 - Membership to the Domain Admins group must be restricted to accounts used only to manage the Active Directory domain and domain controllers.
[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R11 [subsection.2.5]
[FR]ANSSI - Privileged accounts with never-expiring passwords (vuln1_dont_expire_priv)1
P-TrustedCredManAccessPrivilege
Description:The purpose is to ensure that there is no assignment of the SeTrustedCredManAccessPrivilege privilege.
Technical explanation:The Credential Manger is a vault where credentials are being stored.
This privilege can be used to retrieve the secret data.
Please note that, as today, there is no public POC published to exploit this privilege and no supported API needing that privilege.
You should edit the GPO and remove the GPO right assignment.
The setting is located in Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment.
2.8.0.0
Points:5 points if present
Documentation:https://docs.microsoft.com/en-us/windows/win32/secauthn/credentials-management
https://docs.microsoft.com/en-us/windows/win32/secauthn/authentication-functions#credentials-management-functions
[US]STIG V-63843 - The Access Credential Manager as a trusted caller user right must not be assigned to any groups or accounts
P-PrivilegeEveryone
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.
SeManageVolumePrivilege can be use to reset the security descriptor on the C volume and thus, change the inherited permissions to critical files
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.
2.6.0.0
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
https://twitter.com/0gtweet/status/1303427935647531018?s=20
[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R18 [subsubsection.3.3.2]
Read-Only Domain Controllers are used in poor physically secured zones. An incorrect protection level can leak sensitive data.
P-RODCRevealOnDemand
Description:The purpose is to ensure that no privileged group can be revealed on RODC
Technical explanation:There is an attribute on each RODC which enumerates the groups that the RODC can retrieve.
When the RODC retrieve the user account, all secrets are integrated into the data, meaning that the RODC can impersonate the user account.
In this case, a user or a group has been identified that have a RID (the last part of the SID) lower than 1000.
All privileged group have a RID lower than 1000, than means that the RODC can get access at any time to that privileged information.
Edit the attribute msDS-RevealOnDemandGroup and remove the privileged user or group identified.
This can be managed in the Password Replication Policy tab of the computer objecct in the Active Directory Users and Computers console.
2.9.0.0
Points:5 points if present
Documentation:https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-adts/8dfc81be-7461-48f2-8caf-07402bccb0ea
[FR]ANSSI - Dangerous configuration of read-only domain controllers (RODC) (reveal) (vuln3_rodc_reveal)3
P-RODCSYSVOLWrite
Description:The purpose is to ensure that no RODC has write access to the SYSVOL
Technical explanation:The SYSVOL Volume is a special DFS volume used to stored system files such as GPO.
Read Only Controllers (RODC) have a read-only access to it.
If it has a write access, it can change the file locally and propagate them to all writable domain controllers.
And thus enable an attacker to take control of the domain by modifying GPO applied to Domain Controllers.
Locate the domain controller object related to the RODC in ADSIEdit.
Then zoom on CN=DFSR-LocalSettings then CN=Domain System Volume.
Edit the attribute msDFSR-ReadOnly and set it from false to true.
2.9.0.0
Points:5 points per discovery
Documentation:P-RODCNeverReveal
Description:The purpose is to ensure that the protection against revealing privileged group is active
Technical explanation:In addition to the group Denied RODC Password Replication Group there is a custom setting set for RODC in an attribute named msDS-NeverRevealGroup.
This rule check the current value against the default one.
Check the value of the attribute msDS-NeverRevealGroup and the presence of the following expected groups:
- Administrators;
- Server Operators;
- Account Operators;
- Backup Operators;
- Denied RODC Password Replication Group
This can be managed in the Password Replication Policy tab of the computer objecct in the Active Directory Users and Computers console.
2.9.0.0
Points:5 points if present
Documentation:https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-adts/8dfc81be-7461-48f2-8caf-07402bccb0ea
[FR]ANSSI - Dangerous configuration of read-only domain controllers (RODC) (neverReveal) (vuln3_rodc_never_reveal)3
P-RODCAdminRevealed
Description:The purpose is to check if privileged users have already been revealed
Technical explanation:On Active Directory, all users revealed to a RODC are tracked by an attribute set on the computer object of the RODC named msDS-RevealedUsers.
The program check on the list of revealed users if one is known as a privileged user.
Indeed the RODC is caching the authentication secrets related of this user, which can then be used to impersonate it.
In addition to that, RODC are placed in general on more riskier environment.
The admin account should have its secrets change (a password reset) and be sure that the account will not be revealed anymore.
Introduced in:2.9.0.0
Points:5 points per discovery
Documentation:https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-adts/8dfc81be-7461-48f2-8caf-07402bccb0ea
[FR]ANSSI - Privileged users revealed on RODC (vuln2_rodc_priv_revealed)2
P-RODCAllowedGroup
Description:The purpose is to ensure that the Allowed RODC Password Replication Group group is empty.
Technical explanation:Accounts belonging to the Allowed RODC Password Replication Group group have their password hashes revealed on all RODCs.
Advised solution:This group should be emptied, and dedicated groups should only be added to the Password Replication Policy of each relevant RODC.
Introduced in:2.9.0.0
Points:5 points if present
Documentation:P-RODCDeniedGroup
Description:The purpose is to ensure that the Denied RODC Password Replication Group group has at least its default members.
Technical explanation:A set of critical objects are being forbidden to replicate in RODC for security reasons.
This permission is set using the Denied RODC Password Replication Group group.
Removing one of the default members of this group remove this protection, and thus, the isolation of RODC.
Add the items which have been identified as missing to the Denied RODC Password Replication Group group.
2.9.0.0
Points:5 points if present
Documentation:https://docs.microsoft.com/en-us/services-hub/health/remediation-steps-ad/review-the-removal-of-default-members-from-the-denied-rodc-password-replication-group
[FR]ANSSI - Dangerous configuration of replication groups for read-only domain controllers (RODCs) (denied) (vuln3_rodc_denied_group)3
Each line represents a rule. Click on a rule to expand it and show the details of it.
NT4 like trusts do not provide an accurate level of security and by the use of its old protocols, put the domain at risk.
T-Downlevel
Description:The purpose is to ensure that there is no NT4 compatible trusts
Technical explanation:A Downlevel trust is a special kind of trust compatible with NT4. The kind of trust can be displayed in the "Active Directory Domains and Trusts" tool.
Advised solution:Unless the remote party of the trust is a NT4 domain, this trust shouldn't exist. It should be recreated.
Points:20 points if present
Documentation:Isolation of domain is critical to avoid a global compromission.
T-SIDFiltering
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')
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.
100 points if the occurence is greater than or equals than 4
then 80 points if the occurence is greater than or equals than 2
then 50 points if present
https://msdn.microsoft.com/en-us/library/cc237940.aspx
[US]STIG V-8538 - Security identifiers (SIDs) must be configured to use only authentication data of directly trusted external or forest trust.
[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R16 [paragraph.3.3.1.6]
[FR]ANSSI - Outbound forest trust relationships with sID History enabled (vuln1_trusts_forest_sidhistory)1
[FR]ANSSI - Unfiltered outbound domain trust relationship (vuln1_trusts_domain_notfiltered)1
When doing migrations, a double identity may be attributed. It can have side effects up to the compromission of the domain.
T-SIDHistorySameDomain
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:[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R15 [paragraph.3.3.1.5]
[FR]ANSSI - Accounts or groups with SID history set (vuln3_sidhistory_present)3
S-Domain$$$
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:[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R15 [paragraph.3.3.1.5]
T-SIDHistoryDangerous
Description:The purpose is to ensure that the dangerous SID are not stored in the SIDHistory attribute.
Technical explanation:SID History is an attribute used in migration to link with a former account.
This rule checks for SID not coming from a former domain (such as SYSTEM) or from a former domain but having a RID (the last part of the SID) lower than 1000.
Indeed, native privileged accounts have a SID lower than 1000.
A list of Well Known SID is referenced in the documentation below.
Identify the account, computer or group having these dangerous SID set in SID History, then clean it up by editing directly the SIDHistory attribute of the underlying AD object.
2.9.0.0
Points:10 points if present
Documentation:https://support.microsoft.com/en-us/help/243330/well-known-security-identifiers-in-windows-operating-systems
[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R15 [paragraph.3.3.1.5]
[FR]ANSSI - Accounts or groups with unexpected SID history (vuln2_sidhistory_dangerous)2
T-SIDHistoryUnknownDomain
Description:The purpose is to ensure that every account having an SID History is part of an active migration.
Technical explanation:When accounts are migrated from one domain to another, the attribute SID History can be appended to the new account to keep track of its former account. The origin can be tracked by removing the last digit of the SID to guess the SID of the origin domain. If the SID of the origin domain cannot be resolved, that means that the domain has been removed and as consequence that the SID History is not needed. This SID History information can be used to give additional rights and thus alter the real security rights.
Advised solution: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 SID History attribute should be removed. 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:10 points per discovery
Documentation:[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R15 [paragraph.3.3.1.5]
[FR]ANSSI - Accounts or groups with SID history set (vuln3_sidhistory_present)3
A trust is a technical boundary which should not be altered.
T-FileDeployedOutOfDomain
Description:The purpose is to ensure that a compromised domain cannot use file deployed by GPO to compromise other domains
Technical explanation:Files deployed (Application as msi, file copied by GPO, ...) can be stored in any file share available in the network and that includes trusted domains shares. If such file is located in a compromise domain, it can be used to compromise other domains.
Advised solution:Copy the file to a share located inside the domain and not in trusted domains.
Introduced in:2.7.0.0
Points:10 points if present
T-TGTDelegation
Description:The purpose is to ensure that a forest cannot be used to compromise another forest using kerberos delegation
Technical explanation:A Forest trust is a link between two forests. By default, this trust is secure and prohibits SID History attacks.
However, it allows kerberos delegation by default.
By configuring an uncontrainst delegation on forest A, an attacker located in forest A can collect admin or domain controller credentials, the TGT of the session, of the forest B.
This collection can be forced by using services such as the printer spooler, enabled by default on all domain controllers.
Having collected this TGT, the attacker can then request access to other systems in forest B, by asking for a TGS given the TGT, and then gain control of the whole forest.
TGT Delegation on forest trusts should be disabled, except for migrations.
You can use netdom to turn the TGT delegation on forest trust OFF.
Example: netdom.exe trust fabrikam.com /domain:contoso.com /EnableTGTDelegation:No
As an alternative, you can locate the forest trust and change its LDAP trustattribute from the value 8 to the value 520.
The impact is to have non working services which relies on unconstrained delegation. Resource based delegation is not impacted.
See the official Microsoft recommandations and a script to find potentially impacted services in the links below.
2.7.0.0
Points:10 points per discovery
Documentation:http://www.harmj0y.net/blog/redteaming/not-a-security-boundary-breaking-forest-trusts/
https://techcommunity.microsoft.com/t5/Premier-Field-Engineering/Changes-to-Ticket-Granting-Ticket-TGT-Delegation-Across-Trusts/ba-p/440283/tab/rich
https://support.microsoft.com/en-us/help/4490425/updates-to-tgt-delegation-across-incoming-trusts-in-windows-server
[FR]ANSSI - Inbound trust relationships with delegation (vuln3_trusts_tgt_deleg)3
T-ScriptOutOfDomain
Description:The purpose is to ensure that a compromised domain cannot use scripts located in it to compromise other domains
Technical explanation:Login script can be stored in any file share available in the network and that includes trusted domains shares. If a login script is located in a compromise domain, it can be used to compromise other domains.
Advised solution:Copy the login script to a share located inside the domain and not in trusted domains.
Points:10 points if present
Any trust introduce a risk. The secret used for the trust can be exposed to take control of the domain.
T-Inactive
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
[FR]ANSSI - Trust account passwords unchanged for more than a year (vuln2_trusts_accounts)2
T-AzureADSSO
Description:The purpose is to check that password rotation is in place with AzureAD SSO
Technical explanation:AzureAD SSO is performed using a gateway. This gateway converts a kerbros TGS ticket to SAML ticket.
In short, a connection to the computer account AZUREADSSOACC and the secret of this user account is used as a shared secret with AzureAD.
Despite the fact that computer account should have its password automatically changed every 30 days, this computer account does not have its password changed automatically.
That means that an extraction of its password (using DCSync for example) can lead to an AzureAD compromise.
Run the script referenced in the documentation below to change the password of the account AZUREADSSOACC.
Points:20 points if present
Documentation:https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sso-faq#how-can-i-roll-over-the-kerberos-decryption-key-of-the-azureadssoacc-computer-account
https://gallery.technet.microsoft.com/Azure-AD-SSO-Key-Rollover-d2f1604a
https://www.dsinternals.com/en/impersonating-office-365-users-mimikatz/
[FR]ANSSI - Trust account passwords unchanged for more than a year (vuln2_trusts_accounts)2
Each line represents a rule. Click on a rule to expand it and show the details of it.
A-AuditPowershell
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.
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.
2.8.0.0
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
[US]STIG V-68819 - PowerShell script block logging must be enabled
A-AuditDC
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.
Identitfy the Audit settings to apply and fix them.
Beware that there is two places for audit settings.
For "Simple" audit configuration:
in Computer Configuration -> Policies -> Windows Settings -> Security Settings -> Local Policies -> Audit Policies
For "Advanced" audit configuration:
in Computer Configuration -> Policies -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration
Also be sure that the audit GPO is applied to all domain controllers, as the underlying object may be in a OU where the GPO is not applied.
2.8.0.0
Points:10 points if present
Documentation:Althought Active Directory has been designed for redundancy, a backup process is key for a recovery plan.
A-BackupMetadata
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 than or equals than 7
Documentation:https://technet.microsoft.com/en-us/library/jj130668(v=ws.10).aspx
[US]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.
A-NotEnoughDC
Description:The purpose is to ensure the failure of one domain controller will not stop the domain.
Technical explanation:A single domain controller failure can lead to a lack of availability of the domain if the number of servers is too low. To have a minimum redundancy, the number of DC should be at least 2. For Labs, this rule can be ignored and you can add this rule into the exception list.
Advised solution:Increase the number of domain controllers by installing new ones.
Introduced in:2.6.0.0
Points:5 points if the occurence is strictly lower than 2
Documentation:Certificates are an alternative to passwords. Their protection is crucial to avoid any backdoor.
A-WeakRSARootCert2
Description:The purpose is to ensure that there is no use of a certificate using a relatively weak RSA key
Technical explanation:A RSA key certificate with a modulus under 1024 bits is considered as not safe. This is checked by the rule A-WeakRSARootCert.
This rule checks for certificates having a key under 2048 bits which is considered as having a lower level of security and under 3072 bits for certificates valid after 2030.
To solve the matter, the certificate should be removed from the GPO and if needed, certificates depending on it should be reissued.
Please note that this rule is the companion of the rule A-WeakRSARootCert which checks for unsecured certificates (key lower than 1024 bits).
2.9.0.0
Points:1 points if present
Documentation:https://www.iad.gov/iad/library/ia-guidance/ia-solutions-for-classified/algorithm-guidance/commercial-national-security-algorithm-suite-factsheet.cfm
https://www.ssi.gouv.fr/guide/cryptographie-les-regles-du-rgs/
[US]STIG V-14820 - PKI certificates (server and clients) must be issued by the DoD PKI or an approved External Certificate Authority (ECA).
[FR]ANSSI - Weak or vulnerable certificates (vuln3_certificates_vuln)3
A-CertWeakRsaComponent
Description:The purpose is to ensure that there is no use of a certificate with a weak RSA exponent
Technical explanation:The RSA public key is composed of two parts: the modulus and the exponent. The exponent has to be a prime number and its value is usually 65537.
It is not recommended to have a exponent larger than 65537 for compatibility reasons as for example older Windows handle the exponent in 4 bytes.
Having a lower exponent, such as 3, give a significant performance boost (up to 8 times), but it is considered less secure.
To solve the matter, the certificate should be removed from the GPO and if needed, certificates depending on it should be reissued.
Introduced in:2.9.0.0
Points:5 points if present
Documentation:[FR]ANSSI - Weak or vulnerable certificates (vuln3_certificates_vuln)3
A-WeakRSARootCert
Description:The purpose is to ensure that there is no use of a certificate using a weak RSA key
Technical explanation:A RSA key certificate with a modulus under 1024 bits is considered as not safe
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:5 points if present
Documentation:https://www.iad.gov/iad/library/ia-guidance/ia-solutions-for-classified/algorithm-guidance/commercial-national-security-algorithm-suite-factsheet.cfm
https://www.ssi.gouv.fr/guide/cryptographie-les-regles-du-rgs/
[US]STIG V-14820 - PKI certificates (server and clients) must be issued by the DoD PKI or an approved External Certificate Authority (ECA).
[FR]ANSSI - Weak or vulnerable certificates (vuln1_certificates_vuln)1
A-CertWeakDSA
Description:The purpose is to ensure that there is no use of a certificate using a DSA key for signature
Technical explanation:Digital Signature Algorithm (DSA), is a NIST standard signature algorithm, part of the 1993 Digital Signature Standard(FIPS 186). The proposed FIPS 186-5 draft deprecates the use of DSA and will forbid its usage for digital signature purposes.
The annex E of FIPS 186-5 specifies: DSA is no longer approved for digital signature generation. DSA may be used to verify signatures generated prior to the implementation date of this standard.
To solve the matter, the certificate should be removed from the GPO and if needed, certificates depending on it should be reissued.
Introduced in:2.9.0.0
Points:Informative rule (0 point)
Documentation:https://csrc.nist.gov/publications/detail/fips/186/5/draft
[FR]ANSSI - Weak or vulnerable certificates (vuln1_certificates_vuln)1
A-MD2IntermediateCert
Description:The purpose is to ensure that there is no use of the MD2 hashing algorithm in Intermediate Certificate
Technical explanation:The MD2 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:10 points if present
Documentation:https://www.ssi.gouv.fr/archive/fr/sciences/fichiers/lcr/mu04c.pdf
[US]STIG V-14820 - PKI certificates (server and clients) must be issued by the DoD PKI or an approved External Certificate Authority (ECA).
[FR]ANSSI - Weak or vulnerable certificates (vuln3_certificates_vuln)3
A-MD4IntermediateCert
Description:The purpose is to ensure that there is no use of the MD4 hashing algorithm in Intermediate Certificate
Technical explanation:The MD4 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:10 points if present
Documentation:https://tools.ietf.org/html/rfc6150
[US]STIG V-14820 - PKI certificates (server and clients) must be issued by the DoD PKI or an approved External Certificate Authority (ECA).
[FR]ANSSI - Weak or vulnerable certificates (vuln3_certificates_vuln)3
A-MD5IntermediateCert
Description:The purpose is to ensure that there is no use of the MD5 hashing algorithm in Intermediate Certificate
Technical explanation:The MD5 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:5 points if present
Documentation:https://www.kb.cert.org/vuls/id/836068
[US]STIG V-14820 - PKI certificates (server and clients) must be issued by the DoD PKI or an approved External Certificate Authority (ECA).
[FR]ANSSI - Weak or vulnerable certificates (vuln3_certificates_vuln)3
A-SHA0IntermediateCert
Description:The purpose is to ensure that there is no use of the SHA0 hashing algorithm in Intermediate Certificate
Technical explanation:The SHA0 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:5 points if present
Documentation:https://tools.ietf.org/html/rfc6194
[US]STIG V-14820 - PKI certificates (server and clients) must be issued by the DoD PKI or an approved External Certificate Authority (ECA).
[FR]ANSSI - Weak or vulnerable certificates (vuln3_certificates_vuln)3
A-SHA1IntermediateCert
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
[US]STIG V-14820 - PKI certificates (server and clients) must be issued by the DoD PKI or an approved External Certificate Authority (ECA).
[FR]ANSSI - Weak or vulnerable certificates (vuln3_certificates_vuln)3
A-MD2RootCert
Description:The purpose is to ensure that there is no use of the MD2 hashing algorithm in Root Certificate
Technical explanation:The MD2 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. Nevertheless, the root certificate algorithm has no direct impact on the security, but it can be used indirectly to force the use of this algorithm in the issued certificate
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://www.ssi.gouv.fr/archive/fr/sciences/fichiers/lcr/mu04c.pdf
[US]STIG V-14820 - PKI certificates (server and clients) must be issued by the DoD PKI or an approved External Certificate Authority (ECA).
[FR]ANSSI - Weak or vulnerable certificates (vuln3_certificates_vuln)3
A-MD4RootCert
Description:The purpose is to ensure that there is no use of the MD4 hashing algorithm in Root Certificate
Technical explanation:The MD4 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. Nevertheless, the root certificate algorithm has no direct impact on the security, but it can be used indirectly to force the use of this algorithm in the issued certificate
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/rfc6150
[US]STIG V-14820 - PKI certificates (server and clients) must be issued by the DoD PKI or an approved External Certificate Authority (ECA).
[FR]ANSSI - Weak or vulnerable certificates (vuln3_certificates_vuln)3
A-MD5RootCert
Description:The purpose is to ensure that there is no use of the MD5 hashing algorithm in Root Certificate
Technical explanation:The MD5 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. Nevertheless, the root certificate algorithm has no direct impact on the security, but it can be used indirectly to force the use of this algorithm in the issued certificate
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://www.kb.cert.org/vuls/id/836068
[US]STIG V-14820 - PKI certificates (server and clients) must be issued by the DoD PKI or an approved External Certificate Authority (ECA).
[FR]ANSSI - Weak or vulnerable certificates (vuln3_certificates_vuln)3
A-SHA0RootCert
Description:The purpose is to ensure that there is no use of the SHA0 hashing algorithm in Root Certificate
Technical explanation:The SHA0 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
[US]STIG V-14820 - PKI certificates (server and clients) must be issued by the DoD PKI or an approved External Certificate Authority (ECA).
[FR]ANSSI - Weak or vulnerable certificates (vuln3_certificates_vuln)3
A-SHA1RootCert
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
[US]STIG V-14820 - PKI certificates (server and clients) must be issued by the DoD PKI or an approved External Certificate Authority (ECA).
[FR]ANSSI - Weak or vulnerable certificates (vuln3_certificates_vuln)3
A-CertROCA
Description:The purpose is to ensure that there is no private key that can be recovered from a certificate
Technical explanation:"ROCA" is an acronym for "Return of Coppersmith's attack" which enables an attacker to retrieve the private key from a public key.
It is due by a library named RSALib, provided by Infineon Technologies which is incorporated into many smart cards, Trusted Platform Module (TPM), and Hardware Security Modules (HSM) implementations, including YubiKey 4 tokens and used to generate public RSA keys.
This library was generating data in a limited number space, which decreased the number of values that an attacker has to guess.
If the certificates listed below are still valid, you have to revoke and re-issue them. If other certificates depends on them, they should be revoked and replaced too.
If the certificates have been expired, they should be removed.
2.9.0.0
Points:15 points if present
Documentation:https://crocs.fi.muni.cz/public/papers/rsa_ccs17
https://github.com/crocs-muni/roca
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV190026
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV170012
https://keychest.net/roca
[FR]ANSSI - Weak or vulnerable certificates (vuln1_certificates_vuln)1
A-DCLdapsProtocol
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
Apply Windows updates and registry tweaks described in the documentation section to disable the weak SSL protocols.
2.8.0.0
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
There are key secrets in Active Directory which provides seed to the cryptographic process. A leak can lead to a total compromise of a domain.
A-Krbtgt
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 between 40 days and 6 months. 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.
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.
50 points if the occurence is greater than or equals than 1464
then 40 points if the occurence is greater than or equals than 1098
then 30 points if the occurence is greater than or equals than 732
then 20 points if the occurence is greater than or equals than 366
https://gallery.technet.microsoft.com/Reset-the-krbtgt-account-581a9e51
[FR]ANSSI CERTFR-2014-ACT-032
[FR]ANSSI - Krbtgt account password unchanged for more than a year (vuln2_krbtgt)2
the GPO deploy settings which are applied to computers locally and it can be abuse to take control of individual computers.
A-MembershipEveryone
Description:The purpose is to identify if there are restricted group such as local administrators, terminal server access, … where Authenticated Users or Everyone is being granted access by a GPO
Technical explanation:It is possible that a GPO add local membership of a restricted group. In this case the rule trigger if one is found with "Everyone" or "Authenticated Users" as members. It basically means that the Restricted Group has no restriction on belongs to it. This represents a security risk as Restricted Group are supposed to have more accesses or rights
Advised solution:In order to correct the issue, you should edit the GPO and remove the "Members" security access rule. Another solution is to change the group by a more targeted one containing a limited set of users.
Points:15 points per discovery
Documentation:Network attacks such as interception or modification can be used to run commands on behalf an administrator.
A-LMHashAuthorized
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
5 points if present
Documentation:[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R37 [paragraph.3.6.2.1]
[US]STIG V-3379 - The system is configured to store the LAN Manager hash of the password in the SAM.
A-DnsZoneUpdate2
Description:The purpose is to ensure that the DNS Zones are configured to accept only secure update.
Technical explanation:When the unsecure update mechanism is enabled, an attacker can update a DNS record anonymously.
He can then use this feature to add new entries or perform a man in the middle attack to capture credentials.
Please note that the rule A-DnsZoneUpdate1 is the companion of A-DnsZoneUpdate2 and it is used to report anomalies related to the local domain zone or the main _msdcs zone. A-DnsZoneUpdate2 reports all the other zones.
You have to enable secure updates.
Identify the faulty zone in the details below.
Go to the DNS console and select a zone in the "Forward Lookup Zones".
Right click on it and switch to the "General" tab.
Then change Dynamic updates from "Nonsecure and secure" to "Secure only".
You can also run: dnscmd servername /Config zone /AllowUpdate 2
2.9.0.0
Points:1 points if present
Documentation:https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-dnsp/f97756c9-3783-428b-9451-b376f877319a
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/dnscmd
[FR]ANSSI - Misconfigured DNS zones (vuln3_dnszone_bad_prop)3
A-DnsZoneUpdate1
Description:The purpose is to ensure that the DNS Zones are configured to accept only secure update.
Technical explanation:When the unsecure update mechanism is enabled, an attacker can update a DNS record anonymously.
He can then use this feature to add new entries or perform a man in the middle attack to capture credentials.
Please note that the rule A-DnsZoneUpdate1 is the companion of A-DnsZoneUpdate2 and it is used to report anomalies related to the local domain zone or the main _msdcs zone. A-DnsZoneUpdate2 reports all the other zones.
You have to enable secure updates.
Identify the faulty zone in the details below.
Go to the DNS console and select a zone in the "Forward Lookup Zones".
Right click on it and switch to the "General" tab.
Then change Dynamic updates from "Nonsecure and secure" to "Secure only".
You can also run: dnscmd servername /Config zone /AllowUpdate 2
2.9.0.0
Points:15 points if present
Documentation:https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-dnsp/f97756c9-3783-428b-9451-b376f877319a
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/dnscmd
[FR]ANSSI - Misconfigured DNS zones (vuln1_dnszone_bad_prop)1
A-NoGPOLLMNR
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.
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)
2.7.0.0
Points:Informative rule (0 point)
Documentation:A-NTFRSOnSysvol
Description:The purpose is to ensure that the old NTFRS protocol is not used to replicate the SYSVOL share.
Technical explanation:NTFRS is an old protocol and is not considered as secure.
The SYSVOL share is mainly hosted on domain controllers to host GPO files and login scripts.
If the content can be modified, it can be used to grant to an hacker the control of the computers reading these configuration files.
To know if the setting is enabled, PingCastle read the following LDAP entry: CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System
If there is any entry found, the program consider that NTFRS is in use for SYSVOl replication.
You have to migrate from NTFRS to DFS replication. See the documentation below for more details.
2.9.0.0
Points:5 points if present
Documentation:https://docs.microsoft.com/en-us/windows-server/storage/dfs-replication/migrate-sysvol-to-dfsr
https://support.microsoft.com/en-us/help/312862/recovering-missing-frs-objects-and-frs-attributes-in-active-directory
[FR]ANSSI - SYSVOL replication through NTFRS (vuln2_sysvol_ntfrs)2
A-SMB2SignatureNotEnabled
Description:The purpose is to ensure that the SMB version 2 protocol has the signature enabled when communicating with domain controllers
Technical explanation:Python responder is a tool used to compromise a domain by listening for SMB connections and injecting rogue data into the communications at the network level. SMB v1 does not provide a mechanism to enforce integrity and thus is compromised easily. SMB v2 (and subsequent version SMB v3) provides a way to guarantee the integrity of the network communication via a signature of each packet. By establishing a SMB v2 dialog with domain controllers, PingCastle checks the signature capability by looking at the SMB options provided by the server.
Advised solution:Enable the group policy "Digitally sign communications (if client agrees)" or check for any policy which may alter the server settings
Introduced in:2.5.0.0
Points:5 points if present
Documentation:https://msdn.microsoft.com/en-us/library/cc246675.aspx
[FR]ANSSI CERTFR-2015-ACT-021
A-SMB2SignatureNotRequired
Description:The purpose is to ensure that the SMB version 2 protocol has the signature enforced when communicating with domain controllers
Technical explanation:Python responder is a tool used to compromise a domain by listening for SMB connections and injecting rogue data into the communications at the network level. SMB v1 does not provide a mechanism to enforce integrity and thus is compromised easily. SMB v2 (and subsequent version SMB v3) provides a way to guarantee the integrity of the network communication via a signature of each packet. By establishing a SMB v2 dialog with domain controllers, PingCastle checks the signature capability by looking at the SMB options provided by the server.
Advised solution:Enable the group policy "Digitally sign communications (always)" or check for any policy which may alter the server settings
Introduced in:2.5.0.0
Points:Informative rule (0 point)
Documentation:https://msdn.microsoft.com/en-us/library/cc246675.aspx
[FR]ANSSI CERTFR-2015-ACT-021
A-LDAPSigningDisabled
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.
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.
2.7.0.0
Points:5 points if present
Documentation:If the password is a secret which protects, its derivatives, such as the fingerprint named hash, can be used as if it was the password itself.
A-SmartCardRequired
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/
[US]STIG V-72821 - All accounts, privileged and unprivileged, that require smart cards must have the underlying NT hash rotated at least every 60 days.
[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R38 [paragraph.3.6.2.2]
A-ProtectedUsers
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
Informative rule (0 point)
Documentation:https://docs.microsoft.com/en-us/windows-server/security/credentials-protection-and-management/protected-users-security-group
[US]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.
[FR]ANSSI CERTFR-2017-ALE-012
A-LAPS-Not-Installed
Description:The purpose is to make sure that there is a proper password policy in place for the native local administrator account.
Technical explanation:LAPS (Local Administrator Password Solution) is the advised solution to handle passwords for the native local administrator account on all workstations, as it is a simple way to handle most of the subject.
Advised solution:If you don't have any provisioning process or password solution to manage local administrators, you should install the LAPS solution. If you mitigate the risk differently, you should add this rule as an exception, as the risk is covered.
Points:15 points if present
Documentation:https://www.microsoft.com/en-us/download/details.aspx?id=46899
[US]STIG V-36438 - Local administrator accounts on domain systems must not share the same password.
[FR]ANSSI CERTFR-2015-ACT-046
A-DCRefuseComputerPwdChange
Description:The purpose is to check that the computer account password can be changed as usual.
Technical explanation:For each computer, there is a hidden user account. This account is used to maintain the computer inside the Active Directory domain.
The password of this account is changed every 30 days automatically except if the Domain Controller prohibits this.
This is the case when the GPO is enabled.
Locate the GPO specified in Details and change the setting in "Domain controller: Refuse machine account password changes".
Disable this setting, or set it to "Disabled".
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.
2.7.0.0
Points:5 points if present
Documentation:https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/domain-controller-refuse-machine-account-password-changes
[US]STIG V-4408 - The domain controller must be configured to allow reset of machine account passwords.
A-DC-Spooler
Description:The purpose is to ensure that credentials cannot be extracted from the DC via its printer spooler
Technical explanation:When there’s an account with unconstrained delegation configured (which is fairly common) and the Print Spooler service running on a computer, you can get that computers credentials sent to the system with unconstrained delegation as a user. With a domain controller, the TGT of the DC can be extracted allowing an attacker to reuse it with a DCSync attack and obtain all user hashes and impersonate them.
Advised solution:The spooler service should be deactivated on domain controllers. Please note as a consequence that the Printer Pruning functionality (rarely used) will be unavailable.
Introduced in:2.6.0.0
Points:10 points if present
Documentation:https://adsecurity.org/?p=4056
https://www.slideshare.net/harmj0y/derbycon-the-unintended-risks-of-trusting-active-directory
Passwords stored in clear text or obfuscated can be retrieved. By reusing the user's identity, an attacker does not need to perform attack and it is difficult to detect it.
A-ReversiblePwd
Description:The purpose is to verify if a GPO alters the password policy of the domain to enable reversible passwords
Technical explanation:The policy "Store passwords using reversible encryption" is enabled. In this case, it means that the password is actually stored in clear text in the supplementalCredential attribute of the account and that it can be retrieved using DCSync attack.
Advised solution:In order to remove the anonymous access, we advise to identify the GPO indicated by the program and change the setting "Store passwords using reversible encryption"
Points:10 points if present
Documentation:https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/store-passwords-using-reversible-encryption
[FR]ANSSI - Accounts with passwords stored using reversible encryption (vuln3_reversible_password)3
A-UnixPwd
Description:The purpose is to check if password information may be stored in AD attributes
Technical explanation:To perform Single Sign On (SSO) systems need to share secrets with Active Directory.
This is not the case for all systems such as Unix and Mainframe and designers have found a workaround by storing this secret into a user account attribute.
However not all systems did implement a proper and cryptographically safe protocol and they are checking the password submitted in their system with an AD attribute.
At that time, it was not known that these attributes can be queried by everyone and as consequence, they did not enforce a robust protection.
Looking at the attribute unixUserPassword, the password can be retrieved either in clear text (encoded as ASCII) or with a weak algorithm such as ROT 13.
In addition to that, the way to change a password in LDAP system is to modify the value of the special attribute userPassword.
This attribute is not supposed to be visible. However Active Directory is using another attribute named unicodePwd (unless the heuristic fUserPwdSupport is set).
That means that the attribute userPassword is not special anymore and that a change of its value is displayed in clear text, considered as a normal attribute.
A misconfigured application can change the user password using this old mechanism, and as a consequence, set the user password in clear text.
The attribute unixUserPassword and userPassword should be cleared from the mentionned user account, unless the remote system is known to have a strong cryptographic protocol.
Points:Informative rule (0 point)
Documentation:https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-adts/f3adda9f-89e1-4340-a3f2-1f0a6249f1f8
https://www.blackhillsinfosec.com/domain-goodness-learned-love-ad-explorer/
[FR]ANSSI - Accounts with passwords stored using reversible encryption (vuln3_reversible_password)3
A-PwdGPO
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
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
[FR]ANSSI CERTFR-2015-ACT-046
At the begining of an attack, a hacker try to collect as much data as possible. Leaking information just reduce the time an attacker needs to gain control of the domain.
A-DsHeuristicsAllowAnonNSPI
Description:The purpose is to identify domains having the NSPI protocol exposed without any required account
Technical explanation:The way an Active Directory behaves can be controlled via the attribute DsHeuristics of CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration. A parameter stored in its attribute and whose value is fAllowAnonNSPI can be set to allow access to the NSPI protocol without any account.
The NSPI protocol is used internally by Exchange to resolve addresses, and thus can be used to dump all the users of the forest. It can be exposed to the internet via RPC over HTTP.
The easiest and fastest way to correct this issue is to replace the eighth (8th) character of the DsHeuristics attribute. If it is not a 0, replace by 0 to fix the issue.
Introduced in:2.9.0.0
Points:5 points if present
Documentation:https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-adts/e5899be4-862e-496f-9a38-33950617d2c5
https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-nspi/6dd0a3ea-b4d4-4a73-a857-add03a89a543
[US]STIG V-8555 - Anonymous Access to AD forest data above the rootDSE level must be disabled.
[FR]ANSSI - Dangerous dsHeuristics settings (vuln1_dsheuristics_bad)1
A-DsHeuristicsAnonymous
Description:The purpose is to identify domains having a forest setting which allows access to the domain without any account
Technical explanation:The way an Active Directory behaves can be controlled via the attribute DsHeuristics of CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration. A parameter stored in its attribute and whose value is fLDAPBlockAnonOps can be set to allow access without any account on the whole forest level.
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.
The easiest and fastest way to correct this issue is to replace the seventh (7th) character of the DsHeuristics attribute. If it is a 2, replace by 0 to fix the issue.
Points:5 points if present
Documentation:https://msdn.microsoft.com/en-us/library/cc223560.aspx
https://support.microsoft.com/en-us/help/326690/anonymous-ldap-operations-to-active-directory-are-disabled-on-windows
[US]STIG V-8555 - Anonymous Access to AD forest data above the rootDSE level must be disabled.
[FR]ANSSI - Dangerous dsHeuristics settings (vuln2_dsheuristics_bad)2
A-AnonymousAuthorizedGPO
Description:The purpose is to identify domains having a GPO which allows access to the domain without any account
Technical explanation:It is possible that domains are set to authorize connection without any account, which represents a security breach. It allows potential attackers to enumerate all the users and computers belonging to a domain, in order to identify very efficiently future weak targets.
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].
In order to remove the anonymous access, we advise to identify the GPO indicated by the program and change the setting restrictanonymous and restrictanonymoussam
Points:5 points if present
Documentation:https://technet.microsoft.com/en-us/library/cc963223.aspx https://technet.microsoft.com/en-us/library/jj852184.aspx
[US]STIG V-14798 - Directory data (outside the root DSE) of a non-public directory must be configured to prevent anonymous access.
A-PreWin2000Anonymous
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].
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
[US]STIG V-8547 - The Anonymous Logon and Everyone groups must not be members of the Pre-Windows 2000 Compatible Access group.
[FR]ANSSI - The "Pre - Windows 2000 Compatible Access" group includes "Anonymous" (vuln2_compatible_2000_anonymous)2
A-NoNetSessionHardening
Description:The purpose is to ensure that mitigations are in place against the Bloodhound tool
Technical explanation:By default, Windows computers allow any authenticated user to enumerate network sessions to it.
This means an attacker could enumerate network sessions to a file share hosting home directories or a Domain Controller to see who’s connected to SYSVOL (to apply Group Policy) and determine which workstations each user and admin account is logged into.
Bloodhound uses this capability extensively to map out credentials in the network.
Disabling Net Session Enumeration removes the capability for any user to enumerate net session info (Recon).
If this mitigation is not part of the computer image, apply the following recommandations:
Run the NetCease PowerShell script (referenced below) on a reference workstation.
Open the Group Policy Management Console. Right-click the Group Policy object (GPO) that should contain the new preference item, and then click Edit .
In the console tree under Computer Configuration, expand the Preferences folder, and then expand the Windows Settings folder.
Right-click the Registry node, point to New, and select Registry Wizard.
Select the reference workstation on which the desired registry settings exist, then click Next .
Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\DefaultSecurity\
and select the check box for “SrvsvcSessionInfo” from which you want to create a Registry preference item. Select the check box for a key only if you want to create a Registry item for the key rather than for a value within the key.
Click Finish.
The settings that you selected appear as preference items in the Registry Wizard Values collection
2.9.0.0
Points:Informative rule (0 point)
Documentation:https://gallery.technet.microsoft.com/Net-Cease-Blocking-Net-1e8dcb5b
https://adsecurity.org/?p=3299
A-PreWin2000Other
Description:The purpose is check that no additional account has been added to the "Pre-Windows 2000 Compatible Access" group
Technical explanation:The pre-Windows 2000 compatible access group grants access to some RPC calls which should not be available to users or computers.
Advised solution:Remove the members from the PreWin2000 group while making sure that the group "Authenticated Users" is present. Then reboot each DC.
Introduced in:2.9.0.0
Points:2 points if present
Documentation:https://msdn.microsoft.com/en-us/library/cc223672.aspx
[FR]ANSSI - Use of the "Pre-Windows 2000 Compatible Access" group (vuln3_compatible_2000_not_default)3
A-NullSession
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].
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
[US]STIG V-14798 - Directory data (outside the root DSE) of a non-public directory must be configured to prevent anonymous access.
Administrators grant sometimes privileged rights to colleagues without any approval from a security officer.
A-AdminSDHolder
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.
50 points if the occurence is greater than or equals than 50
then 45 points if the occurence is greater than or equals than 45
then 40 points if the occurence is greater than or equals than 40
then 35 points if the occurence is greater than or equals than 35
then 30 points if the occurence is greater than or equals than 30
then 25 points if the occurence is greater than or equals than 25
then 20 points if the occurence is greater than or equals than 20
then 15 points if present
https://msdn.microsoft.com/en-us/library/ms675212(v=vs.85).aspx
[FR]ANSSI - Recommandations de sécurité relatives à Active Directory - R40 [paragraph.3.6.3.1]
Misprotected credentials can be abused to be retrieved in plain text and then, impersonate the user.
A-LimitBlankPasswordUse
Description:The purpose is to identify if accounts without password are allowed to be accessed from the network. This represents a high risk, as an account without a password is essentially an account that cannot be assigned to anyone.
Technical explanation:This rule verifies if there is a GPO with the setting "Limit local account use of blank passwords to console logon only" disabled.
Advised solution:Locate the policy having the setting "Limit local account use of blank passwords to console logon only" disabled and enabled the setting.
Points:5 points if present
Documentation:A-MinPwdLen
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/
[FR]ANSSI - Privileged group members with weak password policy (vuln2_privileged_members_password)2
A-NoServicePolicy
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)
Note: PSO (Password Settings Objects) will be visible only if the user which collected the information has the permission to view it.
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.
Informative rule (0 point)
Documentation:https://www.microsoft.com/en-us/research/publication/password-guidance/
This is the mapping of the ANSSI rules with PingCastle rules.
Number of ANSSI rules matched: 44
1: 18
2: 13
3: 13
1Constrained authentication delegation to a domain controller service (link)
ANSSI ID : vuln1_delegation_a2d2
PingCastle ID : P-DelegationDCa2d2
1Constrained delegation with protocol transition to a domain controller service (link)
ANSSI ID : vuln1_delegation_t2a4d
PingCastle ID : P-DelegationDCt2a4d
12Dangerous dsHeuristics settings (link)
ANSSI ID : vuln1_dsheuristics_bad vuln2_dsheuristics_bad
PingCastle ID : A-DsHeuristicsAllowAnonNSPI A-DsHeuristicsAnonymous P-DsHeuristicsAdminSDExMask
1DnsAdmins group members (link)
ANSSI ID : vuln1_dnsadmins
PingCastle ID : P-DNSAdmin
1Domain controllers in inconsistent state (link)
ANSSI ID : vuln1_dc_inconsistent_uac
PingCastle ID : S-DCRegistration
1Domain controllers with passwords unchanged for more than 45 days (link)
ANSSI ID : vuln1_password_change_dc_no_change
PingCastle ID : S-PwdLastSet-DC
1Dormant accounts (link)
ANSSI ID : vuln1_user_accounts_dormant
PingCastle ID : S-Inactive
1Inactive domain controllers (link)
ANSSI ID : vuln1_password_change_inactive_dc
PingCastle ID : S-DC-Inactive
1Kerberos pre-authentication disabled for privileged accounts (link)
ANSSI ID : vuln1_kerberos_properties_preauth_priv
PingCastle ID : S-NoPreAuthAdmin
1Large privileged group member count (link)
ANSSI ID : vuln1_privileged_members
PingCastle ID : P-AdminNum
13Misconfigured DNS zones (link)
ANSSI ID : vuln1_dnszone_bad_prop vuln3_dnszone_bad_prop
PingCastle ID : A-DnsZoneUpdate1 A-DnsZoneUpdate2
1Outbound forest trust relationships with sID History enabled (link)
ANSSI ID : vuln1_trusts_forest_sidhistory
PingCastle ID : T-SIDFiltering
1Privileged account passwords age too old (link)
ANSSI ID : vuln1_password_change_priv
PingCastle ID : P-AdminPwdTooOld
1Privileged accounts with SPN (link)
ANSSI ID : vuln1_spn_priv
PingCastle ID : P-Kerberoasting
1Privileged accounts with never-expiring passwords (link)
ANSSI ID : vuln1_dont_expire_priv
PingCastle ID : P-ServiceDomainAdmin
1Resource-based constrained delegation on domain controlers (link)
ANSSI ID : vuln1_delegation_sourcedeleg
PingCastle ID : P-DelegationDCsourcedeleg
1Unfiltered outbound domain trust relationship (link)
ANSSI ID : vuln1_trusts_domain_notfiltered
PingCastle ID : T-SIDFiltering
13Weak or vulnerable certificates (link)
ANSSI ID : vuln1_certificates_vuln vuln3_certificates_vuln
PingCastle ID : A-CertROCA A-CertWeakDSA A-CertWeakRsaComponent A-MD2IntermediateCert A-MD2RootCert A-MD4IntermediateCert A-MD4RootCert A-MD5IntermediateCert A-MD5RootCert A-SHA0IntermediateCert A-SHA0RootCert A-SHA1IntermediateCert A-SHA1RootCert A-WeakRSARootCert A-WeakRSARootCert2
2Accounts or groups with unexpected SID history (link)
ANSSI ID : vuln2_sidhistory_dangerous
PingCastle ID : T-SIDHistoryDangerous
2Accounts with never-expiring passwords (link)
ANSSI ID : vuln2_dont_expire
PingCastle ID : S-PwdNeverExpires
2Bad Active Directory versions (link)
ANSSI ID : vuln2_adupdate_bad
PingCastle ID : P-DelegationKeyAdmin
2Kerberos pre-authentication disabled (link)
ANSSI ID : vuln2_kerberos_properties_preauth
PingCastle ID : S-NoPreAuth
2Krbtgt account password unchanged for more than a year (link)
ANSSI ID : vuln2_krbtgt
PingCastle ID : A-Krbtgt
2Privileged group members with weak password policy (link)
ANSSI ID : vuln2_privileged_members_password
PingCastle ID : A-MinPwdLen
2Privileged users revealed on RODC (link)
ANSSI ID : vuln2_rodc_priv_revealed
PingCastle ID : P-RODCAdminRevealed
2SYSVOL replication through NTFRS (link)
ANSSI ID : vuln2_sysvol_ntfrs
PingCastle ID : A-NTFRSOnSysvol
2Servers with passwords unchanged for more than 90 days (link)
ANSSI ID : vuln2_password_change_server_no_change_90
PingCastle ID : S-PwdLastSet-90
2The "Pre - Windows 2000 Compatible Access" group includes "Anonymous" (link)
ANSSI ID : vuln2_compatible_2000_anonymous
PingCastle ID : A-PreWin2000Anonymous
2Trust account passwords unchanged for more than a year (link)
ANSSI ID : vuln2_trusts_accounts
PingCastle ID : T-AzureADSSO T-Inactive
2Unconstrained authentication delegation (link)
ANSSI ID : vuln2_delegation_t4d
PingCastle ID : P-UnconstrainedDelegation
2Use of Kerberos with weak encryption (link)
ANSSI ID : vuln2_kerberos_properties_deskey
PingCastle ID : S-DesEnabled
3Accounts or groups with SID history set (link)
ANSSI ID : vuln3_sidhistory_present
PingCastle ID : T-SIDHistorySameDomain T-SIDHistoryUnknownDomain
3Accounts with modified PrimaryGroupID (link)
ANSSI ID : vuln3_primary_group_id_nochange
PingCastle ID : S-C-PrimaryGroup S-PrimaryGroup
3Accounts with passwords stored using reversible encryption (link)
ANSSI ID : vuln3_reversible_password
PingCastle ID : A-ReversiblePwd A-UnixPwd S-C-Reversible S-Reversible
3Dangerous configuration of read-only domain controllers (RODC) (neverReveal) (link)
ANSSI ID : vuln3_rodc_never_reveal
PingCastle ID : P-RODCNeverReveal
3Dangerous configuration of read-only domain controllers (RODC) (reveal) (link)
ANSSI ID : vuln3_rodc_reveal
PingCastle ID : P-RODCRevealOnDemand
3Dangerous configuration of replication groups for read-only domain controllers (RODCs) (allow) (link)
ANSSI ID : vuln3_rodc_allowed_group
PingCastle ID : P-RODCAllowedGroup
3Dangerous configuration of replication groups for read-only domain controllers (RODCs) (denied) (link)
ANSSI ID : vuln3_rodc_denied_group
PingCastle ID : P-RODCDeniedGroup
3Inactive servers (link)
ANSSI ID : vuln3_password_change_inactive_servers
PingCastle ID : S-C-Inactive
3Inbound trust relationships with delegation (link)
ANSSI ID : vuln3_trusts_tgt_deleg
PingCastle ID : T-TGTDelegation
3Incorrect object owners (link)
ANSSI ID : vuln3_owner
PingCastle ID : P-DCOwner
3Privileged accounts outside of the Protected Users group (link)
ANSSI ID : vuln3_protected_users
PingCastle ID : P-ProtectedUsers
3Servers with passwords unchanged for more than 45 days (link)
ANSSI ID : vuln3_password_change_server_no_change_45
PingCastle ID : S-PwdLastSet-45
3Use of the "Pre-Windows 2000 Compatible Access" group (link)
ANSSI ID : vuln3_compatible_2000_not_default
PingCastle ID : A-PreWin2000Other