Accountability should be shared, but not blurred. The vendor must secure the system it operates, while the customer organisation must vet the vendor, constrain data exposure, and define control expectations in contract terms. Security, procurement, legal, and business owners all need clear roles so that responsibility for prevention, detection, and response does not fall through the gaps.
Shared accountability is the right model, but the obligations are different
When a vendor processes sensitive records for multiple organisations, accountability should be split by control domain, not pooled into a vague shared-responsibility statement. The vendor is accountable for operating the platform securely. Each customer organisation remains accountable for due diligence, contractual safeguards, data minimisation, and deciding whether the vendor’s controls are good enough for the records it entrusts to them.
This division matters because the customer cannot outsource governance, and the vendor cannot infer each customer’s risk tolerance, retention limits, or regulatory obligations. In practice, the answer is defined by who can actually control the control: the vendor controls the service; the customer controls selection, scope, and oversight.
That vendor-control split is easiest to see in multi-tenant services, where one provider may host records for many customers at once. A single failure can therefore create broad exposure, so the accountability model has to cover isolation, access restriction, logging, and incident handling as first-class obligations. NHIMG’s Ultimate Guide to Non-Human Identities notes that only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them, which is a useful reminder that weak lifecycle discipline often turns shared platforms into shared exposure.
For the customer organisation, accountability includes deciding what the vendor is allowed to see, store, process, and retain, then checking that the vendor can prove those limits are enforced. For the vendor, accountability includes segmentation, strong access control, secure configuration, monitoring, and a defensible response process when something goes wrong. Security, procurement, legal, privacy, and the business owner all need explicit ownership so the risk does not fall through the gaps between teams.
What “accountable” means in practice for vendor-handled records
Accountability is strongest when it is evidence-based. The vendor should be able to show who can access the records, how access is granted and removed, how data is isolated between customers, and how incidents are detected and escalated. The customer should be able to show why that vendor was selected, what controls were required, and how the arrangement was reviewed over time.
The practical failure mode is role confusion. If the contract says the vendor is responsible for security, customers may stop validating the provider’s controls. If the contract says the customer owns the data, the vendor may underinvest in platform hardening, monitoring, or segregation. The right arrangement is explicit: the vendor secures the service; the customer governs the risk acceptance decision.
Third-party control expectations are particularly important when records are sensitive or regulated, because the customer’s duty does not end at the handoff. A useful benchmark is SOC 2 Trust Services Criteria, which aligns well with vendor assurance, confidentiality, availability, and processing integrity expectations. For cloud-heavy environments, CSA Cloud Controls Matrix is a useful way to translate that accountability into vendor control areas such as IAM, data security, and supply chain oversight.
Where the records are highly sensitive, it is also reasonable to require explicit control language for breach notification timing, subcontractor approval, retention limits, encryption boundaries, and evidence of access review. Those are not paperwork details, they are the mechanisms that determine whether shared accountability is real or merely rhetorical.
Risk and Threat Considerations
The main risk is accountability drift: each party assumes the other is covering a control, and sensitive records end up with weaker segregation, broader access, or delayed detection than either side intended. In a multi-organisation vendor model, that can turn one control failure into a cross-customer exposure.
Failure mechanism: Access, retention, and incident-response duties are split across organisations without a clear owner, so excessive access, poor isolation, or slow notification persists until records are exposed or misused.
Impact: Sensitive records can be disclosed across tenants, retained longer than intended, or left uncontained after compromise, creating regulatory, contractual, and customer harm.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST CSF 2.0, CIS Controls v8 and NIST SP 800-63 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | GV.RM-01 — Risk Management Strategy | Vendor data handling requires explicit risk ownership and acceptance decisions. |
| PR.AA-01 — Identity Management, Authentication, and Access Control | Sensitive records depend on controlled access and tenant segregation in the vendor platform. | |
| RS.CO-01 — Incident Reporting and Communication | Customers and vendors need clear escalation and notification duties when records are exposed. | |
| Recommendation — Define and maintain risk ownership for vendor-processed records. Enforce least-privilege access and tenant isolation for vendor-held records. Predefine incident notification and escalation responsibilities with the vendor. | ||
| CIS Controls v8 | CIS 15 — Service Provider Management | Third-party processors require due diligence, contractual safeguards, and ongoing oversight. |
| CIS 6 — Access Control Management | Vendor-handled records must be restricted to authorised users and processes. | |
| CIS 17 — Incident Response Management | Shared processing requires agreed response roles when records are compromised. | |
| Recommendation — Assess, contract, and monitor the vendor as a managed service provider. Restrict and review access to sensitive records on a need-to-know basis. Document and test incident response obligations with the processor. | ||
| NIST SP 800-63 | IAL2 — Identity Assurance Level 2 | Assurance of who can access records depends on trustworthy identity proofing and access control. |
| AAL2 — Authenticator Assurance Level 2 | Stronger authentication reduces the chance that vendor access is abused or taken over. | |
| Recommendation — Require appropriate assurance before granting access to sensitive vendor workflows. Require strong authentication for vendor and customer administrators. | ||
Practitioner Guidance
What to prioritise: Assign one named owner for vendor risk acceptance, one for contractual control requirements, and one for operational oversight. If no one can answer who approved access scope, retention, and incident escalation, the accountability model is already broken.
What to verify: Check that the vendor can prove tenant separation, access logging, data retention limits, and deletion or return processes. Also verify that your own organisation can evidence due diligence, approval, and periodic review, because customer accountability does not disappear once the contract is signed.
Common mistake: Treating the vendor as the only accountable party. That shortcut usually leaves the customer organisation without a decision record for why the provider was trusted with sensitive data in the first place.
Practitioner takeaway: Shared accountability only works when each side can demonstrate its own controls, not when both sides assume the other is covering the gap.
Related resources from NHI Mgmt Group
- What should organisations do before expanding AI access to sensitive records?
- How can organisations tell whether confidential computing is actually protecting sensitive identity data?
- Who is accountable when a former worker still has access to sensitive records?
- Who is accountable when a vendor support session exposes sensitive data?
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on September 19, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
