Cybersecurity Malaysia: Which Cyber Incidents Must Be Reported Under the Law?
A cyber incident can affect more than an organisation’s IT systems. It may expose personal data, disrupt business operations or affect services that people and businesses depend on. For any business managing cybersecurity Malaysia obligations, knowing which incidents must be reported is essential.
In Malaysia, certain cyber incidents must be reported to the relevant authorities. However, whether you have to report depends on the type of incident, the organisation involved, and the laws or regulations that apply.
Understanding these obligations is an important part of cybersecurity management. Knowing when to report, who to notify and what information to prepare helps an organisation respond more effectively when an incident happens.
1. Cybersecurity Incidents Affecting Critical Infrastructure
Malaysia’s Cyber Security Act 2024 (Act 854) sets out cybersecurity obligations for designated National Critical Information Infrastructure (NCII) entities.
NCII covers critical systems and services across sectors such as government, banking and finance, healthcare, transportation, energy, and information and communications. Disruption to these systems could seriously affect national security, economic stability, public health or safety.
Under Section 23 of the Act, an NCII entity must notify the relevant authorities if it becomes aware that a cybersecurity incident has occurred, or may have occurred, in relation to the NCII it owns or operates.
Examples of incidents that may fall within this requirement include:
- Ransomware affecting critical systems.
- Unauthorised access to critical infrastructure.
- Malware compromising essential services.
- Cyberattacks disrupting important operational systems.
- Other incidents affecting the security or operation of designated NCII.
The notification rules require immediate electronic notification. Initial incident information must be submitted within six hours of the entity becoming aware of the incident, followed by supplementary information within 14 days, in line with the applicable regulations.
Important: These specific obligations apply to designated NCII entities. They should not be read as a universal six-hour reporting deadline for every Malaysian business.
2. Personal Data Breaches
A personal data breach happens when personal data is compromised, for example through unauthorised access, disclosure, alteration or loss.
Examples include:
- Customer information exposed through a compromised database.
- Employee records accessed by an unauthorised person.
- Personal information sent to the wrong recipient.
- A cyberattack exposing customer details.
- Personal data lost through a security failure.
Malaysia’s Personal Data Protection Act 2010 (Act 709), as amended, together with the Commissioner’s Personal Data Protection Guidelines on Data Breach Notification, sets out when a data controller must notify the Personal Data Protection Commissioner. Notification is mandatory when a breach causes, or is likely to cause, significant harm.
Under the guideline, the Commissioner must be notified within 72 hours, and affected individuals must be told without unnecessary delay and no later than seven days after the initial notification to the Commissioner, where the significant-harm criteria apply to them.
Businesses should assess the nature of the breach, the data involved and the potential consequences, rather than assuming every security alert automatically triggers a statutory notification.
3. Cyber Incidents Affecting Regulated Financial Institutions
Banks and other regulated financial institutions operate under additional requirements set by Bank Negara Malaysia (BNM) and other relevant regulators.
These organisations may need to report incidents involving technology failures, cyber threats, service disruptions or compromised customer information under the rules that apply to their activities.
BNM’s Risk Management in Technology (RMiT) policy sets out technology and cybersecurity risk management expectations for the financial institutions within its scope. BNM also has separate operational risk reporting requirements.
Examples that may need assessment include:
- Cyberattacks disrupting financial services.
- Unauthorised access to customer information.
- Significant technology or service outages.
- Security incidents affecting digital banking services.
- Incidents that meet applicable regulatory reporting thresholds.
The exact reporting requirements depend on the institution, the nature and severity of the incident, and the relevant regulatory rules. Financial institutions should follow their regulator’s current reporting procedures rather than rely on a general timeline.
4. Cyber Incidents Involving Criminal Activity
Some cyber incidents also involve suspected criminal offences.
Examples include unauthorised system access, online fraud, identity misuse or deliberate theft of confidential information.
Depending on the circumstances, an organisation may need to report suspected criminal activity to the Royal Malaysia Police (PDRM), alongside any notifications required by data protection law or a sector regulator. These obligations can apply at the same time.
Businesses should preserve relevant records and evidence, document the incident, and involve the appropriate legal, compliance and cybersecurity teams.
Not every technical issue is a criminal offence, so the organisation should assess the facts before deciding which authorities to notify.
5. Do All Cyber Incidents Need to Be Reported?
No. A common misunderstanding in cybersecurity Malaysia discussions is that one rule covers everyone. In reality, there is no single reporting deadline or rule that automatically applies to every cyber incident across every Malaysian organisation.
A blocked phishing email, for example, may be handled through internal security procedures if there is no reportable breach or other notification trigger. However, a phishing attack that leads to compromised accounts, exposed personal data or disruption to regulated services may need further assessment.
The organisation should consider:
- The type of incident: Was there unauthorised access, data exposure, service disruption or suspected criminal activity?
- The impact: Were personal data, critical systems, customers or essential services affected?
- The organisation’s status: Is it a designated NCII entity or a regulated organisation?
- The applicable law: Which reporting requirements apply to this incident?
- The deadline: How soon must the relevant authority or affected individuals be notified?
When the reporting obligation is unclear, the organisation should quickly seek advice from its legal or compliance team and the relevant authority. Waiting for a full forensic investigation before assessing notification duties can create unnecessary compliance risk.
6. What Should a Business Do When a Reportable Incident Occurs?
A documented incident response process helps an organisation act quickly and consistently.
The process should cover:
- Identify and assess: Establish what happened, which systems or data may be affected and whether the incident is ongoing.
- Contain the incident: Take appropriate steps to limit further impact while preserving evidence.
- Determine reporting obligations: Identify the applicable laws, regulators and notification deadlines.
- Notify the relevant parties: Submit the required information through the correct reporting channels within the applicable timeframe.
- Document the response: Record the timeline, findings, decisions, notifications and remediation actions.
- Review and improve: Identify the weaknesses that contributed to the incident and decide how to reduce the risk of it happening again.
The organisation should not delay a required notification just because some technical details are still unknown. Where permitted, initial information can be submitted first and supplemented later under the relevant rules. For a closer look at the detection and containment steps, see our guide on how a Security Operation Centre responds to a cyber crisis.
How ACEiT Helps Businesses Strengthen Cybersecurity Readiness
Understanding reporting obligations is only one part of cybersecurity readiness. Businesses also need proper monitoring, incident escalation procedures and technical controls to identify and respond to potential threats.
ACEiT offers cybersecurity capabilities through AceTeam Connect, the group’s managed cybersecurity arm, including Security Operation Centre services, threat intelligence, managed security services and network security solutions.
These capabilities help businesses strengthen their security visibility and response arrangements. Depending on the agreed service scope, security monitoring and incident investigation can help teams spot suspicious activity and gather the information needed for internal escalation. An independent review can also show where your response plan falls short, which is one of the reasons businesses bring in outside security expertise.
However, legal reporting decisions remain the responsibility of the organisation and its authorised representatives. Businesses should make sure their incident response procedures clearly assign responsibility for regulatory notifications.
Want to strengthen your business’s cybersecurity readiness? Talk to ACEiT and explore how its cybersecurity services can support your monitoring, threat detection and incident response requirements.
Frequently Asked Questions (FAQ)
It depends on the applicable law and the organisation involved. Examples include reportable personal data breaches, cybersecurity incidents affecting designated NCII, and incidents covered by financial sector or other regulatory reporting requirements.
No. The mandatory notification duty under Section 23 of the Cyber Security Act 2024 applies to designated NCII entities in relation to their NCII. NACSA also offers a channel for reporting cybersecurity incidents more broadly, but an incident reported voluntarily is not subject to the same statutory obligation.
The applicable regulations require immediate electronic notification, initial information within six hours and supplementary information within 14 days, subject to the prescribed requirements.
A data controller must assess the breach against Malaysia's personal data breach notification requirements. Notifying the Commissioner is mandatory when the breach causes or is likely to cause significant harm, as described in the official guideline. Other notification duties may also apply.
Yes. NACSA provides an incident reporting channel for organisations that are not NCII entities. Organisations can also use appropriate internal and external reporting processes to support investigation and coordination. They should keep voluntary reporting separate from legally required notification.
Conclusion
Not every cyber incident carries the same reporting obligation under Malaysian law. Personal data breaches, incidents affecting designated critical infrastructure and incidents involving regulated financial services may each be subject to different notification requirements.
Businesses should understand which laws apply to them, set up clear incident response procedures, and assess reporting obligations as soon as a potential incident is identified.
Good cybersecurity Malaysia practice is about being prepared before an incident, not reacting after it. With the right monitoring, clear escalation processes and defined responsibilities, organisations can improve their readiness to respond to incidents and meet the reporting requirements that apply to them.