DSInternals VS 800-63-3

Thirdly dsinternals suite can be used to resurrect domain controllers from the dead.. it works very well and is pretty easy - https://github.com/MichaelGrafnetter/DSInternals/blob/master/Documentation/PowerShell/New-ADDBRestoreFromMediaScript.md - the person who created this is nothing short of a wizard.

Greetings. I would like to get recommendations for tools that will allow me to audit the password strength of users in Windows Active Directory and Google Workspace. I came across this one for AD that I plan to try. https://github.com/MichaelGrafnetter/DSInternals/blob/master/Documentation/PowerShell/Test-PasswordQuality.md

As you have no AD specific backup or recovery plan nor do you have an idea of when ransomware was copied into the environment I.e. how long was it sitting dormant? I’d suggest you take the backup you have then use this script from DSInternals - https://github.com/MichaelGrafnetter/DSInternals/blob/master/Documentation/PowerShell/New-ADDBRestoreFromMediaScript.md - to restore ONLY Active Directory (NTDS + SYSVOl) into clean media (needs to be the same major OS version).

Note**:** The same can be done using the DSInternals Set-SamAccountPasswordHash command.

To find out, you can use the DSInternals command Test-PasswordQuality. It will extract the password hashes for all your user accounts and compare them against the password hashes for a dictionary of weak passwords.

Recovery is still an option with this module: https://github.com/MichaelGrafnetter/DSInternals/blob/master/Documentation/PowerShell/New-ADDBRestoreFromMediaScript.md

Load DSInternals Powershell Module (Install-Module DSInternals -Force OR https://github.com/MichaelGrafnetter/DSInternals

FYI, there's a PS module you can use to check passwords. Here's a link to some info about that: https://github.com/MichaelGrafnetter/DSInternals/blob/master/Documentation/PowerShell/Get-ADReplAccount.md

I see you got your regex, but please consider reading the nist guidelines https://pages.nist.gov/800-63-3/ It is an excellent resource in password policies that isn't shared nearly enough.

Even NIST outright recommends against SMS/phone 2FA.

ID.me is the first NIST 800-63-3 approved company. https://www.businesswire.com/news/home/20180816005147/en/ID.me-Becomes-First-Identity-Provider-to-Be-Approved-as-NIST-800-63-3-Conformant & https://insights.id.me/article/what-are-the-nist-800-63-digital-identity-guidelines/

NIST has made a series of sensible guidelines:

https://pages.nist.gov/800-63-3/

They now need to be made enforceable, whether by government requiring them in government contracts, or indirectly by insurers excluding coverage if they are not met.

I just tell our customer's compliance systems and vendors (there's usually a space to explain why you're not doing a given thing) that we'll start rotating passwords as soon as NIST recommends it (again) , and no sooner. Nobody has ever failed a test nor have I even been asked about this stance. Flies right under the radar.

Several hundred pages if you want to read it all - https://pages.nist.gov/800-63-3/.