1-4 | Purpose: a principles-based approach so banks can withstand, adapt to and recover from operational hazards, building on the revised PSMOR | 0 |
11-13 | Definitions: operational resilience, tolerance for disruption, critical operations, supporting assets and the respective functions in the three lines of defence | 0 |
14-15 | Seven principle categories, applied on a consolidated basis under the Basel Framework and read together with the PSMOR and earlier guidance | 0 |
5-10 | Context: technology and third-party reliance, pandemic lessons, and the principles as an integration of existing risk management, continuity and third-party practices applied propo | 0 |
P1-16 | Board approval of the operational resilience approach and the tolerance for disruption, tested against severe but plausible scenarios, with policies for capability shortfalls | 0 |
P1-17 | Senior management implements the approach under board oversight and allocates financial, technical and other resources to it | 0 |
P1-18 | Timely senior management reporting to the board on the resilience of business units, especially where deficiencies could affect critical operations | 0 |
P1-19 | Board communication of the approach and its objectives to personnel, third parties and intragroup entities | 0 |
P2-20 | Operational risk function working with other functions to address threats to critical operations and coordinate continuity, third-party, recovery and resolution planning | 0 |
P2-21 | Controls and procedures to identify and assess threats in a timely way, with effectiveness reassessed regularly, on change to critical operations and after incidents | 0 |
P2-22 | Change management used to assess effects on critical operations and their interconnections and interdependencies | 0 |
P3-23-24 | Forward-looking business continuity plans that identify critical operations and dependencies and incorporate impact analysis, recovery strategies, testing, training, communication | 0 |
P3-25 | Regular exercises covering critical operations and their interconnections, including third parties and intragroup entities, that build staff awareness and response capability | 0 |
P3-26 | Plans give detailed guidance for disaster recovery, set roles and succession of authority for key personnel, and define decision-making and invocation triggers | 0 |
P3-27 | Consistency between the continuity plans for critical operations and critical third-party services in recovery and resolution plans and the operational resilience approach | 0 |
P4-28 | Map the people, technology, processes, information, facilities and their interconnections and interdependencies needed to deliver each critical operation, including third-party and | 0 |
P4-29-30 | Harmonise mapping with recovery and resolution plans and map at a granularity sufficient to find vulnerabilities and support continuity testing | 0 |
P5-31 | Risk assessment and due diligence before entering third-party or intragroup arrangements, including verification of at least equivalent operational resilience | 0 |
P5-32 | Continuity, contingency and exit strategies for third-party failure, with scenarios that assess substitutability and alternatives such as bringing the service in-house | 0 |
P6-33 | Inventory of internal and third-party incident response and recovery resources | 0 |
P6-34 | Incident management scope covers the full life cycle: severity classification, response and recovery procedures linked to continuity plans, and internal and external communication | 0 |
P6-35 | Periodic review, testing and updating of response and recovery procedures, with root causes identified and addressed to prevent recurrence | 0 |
P6-36 | Lessons from own and others' incidents reflected in the programme, which covers all incidents including those arising from third parties and intragroup entities | 0 |
P7-37 | Documented ICT and cyber security policy covering governance, risk ownership, security measures, periodic evaluation of controls, incident response, continuity and disaster recover | 0 |
P7-38 | Identify critical information assets and infrastructure, prioritise cyber efforts by risk, keep critical information intact through secure storage and immutable offline backup, and | 0 |