- Purpose / Background: This Code of Practice (CoP) provides regulatory guidance for Authorized Institutions (AIs) designated by the HKMA as "Critical Infrastructure Operators" under the *Protection of Critical Infrastructures (Computer Systems) Ordinance*. It defines baseline security requirements for protecting Critical Computer Systems (CCSs) to ensure the stability and resilience of the banking and financial sector.
- One-line conclusion: Designated AIs must align their cybersecurity frameworks with this CoP, specifically establishing formal management plans, performing mandated risk assessments, and conducting independent security audits for all designated CCSs.
- Key Changes:
- Formalizes the designation process for CCSs based on material impact, data sensitivity, and interdependencies.
- Mandates the establishment of a dedicated "Computer-System Security Management Unit."
- Requires Board-level (or senior management) endorsement of security management plans, reviewed at least every two years.
- Standardizes requirements for incident monitoring, log retention (min. 6 months), and secure tertiary data backups.
- Enforces rigorous vulnerability assessments and penetration testing conducted by qualified professionals.
- Requires systematic management of supply chain and cloud-based risks.
- Key Dates / Deadlines: Effective date is 2 June 2026. Ongoing compliance obligations (e.g., biennial plan reviews, annual privilege reviews) commence immediately upon designation.
- Applicability / Impact scope: All Authorized Institutions (AIs) designated by the Monetary Authority as Critical Infrastructure Operators.
- Recommended management actions:
- Conduct a formal gap analysis between current IT security policies and the requirements in Sections 5 and 6.
- Formally designate a "Computer-System Security Management Unit" with appropriately qualified personnel.
- Establish a process for "material change" notifications for CCSs to the HKMA.
- Implement/update the Computer-System Security Management Plan with Board-level approval.
- Initiate a schedule for regular vulnerability assessments and penetration tests.
- Enhance supply chain and cloud risk management frameworks in line with HKMA circulars and C-RAF maturity standards.
- Document overview: This CoP operationalizes the *Protection of Critical Infrastructures (Computer Systems) Ordinance*. It sets baseline security expectations for CCSs, focusing on availability, confidentiality, and integrity, while noting that these requirements do not override, but complement, existing HKMA Supervisory Policy Manual (SPM) guidance.
- Main requirements:
- Governance: Maintenance of an office in HK and a dedicated security management unit.
- Security Management Plan: Must cover all aspects of Schedule 3 of the Ordinance, including asset management, access control, and physical security.
- Operational Controls:
- Access: Strong password management and privileged access controls.
- Technical: Required encryption (at-rest/in-transit/in-use) and system hardening.
- Resilience: Secure tertiary data backup (STDB) and off-site storage.
- Monitoring: 6-month log retention for security incidents and active threat intelligence monitoring.
- Risk & Audit: Annual and event-based risk assessments (vulnerability scans/penetration tests) and independent security audits.
- Key changes: Increased emphasis on formalizing risk-based "material change" notifications and moving beyond general cybersecurity standards toward specific, auditable compliance targets aligned with the C-RAF (Cyber Resilience Assessment Framework) maturity matrix.
- Important dates & transition: Document is effective from 2 June 2026. While no specific "grace period" for existing systems is listed, reporting and plan submissions must align with the Ordinance's statutory timelines once a designation is received.
- Impact and risks: Operational impact includes increased compliance reporting, requirement for independent audit verification, and necessary infrastructure upgrades to meet specific backup and encryption standards. Non-compliance may lead to HKMA written directions; failure to comply with these constitutes an offence.
- Compliance action checklist:
- [ ] Map all current CCSs against the 3.1.3 designation criteria.
- [ ] Appoint a supervisor for the Computer-System Security Management Unit.
- [ ] Implement/Review log management to ensure 6-month retention.
- [ ] Update Change Management process to flag "material changes" for HKMA notification.
- [ ] Schedule penetration tests and vulnerability assessments for all CCS-related hosts/applications.
- [ ] Secure Board/Executive approval for the comprehensive security management plan.
- Appendices/attachments summary:
- The document does not contain traditional appendices; however, the body references the C-RAF Maturity Assessment Matrix and SPM TM-G-1/G-2 extensively as the compliance standard. These references act as the technical "benchmarks" for the requirements stipulated in Section 6.