password-spraying

To perform a lockout-safe password spray against Active Directory, you must first enumerate the domain's password policy to determine lockout thresholds, then carefully select wordlists based on spray intensity tiers to test username-password combinations safely.

Yes, password spraying supports Kerberos pre-authentication to test credentials safely. Prioritizing Kerberos pre-authentication for password spraying operations enhances OPSEC by reducing network noise compared to other protocols.

The best way to enumerate password policies before a credential spray is to query the target domain's authentication services directly, ensuring you understand lockout thresholds to safely select appropriate wordlists and spray intensity tiers.

Yes, you can use dependencies like netexec and kerbrute to automate password spraying across multiple protocols including SMB, Kerberos, LDAP, SSH, and web forms, ensuring broad service coverage for credential discovery.

Choosing Kerberos pre-authentication for password spraying over SMB provides better OPSEC. Kerberos pre-authentication minimizes detection risk during credential access by reducing the network footprint of authentication attempts.

Password spraying against web forms is limited by the need to carefully select wordlists and spray intensity tiers to avoid triggering lockouts or rate-limiting mechanisms on the target authentication services.