Penetration Testing
A penetration test is a controlled attempt to break into your own systems, carried out with your permission, so that weaknesses are found and fixed before someone else finds them. It answers a question a checklist cannot: if a capable person tried to get in, how far would they get?
- Network, web application, and cloud penetration testing
- Detailed reporting with a remediation plan
- Evidence for regulators, insurers, and customers who ask for it
- Clear priorities for what to fix first
Penetration test or vulnerability scan?
The two are often confused. A vulnerability scan is automated: software checks your systems against a list of known weaknesses and produces a report. It is quick, inexpensive, and worth running regularly. A penetration test goes further. A person uses what a scan finds, along with judgment and technique, to see which weaknesses can actually be used and what an attacker could reach by chaining them together.
Most small businesses should start with scanning and basic hardening. A penetration test is most useful once the obvious problems are already fixed, because otherwise you are paying a specialist to report things a scan would have told you.
When a business needs one
Some standards call for penetration testing directly. PCI DSS includes it for many businesses that handle payment cards, and the FTC Safeguards Rule calls for periodic penetration testing and vulnerability assessments at many covered financial firms. Other rules, including the HIPAA Security Rule, expect you to evaluate your safeguards periodically without naming a specific method. Cyber insurers and larger customers sometimes ask for a recent test as well.
Outside of a formal requirement, good times to test are after a major change such as a new network, a move to the cloud, or the launch of a customer-facing application.
How an engagement works
Every test begins with a written scope: which systems are included, which are off limits, when testing may happen, and who to call if something unexpected occurs. Testing follows, then a report that ranks each finding by how serious it is and explains how to fix it. Once fixes are made, the affected items can be retested.
The report is the part that matters most. A good one is specific enough for whoever maintains your systems to act on, and clear enough for an owner or a board to understand what was at risk.
Not sure whether you need a penetration test or something simpler? Start with a free 15-minute IT Risk Call and we will talk through where it fits in your security and compliance roadmap.