ISMS scope and penetration test scope: close the gap before your auditor does

Your ISMS scope statement and your pen test scope must match — auditors check this at Stage 2, and a visible gap is a nonconformity.

Sarah Jenkins

By Sarah Jenkins

Regulatory & Compliance Analyst · 6 min read · October 15, 2026

Your ISMS scope statement and your pen test scope look like two separate documents. Many teams treat them that way. That is a nonconformity waiting to happen.

When an auditor walks through your Stage 2, they check whether your penetration testing programme covers the systems you declared in scope. A pen test that skips a production service you listed is not an oversight. It is a finding. This article shows where the gap opens and how to close it before certification.

Why pen test scope must follow ISMS scope

ISO 27001 is a management system standard. [source: https://www.iso.org/standard/27001] You define what you protect. You assess the risks to it. You implement controls proportional to those risks and demonstrate you have done so.

Penetration testing is a control. When you complete your Statement of Applicability, you declare whether technical vulnerability testing is applicable to your environment. If you say it is — and for a customer-facing SaaS product it almost certainly is — you are now on record saying you run it. The test must cover what you said it would cover.

The mismatch auditors catch is not subtle. They put your ISMS scope statement and your pen test report on the same table. They check whether the systems listed in one appear in the other. If your scope statement says your customer-facing product runs in AWS eu-west-1 and the pen test report says they tested the web application layer, the auditor asks what happened to the underlying infrastructure. You either have an answer or you have a finding.

Where the gap typically opens

Three patterns account for most mismatches.

Inherited pen tests. Your engineering team bought a web application test two years ago. It covered the application layer. It did not cover your internal admin portal, your data pipeline, or your staging environment where production data sometimes lands. You are now pursuing ISO 27001. That historical report does not map cleanly to the scope you are now declaring. Auditors will notice. Scope updates without test updates. You launched a mobile API endpoint six months after your last pen test. The API handles authentication tokens and processes customer personal data. You updated your ISMS scope document to include it because your compliance team is diligent. The pen test vendor was not told. The next audit cycle, your scope statement covers the mobile API and your pen test report does not. Different briefs for different engagements. Your pen test vendor works from a brief. The brief typically comes from a security engineer or CTO. Nobody cross-references it against the ISMS scope statement before the engagement kicks off. The vendor tests what they are told to test. What they are told to test does not always match what the compliance team declared in the scope document. [source: https://www.isms.online/iso-27001/]

These are not exotic failures. They are routine coordination failures between engineering and compliance functions that are growing at different speeds.

What auditors actually look for

Stage 1 and Stage 2 audits approach pen testing at different levels of depth.

At Stage 1, the auditor reviews documentation. They will ask for your scope statement, your SoA, and your most recent pen test report. If the executive summary of the report describes a scope that visibly omits a system category mentioned in your ISMS scope statement, they flag it. You have a defined window to resolve it before Stage 2.

At Stage 2, the auditor wants evidence the control is running, not just documented. They look at the date of the test — was it recent enough to count as current evidence? Who performed it — was the firm independent? What did the scope cover — does it match your ISMS scope statement? And critically, were the findings remediated? Open high-severity findings without a remediation record are a major nonconformity. A scoping gap is typically a minor nonconformity on first occurrence, but it seeds a recurring finding in every surveillance audit that follows.

Surveillance audits are where the recurring gap costs you most. If your product grew in year two and the pen test scope did not, the surveillance auditor will note it. Explaining it once as an oversight is acceptable. Explaining it twice means your control over scope alignment is not operating effectively.

How to close the gap before certification

The fix is a coordination procedure, not a technical one.

Make the ISMS scope statement a direct input to the pen test brief. Before any engagement kicks off, send the scope statement to the pen test vendor and ask them to confirm that their test plan covers every system it lists. Get that confirmation in writing as part of the engagement kickoff documentation. Write scope coverage into your ISMS documentation explicitly. Your scope statement or a linked control narrative should name what must be covered in technical vulnerability testing. This is not a new ISO 27001 requirement. It is making the implied requirement explicit so you can check it before the auditor does. Check the scope section of the report before the findings section. When you receive the pen test report, read the scope confirmation in the executive section first. Does it match your ISMS scope statement? If a system is absent, raise it with the vendor before the report is finalised. Most firms will address a genuine scoping error for an additional day rate. That cost is a fraction of a certification delay. Tie scope change reviews to your ISMS scope update process. Any time you add a system to your ISMS scope, your process should include a step that asks: does our next pen test engagement need to cover this? Document the decision either way. If you defer to the next annual cycle, say so explicitly. If the system is high-risk enough to warrant an immediate targeted test, commission one and document the rationale.

Managing scope alignment across the certification lifecycle

ISO 27001 surveillance audits run on an annual cadence. [source: https://www.iso.org/standard/27001] Your pen test programme should be designed around that rhythm.

For most Series B SaaS companies, an annual pen test scoped against the current ISMS scope statement, with targeted testing commissioned for significant mid-year additions, will satisfy auditors. The documentation trail matters more than frequency. An auditor who can follow a clear line from scope change to pen test brief to test report to findings closure is satisfied. An auditor who encounters a gap without a documented rationale writes it up.

Keep your scope change log in the same system as your ISMS documentation. If it lives in a project management tool that your compliance team rarely opens, it will fall behind. If it sits as a field in your ISMS management tool, updated whenever the scope statement changes, it will stay current.

Growth-stage SaaS companies add services, acquire tools, and expand into new markets fast. Each of those moves is a potential scope event. The goal is not to run more pen tests. The goal is to prove that what you declared you would protect, you actually tested. Close the documentation loop and the control holds under audit.

Audit prep takes months when pen test evidence and ISMS scope documentation live in different places. CloudAnzen maps your declared scope to control evidence requirements — including penetration testing coverage — so nothing falls through before your auditor arrives. Talk to us.

Keep the momentum

Turn this guidance into a working program

CloudAnzen helps teams connect evidence, review failing controls, manage risk, and stay audit-ready across frameworks from one place.