Skip to main content
Intelligent Security Governance — 340+ Frameworks Powered by Ayurak AI
Blog/Compliance Guides

HKMA Cyber Resilience Assessment Framework (C-RAF): A Guide for Hong Kong Banks

How the HKMA's C-RAF works: inherent risk assessment, maturity assessment, iCAST testing, who must apply it, and a practical path to completing it.

HKMA Cyber Resilience Assessment Framework (C-RAF): A Guide for Hong Kong Banks

The Cyber Resilience Assessment Framework (C-RAF) is the HKMA's tool for helping Hong Kong's authorised institutions measure how exposed they are to cyber risk and how mature their defences are in comparison. It is the assessment pillar of the HKMA's Cybersecurity Fortification Initiative (CFI). This guide explains how it is structured, what it expects, and how to work through it.

What it is

C-RAF is a supervisory framework issued by the Hong Kong Monetary Authority, the city's banking regulator and de facto central bank. The HKMA introduced it in 2016 as part of the Cybersecurity Fortification Initiative, which has three parts:

  • C-RAF, a risk-based method for assessing inherent risk and cyber resilience maturity.
  • The Professional Development Programme (PDP), which builds a local pool of qualified cybersecurity professionals.
  • The Cyber Intelligence Sharing Platform (CISP), which lets institutions exchange threat information.

C-RAF is not a statute. It is supervisory expectation set by the regulator, and the HKMA has the means to follow it up through its normal supervision of banks. It sits alongside the HKMA's Supervisory Policy Manual modules on technology risk management (notably TM-G-1) and operational resilience, and is more specific about cyber. The HKMA later issued an updated version, commonly called C-RAF 2.0, to reflect changes in the threat landscape and lessons from the first rounds of assessments. Check the HKMA's current circulars for the exact version and transition arrangements that apply to your institution, as these have changed over time.

Who it applies to

C-RAF is addressed to authorised institutions (AIs) in Hong Kong, meaning licensed banks, restricted licence banks and deposit-taking companies under the Banking Ordinance. It was rolled out to the sector as a whole, not only to the largest banks, though the HKMA has applied different timelines and expectations depending on institution type and size. Because the framework is risk-based, the depth of work scales with the institution's own profile rather than with a fixed headcount or balance-sheet threshold.

Non-bank entities, such as insurers, securities firms and virtual banks' technology suppliers, are not directly in scope of C-RAF as such, though suppliers to banks will see its requirements flow down through contracts and third-party risk reviews. Other Hong Kong regulators (the Securities and Futures Commission, the Insurance Authority) have their own cyber expectations.

Key requirements and control areas

C-RAF has three connected components. Understanding how they feed each other is the key to using the framework properly.

1. Inherent risk assessment

The institution first assesses how much cyber risk its business creates before considering controls. The assessment looks at factors such as the technologies it uses, its delivery channels (for example internet and mobile banking), the products and technology services it offers, its organisational characteristics, and the cyber threats it is tracking. The result is an inherent risk rating of High, Medium or Low.

2. Maturity assessment

The institution then assesses the maturity of its controls against the framework's control principles. These are grouped into domains covering areas such as governance, identification, protection, detection, response and recovery, situational awareness, and third-party risk management. Each control is assessed against maturity levels: Baseline, Intermediate and Advanced. The inherent risk rating sets the target. In broad terms, a higher inherent risk rating calls for a higher maturity level, and gaps between the target and the assessed level need a remediation plan.

3. Intelligence-led Cyber Attack Simulation Testing (iCAST)

iCAST is a threat-intelligence-driven test that simulates realistic attacks against the institution. It goes beyond conventional penetration testing: scenarios are based on relevant threat intelligence, tests aim to reach defined objectives, and they exercise detection and response, not just technical weaknesses. The HKMA expects iCAST for institutions where the assessment points to higher inherent risk or a higher target maturity. Tester qualification and scenario design have specific expectations in the framework documents, so consult them directly.

Themes that recur across the domains

  • Board and senior management oversight of cyber risk, with clear accountability.
  • Threat intelligence feeding both risk assessment and testing, including participation in intelligence sharing.
  • Detection and monitoring capable of spotting attacks, with defined response and recovery procedures.
  • Management of risk from third parties, outsourced services and the supply chain.
  • Evidence that controls operate in practice, not just that policies exist.

Assessment, audit and enforcement

C-RAF is primarily a self-assessment that the institution performs and documents. It is not a certification scheme, and the HKMA does not issue a pass certificate. Institutions typically submit results to the HKMA, and the supervisor reviews them as part of its ongoing oversight. Assessments are generally expected to be reviewed independently, whether by internal audit or by a qualified external party, so that the ratings are credible. The exact review and submission expectations are set out in HKMA circulars and should be confirmed against the current version.

Because C-RAF is supervisory guidance rather than a statute with its own penalty schedule, there is no C-RAF-specific fine. The consequences are supervisory: follow-up questions, requirements to remediate by a set date, closer review, and, in serious cases, the use of the HKMA's wider powers under the Banking Ordinance. Failing to manage cyber risk adequately can also bear on the HKMA's view of an institution's fitness to remain authorised.

A practical path to meeting it

  1. Confirm scope and version. Check the current HKMA circulars and the version of C-RAF that applies to you. Note deadlines for assessment and remediation.
  2. Assign ownership. Name an accountable executive, a working lead, and contributors from IT, security, operations, risk, outsourcing and internal audit.
  3. Build an inventory. List channels, systems, data flows, third parties and cloud services. The inherent risk assessment depends on an accurate view of these.
  4. Complete the inherent risk assessment. Rate each factor using the framework's criteria and record the reasoning. Have it challenged by someone outside the team.
  5. Assess control maturity. Score each control principle against the Baseline, Intermediate and Advanced criteria. Attach evidence for every rating: configurations, logs, test results, policies, meeting records.
  6. Analyse gaps. Compare assessed maturity to the target set by inherent risk. Prioritise gaps by risk, then assign owners, budgets and dates.
  7. Plan and run iCAST where required. Define scope and objectives, select qualified testers, use relevant threat intelligence, and plan how the security operations and response teams will take part.
  8. Report to governance. Present the ratings, gaps, test findings and remediation plan to senior management and the board, and record their decisions.
  9. Remediate and monitor. Track actions to closure, retest, and repeat the assessment on the HKMA's expected cycle and after major changes to your business or technology.

How it maps to other frameworks

C-RAF overlaps with other frameworks but is not equivalent to any of them. Mapping helps you reuse evidence, not claim compliance by implication.

  • NIST Cybersecurity Framework: Its domains cover similar ground to the CSF functions (identify, protect, detect, respond, recover), and the CSF is a common reference for structuring a maturity assessment. C-RAF's inherent-risk-driven targets and iCAST have no direct CSF counterpart.
  • ISO/IEC 27001: An ISMS supplies many of the governance, risk and control records C-RAF assessors look for. ISO 27001 certification does not demonstrate a given C-RAF maturity level.
  • SOC 2: Control testing reports can support evidence on specific controls, particularly for service providers, but SOC 2 does not address banking inherent risk or intelligence-led testing.
  • Threat-led testing regimes elsewhere: iCAST belongs to the same family of intelligence-led red-team approaches as TIBER-EU and CBEST, though each has its own rules and scope.
  • HKMA Supervisory Policy Manual modules: Technology risk, business continuity and operational resilience expectations overlap heavily and should be managed together.

FAQs

Is C-RAF mandatory?

It is not a statute, but it is a regulator-issued expectation for authorised institutions, and the HKMA supervises against it. In practice, banks treat it as required.

Is there a C-RAF certificate?

No. C-RAF is a self-assessment reviewed within the HKMA's supervisory process. No certification body issues a C-RAF attestation.

How does the inherent risk rating affect what I must do?

It determines the target maturity level. A higher inherent risk rating means higher maturity expectations and, typically, a stronger expectation that you run iCAST.

Is iCAST the same as a penetration test?

No. iCAST is driven by threat intelligence and simulates how real adversaries would target your institution. It tests detection and response as well as technical weaknesses, and it has specific expectations for planning and testers.

Does C-RAF 2.0 replace the original version?

The HKMA updated the framework, and institutions should work to the version and transition arrangements the HKMA currently specifies. Confirm these in HKMA circulars rather than relying on secondary sources.

Can outsourced services be excluded from the assessment?

Generally no. Third-party and cloud dependencies form part of both the inherent risk picture and the control assessment, so you remain accountable for risk in outsourced arrangements.

How Aristiun helps

Aristiun is the AI-powered compliance automation and threat modeling platform, powered by Ayurak AI. A C-RAF assessment is largely an evidence exercise, and the platform's capabilities map onto that work. See the broader list of compliance frameworks for how this fits alongside your other obligations.

  • Automated evidence collection: gather evidence from connected systems such as AWS, Azure, GCP and GitHub without manual screenshots or spreadsheets, to support maturity ratings.
  • Cross-framework mapping: map each piece of evidence to the relevant controls across all applicable frameworks, so a single evidence base can address multiple compliance requirements alongside your C-RAF work.
  • Control monitoring and gap analysis: get alerts when controls drift, and use AI-powered validation to spot gaps before supervisors or auditors do.
  • Threat modeling and vendor risk: generate threat models from code, IaC and architecture diagrams to inform inherent risk and iCAST scoping, and map vendor controls to your requirements.

Found this insightful?

Share it with your security team or save it for later.

Get Started

Ready to secure your organization?

See how Aristiun automates compliance and strengthens your security posture across 340+ frameworks.