How should teams handle Termination And Offboarding under ISO/IEC 27036?
Start with the operational decision: define what Termination And Offboarding means in your ISO/IEC 27036 scope, who owns it, and what record proves the decision is current.
For supplier work, keep the supplier relationship type, tier, contract control, fourth-party exposure, monitoring cadence, incident notice route, and exit evidence in one record. This keeps the answer useful in audits, customer reviews, incidents, supplier reviews, and management review.
When the relationship ends, the offboarding record should also show the practical closeout steps: remove or disable access, recover organizational assets and credentials, return or delete organization information as required, transfer any needed knowledge or work products, and sanitize or retire media and systems that are no longer needed.
- Name the accountable owner and reviewer for Termination And Offboarding.
- Record the scope, assumptions, decision, approval date, evidence location, exception status, and next review trigger.
- Before closure, revoke accounts and access paths, collect badges, devices, keys, and other assets, and confirm what data must be returned, deleted, or retained.
- Document contract closeout actions, including handoff of open work, final deliverables, and any residual support or transition obligations.
- Escalate when Termination And Offboarding changes risk acceptance, service commitments, customer promises, regulatory duties, or certification evidence.
Primary ISO listing for supplier relationship security overview and concepts.
Primary ISO listing for supplier and acquirer relationship requirements.
Supports practical offboarding steps such as account removal, termination coordination, and media sanitization.