Back to Resources
Compliance

PDPA and Your Backups: What Malaysian SMEs Must Know

Under Malaysia's PDPA, backups fall under the Security Principle: you must take practical steps to protect personal data against loss, misuse and unauthorized access.

Under Malaysia's PDPA, backups fall under the Security Principle: you must take practical steps to protect personal data against loss, misuse and unauthorized access. And since the 2024 amendments, a breach affecting that data can trigger mandatory notification. Here is what that means for a Malaysian SME's backup practice, in plain terms.

Where backups sit in the PDPA

The Personal Data Protection Act 2010 applies to almost every Malaysian business that processes personal data in a commercial transaction: customer records, employee files, payroll, supplier contacts. Backups touch the Act in two directions at once:

Backups as protection. The Security Principle requires practical steps to protect personal data from loss, misuse, modification and unauthorized access or disclosure. If a dead disk or a ransomware attack permanently destroys your customer or employee records, "we had no working backup" is precisely the failure of practical steps the principle describes. A backup that has never been verified restorable offers little more defence: you took a step, but couldn't show it was a practical one.

Backups as personal data. Every backup of your HR system or customer database is a copy of personal data. It needs the same protection as the original: encryption, access control, and a story for where it lives and who can read it. An unencrypted backup drive in a drawer is a disclosure risk, not a safeguard.

What changed in 2024

The Personal Data Protection (Amendment) Act 2024 significantly raised the stakes for SMEs. Two changes matter most for backup practice:

Mandatory breach notification. Previously, notifying a breach was effectively voluntary. Now a personal data breach must be notified to the Commissioner and, where the breach is likely to cause significant harm, to the affected individuals. A ransomware event that encrypts or exfiltrates your data is exactly such a breach, which means the question "what data did we lose and can we recover it?" now has a regulator waiting for the answer, on a deadline.

Data Protection Officer. Organisations meeting the prescribed thresholds must appoint a DPO. For an SME this creates, often for the first time, a named person whose job includes asking IT: "can you show me our personal data is protected against loss?" That is a question a verified backup practice answers and an unverified one does not.

The amendments also increased penalties and (via subsequent guidelines) tightened timelines; the direction of travel is unmistakably toward being able to demonstrate protection, quickly, with records.

The retention tension

The PDPA's retention principle says personal data must not be kept longer than necessary; your backup practice says keep copies. These coexist fine, but only deliberately: decide and document how long backup copies are retained, make sure retention actually expires old copies (rather than accumulating years of them by default), and know which backups contain personal data so a deletion obligation can be honoured in practice. "We keep every backup forever" is a retention-principle problem wearing a diligence costume.

Five practical steps for this quarter

Map personal data to backups. One page: which systems hold personal data (HR, payroll, CRM, accounting), and which backup covers each. This is also the first thing you'd need in a breach assessment.

Encrypt and restrict. Backups containing personal data: encrypted at rest, credentials separate from daily admin accounts, access limited to named people.

Verify restorability, and record it. A restore test you performed and documented is your "practical steps" evidence against loss. Schedule one per quarter for the systems in step 1.

Set retention on purpose. Choose backup retention per system, write it into your backup policy, and confirm the software enforces it.

Pre-write the bad-day answer. Given notification deadlines, decide now who assesses a suspected breach, and keep the records that make the assessment fast: what data each backup holds, when it was last verified, and your recovery evidence.

What to keep on file if the Commissioner asks

Think of it as a small evidence pack, maintained continuously rather than assembled in a panic: your backup policy; the personal-data-to-backup map; verification records showing backups are current and restorable; restore-test records with dates and outcomes; and your breach-response contact chain. Companies that can produce this in an afternoon are in a different conversation with a regulator than companies that need three weeks.

A note on how we handle this ourselves: Backup Governor was built PDPA-conscious. Restore evidence is redacted on your own server before anything leaves it (sensitive on-screen data in a restore screenshot never egresses unredacted); storage credentials stay in your machine's own credential store, and the portal works in Bahasa Malaysia and English alike.

This article is general information, not legal advice. The amendment provisions and their commencement dates, thresholds and guidelines evolve; confirm current requirements with the Personal Data Protection Department (JPDP) or your legal advisor. Article last reviewed: September 2026.

Free for one node

Practical steps, demonstrated

Verified, restorable, access-controlled backups with continuous evidence. Free for one node, in Bahasa Malaysia or English.

Get started free
No credit card requiredCancel anytime

Want to see these best practices in action?

Start for free and experience proper backup monitoring firsthand.

No credit card required
Cancel anytime