Publicité
ERP IMPLEMENTATION
🇫🇷 Lire en français →

Cloud ERP Encryption and Key Management: BYOK, HYOK and What to Demand from Your Vendor

BYOK, HYOK or vendor-managed keys: who holds your ERP encryption keys, what SAP, Microsoft, Oracle, Odoo and Sage offer, and 10 questions before you sign.

Cloud ERP Encryption and Key Management: BYOK, HYOK and What to Demand from Your Vendor

“Your data is encrypted” appears in almost every ERP SaaS vendor response. The statement is true and nearly useless: it does not say who holds the key, who can revoke it, or what happens the day it disappears. For a CIO, CISO or DPO at a mid-sized company, the real contract question is not “is it encrypted?” but “who controls the key, and at what operational cost?”

This article focuses on that single subject: encryption and key management for a cloud ERP. For the broader security picture, see our ERP cybersecurity guide. Here we go into the technical and contractual detail.

What the Vendor Encrypts by Default, and What It Does Not

Default encryption from the major vendors generally covers the storage layer. Microsoft states that all customer data stored in Power Platform, and therefore under Dynamics 365, is encrypted at rest with Microsoft-managed keys by default (Microsoft Learn, Power Platform). Odoo states that it encrypts customer data and files at rest with AES-256, in production and in backups (Odoo, security page). Oracle specifies that Fusion Applications environments are protected by default with Oracle-managed keys (Oracle, Fusion Applications).

This default encryption protects against one specific scenario: theft of a storage medium, a disk or a copy of the database. Microsoft puts it this way: a stolen database cannot be restored on another server without the key. It does not protect against hijacked legitimate access, nor against an authenticated application request.

The real scope has to be verified layer by layer. Here is the grid to request from the vendor, in writing.

LayerWhat to confirm
Database at restAlgorithm, level (disk, database, tablespace), key management
Attachments and filesSame key as the database, or separate object storage?
Backups and environment copiesEncrypted with which key, retained for how long
In transitMinimum TLS version, internal service-to-service traffic, integration flows
Sensitive fields (IBAN, salaries, HR data)Field-level application encryption, or just an access right?
Logs and tracesDo they contain business data in clear text?
Test and support environmentsProduction data copied, with what protection?

Limits exist even at the most advanced vendors. Microsoft explicitly lists elements that remain encrypted with a Microsoft key even when a customer key is enabled: connector settings, environment settings, application metadata. And customer-managed encryption applies only to the listed applications and services, with conditions (managed environments, Power Platform integration for Finance and Operations apps). A promise that “everything is encrypted with your key” therefore always deserves a written scope.

Key Models: Who Can Decrypt, Who Can Revoke

Three models coexist, and vendors do not always use the same words to describe them.

Vendor-managed keys. The vendor generates, stores, rotates and protects the key. You have nothing to do, and nothing to decide. You trust its processes and its administrators.

BYOK (Bring Your Own Key). You generate or own the key, then place it in a vault attached to the cloud service (Azure Key Vault or OCI Vault, for example). The vendor uses it to encrypt your data, and you can rotate it or withdraw access to it. The key still lives inside the provider’s ecosystem.

HYOK (Hold Your Own Key) or external key. The key never leaves your HSM or your external key manager. The cloud service calls that device for every encryption operation. You keep maximum control, with a direct dependency: if your key manager does not respond, neither does the ERP.

Comparison of the Three Models

CriterionVendor-managed keyBYOKHYOK / external key
Who can decryptThe vendor (technically)The vendor, as long as the key is accessibleNo one without a call to your device
Who can revokeThe vendorYou, by withdrawing access to the keyYou, immediately
ComplexityNoneMedium: vault, policies, rotationHigh: HSM or external KMS, network, high availability
Outage riskLow, borne by the vendorMedium: expired key or revoked access = ERP downHigh: your KMS becomes a single point of failure for the ERP
CostIncludedVault, possible licences, operations timeHighest: HSM or managed service, on-call, skills
Effect on sovereigntyLowReal, subject to the law applicable to the providerStrongest

One point to keep in mind: revocation is a double-edged sword. Oracle states that a deleted key immediately makes any data encrypted with it unusable or unrecoverable, including the Fusion database (Oracle, Fusion Applications).

What the Major Vendors Offer

Offers change quickly, and so do scopes. The information below is based on official documentation consulted in November 2026: verify it at signing.

Microsoft Dynamics 365. The customer-managed key (CMK) relies on an Azure Key Vault key, including in managed HSM. A Power Platform enterprise policy references the key, then environments are attached to it. The documentation lists the applications concerned, including Dynamics 365 Finance and Supply Chain Management, subject to licensing and configuration conditions (Microsoft Learn). A point of attention: the documentation requires the vault to have soft delete and purge protection enabled.

Oracle Fusion Applications. Customer keys are stored in an OCI vault and protect production and non-production environments. Oracle recommends separate vaults for production and non-production, with distinct keys per test and development environment (Oracle, documentation). Oracle also presents an external key management service, built with Thales (Oracle, External Key Management for Fusion blog).

SAP. The SAP Data Custodian Key Management service lets you manage keys for certain SAP services, with rotation and invalidation mechanisms in case of an incident (SAP Help, Data Custodian BYOK, SAP Community, Customer-controlled key management). According to Thales documentation, the CipherTrust integration enables BYOK and HYOK models for SAP products built on HANA (Thales, SAP HYOK). The point to have SAP clarify: which exact offer (S/4HANA Cloud Public Edition, Private Edition, RISE) is covered, and as of what date.

Odoo. Odoo’s security page documents AES-256 encryption at rest, backups included, but does not mention a customer-managed key (Odoo, security). If you need BYOK, ask the question explicitly: with self-hosting or a partner host, key management falls to the chosen infrastructure.

Sage. Sage publishes its security practices (Sage, security practices). At the time of writing, I found no public documentation describing a customer-managed key for Sage X3 or Sage Intacct. That does not prove the option does not exist: ask for a written answer per product and per hosting provider (encryption also depends on the underlying cloud).

The message to retain: “BYOK available” is never a sufficient answer. You need the exact product, edition, region and scope.

Compliance: GDPR, NIS2, DORA, Sovereignty

None of these texts mandates BYOK. All of them require that encryption be chosen, justified and controlled.

  • GDPR. Article 32 lists encryption among the technical measures to consider according to risk (EUR-Lex, Regulation (EU) 2016/679). The DPO must be able to justify the level chosen for sensitive modules, notably HR and payroll: see our article on GDPR risks in the HR/payroll module and the ERP GDPR guide.
  • NIS2. Article 21 of the directive requires policies and procedures on the use of cryptography and, where appropriate, encryption (EUR-Lex, Directive (EU) 2022/2555). The auditor will want a written policy and evidence: see the NIS2 evidence checklist for ERP.
  • DORA. Delegated Regulation (EU) 2024/1774 devotes one article to the encryption policy and cryptographic controls and another to key management across the whole lifecycle: generation, renewal, storage, backup, with protection against loss and unauthorised access (Springlex, RTS article 7). For the financial sector, see our DORA and ERP guide.
  • Sovereignty and non-EU access. BYOK limits exposure but does not change the provider’s jurisdiction. For trusted-cloud requirements, see our article on the sovereign ERP cloud in Europe, and for data portability and access obligations, the European Data Act (French).

Operational Risks: The Key Is a Point of Failure

This is where BYOK and HYOK are won or lost. The figures and durations below come from official documentation.

Lost key = lost data. Microsoft warns that when an environment is locked by key revocation, nobody can access it, Microsoft support included, the environment becomes disabled and data loss may occur (Microsoft Learn). Oracle states that a disabled key forces all users out of the application, and that deletion makes the data unrecoverable (Oracle).

Silent expiry. At Microsoft, a key with an expiry date that expires brings down every environment it protects. An expiry alert is not a luxury: it is a business continuity control.

Rotation. Microsoft describes rotation through a new key version, without interruption, but specifies that the previous version must not be disabled or deleted for at least 28 days, because it is used to restore databases. Oracle recommends not rotating keys more than once every 15 minutes, and not adding or changing a customer key more than twice in 24 hours. These constraints must go into your procedures, not be discovered in the middle of an incident.

Backups and copies. At Microsoft, restore is limited to the same environment or to an environment encrypted with the same customer key, and copying to an environment encrypted with a different key is restricted. When you remove the customer key, you must keep the old key and its permissions, with the documentation indicating up to 30 days for restoration. Your recovery plans must account for these dependencies.

Performance and planned downtime. Enabling a customer key is not trivial. Microsoft indicates that the environment is disabled during the operation, with a duration tied to database size, and recommends a trial on a copy; full encryption can take up to four days. At Oracle, a key enabled on an existing environment is applied during the next planned maintenance cycle. With HYOK, latency to your key manager becomes a performance parameter to test.

Separation of duties. Microsoft describes the “malicious administrator” scenario: a vault administrator who creates the key, attaches the environments, then revokes access locks the entire tenant. The documented countermeasure is to separate duties: the vault administrator has no access to the Power Platform admin centre, and vice versa.

Logging. Demand key usage logs (encryption and decryption calls, policy changes, rotations) exportable to your SIEM. Without them, “you control the key” remains unverifiable in an audit.

A limit not to forget: BYOK does not protect against a compromised administrator account. Once the ERP is running, the application decrypts data for authorised users. A stolen ERP administrator account reads data in clear text, with or without a customer key. Encryption protects the storage medium and limits vendor access; access governance, MFA and segregation of duties protect against the compromised account.

Ten Questions to Ask the Vendor Before Signing

Each question ends with the contract clause to obtain.

  1. What is the exact scope of default encryption (database, files, backups, logs, test environments)? Clause: a security appendix listing the encrypted layers.
  2. Does the BYOK or external key offer cover our product, edition and region? Clause: list of covered services, with a commitment to maintain them for the term of the contract.
  3. What data remains encrypted with a vendor key even with a customer key? Clause: list of exclusions, such as metadata or settings.
  4. Who can technically decrypt, and under what conditions (support, engineers, subcontractors)? Clause: commitment to logged, authorisation-gated access.
  5. What happens when the key is stopped, expires or is deleted? Clause: documented behaviour, recovery times, responsibilities.
  6. What is the rotation procedure, and what technical restrictions apply? Clause: rotation without interruption, supported frequency.
  7. How are backups encrypted and restored, and what happens to a backup after a key change? Clause: commitment to restore with the old key, retention period.
  8. Which key usage logs are provided, in what form and for how long? Clause: export to our SIEM, minimum retention.
  9. What is the availability impact at activation and when our KMS is unavailable? Clause: agreed maintenance window, exclusion of SLA penalties linked to our own vault, and clarity on what each party is responsible for.
  10. What reversibility is there, and how do we exit with our data? Clause: return of decrypted data and verifiable destruction of keys and copies at the end of the contract (see also the Data Act, in French).

On top of these questions come the classic shared-responsibility clauses: the vendor answers for the platform, you answer for your keys, your access and your vaults. The DPO must validate the record of processing activities and the risk analysis that justify the chosen key model.

When BYOK Is Overkill: A Decision Tree

The right model depends on data sensitivity and on your ability to operate a key. Follow this logic, in order.

  1. Are you subject to an explicit requirement (DORA, a regulated sector, a customer contract requirement, trusted-cloud doctrine) to control keys? If yes, BYOK at a minimum, HYOK if the requirement extends to technical impossibility of vendor access.
  2. Does your ERP host highly sensitive data (large-scale payroll, health data, R&D intellectual property)? If yes, BYOK is defensible, after a restore test.
  3. Do you have a team able to operate a key vault (on-call, rotation, alerts, separation of roles)? If not, stay on vendor-managed keys: a poorly operated key is a more likely outage risk than the risk it claims to cover.
  4. Is your company free of regulatory requirements and of exceptionally sensitive data? Vendor-managed keys, with documented encryption, strict MFA, solid access governance and tested backups, offer the best protection-to-risk ratio.

In most mid-sized companies, the most cost-effective security gain does not come from BYOK. It comes from controlling privileged accounts, logging and restore testing. BYOK is a tool for control and proof, not a substitute for access hygiene.

Further Reading

To turn your encryption policy into presentable evidence, read our NIS2 evidence checklist for ERP. To frame the contractual side and reversibility, see our analysis of the European Data Act and cloud ERP (French), and for general context, our ERP cybersecurity guide.