Dan Aspin’s Post

View profile for Dan Aspin, graphic

Strategic Account Director - Driving Growth & Innovative road maps in Cybersecurity Solutions | Thought Leader in Cyber Defence Strategies

Scoping a penetration test…. It’s that time of year where your web developers, infrastructure team and security leaders all cram into a meeting room (or teams call) and work out what to include in your annual test. From being involved in scoping, selling and delivering penetration tests for 17 years, questions like the below are fairly commonplace. ‘Do we just do what we did last year?’ ‘Not too much has changed, do we even need to test?’ ‘Whose budget is this coming out of?’ ‘Whose turn is it to collect the coffees?’ All valid questions and ones I’ll attempt to answer here. First off, repeating the same test. It’s been going on for decades now and I can, to an extent, see the merit. You’ve gone another year without a breach and it’s the course of least resistance, the budget is pre-approved. No need for time-sapping scoping calls with your existing provider or going to other companies for a quote. That being said, it’s always worth a look at your risk register to see how that marries up against your current scope. Should we test at all. I’m marginally biased here but the simple answer is yes. Zero days come out with such alarming frequency these days that not having an annual test is simply not good practice. Following on from that most compliance drivers these days have penetration testing in some format as a mandatory task. Think PCI, and ISO 27001 talks about management of technical vulnerabilities. Whose paying for the test - well unless the owner of the company is involved in the decision making process then it’s not personally coming out of anyone’s pocket. I’ve arguably saved the most important question till last. Whose doing the coffee run. My suggestion is the leaders (hey they earn the big bucks) but get me involved in your scoping process and who knows I may even come bearing gifts….

Thomas Ballin

What if we already knew where vuls were before finding them?

2mo

I've not read the latest specs, where in ISO or CE does it mandate or mention pentesting?

To view or add a comment, sign in

Explore topics