Security Operations
Penetration testing See how defenses hold
Penetration testing is an authorized attack on your systems that uses real attackers' techniques. "Exploitation of vulnerabilities is now the most common initial access vector for breaches," the Verizon 2026 Data Breach Investigations Report found. We run approved external and internal tests with our testing partner, then a retest.
- Who it is for
- Organizations whose regulator, insurer or clients ask for a test
- How it runs
- Once a year or per project, with our testing partner
- What you get
- Test report, recommendations, validation notes and a retest result
What a penetration test is, in plain terms
A penetration test is a controlled attack on your own systems. Testers copy what real attackers do, within limits agreed in advance, to find ways around your security.
In its guide to security testing, the National Institute of Standards and Technology (NIST) describes testers combining weaknesses, because two gaps together can give more access than either one alone. That is how a test shows the damage a real break-in could do.
A test also checks whether your defenses notice the attack and respond. The Center for Internet Security (CIS) adds that it can expose weak processes, such as settings that are managed inconsistently.
External and internal penetration tests
Our penetration testing covers both, as NIST describes them.
- External penetration testRun from outside your network, usually as seen from the internet, to find what an outside attacker could use. When both tests are done, NIST says this one usually comes first.
- Internal penetration testRun from inside your network, the way a trusted insider or an intruder who already got in would work. It usually starts with ordinary user access and tries to gain more.
Penetration test vs. vulnerability scan
A vulnerability scan flags weak spots that may exist. A penetration test goes further. Testers try to use those weak spots to confirm they are real and see where they lead.
The two work together. CIS notes that a scan is often where a penetration test starts, and that people wrongly use the two terms as if they meant the same thing. NIST describes regular scans with penetration tests from time to time, and says a yearly test may be enough.
For the scans between tests, our vulnerability management service runs regular vulnerability scans for weak spots, with fixes tracked until they are closed.
How a penetration testing project runs
- 01 PlanThe scope, the written authorization and the testing windows are settled before any testing.
- 02 TestExternal and internal tests run with our testing partner, inside the written scope.
- 03 ReportYou get the findings in writing, with recommendations.
- 04 RetestOnce the gaps are fixed, a retest checks that the fixes worked.
- 05 RepeatPlan the next test a year later, or with your next project.
What you receive from a penetration test
Keep these records private, since they show where your systems could be attacked.
- 01Penetration test reportThe findings from your tests, written up for you and your managers.
- 02RecommendationsWhat to change to close the gaps the test found.
- 03Validation notesNotes on how your security measures held up during testing.
- 04Retest resultWhether the fixes closed the gaps, checked by a retest.
Who asks for a penetration test, and how often
Most of the rules and forms below point to once a year.
- FTC Safeguards RuleThis Federal Trade Commission (FTC) rule covers non-bank financial businesses, such as tax preparers and mortgage brokers. It calls for a penetration test every year and vulnerability assessments at least every six months, unless you have effective continuous monitoring (16 CFR 314.4(d)(2)). Firms with customer information on fewer than 5,000 consumers are exempt from this testing (16 CFR 314.6).
- CIS Controls v8.1CIS sets priorities in three Implementation Groups. Control 18 calls for external tests at least once a year by a qualified party in Groups 2 and 3, and yearly internal tests in Group 3.
- Cyber insurance applicationsApplications can ask. One current form lists regular penetration tests among the security controls it asks about, and another asks whether you run a penetration test of your network at least once a year.
- Client security questionnairesClients can ask too. For example, the Cloud Security Alliance, which publishes a security questionnaire for vendors, includes periodic penetration testing by independent third parties in its cloud controls.
- HIPAA, proposedIn January 2025, the U.S. Department of Health and Human Services proposed a rule change for organizations covered by the Health Insurance Portability and Accountability Act (HIPAA), business associates included. It would require a penetration test at least every 12 months (proposed 45 CFR 164.312(h)(2)(iii)). It is not final. The 2026 federal regulatory agenda lists final action for July 2027.
Scope, written authorization and rules of engagement
A penetration test is an attack you allow, so it starts on paper. In NIST's guide, planning comes first. Management approval is documented and the testing goals are set before any testing happens.
The guide says the written plan should settle what is in scope, which systems must not be tested, who is authorized to test, how sensitive data is handled and what happens if there is an incident. Rules of engagement then set the detailed limits for the test, and in the guide's template both the test lead and your senior management sign them.
If some systems sit with a hosting provider or another outside party, the guide notes that the owner of that network usually has to agree in writing as well. It also says legal advisors should always be involved in intrusive tests such as penetration testing, so plan to involve your lawyer.
What we handle, What you decide and approve
CyberBlip
- Coordinate the project with you and our testing partner
- Keep testing inside the scope you approved in writing
- Document the findings and recommend fixes
- Support the retest once the gaps are fixed
You
- Define the scope, including what is off limits
- Give written authorization before any testing
- Approve the testing windows
- Acknowledge the testing risk
Disruption risk and the limits of a penetration test
Penetration testing can disrupt your systems. Testers use real attack techniques, and NIST warns that systems may be damaged or stop working. Skilled testers lower that risk, but it can never be fully removed, which is why you acknowledge the testing risk as part of your approval.
The same guide lists ways to lower the risk: a detailed plan, logging, testing outside peak business hours, testing copies of your live systems, and stopping before a step would cause damage. Your approved testing windows decide when testing can happen.
A test covers only the written scope, so systems you leave out or do not authorize are not tested at all. And no single testing technique gives a complete picture of your security, NIST says, so a clean report is not proof that you are secure.
Questions about penetration testing services
Who does the actual testing?
Testing runs as a project with our testing partner, and we coordinate the work with you. An outside tester brings an independent view. CIS says independent penetration testing can provide objective insight, and one insurer's application describes testing as typically done by an authorized third party.
If we have continuous monitoring, do we still need a penetration test?
It depends on who is asking. The FTC Safeguards Rule calls for a yearly test and vulnerability assessments at least every six months unless you have effective continuous monitoring, or other systems that detect, on an ongoing basis, changes that may create weaknesses. Whether a setup counts as effective is a legal question for you and your counsel. The CIS Controls and insurance applications ask about penetration testing separately.
How is a penetration test different from a cyber risk assessment?
A cyber risk assessment does not attack your systems. It is a review of your security risks and a ranked plan of what to fix first, and under the FTC Safeguards Rule it guides what each yearly penetration test covers. See what our cybersecurity risk assessment covers.
Does everything the test finds have to be fixed?
NIST says the weaknesses a test finds should be mitigated, meaning fixed or their risk reduced. CIS calls for a documented process to fix them, with timing set by each finding's impact. The business and risk decisions stay with you. The retest then shows which gaps are closed.
Will a penetration test help with our cyber insurance application?
If the application asks about penetration testing, the report and the retest result show what was tested and what was fixed. When an insurer or a client sends a security questionnaire, we help you answer it accurately, with the evidence to back your answers. Approval stays the insurer's decision.
Sources
Show all 11 sourcesHide sources
- 2026 Data Breach Investigations Report Verizon, 2026
- SP 800-115, Technical Guide to Information Security Testing and Assessment NIST, 2008-09
- Glossary: penetration testing NIST Computer Security Resource Center
- Glossary: rules of engagement NIST Computer Security Resource Center
- CIS Controls Assessment Specification v8.1, Control 18: Penetration Testing Center for Internet Security
- 16 CFR Part 314, Standards for Safeguarding Customer Information (FTC Safeguards Rule) eCFR, 2026-11-13
- Cyber Insurance Application, form AB-CYB-APP, edition 06/2026 At-Bay, 2026-06
- Smart Cyber Application, Version 3.2, question 17 and glossary Corvus Insurance, 2024-09
- Implementing CCM: Threat & Vulnerability Management Controls Cloud Security Alliance, 2025-11-21
- HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information, proposed rule, 90 FR 898 Federal Register, 2025-01-06
- HIPAA Security Rule update, Unified Agenda entry RIN 0945-AA22 reginfo.gov, Office of Information and Regulatory Affairs, 2026
Next step
Find out where you stand
Tell us how we can best support you.
Icons: Tabler Icons, MIT License. License text: /licenses/tabler-icons.txt