Law / Malaysia

Malaysia

17 of 21 named instruments researched to a stage, across five of the ten areas of law we track: 17 in force. As of .

When each starts17 of 17 carry a date. Earlier is before 2014.
Before 2014: 6 instruments (6 in force) earlier 2014: 0 instruments 2015: 0 instruments ’15 2016: 0 instruments 2017: 0 instruments 2018: 0 instruments 2019: 0 instruments 2020: 0 instruments ’20 2021: 0 instruments 2022: 0 instruments 2023: 0 instruments 2024: 2 instruments (2 in force) 2025: 7 instruments (7 in force) 2026: 2 instruments (2 in force) ’26 today

in forcenot yet in forceblocked by a courtproposedno longer in force

  1. AI law
  2. Privacy law 8
  3. Scraping law 2
  4. Cybersecurity law 4
  5. Communications law not researched
  6. Content moderation law not researched
  7. Product and AI liability law not researched
  8. Digital accessibility law not researched
  9. Age gating law 2
  10. Reuse law 1

Privacy law8 instruments, 8 in force

Research summary (327 words)

Malaysia's comprehensive private-sector data-protection law is the Personal Data Protection Act 2010 (Act 709), substantially amended by the Personal Data Protection (Amendment) Act 2024 (Act A1727), in force on a staged commencement schedule set by Ministerial gazette notification.

Act A1727 s.3, in force since , added a dedicated biometric data definition (technical processing relating to physical, physiological, or behavioural characteristics) directly to the sensitive personal data list, reaching both a faceprint and a voiceprint since either is produced by exactly that kind of technical processing.

Act A1727 also relabels data user as data controller, imposes direct statutory duties on data processors for the first time, replaces the never-exercised Ministerial cross-border whitelist with controller self-assessed adequacy (s.129, in force since ), and adds a mandatory Data Protection Officer duty and data breach notification duty (ss.12A-12B, in force since ) and a data portability right (s.43A, in force since ).

The Act's text is cited from the Department of Personal Data Protection's own PDFs at pdp.gov.my. Section 40 of Act 709 bars a data user from processing sensitive personal data of a data subject except on a listed condition. The first listed condition is the data subject's explicit consent. Contravening section 40(1) is an offence carrying a fine up to RM200,000, imprisonment up to 2 years, or both. Act A1727 s.2 substitutes data controller for data user throughout Act 709.

Section 30 of Act 709 lets a requestor, on payment of a prescribed fee, make a written data access request to a data user. A requestor may also have a copy of the personal data communicated in an intelligible form. A data user must comply with a data access request within 21 days of receiving it. A data user unable to comply within that period must tell the requestor so in writing before it expires. A data user must comply in whole within 14 days after the 21 day period expires.

Biometric privacy

Personal Data Protection Act, biometric data definition and sensitive category

Act 709 (Malaysia) s.4, as amended by Act A1727 s.3, in force official Act A1727 amendment text, Department of Personal Data Protection (pdp.gov.my)

In force since . Binds private bodies.

What this law does

Act A1727 s.3 inserted a dedicated biometric data definition into s.4 (any personal data resulting from technical processing relating to a person's physical, physiological, or behavioural characteristics) and added biometric data to the sensitive personal data list immediately after the offence-related category.

Both a faceprint and a voiceprint fall squarely within physical, physiological, or behavioural characteristics resulting from technical processing, which is exactly how a voice or face embedding is produced. Both are now, in force, sensitive personal data under s.4, requiring explicit consent under s.40's stricter processing conditions. No biometric-specific retention or destruction duty distinct from the Act's general data-minimisation and accuracy principles was found.

What it requires

Breach notification

Personal Data Protection Act, data protection officer and breach notification

Act 709 (Malaysia) ss.12A-12B, as inserted by Act A1727 s.6, in force official Act A1727 amendment text, Department of Personal Data Protection (pdp.gov.my)

In force since . Binds private bodies.

What this law does

Act A1727 s.6 inserts new Division 1A into Part II, requiring both the data controller and data processor to appoint a Data Protection Officer (s.12A) and, at s.12B, requiring the data controller to notify the Commissioner as soon as practicable on reasonable belief that a personal data breach occurred; where the breach causes or is likely to cause significant harm to the data subject, the controller must also notify the data subject without unnecessary delay.

No fixed numeric deadline is set in the statute itself; timing and form are left to the Commissioner's own prescribed manner. Paragraph 6.1 of the Commissioner's Data Breach Notification Guideline states that the notification shall be made as soon as practicable and no later than seventy-two (72) hours from the occurrence of the personal data breach.

Paragraph 4.2 of the Commissioner's Guideline on the Appointment of Data Protection Officer requires a data controller or data processor to appoint one if its processing involves personal data exceeding 20,000 data subjects or sensitive personal data, including financial information data, exceeding 10,000 data subjects. Paragraph 4.2 of that guideline also requires appointment where the processing involves activities that require regular and systematic monitoring of personal data.

Non-compliance with the Commissioner-notification duty is itself an offence, carrying a fine up to RM250,000, imprisonment up to 2 years, or both. Before this amendment, Act 709 had no statutory breach-notification duty at all.

What it requires

Comprehensive regime

Personal Data Protection Act, comprehensive regime and lawful bases

Act 709 (Malaysia), as amended by the Personal Data Protection (Amendment) Act 2024, Act A1727official statute text, Department of Personal Data Protection (pdp.gov.my)

In force since . Binds private bodies.

What this law does

Act 709's lawful basis is a bifurcated consent model: ordinary personal data needs the data subject's consent, subject to contract, legal-obligation, and vital-interest exceptions (s.6), while sensitive personal data needs explicit consent under s.40's stricter conditions.

Contravening any of the seven Data Protection Principles is itself an offence, carrying a fine up to RM1,000,000, imprisonment up to 3 years, or both (s.5(2)), the maxima that Act A1727 s.4(b)(ii) raised from RM300,000 and 2 years. Section 4 of Act A1727 came into operation on . Act A1727 relabels data user as data controller throughout and, for the first time, imposes direct statutory duties on data processors, who were previously reached only through contract with the data user.

Section 1(2) leaves the base Act's own commencement to a Ministerial gazette notification rather than stating a date in the Act's own text; the Department of Personal Data Protection's own published determination fixes that date at , the general commencement date, distinct from the 2024 amendment's own staged commencement dates.

What it requires

Cross border transfer

Personal Data Protection Act, cross-border transfer

Act 709 (Malaysia) s.129, as amended by Act A1727 s.12, in force official statute and Act A1727 amendment text, Department of Personal Data Protection (pdp.gov.my)

In force since . Binds private bodies.

What this law does

The original s.129 barred transferring personal data outside Malaysia except to a place the Minister specified by gazette notification as having a substantially similar law or an adequate level of protection; in practice this whitelist mechanism was never gazetted, making the provision largely inoperative.

Act A1727 s.12 restructures s.129, replacing the Minister's gazetting power with the data controller's own self-assessment against the substantially similar law or adequate level of protection standard, and drops the alternative or that serves the same purposes as this Act language, narrowing the standard. There is no data-localization mandate.

What it requires

Data subject rights

Personal Data Protection Act, data access request

Personal Data Protection Act 2010 (Act 709), ss. 30 and 31official statute text, Department of Personal Data Protection (pdp.gov.my)

In force since . Binds private bodies.

What this law does

Section 30 of Act 709 lets a requestor, on payment of a prescribed fee, make a written data access request to a data user. A requestor may also have a copy of the personal data communicated in an intelligible form. A data user must comply with a data access request within 21 days of receiving it. A data user unable to comply within that period must tell the requestor so in writing before it expires. A data user must comply in whole within 14 days after the 21 day period expires.

What it requires

Personal Data Protection Act, data portability

Act 709 (Malaysia) s.43A, as inserted by Act A1727 s.9, in force official Act A1727 amendment text, Department of Personal Data Protection (pdp.gov.my)

In force since . Binds private bodies.

What this law does

Act A1727 s.9 added s.43A, giving a data subject the right to request the data controller transmit their personal data to another data controller of the subject's choice by written electronic notice, subject to technical feasibility and compatibility of the data format. The controller must complete the transmission within the period as may be prescribed, with no fixed statutory deadline; the specific period is left to subsidiary regulation not read.

What it requires

Enforcement supervision

Personal Data Protection Act, enforcement

Act 709 (Malaysia) ss.5(2), 12B(3)official statute and Act A1727 amendment text, Department of Personal Data Protection (pdp.gov.my)

In force since , effective . Binds private bodies.

What this law does

The Personal Data Protection Commissioner is the supervisory authority.

Enforcement is criminal and administrative: contravening any Data Protection Principle is an offence under s.5(2), which carries a fine up to RM1,000,000, imprisonment up to 3 years, or both since Act A1727 s.4 raised the base Act's original RM300,000 and 2 year maximum, effective , and the new s.12B(3) breach-notification offence, in force since , carries a fine up to RM250,000, imprisonment up to 2 years, or both.

No private right of action provision was located in the sections read; enforcement is Commissioner-driven and criminal, not a statutory civil cause of action for the data subject, though the search was not exhaustive across the full base Act text.

What it requires

Sensitive categories

Personal Data Protection Act, processing of sensitive personal data

Personal Data Protection Act 2010 (Act 709), s. 40official statute text, Department of Personal Data Protection (pdp.gov.my)

In force since . Binds private bodies.

What this law does

Section 40 of Act 709 bars a data user from processing sensitive personal data of a data subject except on a listed condition. The first listed condition is the data subject's explicit consent. Contravening section 40(1) is an offence carrying a fine up to RM200,000, imprisonment up to 2 years, or both. Act A1727 s.2 substitutes data controller for data user throughout Act 709.

What it requires

Scraping law2 instruments, 2 in force

Research summary (263 words)

Malaysia has no scraping-specific statute, so general law governs each dimension separately. The Computer Crimes Act 1997 criminalises unauthorised access to a computer, but section 3 turns on whether the access itself is unauthorised rather than on the manner of access, so a plain reading does not resolve whether reading a public, unauthenticated page without defeating any access control is unauthorised access, and no reported Malaysian decision on the point was located.

No Malaysian court decision on the enforceability of a browsewrap or clickwrap terms-of-service against a scraper was located.

The Copyright Act 1987 excuses limited reproduction for research, private study, criticism, review, or reporting news or current events by way of fair dealing, tested against a four-factor purpose, nature, amount, and market-effect standard, but Malaysia has not enacted a text-and-data-mining exception, so training a model on scraped copyright text rests only on the general fair dealing ground if it can be characterised as research; the Act confers no sui generis database right.

The Personal Data Protection Act 2010, as amended, applies to personal data without a general carve-out for information that is publicly accessible, so scraping personal data from a public Malaysian website remains subject to that Act's lawful-basis and cross-border-transfer duties (see the privacy topic for that Act's provisions).

No Malaysian statute or reported case establishes a scraping-specific unfair-competition, misappropriation, or trespass doctrine, and none assigns legal weight to a robots.txt directive or imposes an AI-training-specific rule. The Dewan Rakyat passed the Cybercrimes Bill 2026 on . The Dewan Negara passed the Cybercrimes Bill 2026 on .

Computer misuse

Computer Crimes Act 1997, unauthorised access to computer material

Computer Crimes Act 1997 (Act 563), s. 3 (Unauthorised Access to Computer Material)official consolidated reprint text, Attorney General's Chambers of Malaysia (Laws of Malaysia portal)

In force since . Binds public and private bodies.

What this law does

Section 3 makes it an offence to cause a computer to perform a function with intent to secure access to a program or data held in any computer, where that access is unauthorised and the person knows at the time that it is unauthorised; the intent need not be directed at any particular program, data, or computer.

Section 2(5) defines access as unauthorised only where the person is not entitled to control access of that kind and does not have consent from, or exceeds a right or consent given by, a person who is so entitled.

Because the offence turns on whether the access itself is unauthorised rather than on the manner of access, reading a public, unauthenticated page without defeating any access control falls outside a plain reading of the provision, though no reported Malaysian decision addresses the point either way.

Sections 4 and 5 separately punish, at higher penalties, unauthorised access committed with intent to commit or facilitate a further offence, and unauthorised modification of the contents of a computer.

What it requires

Cybersecurity law4 instruments, 4 in force

Research summary (1,007 words)

Malaysia's principal cyber-resilience statute is the Cyber Security Act 2024 (Act 854), given royal assent , gazetted , and brought into operation under the Cyber Security Act 2024 (Appointment of Date of Coming into Operation) order [P.U. (B) 334/2024]. Its substantive duties fall into two classes.

First, a national critical information infrastructure (NCII) sector lead, a Government Entity or person the Minister appoints under section 15 upon the recommendation of the Chief Executive of the National Cyber Security Agency (NACSA), may designate a Government Entity or person as an NCII entity under section 17 or 18 wherever the sector lead is satisfied that entity owns or operates a computer or computer system whose disruption would harm a service essential to Malaysia's security, defence, foreign relations, economy, public health, public safety or public order.

A designated NCII entity then carries a duty to implement its sector's code of practice (section 21), to conduct a cyber security risk assessment and an audit by a Chief-Executive-approved auditor within a period the Minister prescribes, submitting the report within thirty days (section 22), and to notify the Chief Executive and its sector lead of a cyber security incident within a period and manner the Minister prescribes by regulation (section 23); the section 21 and section 23 duties each carry a criminal fine of up to five hundred thousand ringgit, and the section 22 assessment and audit duties carry lower fines.

The prescribed incident-notification clock is set by the Cyber Security (Notification of Cyber Security Incident) Regulations 2024 [P.U. (A) 220/2024] and the risk-assessment and audit period by the Cyber Security (Period for Cyber Security Risk Assessment and Audit) Regulations 2024 [P.U. (A) 219/2024]; neither regulation's text was retrievable through the crawler: the Attorney General's Chambers portal exposes a JavaScript-rendered download link for the principal Act's own PDF but returned no equivalent link for its subsidiary legislation on either the compliant or the stealth browser tier, and the portal's own search tool matched the Act number but not a P.U. citation, so no specific clock figure for either duty is stated here.

Because both the sector-lead and NCII-entity classes are individual government designations rather than a status any declared LexLint activity establishes, this whole NCII regime is recorded here rather than raised against a declared activity, the same treatment this profile gives DORA's financial entities, New York's Department of Financial Services Part 500 covered entities, Singapore's designated critical-information-infrastructure owners, and Japan's designated critical-infrastructure operators.

Second, Part VI of the Act requires a person to hold a Chief-Executive-issued licence before providing, or holding out as providing, a "cyber security service", a term the Minister alone defines by regulation under section 27(2); NACSA's own published guidance states that an applicant needs a licence for managed security operation centre monitoring service and for penetration testing service, matching the title of the Cyber Security (Licensing of Cyber Security Service Provider) Regulations 2024 [P.U. (A) 221/2024], and providing an unlicensed cyber security service is an offence carrying a fine of up to five hundred thousand ringgit or imprisonment of up to ten years, or both (section 27(5)).

That is a professional-services licensing duty on a security vendor's client-facing offering rather than a duty on a product or platform, and it too reaches no declared activity, the same treatment this profile gives Singapore's Part 5 cybersecurity-service licence. Malaysia has no enacted law setting security requirements a software product or connected device must meet before or after it is placed on the market.

The Malaysian Communications and Multimedia Commission's "Certification of Communications Equipment" scheme, run under the Communications and Multimedia (Technical Standards) Regulations 2000, certifies radio-frequency and technical-standards compliance for communications equipment, not a device's cyber security posture, and no MCMC scheme was found that does.

There is no general reasonable-security or information-security-programme statute reaching a Malaysian business simply because it holds data; the nearest analogue is the Personal Data Protection Act 2010's own security-safeguards and breach-notification provisions, an article inside the comprehensive consent-based regime this jurisdiction's privacy row already researches, the same architecture as General Data Protection Regulation (GDPR) Article 32, so it is not repeated here.

The Computer Crimes Act 1997's unauthorised-access offence is likewise this jurisdiction's scraping-topic finding, an offence committed against a computer rather than a duty on the operator of one, and is not restated here.

No provision of the Cyber Security Act 2024 was found to create a private right of action; enforcement runs through the Chief Executive of NACSA's investigatory, directive and licensing powers, with an offence prosecuted through the ordinary criminal courts, and no published enforcement record was found under an Act that has been in force a little over two years.

Section 21(1) of the Cyber Security Act 2024 requires a national critical information infrastructure entity to implement the measures, standards and processes specified in the code of practice. Section 23(1) of the Cyber Security Act 2024 requires a national critical information infrastructure entity that learns that a cyber security incident has or might have occurred to notify the Chief Executive and its sector lead within the period and in the manner prescribed.

Paragraph S 11.6 of the Risk Management in Technology policy document of Bank Negara Malaysia requires a financial institution to conduct a Red Team simulation attack on its infrastructure at least once every three years.

Paragraph S 11.18 of the Risk Management in Technology policy document of Bank Negara Malaysia requires a financial institution to notify the Bank of cyber incidents in adherence to the Bank's policy documents on Operational Risk Reporting, Business Continuity Management and Merchant Acquiring Services.

Section 27(1) of the Cyber Security Act 2024 prohibits a person from providing, or holding out as a provider of, a cyber security service unless the person holds a licence issued under Part VI of the Act. Section 27(5) of the Cyber Security Act 2024 makes providing a cyber security service without a licence an offence with a fine not exceeding five hundred thousand ringgit or imprisonment for a term not exceeding ten years or both.

Sector security regimes

BNM Risk Management in Technology Policy Document, Cyber Risk Framework, Monitoring, Red Team Testing and Incident Response Plan

Bank Negara Malaysia, Risk Management in Technology (RMiT) policy document (BNM/RH/PD 028-98), paras. S 11.2 to S 11.16Bank Negara Malaysia, text of the Risk Management in Technology (RMiT) policy document (BNM/RH/PD 028-98) as published on bnm.gov.my

In force since . Binds private bodies.

What this law does

Paragraph S 11.2 requires a financial institution to develop a Cyber Risk Framework that articulates its governance for managing cyber risks, its cyber resilience objectives and its risk tolerance. Paragraph S 11.5 requires a financial institution to adopt the control measures outlined in Appendix 5 to enhance its resilience to cyber-attacks. Paragraph S 11.6 requires a financial institution to conduct a realistic Red Team simulation attack on its infrastructure at least once every three years.

Paragraph S 11.9 requires a financial institution to establish a Security Operations Center supported by competent resources, with monitoring that covers all critical systems including the supporting infrastructure. Paragraph S 11.13 requires a financial institution to establish and implement a comprehensive Cyber Incident Response Plan.

Paragraph S 11.16 requires a financial institution to conduct an annual cyber drill exercise to test the effectiveness of that plan and to report the result to the board in a timely manner.

Paragraph S 11.4 requires a financial institution designated as a National Critical Information Infrastructure entity under the Cyber Security Act 2024 to ensure compliance with the requirements applicable to such entities, including additional directives and standards issued by the National Cyber Security Agency.

Appendix 12 to the policy document constitutes the Code of Practice for national critical information infrastructure entities designated by the Bank under the banking and finance sector.

The policy document applies to licensed banks, licensed investment banks, licensed Islamic banks, licensed insurers, licensed takaful operators, prescribed development financial institutions, approved issuers of electronic money, operators of a designated payment system, registered merchant acquirers and intermediary remittance institutions.

The requirements in the policy document are specified pursuant to sections 47(1), 47(2)(d) and 143(2) of the Financial Services Act 2013, and to the corresponding sections of the Islamic Financial Services Act 2013, the Development Financial Institutions Act 2002 and the Money Services Business Act 2011. Paragraph 5.2 provides that non-compliance with a standard may result in enforcement action. Paragraph 4.1 states that the policy document comes into effect on .

What it requires

Cyber Security Act, National Critical Information Infrastructure Entities, Code of Practice, Risk Assessment and Audit

Cyber Security Act 2024 (Act 854), ss. 17, 20 to 22 and 24Text of the Cyber Security Act 2024 (Act 854)

archived copyRead from a public archive copy, not the publisher directly. The publisher does not serve this page to automated readers, so a direct fetch was not an option here; how we access sources. Archived . Publisher's page: https://lom.agc.gov.my/ilims/upload/portal/akta/outputaktap/2177706_BI/Act%20854.pdf

In force since . Binds public and private bodies.

What this law does

Section 17(1) allows a national critical information infrastructure sector lead to designate a Government Entity or person as a national critical information infrastructure entity if it is satisfied that the entity owns or operates a national critical information infrastructure. Section 21(1) requires an NCII entity to implement the measures, standards and processes specified in the code of practice to ensure the cyber security of the infrastructure it owns or operates.

Section 21(5) makes a contravention of section 21(1) an offence with a fine not exceeding five hundred thousand ringgit or imprisonment for a term not exceeding ten years or both. Section 22(1) requires an NCII entity, within the period prescribed, to conduct a cyber security risk assessment and to cause an audit to be carried out by an auditor the Chief Executive approves, and section 22(2) requires it to submit the report to the Chief Executive within thirty days after completion.

Section 22(7) makes a contravention of section 22(1) or (2) an offence with a fine not exceeding two hundred thousand ringgit or imprisonment for a term not exceeding three years or both. Section 20(1) requires an NCII entity to comply with a request of its sector lead to provide information about the infrastructure it owns or operates.

Section 20(3) requires an NCII entity to notify its sector lead of a material change to the design, configuration, security or operation of the infrastructure within thirty days from the date the change was completed. Section 24(3) allows the Chief Executive to give directions to an NCII entity for a cyber security exercise, and section 24(4) makes a failure to comply an offence with a fine not exceeding one hundred thousand ringgit.

Section 25(1) requires a national critical information infrastructure sector lead to prepare a code of practice, to be endorsed by the Chief Executive, containing measures, standards and processes to ensure the cyber security of the infrastructure in its sector. Section 13(1) allows the Chief Executive to issue a directive considered necessary to ensure compliance with the Act.

Section 2 binds the Federal Government and State Governments, and renders neither liable to prosecution for an offence under the Act. The Prime Minister appointed as the date on which the Act comes into operation. The Act received Royal Assent on and was published in the Gazette on .

What it requires

Vulnerability and incident reporting

BNM Risk Management in Technology Policy Document, Cyber Incident Notification and Threat Intelligence Sharing

Bank Negara Malaysia, Risk Management in Technology (RMiT) policy document (BNM/RH/PD 028-98), paras. S 11.18 and S 11.19Bank Negara Malaysia, text of the Risk Management in Technology (RMiT) policy document (BNM/RH/PD 028-98) as published on bnm.gov.my

In force since . Binds private bodies.

What this law does

Paragraph S 11.18 requires a financial institution to notify the Bank of cyber incidents in adherence to the Bank's policy documents on Operational Risk Reporting, Business Continuity Management and Merchant Acquiring Services, and any other relevant policy documents the Bank specifies.

Paragraph S 11.19 requires a financial institution to share cyber threat intelligence information with the industry on a timely basis, subject to the applicable data protection laws, and to allocate resources to take part in industry-wide initiatives.

The policy document applies to licensed banks, licensed investment banks, licensed Islamic banks, licensed insurers, licensed takaful operators, prescribed development financial institutions, approved issuers of electronic money, operators of a designated payment system, registered merchant acquirers and intermediary remittance institutions.

The requirements in the policy document are specified pursuant to sections 47(1), 47(2)(d) and 143(2) of the Financial Services Act 2013, and to the corresponding sections of the Islamic Financial Services Act 2013, the Development Financial Institutions Act 2002 and the Money Services Business Act 2011. Paragraph 5.2 provides that non-compliance with a standard may result in enforcement action. Paragraph 4.1 states that the policy document comes into effect on .

What it requires

Cyber Security Act, Notification of a Cyber Security Incident to the Chief Executive and the Sector Lead

Cyber Security Act 2024 (Act 854), s. 23Text of the Cyber Security Act 2024 (Act 854)

archived copyRead from a public archive copy, not the publisher directly. The publisher does not serve this page to automated readers, so a direct fetch was not an option here; how we access sources. Archived . Publisher's page: https://lom.agc.gov.my/ilims/upload/portal/akta/outputaktap/2177706_BI/Act%20854.pdf

In force since . Binds public and private bodies.

What this law does

Section 23(1) requires an NCII entity that learns that a cyber security incident has or might have occurred in respect of the infrastructure it owns or operates to notify the Chief Executive and its sector lead within the period and in the manner prescribed. Section 23(2) makes a contravention of section 23 an offence with a fine not exceeding five hundred thousand ringgit or imprisonment for a term not exceeding ten years or both.

Section 4 defines a cyber security incident as an act or activity carried out on or through a computer or computer system, without lawful authority, that jeopardizes or adversely affects the cyber security of that computer or computer system or another one.

Section 4 defines a national critical information infrastructure as a computer or computer system whose disruption or destruction would have a detrimental impact on the delivery of a service essential to the security, defence, foreign relations, economy, public health, public safety or public order of Malaysia. Section 4 defines an NCII entity as any Government Entity or person designated as a national critical information infrastructure entity under section 17 or 18.

Section 2 binds the Federal Government and State Governments, and renders neither liable to prosecution for an offence under the Act. The Prime Minister appointed as the date on which the Act comes into operation.

What it requires

Age gating law2 instruments, 2 in force

Research summary (164 words)

Malaysia's Online Safety Act 2025 (Act 866), in force since , requires a licensed applications service provider or licensed content applications service provider to protect the online safety of a child user, defined as a person under eighteen.

The Malaysian Communications and Multimedia Commission's Child Protection Code, issued under the Act and effective , requires effective age verification, based on government-issued identity records, before a social media service likely to be accessed by children may let a user register or access an age-appropriate feature, limited to users identified as sixteen or older; the same Code separately requires any qualifying applications or content applications service to build in broader child-safety measures (content moderation, parental controls, default privacy and safety settings, and controls over search and recommendation algorithms) for a service likely to be accessed by a child under eighteen.

Malaysia has no adult-content age-verification statute distinct from the Online Safety Act's harmful-content regime, and no app-store-level, device-based age-verification requirement was located.

Age-appropriate design code

Online Safety Act 2025, Child Protection Code, safe design and operation duty for services likely accessed by children

Online Safety Act 2025 (Act 866), Child Protection Code ss. 2, 4-7 (Child Safety by Design)Online Safety Act 2025: Child Protection Code, Malaysian Communications and Multimedia Commission, read with the Act's own text

In force since . Binds private bodies.

What this law does

Section 18 of the Online Safety Act 2025 requires a licensed applications service provider or licensed content applications service provider to implement measures, specified in a code issued by the Commission, to ensure the safe use of its services by a child user, defined as a person under the age of eighteen years; subsection 18(3) requires that, for a service that is, in the provider's opinion, likely to be accessed by child users, those measures include safe design and operation to prevent a child's access to suspected harmful content, limit an identified adult's ability to communicate with an identified child, limit features that increase or sustain a child's use of the service, prevent an identified adult from viewing an identified child's personal information, and control personalised recommendation systems suitable for child users.

The Child Protection Code, issued by the Commission under section 80 read with section 18 and taking effect , applies these duties to any applications service enabling communication between users and any content applications service, and adds content-moderation duties (detecting and removing harmful content, accessible reporting channels for child users, steps against repeated exposure to reported or removed content), a duty to make available parental control features, a duty to set privacy and safety settings to the highest level by default for child users and limit an unconnected adult's direct communication with a child user, and duties over search and recommendation systems.

Those duties include activating safe search by default. Separately, algorithmic recommendation does not display or promote harmful content to child users.

What it requires

Social media and minors

Online Safety Act 2025, Child Protection Code, social-media age verification

Online Safety Act 2025 (Act 866), Child Protection Code s. 3 (Age Verification)Online Safety Act 2025: Child Protection Code, Malaysian Communications and Multimedia Commission

In force since . Binds private bodies.

What this law does

The Child Protection Code, issued by the Malaysian Communications and Multimedia Commission under section 80 of the Online Safety Act 2025 read with section 18, requires a licensed applications service provider or licensed content applications service provider offering a social media service likely to be accessed by child users to implement effective age verification measures so that only users whose ages have been identified as sixteen years or above may register for the service or access a feature of the service appropriate for their age.

The Code requires verification against records issued by the Government of Malaysia (National Registration Identity Card, passport, birth certificate, or another government-recognised document) or an equivalent record issued or recognised by a competent authority in another jurisdiction, and requires that any personal data collected for age verification be adequate, relevant, and limited to what is necessary, and not kept longer than necessary for that process, consistently with the Personal Data Protection Act 2010. The Code was published on and took effect on .

What it requires

Reuse law1 instrument, 1 in force

Research summary (194 words)

Malaysia has no press-publisher neighbouring right, no mandatory platform-to-publisher bargaining code, no recognised hot-news or misappropriation doctrine distinct from ordinary copyright and unfair-competition law, and no located statute or reported case addressing hyperlinking or framing liability specifically; each of those dimensions is an absence rather than an unresolved question.

The relevant instrument is the Copyright Act 1987 (Act 332), which excuses, by way of fair dealing, the reproduction, criticism, review, or reporting of another's work for research, private study, or the reporting of news or current events (s. 13(2)(a)), tested against the purpose, nature, amount, and market-effect factors added by the Copyright (Amendment) Act 2012 (s. 13(2A)).

Unlike some other jurisdictions' copyright statutes, the Act carries no separate exclusion of the news of the day or of mere facts from copyright protection; a bare headline or short news item's protection instead turns on whether sufficient effort was expended to make it original in character (s. 7(3)(a)), and no reported Malaysian decision on a systematic aggregator's reproduction of headlines and snippets, as opposed to a traditional press review, was located. Malaysia has no text-and-data-mining exception, so no machine-readable opt-out mechanism of that kind exists either.

Where nothing was found1 area of law

These areas of law were researched here and no instrument was recorded. Each finding says what the research checked, as of the date under it. It describes our search, not a guarantee that no such law exists.

AI law

Malaysia has no comprehensive, enacted AI-specific statute imposing transparency, risk-management, or output-labelling duties as of the date below.

The Ministry of Science, Technology and Innovation's National Guidelines on Artificial Intelligence Governance and Ethics (AIGE), issued in September 2024, set out ethical principles addressing disclosure of AI use, transparency about training data, and accountability for automated decisions, but the Government's own description of the guidelines states that although voluntary, they are intended to guide policymakers, developers, and the public. No instrument compelling compliance with those principles was located.

As of .

Case law

  • No current case law for Malaysia AI law
  • No current case law for Malaysia privacy law
  • No current case law for Malaysia scraping law
  • No current case law for Malaysia cybersecurity law
  • No current case law for Malaysia communications law
  • No current case law for Malaysia content moderation law
  • No current case law for Malaysia product and AI liability law
  • No current case law for Malaysia digital accessibility law
  • No current case law for Malaysia age gating law
  • No current case law for Malaysia reuse law

Reporting clocks that run here1 instrument

The instruments whose obligation lines set a deadline for reporting an incident, a vulnerability or a personal-data breach, each deadline read from the sentence that carries it and listed shortest first. The law of Malaysia comes first, then the law of the bodies above it that applies here.

Each flag is one law, and a link to it. Read down the scale: the clocks document's time axis, with the empty stretches shortened so the deadlines sit close. Flags on one line set the same duty at the same deadline, and the laws behind them are named to the right, with what each clock counts from.

72 hours
Breach notificationprivacy law
The deadlines above on one time axis, shortest at the top. The axis keeps its order and, between neighbors, its proportion, but a stretch with no deadline on it is shortened, so the hour marks on the left are what say how far apart two stations really are. Beside each action, the laws that set it, what each counts from, and a status where the law is not yet in force. The List tab has the same data in full, with the sentences.

The law of Malaysia

72 hours

Personal Data Protection Act, data protection officer and breach notification

Act 709 (Malaysia) ss.12A-12B, as inserted by Act A1727 s.6, in force privacy law, in force since

The sentence the clocks are read from

A data controller who reasonably believes a personal data breach has occurred must notify the Commissioner as soon as practicable, which the Commissioner's guideline puts at no later than 72 hours from the occurrence of the breach, and must notify affected data subjects without unnecessary delay where the breach causes or is likely to cause significant harm.

Which of these one incident starts turns on the facts: the incident method works that through. The clocks document draws every clock in the LexLint law library on one axis, with the sentence beside every rung.

Drafted with AI

Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made

This page covers the instruments LexLint has researched to a stage. Instruments named in the law library but not yet researched are counted in the head and are not listed here. Every entry carries its own primary source on its note page. This is a research index, not legal advice.