Join our Newsletter — 33% off our NHI Course
Home› Glossary› Governance, Ownership & Risk› Data Processor
Governance, Ownership & Risk

Data Processor

← Back to Glossary
By NHI Mgmt Group Updated November 2, 2026 Domain: Governance, Ownership & Risk

A data processor handles personal data on behalf of a controller under defined instructions. For SaaS teams, the processor relationship matters because access scope, sub-processing, retention, and deletion controls must be enforceable and auditable, not merely promised in a contract.

What a data processor does in practice

A data processor is the service provider, outsourcer, or platform operator that handles personal data for a controller under defined instructions. The core practical issue is not just that processing happens, but that the processor can only act within the scope, purpose, and duration the controller has authorised.

That distinction matters because many SaaS and managed-service relationships blur the operational boundary between provider administration and controller direction. A processor can host, transmit, store, transform, or support access to data, but it should not decide the purposes or essential means of processing on its own.

Why the controller-processor boundary matters

The controller-processor split is a governance boundary, not a paperwork formality. It determines who decides why personal data is processed, who must justify the legal basis, and who remains accountable for the overall processing relationship. In practice, the boundary drives contract terms, security expectations, and auditability.

For organisations using cloud and SaaS services, the relationship only works if the processor can be shown to follow documented instructions and the controller can evidence that those instructions are operationally real. If a provider can access more data than necessary, reuse data for its own purposes, or change sub-processors without control, the relationship starts to drift away from the intended model.

What processors must be able to control

Processor obligations are operational as well as contractual. Access scope should be limited to what is needed for the service, sub-processing should be visible and controlled, and retention and deletion should be enforceable instead of assumed. Those controls are what make the relationship auditable.

The strongest processor arrangements can answer four questions clearly: what data is processed, by whom, for what purpose, under what retention rules, and with which downstream providers. If any of those answers depend on informal practice rather than system enforcement, the processor model becomes fragile.

  • Access should be limited to defined support, hosting, or delivery functions.
  • Sub-processors should be governed through notice, approval, or equivalent contractual control.
  • Deletion and return requirements should map to actual service workflows, not just exit clauses.
  • Logs, support processes, and admin access should be capable of audit review where appropriate.

How to recognise a real processor relationship

In day-to-day procurement and architecture reviews, the processor label should match what the platform actually does. A vendor that merely stores customer data is still a processor if it handles personal data on the controller’s instructions; a vendor that independently decides how to use that data may be operating as a controller for at least part of the activity.

This is why SaaS contracts, privacy notices, and technical architecture should be reviewed together. The legal label alone does not guarantee compliance if the service design gives the provider uncontrolled access, unclear data flows, or undocumented downstream handling.

  • Review whether the service provider can prove instruction-bound processing.
  • Check whether retention and deletion are implementable in the product, not only promised in the contract.
  • Map sub-processors and cross-border transfers to the actual delivery chain.
  • Confirm that support, export, and offboarding processes preserve controller control over personal data.

Risk and Threat Considerations

Processor relationships create concentrated exposure because one provider may handle large volumes of personal data across many customers. If access is overbroad, sub-processing is opaque, or deletion fails, a contractual obligation can become a real confidentiality and compliance failure at scale. The risk is amplified in SaaS environments where administrative access, backups, and support tooling can outlive the business need that justified the processing.

Failure mechanism: The processor cannot enforce the controller’s instructions consistently across live systems, support workflows, replicas, logs, and downstream service providers, so personal data remains accessible or retained beyond the intended scope.

Impact: That failure can produce unauthorised disclosure, unlawful continued processing, failed deletion, or inability to demonstrate compliance after a customer complaint, audit, or incident.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

GDPR and ISO/IEC 27001:2022 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
GDPRArt. 28 — Processor and sub-processor obligationsDefines processor duties, instructions, sub-processing and contractual controls for personal data handling.
Art. 32 — Security of processingRequires appropriate security measures for personal data processed by a processor or controller.
Art. 30 — Records of processing activitiesSupports auditable mapping of processing purposes, categories and recipients in processor arrangements.
Recommendation — Use Article 28 terms to bind the processor to documented instructions, sub-processor control and deletion obligations. Apply Article 32 safeguards to limit processor access and protect personal data in operation. Maintain processing records that show what the processor handles, for whom and under what purpose.
ISO/IEC 27001:2022A.5.19 — Information security in supplier relationshipsCovers supplier governance where a processor delivers services that handle customer personal data.
A.5.20 — Addressing information security within supplier agreementsMaps directly to contractual processor terms, including scope, deletion and security duties.
A.8.13 — Information backupBackups often preserve personal data beyond active service use and affect deletion commitments.
Recommendation — Assess supplier controls to ensure the processor relationship is governed and monitored. Embed processor instructions, security duties and exit obligations into supplier agreements. Control backups so processor-held personal data is not retained longer than agreed.

Practitioner Guidance

Governance implication: Treat the processor role as an operational control question, not just a legal classification. The relationship should be measurable in service design, access control, retention handling, and offboarding evidence, because those are the points where instruction-bound processing either exists or fails.

What to watch for: Be cautious when a vendor’s support model, sub-processor list, or data lifecycle behaviour is vague, because those are the usual places where the processor boundary breaks down. If the service cannot show how it limits access, deletes data, and constrains downstream processing, the contract is carrying more weight than the system.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org