TPM-24.1: Third-Party Transition Planning
Mechanisms exist to define and document third-party transition activities, responsibilities, dependencies, milestones and timelines necessary to support an orderly cessation and transition of third-party services.
Control Question: Does the organization define and document third-party transition activities, responsibilities, dependencies, milestones and timelines necessary to support an orderly cessation and transition of third-party services?
Capability Maturity Model
Level 0 — Not Performed
Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.
Level 1 — Performed Informally
Third-Party Management (TPM) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with TPM domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Third-party management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
Level 2 — Planned & Tracked
Third-Party Management (TPM) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with TPM domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with TPM domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with TPM domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Third-party management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Asset management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
Level 3 — Well Defined
Third-Party Management (TPM) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with TPM domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with TPM domain capabilities are well-documented and kept current by process owners. ▪ A procurement team, or similar function, is appropriately staffed and supported to implement and maintain TPM domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of third-party management operations (e.g., TPRM risk management solution and vendor management solution). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with TPM domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls).
Level 4 — Quantitatively Controlled
Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.
Level 5 — Continuously Improving
Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.
Assessment Objectives
- TPM-24.1_A01 a documented transition plan exists for applicable third-party relationships that defines the activities necessary to support an orderly cessation and transition of third-party services.
- TPM-24.1_A02 the transition plan assigns responsibility for each transition activity to the organization, the outgoing third-party and/or the replacement service provider.
- TPM-24.1_A03 the transition plan identifies the dependencies (e.g., data, interfaces, licenses, personnel and other third-parties) that affect the cessation and transition of third-party services.
- TPM-24.1_A04 the transition plan defines milestones and timelines for the cessation and transition of third-party services, including any contractual notice and transition assistance periods.
- TPM-24.1_A05 progress against transition plan milestones is tracked and deviations are escalated to accountable personnel.
Evidence Requirements
- E-TPM-08 Third-Party Exit / Transition Plan
-
Documented evidence of exit strategies and transition plans for third-party relationships, including TAASD portability, disposition, knowledge transfer and exit contingencies.
Third-Party Management
Technology Recommendations
Micro/Small
- Simple transition checklist for critical vendors
Small
- Documented transition plan for critical third parties
- Contractual transition assistance period
Medium
- Transition plan template with activities, RACI and milestones
- Transition plans maintained in the TPRM records
Large
- Formal transition planning within the C-SCRM program
- TPRM platform tracking of transition plans
- Project management support for vendor transitions
Enterprise
- Enterprise vendor transition playbooks
- TPRM platform with transition plan lifecycle
- Program management office support for critical transitions