You are using an outdated browser and your browsing experience will not be optimal. Please update to the latest version of Microsoft Edge, Google Chrome or Mozilla Firefox. Install Microsoft Edge

March 29, 2024

Thailand Details CII Organizations’ Cybersecurity Duties

Thailand’s Cybersecurity Regulating Committee (CRC) released a notification under the Cybersecurity Act on February 22, 2024, setting key operational obligations for critical information infrastructure (CII) organizations. The notification takes effect on June 20, 2024.

CII organizations are state or private entities that carry out services related to national security, public services, banking and finance, information technology and telecommunications, transportation and logistics, energy and public utilities, or public health. CII organizations will be identified by the National Cyber Security Committee (NCSC) and notified of their status.

The key obligations of CII organizations are laid out below.

Reporting to the National Cyber Security Agency (NCSA)

CII organizations must provide the following to the NCSA:

  • A list of executive and operational staff, along with emergency contacts who can be reached within 60 minutes in the event of a cyber threat. The NCSA must be notified of any updates to this list within 15 days following any changes.
  • A list of internal departments or individuals who are the responsible persons, owners, and holders of the computer systems, along with emergency contacts who can be reached within 60 minutes in the event of a cyber threat. The NCSA must be notified of any updates to this list at least 7 days prior to any changes (or within 15 days after the change if there is a necessary reason).

Policies, Guidelines, and Procedures

As specified in the National Cyber Security Committee (NCSC) guidelines, CII organizations must prepare the following internal documents by June 20, 2025:

  • Cybersecurity practice guidelines, consisting of an inspection plan, risk assessment, and incident response plan.
  • Cybersecurity standards framework, consisting of measures for risk identification, risk prevention, threat detection and monitoring, incident responses, and resilience and recovery.

CII organizations must also prepare the following:

  • Mechanisms, procedures, and steps for monitoring and detecting cyber threats or incidents related to critical infrastructure cybersecurity, as well as cybersecurity resolution systems as designated by the NCSC or CRC. These must comply with the standards set by the regulators (the specific regulator depends on the characteristics of the organization) and the NCSC guidelines.
  • Internal methods and procedures for cybersecurity risk management, which must identify risk appetite, conform with the cybersecurity management policy announced by the NCSC, and be approved by the regulator before finally being submitted to the NCSA.

Ongoing Compliance

CII organizations are also responsible for the following ongoing requirements:

  • Submit an annual report covering the number and types of cyber threats that arose during the relevant reporting period, as well as the causes and effects of the cyber threats, problems and obstacles in operation, and policy recommendations. The first report must be submitted by January 31, 2025, and by January 31 of each year thereafter.
  • Review the cybersecurity guidelines and standards framework described above at least once a year, or whenever there is a significant change to cybersecurity operations.
  • Review the methods and procedures for cybersecurity risk management described above at least once a year, or when there is a significant change to cybersecurity operations.
  • Review the cybersecurity mechanisms described above at least once a year.
  • Conduct a cybersecurity risk assessment in accordance with the NCSC guidelines. The report must be submitted to the NCSA within 30 days of completion, but no later than January 31 of the following year. The report must also be submitted to the regulator. This report is distinct from the CII organization’s own risk assessment report.
  • Have a third-party or internal cybersecurity auditor conduct a cybersecurity audit at least once a year. The auditor’s report must be submitted to the NCSA within 30 days of completion, but no later than January 31 of the following year. A summary of the report must also be delivered to the regulator.
  • Organize a business continuity plan training program at least once a year to evaluate the plan’s effectiveness in addressing cyber threats.

Cybersecurity Incident Response

If a cybersecurity incident occurs, CII organizations must:

  • Run detection and analysis procedures as outlined in the NCSC guidelines.
  • Notify and submit a report to both the NCSA and the regulator within 24 hours.
  • Cooperate with the collection and investigation of evidence relating to the cybersecurity incident by officers under the Cybersecurity Act.

The penalty for a CII organization not reporting a cybersecurity incident that has a significant impact on their systems to the NCSA and the regulator without reasonable cause is a fine of up to THB 200,000 (approx. USD 5,500).

Other Obligations

In addition, CII organizations must do the following:

  • Mitigate cybersecurity risks and implement plans to deal with cybersecurity incidents.
  • Collaborate with the NCSC, CRC, and NCSA to organize cyber threat response training, including supplying necessary information for the planning and execution of the training.
  • Participate in cyber threat readiness tests conducted by the NCSA to ensure preparedness for handling cybersecurity incidents.
  • Prepare a business continuity plan in accordance with the prescribed criteria to ensure the ongoing provision of critical services.
  • If evidence suggests a cybersecurity incident may have occurred, evaluate the computer systems, data, and surrounding circumstances in order to determine whether the incident occurred and its impact on the organization’s information system.
  • State CII organizations must establish a computer emergency response team (CERT) for CII organizations and CII services in their sector, or promptly notify the NCSC of the reason for its inability to do so.
  • Cooperate with the relevant sectoral CERT as well as the Thailand Computer Emergency Response Team (ThaiCERT) on cybersecurity incident responsiveness, dealing with the effects of cyber threats, and other cybersecurity issues.
  • Comply with any orders or notifications issued by the NCSC or the CRC.

The NCSA will review the obligations under this notification at least every two years, or when there is a significant change regarding cybersecurity.

For more information on compliance with Thailand’s cybersecurity regulations, please contact Nopparat Lalitkomon at [email protected], Napassorn Lertussavavivat at [email protected], or Nitcharat Siraprapasiri at [email protected].

RELATED INSIGHTS​ 

June 25, 2026
On June 18, 2026, Thailand’s Office of the Personal Data Protection Committee (PDPC) published two notifications in the Government Gazette establishing Thailand’s first formal certification framework for personal data protection standards under the Personal Data Protection Act B.E. 2562 (2019) (PDPA). The notifications, which took immediate effect, introduce a voluntary certification framework aimed at promoting accountability, strengthening organizational data protection governance, and aligning Thailand more closely with international frameworks that recognize certification as a key compliance tool. Certification Criteria The first notification sets out the assessment criteria for organizations seeking certification. Applicants must undergo an evaluation against a framework comprising four assessment categories, 10 focus areas, and 128 assessment criteria covering key elements of a privacy management program. These include: Organizational oversight and internal policies and procedures. Human resource development, including staff training and awareness programs. Clearly defined operational processes and procedures covering data subject rights, transparency obligations, records of processing activities, and lawful basis management, as well as contractual safeguards such as data-processing and data-sharing agreements and risk assessments, including Data Protection Impact Assessments. Technical measures encompassing data security controls and breach response capabilities Based on the assessment results, organizations may be awarded either a PDPA Compliance Certificate or a higher-level PDPA Certificate accompanied by a certification mark. Application and Assessment Process The second notification establishes the application and assessment process for obtaining certification. Eligible applicants include government agencies and private-sector entities that demonstrate sufficient privacy governance maturity and meet the prescribed eligibility requirements. Applicants must submit their applications along with supporting documentation for review. Upon receiving an application, the Office of the PDPC will conduct a detailed evaluation, which may include both documentary review and on-site inspections. Incomplete applications may be rejected, though applicants are typically given a limited period to correct deficiencies before a final decision
June 23, 2026
On May 26, 2026, Thailand’s Department of Land Transport (DLT) published for public consultation a draft amendment to the Ministerial Regulation on Electronic Ride-Hailing Vehicles that would, for the first time, allow juristic persons (legal entities) to register vehicles as electronic ride-hailing cars—a right that currently belongs exclusively to natural persons, limited to one person per one vehicle. If finalized in its current form, the regulation would significantly expand the supply side of Thailand’s ride-hailing market by enabling corporate fleet operators to enter the space. The public comment period is open through June 24, 2026. Key Principles Under the Draft Regulation Under the proposed amendment, juristic persons that maintain a fleet of at least 50 vehicles will be permitted to register vehicles as electronic ride-hailing cars. This represents a fundamental shift from the current framework, which restricts registration to individual natural persons on a one-person-one-car basis. Vehicle Specifications Corporate-owned ride-hailing vehicles must meet the following requirements: Be brand new from the factory, or no more than two years old from first registration with no more than 20,000 km of use. Not be a vehicle that has been reconstructed or repaired after involvement in a serious accident affecting safety—a standard consistent with public transport vehicles (RorYor. 6). Be classified as small, medium, or large in accordance with ministerial or director-general specifications. The vehicles may be equipped with safety devices such as interior or exterior cameras (video/photo recording) and can retain the original factory color of the vehicle body (no mandatory color change is required). License Plates Corporate ride-hailing vehicles will use license plates of the same size, characteristics, and color as those for private passenger vehicles not exceeding seven seats (RorYor. 1), rather than public transport plates. Potential Impact The government has stated that the regulation is intended to: Promote
June 23, 2026
On May 14, 2026, Thailand published a ministerial regulation in the Government Gazette to prescribe measures for prevention and suppression of technology crimes. The regulation creates a comprehensive procedural framework for returning money and digital assets to victims of technology crimes. It will take effect 90 days after publication (in mid-August 2026), giving affected entities a limited window to prepare. Mandatory Reporting Obligations for Financial Institutions When a deposit account, e-money account, or digital asset wallet is frozen in connection with a technology crime, the relevant financial institution or business operator must report transaction data to the Anti-Money Laundering Office (AMLO) via AMLO’s designated electronic system. Required data elements include account numbers (sender and receiver), names, identification or passport numbers, legal entity registration numbers, phone numbers, remaining balance, damage amount, transaction reference numbers, and the bank case ID. Institutions that already share data through the information-sharing system under the emergency decree are deemed to have satisfied this reporting obligation, creating an incentive for platform participation. When the Royal Thai Police or the Department of Special Investigation seize or freeze assets related to technology crimes, they must provide AMLO with investigation reports, complaint evidence, money-trail data, and account statements. Notification and Claims Process Once the AMLO secretary-general approves verified reports of a technology crime, the account information of persons connected to the crime will be published in the Government Gazette, triggering a 90-day window for victims to file claims and for related persons to file objections. Officers will also publish details on AMLO’s electronic media and send registered mail to identified victims, which will be deemed received after 7 days domestically or 15 days internationally. Victims have 90 days from the date the crime is published in the Government Gazette to file claims through AMLO’s electronic system. Claims must include
June 15, 2026
The surge in AI development has led to a desperate demand for large, high-quality training data. However, real-world data can be expensive to collect, difficult to access, and often subject to strict privacy and regulatory constraints. Synthetic data, which consists of artificially generated records that replicate the statistical properties of real-world data without reproducing specific individuals’ information, provides an appealing solution by generating artificial datasets at scale without relying on identifiable personal information. It combines speed, cost efficiency, and regulatory compliance, making it a sensible alternative for organizations seeking to reduce risks while maintaining data utility. When properly anonymized, synthetic datasets may fall outside the scope of laws such as the EU’s General Data Protection Regulation (GDPR) or Thailand’s Personal Data Protection Act (PDPA), reducing compliance burdens while still supporting high-quality model training. However, relying on synthetic data without rigorous legal due diligence could be a strategic mistake. It replaces one set of known risks (scraping, direct privacy liability) with a new set of complex liabilities. The narrative that synthetic data is a “silver bullet” for privacy and IP compliance is dangerous and could be misleading. While synthetic data addresses data scarcity, it also introduces new legal uncertainties. Legal counsel should anticipate downstream risks arising from compromised data sources. Models trained on unlawfully obtained data may need to be decommissioned, even if their outputs appear lawful. What is synthetic data? Synthetic data refers to artificially generated information created using AI techniques such as deep learning and generative models. Instead of copying real records, it reproduces the statistical patterns and relationships found in the original dataset. Synthetic data generally falls into three categories: Fully synthetic data – Entirely new data points generated from learned patterns. The model studies the structure of the original data and produces records that resemble real-world