PDPA security measures are the protections that Thailand's Personal Data Protection Act B.E. 2562 (2019) requires a data controller (the organization that decides why and how personal data is used) to put in place. Their purpose is to stop personal data from being lost, or accessed, used, changed or disclosed without authority. This article reads the Act and the notifications of the Personal Data Protection Committee (PDPC) from a security team's point of view. It is general information, not legal advice; confirm the details with your data protection officer or a lawyer.
What the law requires
Section 37(1) of the Act requires a controller to provide appropriate security measures, to review them when necessary or when technology changes, and to meet the minimum standard that the PDPC announces. Section 37(4) requires the controller to report a breach to the PDPC office within 72 hours, as explained below. We read both sections in the Act as published in the Royal Gazette on 27 May 2019.
The PDPC set that minimum standard in its notification on security measures of data controllers, dated 10 June 2022 and published in the Royal Gazette on 20 June 2022. It took effect on the day after publication. A second notification, on how to report a breach, was published on 15 December 2022. Both are on the PDPC website, and the references list the links.
The security notification does not name products or technologies. It says what the measures must cover and that they must fit the level of risk. So there is no official checklist of tools, and deciding what is appropriate is a judgement the organization must make and be able to explain. In our view, a documented risk assessment is what lets you explain that judgement.
Clause 7 of the security notification says that if another law also requires security measures, the controller follows that law and must still meet this minimum standard. Organizations designated as critical information infrastructure, for example, have extra duties; see Thailand Cybersecurity Act and CII: Who Is Covered.
What the minimum standard covers
Clause 4 of the security notification says the measures must include at least these seven points:
- Every form of data: the measures cover the collection, use and disclosure of personal data, whether it is on paper, in electronic form or in any other form.
- Organizational and technical measures: both are needed, plus physical measures where necessary. They are scaled to the level of risk, the purpose of the processing, and the likelihood and impact of a breach.
- The whole lifecycle: identify the significant risks to important information assets (the systems and data the organization holds), protect against them, detect and monitor threats and breaches, respond when one is found, and recover from the damage. All of this is as necessary, appropriate and feasible for the level of risk.
- Confidentiality, integrity and availability: keep these three properties of the data at a level that fits the risk (confidentiality means only authorized people can see it, integrity means it is not wrongly altered, availability means it can be used when needed), taking account of technology, context, accepted standards for similar organizations, and the resources available.
- Every part of the system: for electronic data, this includes storage systems and devices, servers, client computers and devices, the network, and software and applications. The notification asks for defense in depth, meaning several layers of controls so that one weak control does not leave the data exposed.
- Control of access: explained in the next section.
- Awareness: staff and other users must be told about the organization's privacy and security policies and measures, including when they change, and be made aware of why they matter.
Access control and audit trails
The most concrete part of clause 4 is its item 6. It says the measures for accessing and using personal data must contain at least these four things, appropriate to the level of risk:
- Access control: identity proofing and authentication, and authorization that follows the need-to-know and least privilege principles.
- User access management: the notification says this may include registering and removing users, granting access rights, managing privileged access rights, managing secret authentication information (such as passwords), reviewing access rights, and removing or adjusting them.
- User responsibilities: duties for users that prevent unauthorized access, use, change, deletion or disclosure, including acting outside one's assigned role, secretly copying personal data, and theft of devices that store or process it.
- Audit trails: a way to look back at who accessed, changed, edited or deleted personal data, suited to the method and medium used to handle the data.
Technical controls that support it (our own view)
The notification names few specific technologies. The mapping below is our own view of what a security team can use to show that each part is covered. The PDPC has not approved this list, and the notification does not name encryption, MFA or any specific tool.
- Know where the data is: keep an inventory of the systems, databases, file shares and SaaS apps that hold personal data, and label them by sensitivity. See Data Classification: A Practical How-to Guide.
- Strong access: MFA (multi-factor authentication, a second proof of identity besides the password), role-based access, a joiner-mover-leaver process for staff changes, regular access reviews, and tighter control of administrator accounts than of ordinary ones.
- Audit trails you can use: collect logs that show who accessed, changed or deleted personal data, protect them from tampering, and keep them long enough to investigate.
- Layers around the data: network segmentation, endpoint protection, timely patching, secure configuration and email filtering, so that one failure is not enough to expose the data.
- Protection of the data itself: encryption in transit and at rest, and masking or tokenization where full values are not needed.
- Watching for leaks: DLP (data loss prevention, tools that detect personal data leaking through email or devices). See What Is DLP? Data Loss Prevention and Shadow AI Risk.
- Detect, respond and recover: monitoring and alerting, a tested incident response plan, and backups that can really be restored. See Incident Response Plan Under NIST SP 800-61 Rev. 3.
Breach reporting and the 72-hour rule
Section 37(4) requires a controller to report a personal data breach to the PDPC office without delay and within 72 hours of becoming aware of it, as far as it is able to, unless the breach is unlikely to put people's rights and freedoms at risk. If the breach is likely to put them at high risk, the controller must also tell the affected data subjects (the people the data is about), together with ways to remedy the harm, without delay. The details are in the PDPC notification on breach reporting published on 15 December 2022.
The notification defines a personal data breach as a breach of security measures that leads to personal data being lost, accessed, used, changed, edited or disclosed without authority or wrongfully. The cause does not matter: intent, negligence, computer crime, cyber threats, errors and accidents all count. It names three types: confidentiality breach, integrity breach and availability breach (the data cannot be accessed, or is destroyed). In our reading, ransomware that locks the data is an availability breach.
Clause 5 sets what a controller must do when it is told, or finds out, that a breach has happened or probably has:
- Assess how reliable the information is and check the basic facts without delay, to see whether there is reason to believe a breach really happened.
- If the check shows a high risk to people's rights and freedoms, act at once, itself or by instructing a processor (an organization that handles personal data for the controller) or others, to prevent, stop or correct the breach.
- If there is reason to believe a breach really happened, report it to the PDPC office without delay and within 72 hours of becoming aware, as far as possible, unless there is no risk to people's rights and freedoms.
- If the risk is high, tell the affected people, with ways to remedy the harm, without delay.
- Take the measures needed to stop, respond to, correct or recover from the breach, and to prevent and reduce similar breaches in future, including a review of the security measures.
The 72 hours run from the moment the controller becomes aware of the breach. If necessary reasons make a report later than 72 hours, such as the first fact check, containment work or other unavoidable causes, clause 7 lets the controller ask the PDPC office to excuse the delay by explaining the reasons. The controller must still notify the office promptly, and no later than 15 days after becoming aware. Separately, clause 9 lets a controller claim that no report is needed if it can prove that the breach carries no risk to people's rights and freedoms, for example because the data cannot identify anyone or is unusable thanks to adequate technical measures. The controller must then give the office evidence, including details of its security measures.
A report to the PDPC office is made in writing, or electronically or another way the office specifies, and should state, as far as possible: the nature and type of the breach, with the number of people or records involved; the name and contact details of the data protection officer (DPO) or of the person assigned to coordinate; the likely impact; and the measures used or planned to prevent, stop or correct the breach. The PDPC website carries a breach report form (updated February 2026) and a January 2025 announcement of the electronic reporting channel. Check those pages for the current method before you need it.
If the controller uses a processor, clause 8 of the breach notification says the contract must require the processor to tell the controller about a breach without delay, within 72 hours of the processor becoming aware, as far as possible. Clause 6 of the security notification adds that the controller should consider requiring its processors to have appropriate security measures too.
To judge whether a breach carries a risk, or a high risk, clause 12 lists factors a controller may consider: the nature and type of the breach; the type of data; the volume of data; who is affected, for example minors, disabled people or other vulnerable persons; the severity of the impact and how well the mitigation works; the wider impact on the business or the public; the storage systems and security measures involved; and the controller's legal status and the size of its business.
What security teams should prepare (our own view)
- An owner and a clock: name who decides that a breach is real, and record the time the organization became aware, because the 72 hours run from then.
- A ready report: keep a draft that already has the fields listed in clause 6, with the DPO's contact details filled in.
- Evidence of scope: keep the logs and inventories needed to say which people and records were affected and what the impact is.
- Vendor contacts and contract terms: hold the contacts of your processors, and a contract term that requires them to tell you within 72 hours.
- Practice: rehearse a breach with legal, the DPO and communications staff, not only IT.
Penalties and what may change
Section 83 of the Act sets an administrative fine of up to 3 million baht for a controller that breaches section 37, among other sections. The PDPC has separate notifications on how administrative fines are decided, which we did not review.
The PDPC has also opened a public hearing on a draft amendment of the Act (the PDPC page is dated November 2025). We did not verify whether any amendment has since been enacted, so check the current text of section 37 and of the notifications before relying on this article.
Common mistakes
- Treating security measures as one policy document, with no logs, access reviews or other proof that they are applied.
- Waiting for the investigation to finish before the 72 hours start to count, although the law counts from when the controller becomes aware and asks for the details it has so far.
- Forgetting paper records and exported files, although the notification covers personal data in every form.
- Leaving the 72-hour reporting duty out of contracts with processors.
- Keeping no audit trail of who accessed personal data, so the organization cannot say who was affected.
- Treating compliance as a one-time job, although section 37(1) requires a review when necessary or when technology changes, and the security notification treats a breach as a reason to review (unless the breach carries no risk).
On paper
- Policy but no logscannot say who accessed data
- Rights never reviewedunneeded rights remain
- No breach clauseprocessor need not tell us
Provable
- Logs show who did whataffected people can be identified
- Regular access reviewsunneeded rights removed
- Contract sets 72 hoursprocessor must tell us
Start today
- List the data: note which systems hold personal data and who can access them.
- Check access: review the rights of the accounts that reach those systems and remove what is not needed.
- Turn on logs: make the systems that hold personal data record access, changes and deletions.
- Prepare the report: draft the clause 6 fields in advance, with contact names.
- Check contracts: see whether your contracts with processors require a breach report within 72 hours.
To see how your wider security program compares, try the self-assessment.
Scope and accuracy
This article is general information, not legal advice. Our statements about the Act and the two PDPC notifications come from the Royal Gazette texts published on the PDPC website, which we read in full. We did not read PDPC guidance documents, decisions or the fine-setting notifications. The mapping to technical controls and the preparation list are our own view. Thai law and PDPC notifications can change, so check the current texts, and ask a lawyer about your own situation.
References and further reading
- Personal Data Protection Act B.E. 2562 (PDPC page, Thai): the Act as published in the Royal Gazette; sections 37 and 83
- PDPC notification on security measures of data controllers B.E. 2565: the minimum standard, clauses 4 to 7
- PDPC notification on criteria and methods for breach reporting B.E. 2565: the 72-hour report, clauses 3 to 12
- PDPC announcement on the electronic channel for breach reports B.E. 2568: the office's channel notice, January 2025
- PDPC breach report form page: the form for reporting a breach, updated February 2026
- PDPC public hearing on a draft amendment of the Act: the draft amendment hearing page, November 2025