A regional operator running essential services across Asia Pacific now faces five national cyber laws with different triggers, different regulators and incident clocks that range from two hours to 72 hours. Singapore amended its Cybersecurity Act in 2024, Malaysia's Cyber Security Act 2024 came into operation in August 2024, Hong Kong's Protection of Critical Infrastructures (Computer Systems) Ordinance has applied since 1 January 2026, Japan's Act No. 42 of 2025 took effect on 1 October 2026, and Australia layers its Cyber Security Act 2024 on top of the Security of Critical Infrastructure Act 2018. This page compares the five regimes on scope trigger, regulator, core duties, reporting deadlines, supplier reach and penalties, then works through how a regional programme can meet all of them without running five separate ones. It is for CISOs, compliance leads and OT security teams at regional operators, and for cloud, managed security and technology suppliers who serve them. Status line: checked against CSA Singapore, NACSA, Japan's Cabinet Secretariat, the Australian Cyber and Infrastructure Security Centre and Department of Home Affairs, and law firm summaries of the Hong Kong Ordinance, on 14 November 2026.
Key takeaways
- Designation is the common trigger, except in Australia. Singapore, Malaysia, Hong Kong and Japan regulate systems or operators that the state designates; Australia's SOCI Act applies by asset class across 11 sectors, and its ransomware reporting duty applies to any business above AUD 3 million turnover.
- Reporting clocks differ by a factor of 36. Singapore expects a report within 2 hours, Malaysia particulars within 6 hours, Hong Kong 12 hours for serious incidents, and Australia 12 or 72 hours under SOCI and 72 hours after a ransom payment.
- Audit cadence is converging. Malaysia and Hong Kong both require an annual risk assessment and an audit at least every two years, which makes a shared assurance calendar practical.
- Supplier and cloud systems are in scope. Singapore can designate virtual systems as CII, Hong Kong expects supplier security terms in contracts, Malaysia and Singapore license penetration testing and managed SOC providers.
- Japan is different in kind. Its operator duties are asset notification and intrusion reporting to the competent minister and the Prime Minister, part of a wider active cyber defence framework rather than a controls regime.
Regulations and frameworks at a glance
Jurisdictions follow the order of the page title. Each has a detailed single-law guide on nhimg.org, linked in its section below; this page compares rather than repeats.
| Jurisdiction | Instrument | Regulator | In force | Who is regulated |
|---|---|---|---|---|
| Singapore | Cybersecurity Act 2018, as amended by the Cybersecurity (Amendment) Act 2024 | Cyber Security Agency of Singapore (CSA), Commissioner of Cybersecurity | 2018 Act in force; amendment passed 7 May 2024, key provisions in force 31 October 2025 | Owners of designated critical information infrastructure (CII), systems of temporary cybersecurity concern (STCC), and newer categories: entities of special cybersecurity interest (ESCI) and foundational digital infrastructure (FDI) |
| Malaysia | Cyber Security Act 2024 (Act 854) and four regulations | National Cyber Security Agency (NACSA), Chief Executive; NCII sector leads | Gazetted 26 June 2024, in operation 26 August 2024 | National critical information infrastructure (NCII) entities in 11 sectors; licensed cyber security service providers |
| Hong Kong | Protection of Critical Infrastructures (Computer Systems) Ordinance (Cap. 653) | Office of the Commissioner of Critical Infrastructure (Computer-system Security); Monetary Authority and Communications Authority as designated authorities for their sectors | 1 January 2026 | Designated critical infrastructure operators (CIOs) for their designated critical computer systems (CCSs), in 8 sectors |
| Japan | Act on the Prevention of Damage from Unauthorised Acts Against Critical Computers (Act No. 42 of 2025) | Competent sector ministers and the Prime Minister (Cabinet Secretariat National Cyber Office) | Enacted 16 May 2025, promulgated 23 May 2025, in effect 1 October 2026 except some provisions | Specified social infrastructure operators designated under the Economic Security Promotion Act (257 operators in 15 sectors as of 31 July 2025) |
| Australia | Security of Critical Infrastructure Act 2018 (SOCI) and Cyber Security Act 2024 | Cyber and Infrastructure Security Centre (CISC), Australian Signals Directorate (ASD), Department of Home Affairs | SOCI in force; Cyber Security Act Royal Assent 29 November 2024, ransomware reporting from 30 May 2025 | Responsible entities for critical infrastructure assets in 11 sectors; for ransomware reporting, businesses above AUD 3 million turnover and SOCI Part 2B entities |
Side-by-side comparison of core duties
| Duty | Singapore | Malaysia | Hong Kong | Japan | Australia |
|---|---|---|---|---|---|
| Scope trigger | Designation of CII by the Commissioner; Part 3 covers CII wholly or partly in Singapore | Designation as NCII entity | Designation as CIO and of CCSs | Designation under the Economic Security Promotion Act | Asset class definitions in SOCI; turnover test for ransomware reporting |
| Initial incident report | Within 2 hours of becoming aware | Immediately by electronic means; particulars within 6 hours | 12 hours (serious), 48 hours (other) | Report intrusion events and precursor events to minister and Prime Minister | 12 hours (significant impact), 72 hours (relevant impact); oral reports followed in writing within 84 or 48 hours |
| Follow-up report | Further information as required under the Act and codes of practice | Supplementary information within 14 days | Written report within 14 days | Detail set by ministerial ordinance | Written record after oral report, as above |
| Risk assessment and audit | Periodic audits and risk assessments by CII owners (s.15) | Risk assessment yearly; audit at least every two years | Risk assessment yearly; audit every two years; reports within 3 months | Not a controls regime | Written critical infrastructure risk management program (CIRMP); enhanced obligations for Systems of National Significance |
| Asset or change notification | Provide CII information and notify changes in ownership when required | Provide NCII information to sector lead | Notify material CCS changes and operator changes | Notify the minister of each specified critical computer introduced, including product name | Operational and ownership information to the Register of Critical Infrastructure Assets |
| Exercises | Cybersecurity exercises as directed by the Commissioner | Cyber security exercises as directed by the Chief Executive | Drills on the Commissioner's notice, no more than every two years | Cooperation with government analysis | Cyber security exercises for Systems of National Significance |
| Service provider licensing | Licensing for penetration testing and managed SOC monitoring | Licensing for managed SOC monitoring and penetration testing | Supplier security through CIO contracts | Not a licensing regime | Not a licensing regime; data storage providers must be notified of their status |
Singapore: CII owners, cloud systems and a two-hour clock
Threat model: Singapore treats compromise of essential service systems, including those hosted by suppliers or in the cloud, as a national risk that the CII owner must manage regardless of who runs the infrastructure. For section detail see the Singapore Cybersecurity Act Guide.
- Architecture in words: the Commissioner designates CII; the owner meets codes of practice, audits, risk assessments and incident reporting. Since 31 October 2025 virtual computers and systems can be designated, and STCCs can be designated for a set period (CSA gives election systems and pandemic vaccine distribution as examples).
- Reporting: CII owners must report prescribed incidents, now including incidents suspected of being caused by advanced persistent threats and those disrupting essential services on non-interconnected systems under their control, within 2 hours of becoming aware.
- New categories: CSA describes ESCI (entities holding sensitive information or performing functions of national interest) and FDI (cloud service providers and data centres bound by codes and incident reporting).
- Failure modes: a detection-to-report pipeline that cannot meet 2 hours outside business hours; treating a cloud-hosted CII workload as the provider's problem; and incident criteria that exclude suspected APT activity before attribution is complete.
Malaysia: NCII entities, sector leads and licensed providers
Threat model: Malaysia moves NCII protection from guidance to statute, with sector leads coordinating each of the 11 sectors and NACSA's Chief Executive able to direct exercises and audits. For detail see Malaysia Cyber Security Act 2024; financial institutions also follow Bank Negara Malaysia RMiT.
- Sectors: government; banking and finance; transportation; defence and national security; information, communication and digital; healthcare services; water, sewerage and waste management; energy; agriculture and plantation; trade, industry and economy; and science, technology and innovation.
- Notification: under the Cyber Security (Notification of Cyber Security Incident) Regulations 2024 (P.U.(A) 220), an NCII entity notifies immediately by electronic means, gives particulars within six hours (entity, sector, incident type, severity, discovery time and method), and supplementary information within 14 days (affected NCII, hosts, threat actor, artefacts, tactics and techniques, impact, actions taken) through the National Cyber Coordination and Command Centre System.
- Assurance: a cyber security risk assessment at least yearly and an audit at least every two years, or more often if the Chief Executive directs.
- Licensing: managed SOC monitoring and penetration testing providers need a licence under the Cyber Security (Licensing of Cyber Security Service Provider) Regulations 2024.
- Failure modes: collecting the 14-day dataset only after the incident closes; engaging unlicensed testing or SOC providers; and assuming group-level policies satisfy sector-specific codes of practice.
Hong Kong: designated operators and three categories of duty
Threat model: Hong Kong regulates the computer systems behind core functions of eight sectors: energy, information technology, banking and financial services, air transport, land transport, maritime transport, healthcare services, and telecommunications and broadcasting. The official Ordinance text did not serve readable text when checked, so the Hong Kong points in this section rely on law firm summaries (Mayer Brown and Ashurst Perkins Coie, secondary sources). For detail see the Hong Kong Protection of Critical Infrastructures Ordinance Guide.
- Organisational duties: keep a Hong Kong address and office, report operator changes and set up a computer system security management unit.
- Preventive duties: notify material changes to CCSs, implement a security management plan, conduct an annual risk assessment and a biennial audit, each reported within 3 months.
- Incident duties: take part in drills, maintain an emergency response plan, report serious incidents within 12 hours and other incidents within 48 hours, with a written report within 14 days.
- Reach beyond Hong Kong: in an investigation, a CIO must produce relevant documents in its possession or control whether located in or outside Hong Kong.
- Failure modes: no contractual security terms with suppliers and cloud providers, which law firm guidance on the Code of Practice expects; CCS inventories that miss connected OT systems; and change notification missed during routine upgrades.
Japan: asset notification and intrusion reporting
Threat model: Japan's law is part of a national active cyber defence framework aimed at attacks on critical computers, including those originating overseas. Operator duties are narrow but government-facing. For detail see the Japan Active Cyber Defence Act Guide.
- Who: specified social infrastructure operators under the Economic Security Promotion Act, which the Cabinet Secretariat notes are not the same population as critical infrastructure operators under the Basic Act on Cybersecurity. As of 31 July 2025 there were 257 across 15 sectors, including electricity, gas, oil, water, railways, telecommunications, broadcasting, finance and credit cards.
- Asset notification: when an operator introduces a specified critical computer, it notifies its competent minister of the product name and related details, and the minister informs the Prime Minister.
- Incident reporting: when an operator becomes aware of a compromise of a specified critical computer, or a precursor event, it reports to the competent minister and the Prime Minister.
- Penalties: failure to report or respond after a corrective order can lead to a fine of up to 2 million yen; failure to provide requested materials up to 300,000 yen.
- Failure modes: incomplete product inventories for specified critical computers, and no process to recognise precursor events that are reportable before any damage occurs.
Australia: SOCI asset obligations plus economy-wide ransomware reporting
Threat model: Australia combines an all-hazards critical infrastructure regime with a separate economy-wide duty to report ransom payments. Detail: Australia SOCI Act Guide and Australia Cyber Security Act 2024 Guide.
- SOCI sectors: communications; financial services and markets; data storage or processing; defence industry; higher education and research; energy; food and grocery; healthcare and medical; space technology; transport; and water and sewerage.
- Positive security obligations: register operational and ownership information, report cyber incidents to the ACSC (12 hours for significant impact, 72 hours for relevant impact), and adopt, maintain and comply with a written risk management program, depending on asset class.
- Systems of National Significance: incident response plans, exercises, vulnerability assessments and system information for a near real-time threat picture.
- Ransomware payments: report to ASD within 72 hours of making a ransomware or cyber extortion payment, or becoming aware one was made on your behalf; failing to report can attract a civil penalty of up to 60 penalty units.
- Watch item: CISC says it is changing its compliance posture from 2026-27 in response to the 2026 Independent Review of the SOCI Act.
Worked scenario: a regional payments and cloud operator
A payments company runs a processing platform hosted in a Singapore cloud region, with operations in Kuala Lumpur, Hong Kong, Tokyo and Sydney. Its Singapore platform is designated CII, its Malaysian entity is an NCII entity in banking and finance, its Hong Kong entity is designated a CIO, its Japanese card business is a specified social infrastructure operator, and its Australian entity holds a SOCI asset.
- One incident, five clocks: a suspected APT intrusion on the shared platform starts a 2 hour clock in Singapore, a 6 hour particulars clock in Malaysia, a 12 hour clock in Hong Kong if a core function is disrupted, a report to the minister and Prime Minister in Japan if a specified critical computer is affected, and 12 or 72 hours in Australia depending on impact.
- Design response: a single regional incident desk triages against the shortest clock first, with a pre-mapped table of which entities and systems are designated in each country, and pre-approved report templates holding the union of fields (Malaysia's 14-day dataset is the most detailed).
- Assurance: one annual risk assessment and one two-yearly audit cycle covers Malaysia and Hong Kong, with Singapore and Australian programme evidence drawn from the same control set.
- Suppliers: contracts with the cloud provider and managed SOC include incident notification well inside 2 hours, evidence access, and confirmation that testing and SOC providers hold Singapore and Malaysia licences where required.
Decision guidance and trade-offs
| Approach | Works well when | Trade-off |
|---|---|---|
| Regional baseline set to the strictest rule (2 hour triage, yearly risk assessment, two-yearly audit) | Several entities are designated and systems are shared | Over-engineering for entities with lighter duties |
| Country-by-country programmes | Systems and teams are fully local | Duplicate evidence, inconsistent incident criteria |
| Baseline plus country annexes | Most regional groups | Annexes must be maintained as laws change, especially Singapore's uncommenced provisions and Australia's SOCI review |
Smaller organisations: most are not designated anywhere; the duty most likely to reach them is Australia's ransomware payment reporting, and supplier obligations flowing from designated customers. Larger groups: keep a designation register per country and treat a new designation notice as a programme change with a dated plan.
Where identity fits
Every regime here covers the accounts that run critical systems even where it does not name them: vendor remote access, service accounts in OT and payment platforms, automation and AI agents with privileged access. Incident datasets such as Malaysia's 14-day report ask for threat actor tactics and affected hosts, which depend on identity logs. Keep an inventory of machine identities per designated system and log their use centrally. See the Critical Infrastructure Identity Security Guide.
Compliance steps
- Map designations: list each entity and system designated, or likely to be, under each of the five laws.
- Build a clock matrix: for each system, record which reporting deadlines apply and to which regulator.
- Harmonise incident criteria: include suspected APT activity and precursor events so Singapore and Japan triggers are not missed.
- Align assurance: run a single annual risk assessment and two-yearly audit calendar, with country annexes.
- Update supplier contracts: notification inside the shortest clock, evidence access, licence confirmation for testing and SOC services.
- Test: run a regional tabletop on one shared-platform incident against all clocks, then fix gaps.
- Track change: review quarterly for Singapore ESCI and FDI commencement, Hong Kong designations, Japan ordinances and SOCI reform.
Detection and measurement
- Time to regulator report: minutes from detection to first report, against each applicable clock.
- Designation coverage: percentage of designated systems with a current owner, clock mapping and response plan.
- Assurance on time: risk assessments and audits completed and reported within statutory windows.
- Supplier compliance: percentage of critical suppliers with notification and licence clauses in force.
- Machine identity coverage: percentage of designated systems with an inventory of service accounts and vendor access.
Common failure patterns
- Using one regional clock: setting a 24 or 72 hour target misses Singapore's 2 hours and Malaysia's 6 hours.
- Waiting for attribution: holding a report until an APT is confirmed, when Singapore's trigger covers suspected APT activity.
- Ignoring the turnover test: Australian businesses outside SOCI forgetting ransomware payment reporting applies above AUD 3 million.
- Stale inventories: Japan's product notification and Hong Kong's change notification both fail when asset inventories lag.
- Unlicensed providers: engaging testing or SOC services without checking Singapore and Malaysia licences.
Practitioner checklist
- Designation register per country, reviewed quarterly.
- Clock matrix covering 2, 6, 12, 48 and 72 hour deadlines and follow-up reports.
- Incident criteria include suspected APT and precursor events.
- Report templates holding the union of required fields.
- Annual risk assessment and two-yearly audit calendar with country annexes.
- Supplier contracts with notification, evidence and licence clauses.
- Machine identity inventory for every designated system.
- Ransomware payment reporting route to ASD for Australian entities.
Standards and references
- Cyber Security Agency of Singapore: Provisions in the Cybersecurity (Amendment) Act to come into force on 31 October 2025
- Cyber Security Agency of Singapore: Cybersecurity Act
- NACSA: Act 854 Cyber Security Act 2024
- Cabinet Secretariat National Cyber Office (Japan): Reference material on the Cyber Countermeasures Act
- Cyber and Infrastructure Security Centre: Security of Critical Infrastructure Act 2018
- Cyber and Infrastructure Security Centre: Mandatory Cyber Incident Reporting Guidance
- Department of Home Affairs: Ransomware Payment Reporting Factsheet
- Clyde and Co: Key highlights of the Protection of Critical Infrastructures (Computer Systems) Bill
This guide summarises cyber security laws for critical infrastructure in Singapore, Malaysia, Hong Kong, Japan and Australia as at 14 November 2026 and is not legal advice; confirm obligations with counsel and the primary texts. Related NHI Mgmt Group resources: Critical Infrastructure Regulation Map · Global Cybersecurity Regulatory Map · Cyber Incident Reporting Requirements Map · Ransomware Payment and Reporting Laws Compared