Organisations should standardise secure email as the default, then define a controlled fallback for the limited cases where a customer cannot support it. That fallback should still protect sensitive communications through approved secure channels, clear exception handling, and documented approval. The goal is to prevent convenience from becoming a permanent exception that weakens message confidentiality.
Why a secure email default beats ad hoc exceptions
When secure email is required for some customers but not others, the control decision should start from the message sensitivity, not from the customer’s preferred convenience. A default secure standard reduces the chance that staff make one-off judgment calls about whether a message is “important enough” to protect, while still allowing a controlled exception path for customers who genuinely cannot receive secure email.
That structure matters because email is often treated as a routine channel even when the content is not routine. If the organisation allows the exception to become the normal operating mode, confidentiality and auditability drift over time. Security expectations should therefore be defined centrally, then applied consistently with documented fallback handling where justified.
How to design the fallback without weakening confidentiality
A fallback is safest when it is narrower than the default, not broader. The organisation should define which customers qualify for it, what kinds of messages may use it, which approved secure channels are acceptable, and who can approve the exception. That keeps the control focused on preserving confidentiality rather than simply finding any easier delivery path.
The fallback also needs a lifecycle. Exceptions should have an owner, a review date, and a removal trigger if the customer’s capability changes. If the fallback is not time-bound and reviewed, it becomes a shadow standard. That is where operational convenience starts to erode message protection, especially for recurring communications that eventually feel “normal” enough to skip review.
What good customer-specific handling looks like in practice
Good practice is to separate delivery flexibility from security downgrade. For customers who cannot support the standard secure method, use an approved alternative that still protects sensitive content, then record why the exception exists and what compensating channel was used. Where the content is especially sensitive, the safer answer may be to change the communication method rather than send the same message through a weaker path.
That approach works best when customer support teams, compliance owners, and the service owner all understand the rule set. Without clear ownership, staff improvise, and improvisation is how exceptions proliferate. A simple policy statement is not enough if the process does not tell people how to decide, how to approve, and how to close the exception later.
Risk and Threat Considerations
Mixed secure-email requirements create a predictable confidentiality gap if exceptions are informal or too easy to obtain. The main risk is not that one fallback exists, but that repeated use of the fallback slowly turns it into the default for sensitive communications, especially where operational pressure favours speed over protection.
Failure mechanism: Staff begin to treat exception handling as a convenience path, sensitive messages travel through weaker or less controlled channels, and the organisation loses consistent protection, visibility, and evidence of approved handling.
Impact: Confidential customer information can be exposed, misrouted, or sent without the level of assurance the organisation intended, which increases privacy, contractual, and reputational risk.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-4 — Information Flow Enforcement | Controls approved message routing and channel restrictions for sensitive communications. |
| Recommendation — Enforce approved channels for sensitive email and constrain exception paths to documented handling. | ||
| ISO/IEC 27001:2022 | A.5.14 — Information transfer | Addresses secure transfer of information between parties and controlled delivery methods. |
| Recommendation — Define secure transfer rules and approved fallback methods for customer communications. | ||
| CIS Controls v8 | CIS-3 — Data Protection | Supports protecting sensitive data in transit when email delivery methods vary. |
| Recommendation — Protect sensitive messages with approved secure transmission and exception controls. | ||
Practitioner Guidance
What to prioritise: Define the secure email standard first, then document the narrow fallback criteria and approval owner. If the fallback is not limited to clearly identified customer cases, it will expand into an informal normal path.
What to verify: Check that the approved alternative still protects sensitive content, that exceptions have an expiry or review point, and that staff can show why a given customer was not able to use the standard method. If you cannot evidence those three points, the exception is too loose.
Decision rule: If the communication contains sensitive information and the customer can support secure email, use the standard method. If they cannot, route through the approved fallback and document the exception rather than inventing a new one-off process.
Practitioner takeaway: The control objective is consistency with bounded flexibility, not allowing every customer limitation to redefine what “secure enough” means.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on September 28, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
