Lithnet Password Protection for AD
Request a quote for supportDownloads
v1.0 - LPP
v1.0 - LPP
  • About Lithnet Password Protection
    • How does Password Protection help my organisation
    • Enterprise Support
  • Installation
    • Getting Started
    • Installation of Password Protection
    • Creating a new store
      • Understanding the store
    • Configure the password group policy
    • Testing the password filter
    • Audit existing passwords
    • Event logging and reporting
  • Configuration
    • Configuring a length based complexity policy
    • Configuring a points based complexity policy
  • Help & Support
    • Normalization Rules
  • Advanced Help
    • Powershell reference
      • Add-BannedWord
      • Add-CompromisedPassword
      • Get-PasswordFilterResult
      • Import-BannedWordHashes
      • Import-BannedWords
      • Import-CompromisedPasswordHashes
      • Import-CompromisedPasswords
      • Open-Store
      • Remove-BannedWord
      • Remove-CompromisedPassword
      • Test-IsADUserPasswordCompromised
      • Test-IsBannedWord
      • Test-IsCompromisedPassword
Powered by GitBook
On this page
  1. Installation

Getting Started

PreviousEnterprise SupportNextInstallation of Password Protection

Last updated 2 years ago

In order to get up and running with Lithnet Password Protection, you'll need to complete the following steps

  • You'll need to download and install the application on your writable domain controllers to enable password filtering. You can also install the application on other servers to allow you to use the PowerShell cmdlets and manage the password settings via group policy.

  • If you plan on using the compromised password functionality, then once the module is installed you'll need to create the database that contains the compromised passwords. You can use PowerShell to import compromised passwords from data sets such as the haveibeenpwned.com pwned password list.

  • Once filter has been installed and configured, you can start testing the password filter.

  • As an optional step, you can test the passwords of all existing users in your domain, to see if any of them are in the compromised password store. As these passwords have already been converted to a one-way hash in the Active Directory database, you cannot test other policies such as length and complexity against them.

  • Understand the events logged by the password filter, so you can audit and report on password change results.

Install the module
Create a new store
Test the password filter
Audit existing passwords
Event logging and reporting