The way in rarely changes. What changes is who asks for proof of testing, and how often.
We start by listing the rules that apply to you, then write the scope so the report answers them. Seven sectors below, each with the test we usually run first.

Some rules ask for testing outright, some ask for an evaluation and leave the method to you. Either way, the report has to stand up in front of an examiner.
Hospital groups, clinics and billing firms. We agree quiet windows with clinical IT and keep away from anything that touches patient care.
Usually starts with Internal and AD, 7 days
Rule | What it asks for |
HIPAA Security Rule, 45 CFR 164.308(a)(8) | Periodic technical and nontechnical evaluation of your safeguards. |
HIPAA Security Rule, 45 CFR 164.308(a)(1)(ii)(A) | An accurate risk analysis. A test gives it evidence. |
GDPR Art. 32(1)(d) | Regular testing of security measures, for groups that treat EU patients. |
Lenders, insurers, credit unions and banks. Examiners read the scope first, so we write it with them in mind.
Usually starts with External network, 5 days
Rule | What it asks for |
GLBA Safeguards Rule, 16 CFR 314.4(d)(2) | Without continuous monitoring: a penetration test every year and vulnerability assessments every six months. |
23 NYCRR 500.5 | Penetration testing at least once a year for firms licensed in New York. |
DORA, Regulation (EU) 2022/2554, Art. 26 | Threat-led penetration testing at least every three years for identified EU firms. |
Stores, online sellers and anyone else who takes cards. We test the card environment and the walls around it.
Usually starts with Web and API, 8 days
Rule | What it asks for |
PCI DSS v4.0.1, Req. 11.4.2 and 11.4.3 | Internal and external penetration tests every 12 months and after significant change. |
PCI DSS v4.0.1, Req. 11.4.4 | Exploitable findings fixed, then retested. Day 38 covers this. |
PCI DSS v4.0.1, Req. 11.4.5 | Proof that segmentation really does isolate the card environment. |

For software firms the request usually comes from a customer's security questionnaire, not a regulator. We add a one-page letter you can pass on.
Usually starts with Web and API, 8 days
Rule | What it asks for |
SOC 2, CC4.1 | Ongoing or separate evaluations of your controls. |
SOC 2, CC7.1 | Finding vulnerabilities and configuration changes. |
ISO/IEC 27001:2022, A.8.8 and A.8.29 | Managing technical vulnerabilities and testing security in development. |

Freight, rail and shipping platforms. Partners connect through APIs, so one customer's login should never reach another customer's data.
Usually starts with Web and API, 8 days
Rule | What it asks for |
NIS2, Art. 21(2)(f) | Ways to assess whether your security measures work, for EU transport operators. |
GDPR Art. 32(1)(d) | Regular testing where you hold EU customer data. |

Law and accounting firms. Client confidence is the asset, so the front desk and the phone are in scope along with the network.
Usually starts with Social engineering, 5 days
Rule | What it asks for |
ABA Model Rule 1.6(c) | Reasonable efforts to prevent unauthorized access to client information. |
GDPR Art. 32(1)(d) | Regular testing where you act for clients in the EU. |

Office networks get a normal test. Control systems get a passive review, or active work on a test bench or during an outage you choose.
Rule | What it asks for |
NERC CIP-010, R3 | Vulnerability assessments, active ones at least every 36 months for high impact systems. |
IEC 62443 | Security requirements for industrial systems, including verification of them. |
NIS2, Art. 21(2)(f) | Ways to assess whether your measures work, for EU energy operators. |
Plain summaries for orientation, not legal advice. Your auditor has the final word.