SentraMind

Briefing

Six hours is not seventy-two

Malaysia runs two incident clocks: Act 854 NCII reporting and PDPA notification. They are different populations and different deadlines.

In-force notice windows. The 6-hour bar is the one a single “72 hours” label hides.
  • Malaysia NCII initial 6 h
  • Malaysia PDPA notice 72 h

Six hours is the Act 854 initial report

Act 854 has been in operation since 26 August 2024, with four regulations beside it. National critical information infrastructure covers 11 sectors, and government and banking are among them. For an incident in that scope the sheet records three steps toward NACSA. There is an immediate electronic notice. There is an initial report within 6 hours. There is a supplemental report within 14 days.

The six-hour document is the initial report. The fourteen-day document is supplemental, and its deadline does not move the initial one. The sheet calls the six-hour clock the design-driving case. Set against the other in-force windows the sheet lists, it is the short one, with personal-data notices at 72 hours or at three calendar days. A timestamp taken from a personal-data rule describes a different duty and a different recipient, and the supplemental report remains a further point, at 14 days.

Seventy-two hours, then seven days, is the PDPA sequence

Notice to the Commissioner under the amended PDPA falls within 72 hours. The sheet dates that notification rule to 1 June 2025. Act A1727, the amending instrument, was phased across 1 January, 1 April, and 1 June 2025, so the June date belongs to the notification rule and does not pull every new PDPA duty onto the same day. Affected individuals are notified within 7 days after the Commissioner is notified, when the tests are met.

The sheet attaches two markers to that individual notice: significant harm, and a population above 1,000 people, which it calls a trigger. The Commissioner is the first recipient. The individual notice follows only when a test is met, and the seven days run from the Commissioner notice. That follow-on does not lengthen the six-hour report to NACSA, and it does not stand in for it. The order is the one the sheet records. This briefing does not file either notice.

The two clocks attach to different populations

Act 854 speaks to national critical information infrastructure. The PDPA speaks to personal data, and the individual notice under it waits on the harm and population tests. An incident at a bank inside the 11 sectors can meet both regimes, in which case both clocks run. A personal-data incident outside that infrastructure can sit under the PDPA alone. The initial report within 6 hours does not discharge the notice to the Commissioner. The notice within 72 hours does not discharge the initial report to NACSA.

The table captioned “Six hours and seventy-two hours are different duties” sets each deadline next to its population, and it puts the CSSP licence on a third row so a service permission is kept apart from both clocks. The bar figure is captioned “In-force notice windows. The 6-hour bar is the one a single “72 hours” label hides.” Those bars draw the in-force windows as length. The duties are still sayable with no drawing at all. NACSA receives an immediate electronic notice, an initial report within 6 hours, and a supplemental report within 14 days. The Commissioner receives notice within 72 hours, and affected individuals receive notice within 7 days after that when the tests are met.

The CSSP licence covers managed monitoring and penetration testing

The sheet narrows an earlier claim about CSSP licensing. The licensable services are managed monitoring of the kind a security operations centre provides, and penetration testing. A sale of the product sits outside that pair. The correction says that selling on-premises data-loss software does not itself require a CSSP licence. The licence becomes relevant if the vendor or a partner runs managed monitoring in Malaysia.

A matching boundary is recorded for Singapore, where a CSA licence covers penetration testing and managed monitoring. The parallel is about services in both places. It leaves the six-hour report, the fourteen-day supplement, and the PDPA sequence where they are. The licence question asks whether managed monitoring or a penetration test is being offered. The clock question asks which population was affected, and which of the two deadlines that population brings with it.

Regular and systematic monitoring can trigger a data-protection officer duty

The sheet records an onboarding consequence that is separate from any product feature. Regular and systematic monitoring can trigger a mandatory data-protection officer appointment under the amended PDPA. A control that watches activity on a regular and systematic basis is the pattern that threshold describes. The appointment sits with the organisation whose processing meets the test. The sheet presents it as a duty the monitoring can create, and the software does not make the appointment.

Data processors have carried direct statutory security duties since April 2025, one of the phased dates of Act A1727. That processor duty is distinct from the officer appointment. Both are distinct from the six-hour report to NACSA. The sheet also treats an employee-monitoring disclosure pack as a deliverable in all five markets, and it names regular and systematic monitoring as the Malaysia trigger in that subject. The trigger is a consequence of watching use. It is recorded so that onboarding states it, and it remains an organisation-side duty.

Watch-list item 5 is still open PDPA rulemaking

Watch-list item 5 is a set of PDPA texts the sheet has not placed in force. The named pieces are a data-protection impact assessment guideline, a data-protection-by-design guideline, amendments to the PDP Regulations under PCP 4/2025, and automated-decision provisions. They remain open. Writing any of them up as a duty that already binds would go past the sheet.

The deadlines in the earlier sections are the ones the sheet already dates. Act 854 contributes the six-hour initial report and the fourteen-day supplement. The PDPA contributes 72 hours to the Commissioner and 7 days to individuals after that. The rulemaking wave is not among those dated notification clocks. Federal and state government stand outside the PDPA under section 3(1), which the sheet says is unchanged. Their account runs through Act 854 and government directives, including Arahan Keselamatan, OSA 1972, and the Data Sharing Act 2025. Enterprise and financial institutions can fall under the PDPA, and a financial institution that is also national critical information infrastructure can fall under Act 854 at the same time. That overlap, and the government exclusion, are why one deadline cannot describe every buyer.

How to read this

Six hours and seventy-two hours are different duties
Six hours and seventy-two hours are different duties
ClockDeadline on the sheetPopulation
Act 854 NCII Initial report within 6 hours National critical information infrastructure
PDPA notice Commissioner within 72 hours Personal data, when the tests are met
CSSP licence Managed monitoring and pentest A product sale

Orientation only. This briefing is not legal advice. A watch-list item is not a statement that the cited instrument is in force.