The question to settle first: are you an NCII entity, a supplier to one, or neither?
Malaysia's Cyber Security Act 2024 (Act 854) took effect on 26 August 2024. If your organization runs systems that matter to the country's critical services, or sells to one that does, three questions need answers. Has a regulator designated you, or will it? What will the yearly compliance cycle cost? How fast can you get incident reporting working?
Malaysia Cyber Security Act compliance isn't a voluntary framework you adopt when convenient. It's a statutory regime run by the National Cyber Security Agency (NACSA), with criminal penalties attached. Failing to notify an incident can bring fines in the hundreds of thousands of ringgit and possible imprisonment. The Act also has provisions that can reach company officers, not just the company.
This guide is for CFOs, CISOs and risk managers at Malaysian companies, regional headquarters, and multinationals with infrastructure in Malaysia. It explains how the regime works in general. Malaysian counsel should confirm your scope, and your sector lead if you're designated.
Looking to streamline vendor RFP selection?
Access pre-negotiated tier discounts through our independent institutional network.
How designation works across the 11 NCII sectors
The Act defines national critical information infrastructure (NCII) as computers or computer systems whose disruption would harm national security, defence, foreign relations, the economy, public health, public safety or public order. It names 11 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
- Science, technology and innovation
Working in one of these sectors doesn't automatically put you in scope. Each sector has an NCII sector lead, usually the agency or regulator that already oversees the industry. The sector lead designates the specific organizations that own or operate NCII, and that designation makes you an NCII entity. Two points catch multinationals out. The Act reaches NCII located wholly or partly in Malaysia, wherever the owner is incorporated. And government bodies are bound too.
The practical test: if a sector lead has asked you for information about your systems, assume designation is coming. Budget now, not after the letter arrives.
NCII entity obligations Malaysia places on owners, and how they flow to suppliers
Once designated, an entity has a fixed set of duties. These NCII entity obligations Malaysia imposes come from the Act and the regulations made under it in 2024:
| Obligation | Frequency or deadline | Who is involved |
|---|---|---|
| Provide information about your NCII to the sector lead | On request, and when you acquire or commission new NCII | Internal IT and asset owners |
| Implement the sector code of practice | Continuous | CISO, control owners |
| Cyber security risk assessment | At least once a year; report submitted within the period the regulations set | Internal team or an external assessor |
| Cyber security audit | At least once every two years, or more often if directed | Auditor approved by NACSA's Chief Executive |
| Incident notification | Initial notice within 6 hours of becoming aware; fuller details within 14 days | SOC, incident lead, legal |
| Cyber security exercises | When directed | Security and business continuity teams |
Suppliers usually aren't designated themselves. A cloud host, managed service provider, OT integrator or software vendor isn't an NCII entity unless it owns or operates the NCII. The duties reach suppliers through contracts instead. An NCII entity can't meet a six-hour window if its outsourced SOC takes a day to call, so expect new clauses on notice periods, audit cooperation, evidence retention and flow-down of code-of-practice controls.
If you're a supplier, write down your own six-hour escalation path before procurement asks for it. Offering it up front helps at renewal.
NACSA service provider licensing: what buyers must check
The Act also licenses certain security vendors. Under the 2024 licensing regulations, two services need a NACSA licence: managed security operation centre (SOC) monitoring and penetration testing. The requirement applies to anyone offering these services in Malaysia, not only vendors serving NCII entities. Providing them without a licence is an offence.
That changes procurement. Under NACSA service provider licensing, a global MSSP or a boutique testing firm needs a current Malaysian licence before it can legally deliver those services in the country. A foreign provider without a local presence should take local advice on how it may operate. Before you sign or renew, check four things:
- The licence covers the specific service you're buying. SOC monitoring and penetration testing are separate.
- The licensed entity is the one signing your contract, not a related company.
- The licence won't expire during the term, and the contract obliges the vendor to tell you if it's suspended.
- The people doing the work meet any qualification conditions attached to the licence.
A red flag: a vendor that answers a licence question by citing CREST or ISO 27001. Those are useful quality evidence. They don't replace the licence.
Looking to streamline vendor RFP selection?
Access pre-negotiated tier discounts through our independent institutional network.
Where the Act overlaps the amended PDPA and sector rules
One incident can start several reporting clocks at once. The Personal Data Protection (Amendment) Act 2024 introduced mandatory breach notification, brought into force in 2025. So the Malaysia PDPA breach notification duty runs alongside the Cyber Security Act and any sector rules. Banks, for example, also answer to Bank Negara Malaysia's technology risk requirements.
| Regime | Trigger | Typical deadline | Regulator |
|---|---|---|---|
| Cyber Security Act 2024 | Cyber security incident affecting NCII | 6 hours initial; 14 days follow-up | NACSA, via sector lead |
| PDPA (as amended) | Personal data breach | Commissioner generally within 72 hours under current guidance; affected individuals without undue delay where significant harm is likely | Personal Data Protection Commissioner |
| Sector rules (e.g., financial services) | Defined by the sector regulator | Often hours, set by the regulator | Sector regulator |
The amended PDPA also requires data protection officers for many controllers, puts security duties directly on processors, and raises the maximum fine to RM1 million. Run all of this as one incident playbook with a single triage step that decides in the first hour which clocks have started. Three separate processes is how organizations miss the six-hour deadline while lawyers argue over whether personal data was involved.
Multinationals will recognize the model. It resembles Singapore's Cybersecurity Act, the EU's NIS2 Directive and Australia's SOCI regime. But Malaysia's six-hour window is tighter than many group standards, so a blanket 24- or 72-hour policy won't be enough here.
What compliance costs: typical 2026 budget ranges
These are typical 2026 market ranges in USD. They vary widely by contract, scope and how mature your controls already are. Malaysian firms often price in ringgit below what regional offices of global firms charge. Confirm with vendors before setting a budget.
| Item | Mid-size NCII entity | Large or multi-site NCII entity |
|---|---|---|
| Initial gap assessment against the sector code | $15,000–$50,000 | $50,000–$150,000 |
| Annual cyber security risk assessment | $15,000–$60,000 | $60,000–$200,000 |
| Cyber security audit (every two years, approved auditor) | $25,000–$80,000 | $80,000–$250,000 |
| Licensed 24/7 SOC monitoring | $4,000–$15,000 per month | $15,000–$60,000 per month |
| Licensed penetration testing (per year) | $10,000–$40,000 | $40,000–$150,000 |
| Remediation (tooling, segmentation, OT controls) | $50,000–$300,000 one-off | $300,000–$2M+ one-off |
| Internal headcount (compliance lead, incident coordinator) | 1–2 FTE | 3–6 FTE |
Remediation is the biggest cost driver and the line most often missing from budgets. Operational technology in energy, water and transport usually costs the most to fix, because segmentation work has to fit around maintenance windows. Over a first two-year cycle, the audit fee is small next to the cost of closing what the audit finds.
A worked 12-month timeline after designation
Hypothetical example: say a 1,200-person logistics operator in the transportation sector is designated in January. It already holds ISO 27001 certification and uses an outsourced SOC. A realistic plan:
- Months 1–2: Inventory in-scope systems, collect what the sector lead has asked for, and name an owner for the Act. Check that the SOC and testing vendors hold NACSA licences.
- Months 2–3: Run a gap assessment against the sector code of practice. Rewrite the incident playbook around the six-hour notice and test it with a tabletop exercise.
- Months 3–9: Remediate in order of risk. Add notification and audit-cooperation clauses to supplier contracts as they come up for renewal.
- Months 9–11: Complete the first annual risk assessment and submit the report.
- Months 12–24: Book an approved auditor early, since capacity is likely to be tight. Finish the first audit well before the two-year mark.
A company with existing ISO 27001 or NIST CSF documentation can reuse a good share of it, particularly asset inventories, risk registers and policies. Starting from scratch, a full cycle is more likely to take 18 months than 12.
Choosing the cyber security audit Malaysia regulators will accept
A cyber security audit Malaysia requires isn't a certification audit. The auditor must be approved by NACSA's Chief Executive, and the audit tests compliance with the Act and your sector code. ISO conformance alone doesn't count. When comparing firms, look at:
- Independence: don't use the firm that designed your controls or runs your SOC.
- Sector experience: OT-heavy sectors need auditors who understand industrial control systems, not only IT.
- Reporting format: ask for a sample report structured around your sector code's controls.
- Combined scoping: where possible, schedule the risk assessment and audit so evidence collection overlaps. That saves internal effort.
Tell your cyber insurer as well. Underwriters ask about regulatory status, and a clean audit plus a tested six-hour reporting process can help at renewal. A known compliance gap may draw questions or exclusions. A licensed broker can advise on how your policy treats regulatory fines, which depends on whether local law allows them to be insured.
Red flags and the decision rule for this quarter
These signs mean your exposure is higher than you think:
- Nobody in the organization can name your sector lead.
- Your SOC contract allows 24 hours or more before it must notify you.
- Your penetration testing or SOC vendor can't show a NACSA licence for the specific service.
- Your PDPA and cyber incident processes have different owners and different triage steps.
- Your remediation budget assumes the audit will find nothing.
Decision rule: if you operate in one of the 11 sectors and your systems support a service the public relies on, act as though you're designated. This quarter, fund a gap assessment and an incident tabletop exercise built around the six-hour notice. If you're a supplier, put your licence status and escalation commitments in writing before your client's procurement team asks. Either way, have Malaysian counsel confirm your scope before you commit the full budget.