Menu

The IT Side of a Pen Test Week, a Client-Side Runbook
📰

The IT Side of a Pen Test Week, a Client-Side Runbook

DEV Community: infosec·Uprite Services·1 day ago
#tZP6zX47
#devtoinfosec#devto#dev#stopransomware#tester
Reading 0:00
15s threshold

A pen tester at a company of 30 to 80 people usually works for 3 to 5 days, and the prep around those days takes closer to 4 weeks. This is the runbook I use from the client side for the IT part of that month, written for whoever on staff ends up owning it.

Defending against the tester isn't on the list. What is on it is knowing which traffic is theirs, not changing the network mid-test, having someone who can stop things, and protecting the old servers that can't take much load.

The problem

The report you pay for describes one week of your network. Push a firewall change on day 2, or let the tester get blocked on day 1, and it ends up describing a week that didn't really happen, which nobody on your side can do much with.

NIST SP 800-115 calls planning the first phase of a security test (it comes before any testing traffic is sent), and in my experience nearly all of the planning below lands on IT.

Get the tester's source addresses into the scope letter Along with the systems in scope by IP address,…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.