Skip to content
CTEM Vendors

Home / Guides / CTEM roles and ownership: a RACI by stage

Guide, read 12 Nov 2026

Security runs the CTEM cycle; asset owners own the fixes

Stage Coverage MapAll guides

Six roles cover a CTEM program

A CTEM program crosses teams that report to different executives. NIST SP 800-40 Rev. 4 (April 2022) notes a divide between business or mission owners and security or technology management about the value of patching; a RACI is the plainest way to close it. Six roles are enough, whatever the org chart calls them.

The RACI by stage

R is responsible for doing the work, A is the one accountable name, C is consulted, I is informed. Each stage has exactly one A.

StageCISOBusiness ownerExposure teamValidation teamIT operationsCloud and app owners
ScopingARRCCC
DiscoveryIIA, RCCC
PrioritizationICA, RCCC
ValidationIICA, RCC
Mobilization: fixesICRCA, R for their assetsA, R for their assets
Mobilization: accepted riskA above thresholdA for their serviceRCCC
Re-test and closureIIARII

Scoping and discovery roles

Scoping needs the business owner in the room. Gartner's 21 Aug 2023 article starts the cycle with the business's attack surface, including social media accounts, code repositories and supply chain systems that no single IT team owns. The CISO is accountable for the scope; the business owner and exposure team write it.

Discovery belongs to the exposure team, but its quality depends on owners outside security. New York's Part 500.13, as amended, requires covered entities to keep an asset inventory with each asset's owner, location, classification or sensitivity, support expiration date and recovery time objective. The UK NCSC's guidance asks organizations to know who is responsible for what. If the cloud team owns the cloud inventory, it is consulted on every discovery run, and gaps it reports count as discovery findings.

Prioritization and validation roles

The exposure team ranks the list and is accountable for its reasons. Asset owners are consulted because they know what compensating controls exist; Gartner lists availability of compensating controls as a prioritization factor. The business owner is consulted on impact, because a path to a system that holds customer data and a path to a test server can look the same in a tool.

Validation has its own accountable lead, separate from the team that ranked the list, so a test result is not graded by the people who predicted it. The validation team needs written permission to test in the scope, agreed during scoping. Gartner also asks that business stakeholders agree on what triggers lead to remediation; the validation lead records that agreement.

Mobilization roles

Each fix has one accountable owner: the person who owns the asset where the change is made. IT operations owns patches and configuration on servers and endpoints; cloud platform teams own guardrails and account settings; application owners own code, dependencies and pipeline changes. The exposure team is responsible for packaging the fix, tracking it and requesting the re-test.

Gartner says to document cross-team approval workflows and not to rely wholly on automated remediation. Write the approval path per asset type during scoping. The mobilization guide covers deduplication and SLAs.

Where one fix spans several owners, for example a base image change that the platform team makes and every application team must redeploy, name one accountable owner for the change and list the others as responsible for their part. Split accountability is the most common reason fixes stall.

Exceptions and accepted risk

Not every proven exposure gets fixed this cycle. The NCSC treats a decision not to update as a senior-level risk decision, made in the context of organizational risk management policy. In the RACI, the business owner is accountable for accepting risk on their service, and the CISO is accountable above a threshold the board sets. Each accepted risk carries an expiry and a re-test in the next cycle.

Under Part 500.4(b), the CISO's annual written report to the senior governing body includes plans for remediating material inadequacies, so the accepted-risk register is board material at covered entities. NYDFS's FAQs confirm that an authorized committee of the board can receive that report. The board reporting guide shows where it fits.

Common ownership gaps

The same gaps appear in most first cycles:

Put the RACI where people will see it

Attach the RACI to the scope statement for each cycle, with names, not team labels. The first cycle guide includes owners in the scoping checklist, and the program starter has a blank RACI. Vendors that sell tooling for each stage are on the index.

Review the RACI at the start of every cycle. People change roles, systems change hands in reorganizations, and a name that was right in the first cycle may be wrong by the fourth. A stale RACI shows up first as tickets bouncing between teams; check the names before that happens.

Sources

  1. https://web.archive.org/web/20251230022449/https://www.gartner.com/en/articles/how-to-manage-cybersecurity-threats-not-episodes, read 12 Nov 2026
  2. https://www.dfs.ny.gov/system/files/documents/2023/12/rf23_nycrr_part_500_amend02_20231101.pdf, read 12 Nov 2026
  3. https://www.dfs.ny.gov/cybersecurity/faqs, read 12 Nov 2026
  4. https://www.ncsc.gov.uk/guidance/vulnerability-management, read 12 Nov 2026
  5. https://csrc.nist.gov/pubs/sp/800/40/r4/final, read 12 Nov 2026

Last reviewed 12 Nov 2026.