Penetration Testing Requirements in Thailand: Bank of Thailand, SEC, OIC and NCSA
Published by Zero Hunt, an autonomous AI red team on an on-premise appliance running private AI: automated penetration testing for networks and infrastructure, black-box or gray-box, with a human approving every step that matters.
Short definition
Thai banks must penetration test internet-facing systems at least once a year and after any significant change, and assess vulnerabilities in critical systems on the same rhythm (BOT FPG 19/2560). Critical information infrastructure operators need a yearly cybersecurity risk assessment and audit under the Cybersecurity Act B.E. 2562.
Why this matters now
On 10 November 2026 the Bank of Thailand met bank CIOs and told them to fix remaining weaknesses, share threat information faster and report attempted attacks daily. The written rules behind that message are older and specific: a yearly penetration test for banks, a yearly audit for critical infrastructure, and third-party testing duties that reach cloud and service providers. For a security team, the open questions are how to keep testing between the yearly checkpoints and where the test data ends up.
Key points
- ▸BOT Notification FPG 19/2560 (in force 1 April 2018): penetration test of internet-facing systems at least once a year and on any significant change, by an independent internal or external expert.
- ▸The same notification requires a vulnerability assessment of critical IT systems at least once a year and on significant change, and an IT audit at least once a year.
- ▸BOT SorNorSor 21/2562 extends testing to third parties: the bank must make sure providers run vulnerability management and penetration testing, and must review the scope and results.
- ▸Cybersecurity Act B.E. 2562 Section 54: critical information infrastructure organizations run a cybersecurity risk assessment and examination at least once a year and report to the NCSA within 30 days.
- ▸The SEC sets risk-based penetration-test frequencies for capital-market firms (eased for small operators from 1 January 2025); the OIC has proposed a yearly pentest for insurers, still a draft in 2026.
Banks: Bank of Thailand Notification FPG 19/2560
BOT Notification FPG 19/2560 (สนส. 19/2560) on regulations on information technology risk of financial institutions was issued under Section 41 of the Financial Institution Business Act B.E. 2551 and applies to all financial institutions under that Act. It was announced on 20 December 2017 and took effect on 1 April 2018. The testing duties sit in clause 5.3.2 on IT security:
- (6.6) Vulnerability management. A vulnerability assessment of critical IT systems at least once a year and whenever there is a significant change.
- (6.7) Penetration test. It must cover internet-facing systems and run at least once a year and whenever there is a significant change. It may be done by an independent internal or external expert.
- (6.5) Security monitoring. Processes or tools to detect suspicious events and threats against critical systems.
Clause 5.3.5 adds an IT audit at least once a year, by internal auditors, external auditors or specialists who are independent of IT operations and IT risk management.
The BOT's question-and-answer annex adds one practical point for foreign groups: a subsidiary of a foreign bank that runs on its parent's core banking systems may use the parent's penetration test results, but the test must cover all critical systems the subsidiary uses.
In practice: the yearly test is a minimum. "Significant change" triggers a new test, so a bank that ships changes to internet-facing services often will test more than once a year.
Third parties and cloud: BOT SorNorSor 21/2562
BOT Notification SorNorSor 21/2562 on criteria of IT risk governance of financial institutions carries Third Party Risk Management Implementation Guidelines. As reproduced in Google Cloud's compliance mapping of the notification:
- Clause 7.1 requires a written risk assessment before and after using, connecting to or giving data access to a third party, and on significant change. The listed risks include in-country and cross-border risk where the third party is located or operates.
- Clause 10.3 requires material third-party arrangements to be assessed at least once a year, with a report to the board or executives.
- Clause 12.10 requires the bank to make sure the third party runs vulnerability management and penetration testing in line with generally accepted international standards and the bank's own policy, and to audit the scope and results so that the tests cover all systems the bank uses or connects to.
FPG 19/2560 also requires IT outsourcing to follow the BOT's separate IT outsourcing notification. For a testing service, this means the pentest provider is itself a third party to be assessed, and a cloud platform that stores test results is an outsourcing arrangement.
Testing duties at a glance
| Rule | What must be tested | How often | Who may test | |
|---|---|---|---|---|
| Banks | BOT FPG 19/2560 cl. 5.3.2 (6.7) | Penetration test of internet-facing systems | At least once a year and on significant change | Independent internal or external expert |
| Banks | BOT FPG 19/2560 cl. 5.3.2 (6.6) | Vulnerability assessment of critical IT systems | At least once a year and on significant change | Not specified |
| Banks | BOT FPG 19/2560 cl. 5.3.5 | IT audit | At least once a year | Auditors independent of IT operations and IT risk |
| Banks' third parties | BOT SorNorSor 21/2562 | Provider's vulnerability management and penetration testing | Material providers assessed at least yearly | Provider; the bank reviews scope and results |
| Capital-market firms | SEC IT rules (amended 2025) | Penetration test and vulnerability assessment | Risk-based; lower for small operators | Not verified |
| Insurers | OIC draft amendment (2026) | Vulnerability assessment and penetration test | At least annually (proposed) | Not specified |
| CII organizations | Cybersecurity Act s. 54 | Risk assessment and cybersecurity examination | At least once a year | Information security, internal or external independent auditor |
Rule
- Banks
- BOT FPG 19/2560 cl. 5.3.2 (6.7)
- Banks
- BOT FPG 19/2560 cl. 5.3.2 (6.6)
- Banks
- BOT FPG 19/2560 cl. 5.3.5
- Banks' third parties
- BOT SorNorSor 21/2562
- Capital-market firms
- SEC IT rules (amended 2025)
- Insurers
- OIC draft amendment (2026)
- CII organizations
- Cybersecurity Act s. 54
What must be tested
- Banks
- Penetration test of internet-facing systems
- Banks
- Vulnerability assessment of critical IT systems
- Banks
- IT audit
- Banks' third parties
- Provider's vulnerability management and penetration testing
- Capital-market firms
- Penetration test and vulnerability assessment
- Insurers
- Vulnerability assessment and penetration test
- CII organizations
- Risk assessment and cybersecurity examination
How often
- Banks
- At least once a year and on significant change
- Banks
- At least once a year and on significant change
- Banks
- At least once a year
- Banks' third parties
- Material providers assessed at least yearly
- Capital-market firms
- Risk-based; lower for small operators
- Insurers
- At least annually (proposed)
- CII organizations
- At least once a year
Who may test
- Banks
- Independent internal or external expert
- Banks
- Not specified
- Banks
- Auditors independent of IT operations and IT risk
- Banks' third parties
- Provider; the bank reviews scope and results
- Capital-market firms
- Not verified
- Insurers
- Not specified
- CII organizations
- Information security, internal or external independent auditor
Summarized from the texts and summaries listed under Sources, as read on 20 November 2026. Check the official Thai text and your regulator's guidance before relying on it.
Capital-market firms: SEC
The Securities and Exchange Commission regulates securities firms, asset managers, digital asset operators and other capital-market businesses through its Rules on Establishment of Information Technology System and the accompanying SEC Office guidelines.
- The guidelines cover vulnerability assessment and penetration testing; firms define the scope and frequency of technical vulnerability assessments.
- Amendments in force since 1 January 2025 align the requirements with each operator's risk profile. According to the SEC's announcement as reported by InfoQuest, cyber hygiene measures for small operators were adjusted, including the penetration-test frequency.
We could not read the current Thai text from the SEC site, so this guide does not state a number. Check the frequency that applies to your licence category in the current notification before planning the year.
Insurers: OIC
The Office of Insurance Commission issued Notifications on criteria for the supervision and management of IT risks for life and non-life insurance companies B.E. 2563 (2020), in force since 1 January 2021. They cover IT security, IT audit (with the audit plan reviewed at least once a year or on significant change), outsourcing and incident reporting, but contain no explicit penetration-testing clause.
In May 2026 the OIC put a revised notification out for public consultation (8 May to 9 June 2026). According to Tilleke & Gibbins, the draft makes vulnerability assessment and penetration testing mandatory at least annually, requires external IT auditors to hold CISA or ISO/IEC 27001 lead auditor certification, and adds chapters on data and AI governance. It was still a draft when this guide was written; plan for it, but check the final text.
Critical information infrastructure: Cybersecurity Act B.E. 2562 and NCSA
The Cybersecurity Act B.E. 2562 (2019), published in the Government Gazette on 27 May 2019, lets the National Cyber Security Committee designate critical information infrastructure (CII) organizations in eight areas, including banking and finance, IT and telecommunications, energy and public health (Section 49).
- Section 54. CII organizations must carry out a cybersecurity risk assessment, including an examination by an information security auditor, an internal auditor or an external independent auditor, at least once per year, and send a summary to the NCSA within 30 days.
- CRC notification on CII duties (issued 22 February 2024, in force 20 June 2024): yearly risk assessment and yearly cybersecurity audit by a third-party or internal auditor, with reports to the NCSA within 30 days and no later than 31 January of the following year; incident reports within 24 hours. Not reporting a cyber threat without reasonable cause can be fined up to THB 200,000 (Section 73).
- NCSC minimum standards B.E. 2566 (in force 18 January 2025): organizations classify each data or information system by confidentiality, integrity and availability, apply the minimum measures for that category, and review the category at least every three years.
The Act does not use the words "penetration test". The yearly assessment and audit need evidence that controls work, and testing is the usual way to produce it. A draft amendment released in July 2025 would extend NCSA oversight to cloud and data centre providers that host CII data; it was still in the legislative process.
Personal data: PDPA
The Personal Data Protection Act B.E. 2562 has been fully in force since 1 June 2022. The PDPC Notification on Security Measures of the Data Controller B.E. 2565, in force since 21 June 2022, requires organizational and technical measures matched to the level of risk, and a review of those measures when necessary, when technology changes or after a breach.
The PDPA does not prescribe penetration tests. Enforcement has started, though: in August 2025 the PDPC published fines of up to THB 7 million, and the failings it listed included missing security measures and no risk assessment or review of them. A test record is one way to show the review happened.
Data location and the testing tool itself
None of the rules reviewed here imposes a general duty to keep all data in Thailand. They regulate the question instead:
- BOT SorNorSor 21/2562 requires banks to assess in-country and cross-border risk of every third party, and FPG 19/2560 sends IT outsourcing through the BOT outsourcing notification.
- PDPA Sections 28 and 29 allow personal data to leave Thailand only to destinations with adequate protection or under safeguards such as binding corporate rules or standard contractual clauses; the PDPC notifications took effect on 24 March 2024.
- The draft Cybersecurity Act amendment would bring cloud and data centre providers that host CII data under NCSA oversight.
A penetration test produces credentials, network maps and step-by-step evidence of how to get into the bank. A SaaS testing platform that stores them abroad, or an AI model hosted overseas that reads them, is a third party with cross-border risk under the BOT rules and may involve a PDPA transfer. An appliance that runs inside your own data centre, on its own models, keeps that data on your network. See the sovereign AI red team guide.
Compliance checklist
- Schedule the yearly penetration test of internet-facing systems and the yearly vulnerability assessment of critical systems, and define what counts as a significant change that triggers a new test.
- Record who tested and why they are independent of the team that runs the systems.
- For every testing or security provider, run the third-party risk assessment of SorNorSor 21/2562, including cross-border risk, and review the scope and results of the provider's own tests.
- If you are a CII organization, plan the yearly risk assessment and audit, and the NCSA reports within 30 days and by 31 January.
- For SEC or OIC scope, confirm the frequency for your licence category or the final OIC text.
- Check where every security tool stores test data and whether it creates a PDPA transfer.
- Re-test fixes and keep the evidence for the auditor and the regulator.
The requirements by regulation page compares Thailand's approach with other jurisdictions.
Where Zero Hunt fits
Zero Hunt is an autonomous AI red team on an on-premise appliance: it runs black-box and gray-box penetration tests of networks and infrastructure from inside your data centre, on its own models with no third-party LLM, so no customer data leaves your network. A human stays in the loop: intrusive steps wait for operator approval. Evidence records are signed and hash-chained, and exported reports are ECDSA-signed, which helps when an auditor asks what was tested and when.
Zero Hunt maps findings to 34 frameworks, including ISO/IEC 27001, PCI DSS and NIST CSF. It does not ship a BOT-, SEC-, OIC- or NCSA-specific mapping or report template; your team or partner maps the evidence to those rules. Zero Hunt holds no Thai certification or registration and is not an auditor, so it does not replace the yearly audit under Section 54 or FPG 19/2560; it lets you test between those checkpoints.
Questions
Does the Bank of Thailand require an annual penetration test? Yes. FPG 19/2560 requires a penetration test of internet-facing systems at least once a year and whenever there is a significant change, and a vulnerability assessment of critical IT systems on the same rhythm.
Must an external firm do the test? Not for banks: FPG 19/2560 allows an independent internal or external expert. The IT audit must be done by auditors independent of IT operations and IT risk.
Can a Thai subsidiary use its foreign parent's pentest? According to the BOT's Q&A, yes, if the test covers all critical systems the subsidiary uses.
Does the Cybersecurity Act require penetration testing? Not by name. Section 54 requires a yearly risk assessment and cybersecurity examination for CII organizations; testing is the usual evidence behind it.
Can we use a cloud or SaaS pentest platform hosted outside Thailand? There is no blanket ban in the rules reviewed here, but a bank must assess the provider's cross-border risk under SorNorSor 21/2562, and personal data in test results may trigger PDPA transfer rules. Check with compliance.
What about insurers? The 2020 OIC notifications have no explicit pentest clause; a 2026 draft would require vulnerability assessment and penetration testing at least annually.
Sources
- BOT Notification FPG 19/2560, unofficial English translation (bot.or.th)
- BOT Notification FPG 12/2564, unofficial English translation (bot.or.th)
- BOT SorNorSor 21/2562: Google Cloud compliance mapping
- Nation Thailand: Thai banks boost IT spending and 24-hour cyber monitoring (10 Nov 2026)
- Thailand Business News: the SEC revises IT system rules (Dec 2024)
- InfoQuest: SEC adjusts IT requirements for capital-market operators (Thai)
- Thales: SEC Guidelines for the Provision of IT Systems
- Tilleke & Gibbins: OIC IT risk criteria for insurers (2021)
- Tilleke & Gibbins: OIC proposes amendments to IT risk rules (2026)
- Cybersecurity Act B.E. 2562, unofficial English translation
- ThaiCERT: critical information infrastructure
- Tilleke & Gibbins: Thailand details CII organizations' cybersecurity duties
- Tilleke & Gibbins: Thailand lays out new cybersecurity standards
- Tilleke & Gibbins: draft amendments to the Cybersecurity Act (2025)
- Tilleke & Gibbins: first PDPA subordinate regulations
- Tilleke & Gibbins: eight PDPA fines (2025)
- Tilleke & Gibbins: cross-border personal data transfer rules
Goes deeper
Want this against your environment?
Book a 30-minute scoping call — we will map this directly to your current compliance scope and threat profile.