Confidentiality obligations are the duties an employee has to protect sensitive company information during and after employment. They usually come from contracts, policy, or law, and they matter at offboarding because they reinforce that trade secrets, customer data, and internal records must not be taken or disclosed.
What confidentiality obligations cover
Confidentiality obligations are not just a promise not to gossip about company information. They typically cover trade secrets, customer records, internal strategy, technical documents, credentials, and other sensitive material that someone can access through their role. The duty often continues after employment ends, which is why offboarding is a critical moment for reinforcement.
In practice, the obligation is about limiting disclosure, copying, retention, and misuse. It may arise from employment contracts, handbook policies, statutory duties, or sector-specific rules, but the practical effect is the same: protected information should stay protected even when the employment relationship changes.
Why they matter at offboarding
Offboarding is the point where access is removed, but knowledge and copies of information may still remain with the person leaving. That creates a risk that confidential material can be taken into a new role, shared with a competitor, or reused outside its intended context. The legal duty helps make the boundary explicit before access ends.
Confidentiality obligations also support a cleaner separation between what a former employee may remember and what they may lawfully use. Organisations usually rely on them alongside exit interviews, return-of-assets processes, and reminders about ongoing duties to reduce disputes later.
What typically falls within scope
The scope is usually broader than many employees expect. It can include pricing, source code, architecture diagrams, customer data, incident reports, internal metrics, financial records, and non-public operational plans. The exact scope depends on the contract, policy wording, and applicable law, but the common theme is protection of information that would harm the business if disclosed.
Some categories are especially sensitive because they can create downstream legal, competitive, or security consequences. For example, exposing customer data can create privacy and contractual issues, while exposing internal records can reveal weak points in controls or investigations.
How confidentiality duties are enforced
Enforcement usually combines legal terms with operational controls. A contract can state the duty, but the organisation still needs practical measures that reduce unnecessary access, confirm asset return, and remove lingering access to email, files, and collaboration tools. The duty is strongest when it is backed by process, not just wording.
It is also important to distinguish confidentiality from ownership. A former employee may no longer have access or permission to use company materials even if they personally created them. That distinction matters when teams discuss exit rights, file retention, and post-employment publication or disclosure.
Risk and Threat Considerations
Confidentiality obligations exist because sensitive information is often most vulnerable at the end of an employment relationship, when access is being withdrawn but the person still knows where valuable material lives. Misuse can be intentional, but it can also happen through casual retention of files, screenshots, downloads, or reuse of information in a new job.
Failure mechanism: A departing employee retains, forwards, or reuses non-public information after access removal, or discloses it to a third party who should not receive it.
Impact: The organisation can face loss of trade secrets, privacy exposure, litigation, regulatory fallout, competitive harm, and reduced trust in its handling of sensitive data.
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, CIS Controls v8 and NIST CSF 2.0 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-6 — Least Privilege | Limits what departing staff can access before and during offboarding. |
| IA-5 — Authenticator Management | Covers credential handling that protects confidential systems and records during offboarding. | |
| Recommendation — Apply AC-6 to remove unnecessary access before exit and restrict exposure to confidential material. Revoke or reset authenticators tied to confidential systems when employment ends. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | Supports controlled access to confidential information and its removal at offboarding. |
| Recommendation — Use A.5.15 to define and enforce access restrictions for confidential information. | ||
| CIS Controls v8 | CIS-5 — Account Management | Addresses lifecycle control of user accounts that can expose confidential material. |
| Recommendation — Use CIS-5 to disable departing-user accounts and reduce post-employment exposure. | ||
| NIST CSF 2.0 | PR.AA-05 — Access Permissions Management | Directly fits managing and removing permissions to sensitive information. |
| Recommendation — Manage and revoke access permissions for confidential information at offboarding. | ||
Practitioner Guidance
Why practitioners should care: Confidentiality obligations only work when legal language and operational offboarding are aligned. If the exit process removes accounts but does not explicitly restate continuing duties, teams can overestimate how well sensitive information is protected after departure.
Governance implication: Treat confidentiality as a lifecycle control, not just an HR clause. The obligation should be reflected in employment terms, policy acknowledgement, offboarding checklists, and records retention rules so that responsibility is clear before and after termination.
Practitioner takeaway: The strongest protection comes from pairing enforceable wording with practical exit controls that make it easy to comply and hard to walk away with sensitive material.
Related resources from NHI Mgmt Group
- Why do third-party AI models still create compliance obligations?
- How should security teams implement confidentiality controls without slowing work down?
- Why do confidentiality policies fail even when the wording looks complete?
- How can organisations avoid vendor lock-in as compliance obligations grow?
Deepen Your Knowledge
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.
Reviewed and updated by the NHIMG editorial team on November 1, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org