Reconix LogoReconix
Bank of Thailand

Navigate BOT Penetration Testing & iPentest with Confidence

BOT rules require banks, specialized financial institutions, and non-bank payment operators to pentest their Internet-facing systems at least once a year and after significant change. D-SIBs and commercial banks with high cyber inherent risk also fall under BOT's iPentest direction. We run the tests, write board-ready reports, and include one retest of every Critical and High finding.

Yearly
Minimum Pentest Frequency
D-SIB & High-Risk Banks
iPentest Directed For
Internet-Facing
Minimum Pentest Scope
Board-Ready
Our Reporting
Scope Your BOT Pentest
Attachment 2, ข้อ 6.6 and 6.7

The Foundation: BOT IT Risk Notification สกช. 5/2566

สกช. 5/2566 sets the IT risk rules for every financial institution under the Financial Institutions Businesses Act, including commercial banks and foreign bank branches, and every specialized financial institution (ข้อ 4), with the testing duties in attachment 2. Non-bank payment operators follow a parallel notification, สนช. 1/2564.

  • Pentest by independent internal or external experts, covering at least Internet-facing applications and networks, at least once a year and after significant change (att. 2 ข้อ 6.7)
  • Vulnerability assessment of all systems by risk, with critical systems assessed at least once a year and after significant change (att. 2 ข้อ 6.6)
  • BOT's Q&A expects the yearly pentest to cover public-network systems such as the bank website, mobile banking, and internet banking (Q&A item 3)
  • Security test before go-live, against the security process set in the technical specification (att. 2 ข้อ 7.2)
  • IT risk compliance self-assessment to BOT within 30 days of calendar year end, a compliance report separate from testing (ข้อ 10.5)
Intelligence-Led Guideline

iPentest: Intelligence-Led Testing for Priority Banks

iPentest is the intelligence-led penetration testing guideline BOT co-authored with TB-CERT. BOT circular ว. 1252/2562 sets which banks must adopt it.

  • BOT directed D-SIBs and commercial banks with high cyber inherent risk to adopt iPentest within 2563 (2020) (ว. 1252/2562)
  • Other commercial banks consider it according to their risk and readiness; for all banks and specialized financial institutions it is an optional enhancement under สกช. 5/2566
  • The guideline sets no fixed test frequency
  • Testers may be internal or hired from outside (guideline 1.2.3); the guideline says the bank should set tester selection criteria (1.6)
  • Our method: we build scenarios from current threat intelligence and measure how your team detects and responds

Who Is in Scope?

Scope follows the license. Each group below names the BOT rule that covers it.

Commercial Banks

Pentest and VA duties under สกช. 5/2566. D-SIBs and banks with high cyber inherent risk also fall under the iPentest direction in ว. 1252/2562.

Specialized Financial Institutions

Covered by สกช. 5/2566 (ข้อ 4). The mobile banking notification 4/2568 does not apply to them.

Foreign Bank Branches and Subsidiaries

BOT guidance lets them use the parent bank's pentest results if those cover every critical system the branch or subsidiary uses (สกช. 5/2566 Q&A item 2).

Non-Bank Payment System Operators

Systemically important or regulated payment systems under the Payment Systems Act. Testing duties sit in สนช. 1/2564, which covers non-banks only.

Payment Service and e-Money Operators

Every operator follows the Cyber Hygiene pentest and VA duties in สนช. 1/2564 ข้อ 5.1.6. e-Money apps that transfer to accounts at other providers also carry app controls under BOT 18/2568.

Which BOT rule sets your pentest cadenceThree routes. Commercial banks, foreign bank branches, and specialized financial institutions fall under สกช. 5/2566 attachment 2 ข้อ 6.7: pentest Internet-facing systems at least once a year and on significant change, by independent internal or external testers. D-SIBs and commercial banks with high cyber inherent risk also fall under circular ว. 1252/2562: adopt the iPentest guideline within 2563 (2020), with no fixed frequency; the สกช. 5/2566 yearly pentest still applies. Non-bank payment system, payment service, and e-money operators fall under สนช. 1/2564 ข้อ 5.1.6: pentest Internet-facing systems at least once a year and on every significant change, by independent experts.Institution typeCommercial banks,foreign bank branches,specialized financialinstitutionsBOT documentสกช. 5/2566att. 2 ข้อ 6.7Pentest cadenceInternet-facing systemsyearly and on significantchange; independentinternal or externaltestersInstitution typeD-SIBs and commercialbanks with high cyberinherent riskBOT documentว. 1252/2562iPentest guidelinePentest cadenceNo fixed frequency;adopt within 2563 (2020);the สกช. 5/2566 yearlypentest still appliesInstitution typeNon-bank paymentsystem, payment service,and e-money operatorsBOT documentสนช. 1/2564ข้อ 5.1.6Pentest cadenceInternet-facing systemsyearly and on everysignificant change;independent experts
Requirements

What the BOT Requires, Clause by Clause

Bank duties and payment operator duties sit in separate tables. Each row names its clause, marks it as a binding rule or a guideline, links to the BOT page that holds it, and states what our testing proves.

Bank and specialized financial institution duties by clause

Payment operator duties by clause

Testing Scope

The first three items are the BOT minimum: Internet-facing systems, with the bank website, mobile banking, and internet banking named in BOT's Q&A. We recommend scoping the rest by risk.

  • Mobile Banking Applications (iOS & Android)
  • Bank Website & Internet Banking
  • Other Internet-Facing Applications & Networks
  • API Interfaces & Core Banking Systems
  • Internal Network & Segmentation
  • Cloud Environments
  • Payment Gateway Infrastructure
  • Third-Party Vendor Integrations
Methodologies

Testing Standards We Work To

สกช. 5/2566 and สนช. 1/2564 set what to test and how often and prescribe no method; the iPentest guideline sets the method for banks directed to adopt it. For payment operators, BOT's Q&A points to a method such as OWASP (สนช. 1/2564 Q&A item 2).

OWASP WSTG / MASTG

Web and Mobile Application Security Testing Guides, the benchmarks we use for banking portals and mobile apps.

NIST SP 800-115

Technical Guide to Information Security Testing and Assessment, the framework behind our structured test phases.

Secure Code Review

BOT's IT risk implementation guideline recommends independent source code review on every development or change that touches important transactions (s.2.7.2).

Legal Framework

The Legal Backbone

Three statutes sit around the BOT rules, and each applies on its own terms.

Cybersecurity Act B.E. 2562 (2019)

Applies to organizations designated as Critical Information Infrastructure (CII); a financial institution is CII only once designated. Under the 2568 criteria, regulators propose lists and the NCSC designates them (2568 criteria ข้อ 8). The critical finance services BOT lists are retail deposit and withdrawal, BAHTNET, ICS cheque imaging, PromptPay, and the Single Payment System. Designated organizations run a cybersecurity risk assessment and a cybersecurity audit at least once a year (Act s.54), and report significant threats to NCSA within 24 hours (Cybersecurity Regulating Committee Notification on Criteria and Methods for Reporting Cyber Threats B.E. 2566, ข้อ 4, 5; Act s.57).

Personal Data Protection Act (PDPA) B.E. 2562 (2019)

Requires appropriate security measures for personal data, reviewed when necessary and when technology changes (s.37(1)). The law names no testing. Our view: testing is a common way to show those measures work.

Payment Systems Act B.E. 2560 (2017)

The act under which BOT supervises payment system and payment service operators. BOT rules under it require non-bank operators to pentest Internet-facing systems at least once a year (สนช. 1/2564 ข้อ 5.1.6) and to run an annual IT security audit, which is an audit separate from the pentest (สนช. 11/2561 ข้อ 4.2.2).

How a Reconix Pentest Runs the BOT Cycle

Scope, test, and the year-end self-assessment come from BOT rules. The CVSS 4.0 and PoC report and one retest of every Critical and High finding are what Reconix adds.

The Reconix pentest cycle under BOT rulesFive steps. Three come from BOT rules and two are Reconix additions. Rule step, Scope: Internet-facing applications and networks (สกช. 5/2566 attachment 2 ข้อ 6.7; สนช. 1/2564 ข้อ 5.1.6). Rule step, Test: independent testers. Reconix addition, Report: each finding with CVSS 4.0 severity and a PoC. Reconix addition, Retest: one retest of every Critical and High finding after your team fixes them. Rule step, Self-assessment: sent to BOT within 30 days of calendar year end (สกช. 5/2566 ข้อ 10.5, สนช. 1/2564 ข้อ 7.3).1ScopeInternet-facingapplications and networksBOT rule2TestIndependent testersBOT rule3ReportEach finding with CVSS4.0 severity and a PoCReconix addition4RetestOne retest of everyCritical and Highfinding after yourteam fixes themReconix addition5Self-assessmentTo BOT within 30 daysof calendar year endBOT rule
Readiness Checklist

BOT Compliance Readiness Checklist

Check your institution against the BOT rules above before the next examination cycle. Items marked as recommended are our advice, not BOT rules.

  • Yearly pentest of Internet-facing systems scheduled, plus a test after each significant change (สกช. 5/2566 ข้อ 6.7 or สนช. 1/2564 ข้อ 5.1.6)
  • Testers independent of the systems they test, internal or external
  • Vulnerability assessment of all systems by risk, critical systems at least once a year (ข้อ 6.6)
  • Bank website, mobile banking, and internet banking inside the pentest scope (Q&A item 3)
  • Security test completed before each go-live (ข้อ 7.2)
  • D-SIB or high cyber inherent risk bank: iPentest adopted per ว. 1252/2562
  • Mobile banking app controls under BOT 4/2568 in place: pinning, anti-tampering, obfuscation, rooted or jailbroken device blocking
  • IT contingency plan reviewed and tested at least once a year (สกช. 5/2566 att. 2 ข้อ 9.5)
  • IT risk self-assessment sent to BOT within 30 days of calendar year end
  • Payment operators under the สนช. 1/2564 IT risk rules: copy of IT audit results sent to BOT within 45 days of audit completion (att. 4); other payment operators: the same under the สนช. 11/2561 guideline
  • Critical and high findings fixed and retested (recommended)
  • Board-level summary of results presented (recommended)
Deliverables

What You Receive: BOT-Ready Deliverables

Every engagement produces the documentation your team needs for the next BOT examination.

Executive Board-Level Summary

A non-technical risk overview designed for board of directors presentation.

Technical Findings with CVSS Scoring

Detailed vulnerability report with industry-standard severity ratings.

Prioritized Remediation Roadmap

An actionable fix plan ordered by risk severity and business impact.

Retest Evidence

The result of the included retest: one retest of every Critical and High finding.

Assessment Report Mapped to BOT Clauses

The full report, with each finding mapped to the สกช. 5/2566 or สนช. 1/2564 clause it relates to.

BOT Penetration Testing FAQs

Answers to the most common questions about BOT penetration testing, iPentest, and compliance timelines.

Free tool

How mature is your security program?

Answer 14 questions and see your NIST CSF 2.0 tier and top 3 gaps on screen. No signup needed.

Stay Ahead of Your Next BOT Examination

Get penetration testing and iPentest assessments mapped to the BOT clauses that apply to you, with board-ready reports and a clear remediation roadmap.

Reconix is the proof-first offensive security specialist for digital businesses in Thailand where a breach ends the business.