Five settings that slow us down the most

Tester's hands at a keyboard, a dark log console and a hardware key on the desk

Small Active Directory changes can turn a one-day path to domain admin into a week of noise. None of the five below needs a new product.

We start most internal tests from one staff laptop. What we want next is a password or a hash that works somewhere else. These settings take that away.

The five

  1. A unique local administrator password on every machine, rotated by a managed tool.
  2. Legacy name resolution turned off across the network.
  3. Print spooler off on every server that does not print.
  4. Service accounts with long random passwords, reviewed once a year.
  5. Admin accounts that never sign in to a staff laptop.

The goal is not to stop us. The goal is to make us loud enough that your team notices.

Where to start

Start with the local administrator password. It breaks the most paths for the least effort, and it rarely breaks anything else. Then read your own logs while the next test runs, and see what you would have caught.

About the author

Ravi leads the red team at Wardline and has run campaigns since 2019. He phones the client before he writes the report. Fictional author, demo content.

Related field notes