Hong Kong's Critical Infrastructure Cyber Law: Who's Designated, Costs and Deadlines
Hong Kong's critical infrastructure cyber ordinance took effect on 1 January 2026. Here's who gets designated, what the 12-hour reporting clock demands, realistic first-year budgets, and how the law changes supplier contracts and cyber cover.
Who can be designated under Hong Kong's critical infrastructure cybersecurity law
If your organization runs infrastructure in Hong Kong, or supplies technology to someone who does, the first question is whether you'll be designated. Hong Kong's critical infrastructure cybersecurity law, formally the Protection of Critical Infrastructures (Computer Systems) Ordinance (Cap. 653), passed in March 2025 and took effect on 1 January 2026. It doesn't apply to every company with a Hong Kong office. It applies to organizations the regulator names as critical infrastructure operators (CIOs), and only to the computer systems it names as critical computer systems (CCSs).
The ordinance sets out two categories of critical infrastructure:
- Category 1: infrastructure that delivers essential services in eight sectors: energy, information technology, banking and financial services, air transport, land transport, maritime transport, healthcare services, and telecommunications and broadcasting.
- Category 2: other infrastructure whose disruption could undermine important societal or economic activities.
Designation is case by case. The regulator looks at the service the infrastructure provides, how heavily that service depends on computer systems, how much sensitive data those systems hold, and how far the organization actually controls the infrastructure. Government policy statements describe the regime as aimed at large operators, not small businesses or the public.
Enforcement is split. The Commissioner of Critical Infrastructure (Computer-system Security), supported by the Security Bureau, covers most sectors. The Hong Kong Monetary Authority supervises designated banking operators, and the Communications Authority supervises telecom and broadcasting operators. Two details catch multinationals off guard. First, the operator stays responsible for a CCS even when a third party runs it. Second, the regulator's information powers can reach material relating to a designated system that sits outside Hong Kong. A regional data center in Singapore or a SOC in India doesn't automatically put a system out of reach.
Hong Kong CI operator obligations in three layers
Obligations fall into three groups. Most of the cost and effort sits in the second.
| Obligation group | What it requires | Recurrence |
|---|---|---|
| Organizational | Keep a Hong Kong address and office; report changes in ownership or operatorship; set up a computer-system security management unit led by a supervisor with appropriate professional knowledge | Set up after designation, then maintained continuously |
| Preventive | Report material changes to CCSs; submit and implement a security management plan; carry out security risk assessments; commission an independent critical computer system audit; join drills the regulator organizes; submit and maintain an emergency response plan | Risk assessment at least annually; audit and drills at least every two years |
| Incident reporting and response | Notify security incidents within set windows, file a written report, and cooperate with investigations | Every reportable incident |
Year-one deadlines run from the date of your designation notice. Plans and organizational set-up fall due within weeks to a few months, and the Code of Practice says what each submission must contain. Read your notice and the current Code side by side rather than relying on any summary, this one included.
The critical computer system audit is the item most often underestimated. It must be independent, so your internal audit team usually won't qualify for systems it already reviews. The auditor also needs OT or sector-specific expertise and familiarity with the Code. For niche environments such as port systems, rail signaling or hospital clinical systems, the qualified pool in Hong Kong is likely small. Book early.
Hong Kong incident reporting requirements compared with other regimes
The deadlines are short. A serious incident, meaning one that has disrupted or is likely to disrupt the essential service, must be reported within 12 hours of the operator becoming aware of it. Other reportable incidents have 48 hours. A written report follows within 14 days. The clock runs all year, weekends and public holidays included.
For groups operating in several countries, the difficulty is that each regime counts time differently and sets its own threshold for what's reportable:
| Jurisdiction | Initial notice for most serious incidents | Other incidents / follow-up |
|---|---|---|
| Hong Kong (Cap. 653) | 12 hours | 48 hours; written report within 14 days |
| Australia (SOCI Act) | 12 hours for significant impact | 72 hours for relevant impact |
| EU (NIS2, national transpositions) | 24-hour early warning | 72-hour notification; final report within one month |
| Singapore (Cybersecurity Act, CII) | A few hours; the statutory window is very short | Supplementary details to follow |
Treat this table as orientation, not legal advice. Thresholds and clock-start rules differ, and some regimes are still being amended. The design rule that works: run one global triage process that classifies an incident against every regime that applies to you within the first two to three hours, then work backward from the shortest deadline. If your incident response retainer can't get a responder engaged inside that window, a 12-hour filing will have little real content in it.
Penalty exposure and investigation powers
Maximum fines for offences under the ordinance run from roughly HK$500,000 to HK$5 million (about US$64,000 to US$640,000), with additional daily fines for some continuing offences. Confirm the figure for each offence in the current text. The penalties are directed at the organization rather than individual employees, a deliberate contrast with regimes that attach personal liability to directors.
Against a large operator's revenue, those maximums are modest. The bigger exposures usually come from elsewhere:
- Investigation disruption. The regulator can require information, documents and answers. In defined circumstances, and generally with a magistrate's warrant, it can enter premises and connect equipment to a CCS or install software on it. That's an unwelcome prospect in the middle of a live incident.
- Directions. Written instructions to fix deficiencies can force unplanned capital spending on short notice.
- Sector regulator overlap. Banks, telecoms and healthcare providers also answer to existing sector regulators, and one incident can trigger separate reviews.
- Contract and reputational fallout. A conviction or public finding gives counterparties grounds to renegotiate.
If you think a designation is wrong, the ordinance provides a route to object or appeal within a stated window. Argue the designation criteria, such as how far the service really depends on the system, rather than the cost of compliance.
Indicative first-year compliance budgets
Cost depends on three things: how many CCSs are designated, how much of the environment is operational technology, and how mature you were before designation. An operator already aligned with ISO/IEC 27001 and running a 24x7 SOC is filling gaps. One without those is building a program from scratch.
The ranges below are typical 2026 market ranges in USD for Hong Kong-based delivery. They vary by contract and scope, and local and offshore pricing differ, so confirm with vendors.
| Cost item | Mid-size operator, 1-3 CCSs, existing ISMS | Large operator, many CCSs, significant OT |
|---|---|---|
| Gap assessment against the Code of Practice | $25,000-$70,000 | $100,000-$300,000 |
| Security management unit (supervisor plus incremental staff, annual) | $150,000-$400,000 | $600,000-$2,000,000 |
| Annual security risk assessment | $30,000-$90,000 | $120,000-$400,000 |
| Independent critical computer system audit (per cycle) | $40,000-$120,000 | $150,000-$500,000 |
| Emergency response plan, playbooks, drill preparation | $20,000-$60,000 | $80,000-$250,000 |
| 24x7 detection and incident response retainer (annual) | $80,000-$250,000 | $300,000-$1,200,000 |
| Legal counsel and regulatory liaison | $30,000-$100,000 | $100,000-$350,000 |
| Indicative year-one total | $375,000-$1,090,000 | $1,450,000-$5,000,000 |
A hypothetical example: say a regional logistics operator has two designated CCSs, a terminal operating system and a gate-automation platform, plus an ISO 27001 certificate that covers only corporate IT. Its biggest new costs are OT-aware risk assessment, an auditor who understands terminal systems, and SOC coverage extended into the OT network. A plausible year-one budget is $600,000-$800,000, falling by roughly a third in year two once plans and tooling exist.
Be wary of vendors selling a generic Cap. 653 package without asking which systems are designated. Be equally wary of any firm that offers to write your security management plan and then audit it. That destroys the independence the audit depends on.
What designation means for suppliers to designated operators
Suppliers aren't designated themselves, but the obligations reach them through contracts. Because the operator stays responsible for outsourced systems, expect procurement and legal teams at designated operators to flow requirements down to managed service providers, cloud and hosting providers, OT integrators and software vendors with remote access.
The clauses you're likely to see:
- Incident notification to the operator within roughly 2-6 hours, well inside the operator's own 12-hour window
- Audit and inspection rights, including access for the operator's independent auditor
- A duty to support the operator's responses to regulator information requests, including for data held outside Hong Kong
- Required controls aligned with the Code of Practice, plus advance notice of changes that could count as a material change to a CCS
- Participation in drills and named contacts available around the clock
Price these obligations before you sign. A supplier that commits to a two-hour notification SLA but has no overnight coverage is taking on liability it can't service. Push for a precise definition of the incident that triggers notice, cap audit frequency, and resist uncapped indemnities for regulatory fines. Those fines are the operator's own statutory liability, and many jurisdictions restrict shifting them by contract anyway.
Adjusting cyber insurance for designated operators and their vendors
Start with whether fines are insurable. Penalties under the ordinance follow conviction of an offence. Insurers generally won't cover criminal fines, and in many jurisdictions public policy forbids it, so don't assume a regulatory fines sublimit will respond. What cyber cover can realistically provide is legal defense costs during a regulator's investigation, incident response and forensics, breach-related liability, and business interruption.
For designated operators, review four things with your broker:
- Panel vendor speed. Check that the insurer's incident response panel can engage within hours, in Hong Kong, with OT capability. If not, negotiate approval for your own pre-retained firm.
- Regulatory investigation cover. Make sure the definition includes requests and investigations by the Commissioner and the designated authorities, not only data-protection regulators.
- Infrastructure and war exclusions. Many policies exclude utility or telecom failures, and many carry state-backed attack wording. For an operator whose own systems are the infrastructure, read these exclusions closely.
- Notification clauses. Align the insurer's notice requirement with your 12-hour regulatory deadline so one triage decision triggers both.
Suppliers should check that their technology errors and omissions and cyber liability limits match the indemnities designated customers ask for, and whether the policy excludes liability assumed by contract beyond what they'd owe at law. Operators should consider contingent business interruption cover for critical vendors.
Decision rule for the next 30 days: if you operate in one of the eight Category 1 sectors at meaningful scale in Hong Kong, assume designation is possible. Commission a gap assessment of your most service-critical systems, test your incident response retainer against the 12-hour clock, and brief your broker before the next renewal. Use Hong Kong-qualified counsel and a licensed broker, because designation notices and policy wordings differ in the details.
Questions buyers ask
When did the Protection of Critical Infrastructures (Computer Systems) Ordinance take effect?
It passed in March 2025 and took effect on 1 January 2026. Obligations apply only after an organization receives a formal designation as a critical infrastructure operator. Most year-one deadlines run from the date of that designation notice, not from commencement.
Will small and mid-size companies in Hong Kong be designated?
Government policy statements say the regime targets large operators of infrastructure critical to essential services or major societal activity. Mid-size firms are more likely to feel it indirectly, as suppliers to designated operators. Size alone doesn't decide designation, though. The regulator looks at the service, its dependence on computer systems, and how much control the organization has over the infrastructure.
What are the Hong Kong incident reporting deadlines for designated operators?
Serious incidents that disrupt or are likely to disrupt the essential service must be reported within 12 hours of becoming aware of them. Other reportable incidents have 48 hours. A written report follows within 14 days. The deadlines run all year, including weekends and public holidays.
How often is a critical computer system audit required?
Designated operators must commission an independent audit of their critical computer systems at least once every two years, and carry out a security risk assessment at least once a year. The auditor must be independent of the work being audited, so firms that built your controls or wrote your plans are poor choices.
Can cyber insurance pay fines under the ordinance?
Generally no. The ordinance's penalties follow criminal conviction, and criminal fines are commonly uninsurable as a matter of public policy. Policies may still cover legal costs during a regulatory investigation, incident response and business interruption. Confirm the wording with a licensed broker and Hong Kong counsel.
Does the ordinance apply if our critical systems are hosted outside Hong Kong?
It can. Operators stay responsible for designated systems regardless of where they are hosted or who runs them, and the regulator's information powers may reach relevant material held abroad. Offshore data centers, cloud regions and SOCs need contracts and processes that let you meet those requests. Take advice from Hong Kong counsel on your specific setup.
Written by the Armorinsurecorp editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.