Home / Guides / Scoping a first CTEM cycle: one scope, named owners, six weeks
Guide, read 12 Nov 2026
Start with one business-critical scope, named owners and a six-week clock
One scope a business owner will sign
The first cycle exists to prove the loop works, not to cover the estate. Pick one service whose loss the business would feel within a day: payments, order intake, the customer portal, a trading platform, a clinical system. The test is simple. If no executive will put their name on the scope, the cycle will stall at mobilization when fixes need approval.
Gartner's 21 Aug 2023 article suggests two pilot areas: the external attack surface, which it calls a relatively narrow scope with a growing ecosystem of tools, and SaaS security posture, as more critical business data sits in SaaS. Both work. A single business service often works better, because it gives the cycle an owner and a clear bad outcome.
The UK NCSC's vulnerability management guidance (reviewed 1 May 2026) makes the same point for any exposure program: it is easy to become overwhelmed by the number of issues found, so start in a small or focused way, for example only critical systems, and grow from there.
Write the scope as a service, then list what supports it
A scope statement fits on one page. It names the service and the business owner, states the bad outcome in plain words (customer card data copied out, orders stopped for four hours), then lists what the service depends on.
For the system list, borrow a field set that regulators already use. New York's Part 500, as amended, asks covered entities to track for each asset its owner, location, classification or sensitivity, support expiration date and recovery time objective. Those five fields are enough to start, and they become the routing table for mobilization later.
- Applications and the hosts, containers or functions that run them.
- Cloud accounts, subscriptions or projects that hold them.
- Identities: admin groups, service accounts, the identity provider tenant.
- Data stores the bad outcome would touch.
- Third parties and SaaS tenants in the path, with the contract owner for each.
- Internet-facing entry points: domains, IP ranges, APIs.
Name owners before discovery starts
Every system on the list needs a person, not a team mailbox, who can approve a change to it. Find them now. Discovery will produce findings within days, and a finding with no owner sits in a queue until the cycle ends.
Gartner puts the same requirement at the other end of the cycle: the mobilization effort exists to remove obstacles to approvals, implementation and mitigation deployment, and cross-team approval workflows should be documented. Writing down owners and the approval path during scoping is the cheapest way to meet that. The roles guide gives a RACI by stage.
Third parties need the same treatment. If a SaaS tenant or a hosting provider sits in the path to the bad outcome, name the internal contract owner who can raise a change with the supplier, and check the contract for testing rights before validation week. A supplier that forbids testing is itself a finding for the scope statement.
Agree the test permission in writing at the same time: which systems may be tested, by which methods, in which hours, and who may stop a test. Validation that waits for permission in week three loses the cycle.
Set the cycle at 4 to 6 weeks
This site's method assumes a cycle of 4 to 6 weeks per scope. Shorter than four and validation gets squeezed; longer than six and the discovery data is stale by the time owners see it. The split below is a starting plan, not a standard.
Hold one short meeting at each boundary: the business owner signs the scope at the end of week one, the exposure team presents the short list at the end of week three, and owners see proven items as soon as validation marks them. Waiting for a single end-of-cycle report wastes the weeks mobilization needs.
| Week | Stage | Done when |
|---|---|---|
| 1 | Scoping | Scope statement signed; owners named; test permission granted |
| 1 to 2 | Discovery | Inventory of in-scope assets and exposures; visibility gaps listed |
| 2 to 3 | Prioritization | Short list with one stated reason per item |
| 3 to 4 | Validation | Each item marked proven, not proven or blocked, with evidence |
| 4 to 6 | Mobilization | Fixes, mitigations or accepted risks recorded; re-tests run |
Emergencies run outside the cycle
A cycle length is not a reason to wait on an actively exploited flaw. CISA's BOD 26-04 (10 Jun 2026) starts the federal remediation clock when a CVE enters the KEV catalog or is found on an asset, whichever comes first, and the catalog held 1,779 entries in version 2026.11.10. Keep the existing emergency patch path running. If an emergency touches the scope, record it in the cycle so the re-test covers it.
Define done for cycle one
Write the exit criteria into the scope statement so the cycle can be judged against them:
- The scope statement is signed by the business owner.
- Every in-scope system has a named owner and the five inventory fields.
- The short list exists and each item has a reason.
- Every short-list item has a validation result with a date.
- Every proven item is fixed, mitigated or accepted by a named person, and fixed items are re-tested.
- A one-page summary states the number of proven exposures found and closed, which feeds the board report.
Mistakes that sink a first cycle
Gartner says confusing scoping with discovery is often the first failure in building a CTEM program. The usual form: the team runs a scanner across everything, calls the output the scope, and spends the cycle sorting findings no one owns. Other common errors are choosing a scope the security team cares about but no business owner does, skipping test permission until validation week, and counting the number of findings as progress.
The program starter has a fill-in scope statement, and the scoping stage page lists which vendors on the index sell scoping support.
Sources
- https://web.archive.org/web/20251230022449/https://www.gartner.com/en/articles/how-to-manage-cybersecurity-threats-not-episodes, read 12 Nov 2026
- https://www.ncsc.gov.uk/guidance/vulnerability-management, read 12 Nov 2026
- https://www.dfs.ny.gov/system/files/documents/2023/12/rf23_nycrr_part_500_amend02_20231101.pdf, read 12 Nov 2026
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk, read 12 Nov 2026
- https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json, read 12 Nov 2026
Last reviewed 12 Nov 2026.