1.1 | Align IT strategy with business strategy, with the Governing Body accountable and senior management resourced to deliver | 0 |
1.2 | Ensure the Governing Body, senior management, staff and third parties are competent to manage IT risk | 0 |
1.3 | Assign clear accountability for IT risk, name an owner for every risk source and make consequences realistic | 0 |
10.1 | Maintain cyber threat awareness through intelligence, controlled dissemination, oversight of third-party threats and participation in sharing | 0 |
10.2 | Detect and manage cyber events to resolution: log analytics, response procedures integrated with incident management, updated monitoring and oversight of outsourced monitoring | 0 |
10.3 | Validate controls through regular vulnerability assessments and scoped adversarial testing with remediation and retest | 0 |
11.1 | Manage credentials through their lifecycle: approved issuance, secure storage, uniqueness, strong passwords or password-less controls, third-party parity, regular reviews, vetted f | 0 |
11.2 | Authorise on least privilege with segregation of duties, never-alone for privileged activity, no unfettered access for anyone, and regular policy reviews | 0 |
11.3 | Authenticate in proportion to criticality with risk-based MFA, lockout limits, controlled concurrency, vetted external solutions and reviews, and secure OTP, biometric and SSO impl | 0 |
12.1 | Secure online financial services: MFA at login, step-up authentication on distinct channels for high-risk activities, hardened sessions, blocked anonymising protocols, and vetted t | 0 |
12.2 | Detect, report and investigate fraud on online services, notify and support affected customers and replace compromised credentials | 0 |
12.3 | Keep customers informed of online risks, rights and responsibilities, threat techniques and platform changes | 0 |
13.1 | Use recognised, current cryptographic schemes suited to each use case, keep them resistant to new techniques, secure any PKI and assess post-quantum needs | 0 |
13.2 | Manage cryptographic keys securely through their lifecycle: generation in secure modules, protected storage and transport, purpose and expiry controls, revocation and destruction, | 0 |
14.1 | Govern algorithm-driven solutions: an approved framework with materiality classification, competent staff, executive accountability per solution, defined objectives with error dete | 0 |
14.2 | Use algorithm-driven solutions safely: explainable decisions aligned to ethical norms and law, trained human-in-the-loop staff, defence against model attacks, disclosure to affecte | 0 |
15.1 | Understand each decentralised infrastructure solution and its specific IT risks before adopting or participating | 0 |
15.2 | Participate securely in decentralised infrastructure: an approved governance framework, due diligence and ongoing oversight, criminal-use safeguards, monitoring and tracing, regula | 0 |
2.1 | Foster a culture of IT risk awareness from the top, with open incident reporting and monitored awareness | 0 |
2.2 | Run a regular, tailored IT risk awareness training programme for all staff and keep it current | 0 |
2.3 | Operate a risk assessment framework covering all IT risk domains, integrated with operational risk, with governance, a risk appetite, residual risk acceptance and a risk register | 0 |
2.4 | Measure control effectiveness with defined metrics, collect them reliably, review them and redesign failing controls | 0 |
2.5 | Maintain an incident management framework: detection, investigation and escalation, response and recovery, communication, regulatory and law enforcement reporting, and contractual | 0 |
2.6 | Practise problem management: study risk events over time to find and fix systemic causes | 0 |
2.7 | Mitigate insider risk with proportionate background checks and monitoring | 0 |
3.1 | Govern third-party risk within the risk framework: accountability, a management framework and forum, intra-group oversight, KPIs, a register, concentration risk, materiality and ou | 0 |
3.2 | Manage each third-party arrangement through its lifecycle: documented due diligence, enforceable contracts with sub-contracting and data clauses, proportionate monitoring and audit | 0 |
3.3 | Understand and diversify the supply chain behind material third parties and oversee onward data sharing | 0 |
4.1 | Build IT regulatory obligations into the compliance programme and test compliance with them | 0 |
4.2 | Give the audit function the competence and coverage to assess IT risk independently, with a board-approved plan, tracked findings and external audit | 0 |
5.1 | Govern IT projects through a project management framework with competent oversight, a justified business case and a defined plan | 0 |
5.2 | Control system acquisition, development and testing: end-user computing approval, vendor due diligence and security parity, cloud responsibilities, secure development practices, co | 0 |
5.3 | Track system lifespans to avoid unsupported technology, approve any retained legacy through risk acceptance, and decommission systems and data securely with a documented chain of c | 0 |
6.1 | Inventory every technology asset, classify it by criticality and data sensitivity, and define what makes a system critical | 0 |
6.2 | Assign every asset to a responsible party and manage asset credentials with recovery procedures | 0 |
7.1 | Standardise configurations through a maintained library of hardened images or templates reviewed against known threats | 0 |
7.2 | Secure physical assets: enforced configurations, endpoint protection, a data loss prevention strategy, encryption of sensitive devices and only authorised devices and services | 0 |
7.3 | Secure networks and connections: segmentation, documented design, access controls and perimeter defences, wireless, VPN, encrypted transfers, API security and hardened internet-fac | 0 |
7.4 | Secure virtual environments: BYOD and virtual machine controls, device posture checks, remote wipe, data transfer policies and vetted web and mobile services | 0 |
7.5 | Keep environments current and controlled: segregated environments, governed use of production data, change and patch management from verified sources, testing, controlled productio | 0 |
8.1 | Establish data governance structures with a senior executive accountable for each dataset, competent data managers and approved, reviewed deviations | 0 |
8.2 | Manage data across its lifecycle: identification and inventory, minimised collection, disciplined processing, classification-based controls, a storage and backup framework with res | 0 |
8.3 | Design for regulated data from the outset: locate it quickly, enforce retention and other obligations, and report risk events affecting it | 0 |
9.1 | Architect systems, networks and data centres for availability objectives: remove single points of failure and concentration risk, provision capacity, add redundancy and diversity, | 0 |
9.2 | Plan business continuity: identify critical services, set minimum service levels, tolerable disruption, RTOs and RPOs, prioritise systems, and maintain an IT BCP with a steering gr | 0 |
9.3 | Build scenario-based recovery plans aligned to RTOs and RPOs, approve, review and test them regularly with stakeholders and third parties, operate from recovery arrangements, and f | 0 |
i-xiii | Purpose, key IT risks, structure and applicability of the Guidance | 0 |
xiv-xv | Building effective control environments | 0 |