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.
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)
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.
Banks with Mobile Banking Apps
See the BOT 4/2568 app controls on our BOT Mobile Banking Security page.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
| Clause | What the rule says | What Reconix testing proves | Source |
|---|---|---|---|
| สกช. 5/2566 att. 2 ข้อ 6.7 | Binding rule You must have independent internal or external experts pentest at least your Internet-facing applications and networks, at least once a year and on significant change, such as a significant change to your systems, risks, or international IT standards. | Penetration Testing of your Internet-facing applications and networks, by testers external to and independent of your organization, shows which flaws an attacker can exploit. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification สกช. 5/2566 on IT Risk Governance of Financial Institutions and Specialized Financial Institutions, with attachments and Q&A (rev. 24 Sep 2568), p. 18 (opens in a new tab) |
| สกช. 5/2566 Q&A ข้อ 3 | Guideline BOT's Q&A states which systems it expects the yearly pentest to cover: systems connected to public networks, such as the bank website, mobile banking, and internet banking. | Penetration Testing of your bank website, mobile banking, and internet banking, by testers external to and independent of your organization, shows which flaws an attacker can exploit. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification สกช. 5/2566 on IT Risk Governance of Financial Institutions and Specialized Financial Institutions, with attachments and Q&A (rev. 24 Sep 2568), p. 32 (opens in a new tab) |
| สกช. 5/2566 att. 2 ข้อ 6.7 para 2 | Binding rule BOT may order you to appoint an independent external expert to run an additional pentest when it finds your results incomplete, finds the scope or method misses generally recognized significant vulnerabilities, or deems it necessary. Your duty applies only once BOT orders it. If BOT orders it | Reconix testers are external to your organization and independent of it, the kind of expert BOT can order you to appoint. You receive: Report naming each tester and stating their independence from your system owners | BOT Notification สกช. 5/2566 on IT Risk Governance of Financial Institutions and Specialized Financial Institutions, with attachments and Q&A (rev. 24 Sep 2568), p. 18 (opens in a new tab) |
| ว. 1252/2562 para 2, D-SIBs; iPentest guideline 1.2.3, 1.6 | Binding rule BOT directed D-SIBs and commercial banks with high cyber inherent risk to adopt the iPentest guideline within 2563 (2020). The guideline sets no fixed frequency. Testers may be internal or hired from outside, and the bank should set clear tester selection criteria covering certifications, experience, and ethics (guideline 1.6). If D-SIB or high cyber inherent risk (commercial banks) | Red Teaming builds each scenario from threat intelligence, so you can run it toward the iPentest guideline. Whether Reconix testers meet your tester criteria under guideline 1.6 is your bank's decision. You receive: Report with an executive summary, a timeline of Red Team actions, successful and unsuccessful attack paths, a map of detection gaps, and a prioritized remediation roadmap | BOT Circular ว. 1252/2562 on Intelligence-led Penetration Testing (iPentest), cover letter, p. 1 (opens in a new tab) |
| ว. 1252/2562 para 2, other banks; สกช. 5/2566 att. 2 ข้อ 6.7 | Guideline For commercial banks that are neither D-SIBs nor high cyber inherent risk, BOT's circular asks each bank to consider iPentest by its own risk level and readiness. สกช. 5/2566 att. 2 ข้อ 6.7 lets every bank and specialized financial institution apply iPentest to make its pentest more realistic. If neither D-SIB nor high cyber inherent risk | Red Teaming builds each scenario from threat intelligence, so you can run it toward the iPentest guideline. Whether Reconix testers meet your tester criteria under guideline 1.6 is your bank's decision. You receive: Report with an executive summary, a timeline of Red Team actions, successful and unsuccessful attack paths, a map of detection gaps, and a prioritized remediation roadmap | BOT Circular ว. 1252/2562 on Intelligence-led Penetration Testing (iPentest), cover letter, p. 1 (opens in a new tab) |
| สกช. 5/2566 att. 2 ข้อ 6.6 | Binding rule You must run a vulnerability assessment of every system by risk level. Critical systems: at least once a year and on significant change. | Vulnerability Assessment of your critical systems, and of others by risk, finds known CVEs and misconfigurations on the yearly cycle. You receive: Report stating scope and test dates; each finding with CVSS 4.0 severity and remediation steps | BOT Notification สกช. 5/2566 on IT Risk Governance of Financial Institutions and Specialized Financial Institutions, with attachments and Q&A (rev. 24 Sep 2568), p. 18 (opens in a new tab) |
| สกช. 5/2566 att. 2 ข้อ 7.2 | Binding rule You must test a system before go-live, including a security test against the security process set in your technical specification. The clause does not require independent testers. | Penetration Testing of your new system before launch shows what an attacker could exploit before your users can reach it. It is evidence toward the security test your technical specification sets, which stays your duty. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification สกช. 5/2566 on IT Risk Governance of Financial Institutions and Specialized Financial Institutions, with attachments and Q&A (rev. 24 Sep 2568), p. 20 (opens in a new tab) |
| IT Risk Management Guideline 2.7.2 | Guideline The guideline says that, before go-live, security testing should include a vulnerability assessment, plus a pentest by external experts where the system connects to external networks. It also lists an independent source code review each time you develop or change the part of a system that handles important transactions. | Vulnerability Assessment and external Penetration Testing of your system before go-live show which flaws exist and which an attacker can exploit. Secure Code Review by Reconix engineers, who are independent of your developers, checks the code behind important transactions. You receive: Vulnerability Assessment report with CVSS 4.0 severity and remediation steps per finding; Penetration Testing report with CVSS 4.0 severity and a PoC per finding, plus one retest of every Critical and High finding; Secure Code Review report with line-specific references for developers | BOT IT Risk Management Implementation Guideline (bundled in the สกช. 5/2566 PDF from p.39), p. 72 (opens in a new tab) |
| สกช. 5/2566 ข้อ 10.5 | Binding rule You must send BOT your assessment of compliance with this notification within 30 days of calendar year end. It is a compliance self-assessment, not a test. | No Reconix assessment covers this duty. Group service from BAYCOMS (opens in a new tab) and ECOP (opens in a new tab): governance, risk and compliance (GRC) | BOT Notification สกช. 5/2566 on IT Risk Governance of Financial Institutions and Specialized Financial Institutions, with attachments and Q&A (rev. 24 Sep 2568), p. 9 (opens in a new tab) |
| สกช. 5/2566 att. 2 ข้อ 9.5 | Binding rule You must review and test your IT contingency plan at least once a year and on every significant change. | No Reconix assessment covers this duty. Group service from BAYCOMS (opens in a new tab) and ECOP (opens in a new tab): business continuity planning and tabletop exercises | BOT Notification สกช. 5/2566 on IT Risk Governance of Financial Institutions and Specialized Financial Institutions, with attachments and Q&A (rev. 24 Sep 2568), p. 21 (opens in a new tab) |
| สกช. 5/2566 att. 5 ข้อ 1.4 para 2, 2.1, 2.2 | Binding rule You must audit significant IT work at least once a year and after every significant abnormal IT event, and audit to the set plan and scope at least once a year. BOT may order you to appoint an external auditor when it finds your audit results incomplete or unclear, or deems it necessary; that duty applies only once BOT orders it. This is an audit, not a test. | No Reconix assessment covers this duty. | BOT Notification สกช. 5/2566 on IT Risk Governance of Financial Institutions and Specialized Financial Institutions, with attachments and Q&A (rev. 24 Sep 2568), p. 28 (opens in a new tab) |
สกช. 5/2566 att. 2 ข้อ 6.7
Binding rule- What the rule says
- You must have independent internal or external experts pentest at least your Internet-facing applications and networks, at least once a year and on significant change, such as a significant change to your systems, risks, or international IT standards.
- What Reconix testing proves
Penetration Testing of your Internet-facing applications and networks, by testers external to and independent of your organization, shows which flaws an attacker can exploit.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
สกช. 5/2566 Q&A ข้อ 3
Guideline- What the rule says
- BOT's Q&A states which systems it expects the yearly pentest to cover: systems connected to public networks, such as the bank website, mobile banking, and internet banking.
- What Reconix testing proves
Penetration Testing of your bank website, mobile banking, and internet banking, by testers external to and independent of your organization, shows which flaws an attacker can exploit.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
สกช. 5/2566 att. 2 ข้อ 6.7 para 2
Binding rule- What the rule says
- BOT may order you to appoint an independent external expert to run an additional pentest when it finds your results incomplete, finds the scope or method misses generally recognized significant vulnerabilities, or deems it necessary. Your duty applies only once BOT orders it.
- If BOT orders it
- What Reconix testing proves
Reconix testers are external to your organization and independent of it, the kind of expert BOT can order you to appoint.
You receive: Report naming each tester and stating their independence from your system owners
ว. 1252/2562 para 2, D-SIBs; iPentest guideline 1.2.3, 1.6
Binding rule- What the rule says
- BOT directed D-SIBs and commercial banks with high cyber inherent risk to adopt the iPentest guideline within 2563 (2020). The guideline sets no fixed frequency. Testers may be internal or hired from outside, and the bank should set clear tester selection criteria covering certifications, experience, and ethics (guideline 1.6).
- If D-SIB or high cyber inherent risk (commercial banks)
- What Reconix testing proves
Red Teaming builds each scenario from threat intelligence, so you can run it toward the iPentest guideline. Whether Reconix testers meet your tester criteria under guideline 1.6 is your bank's decision.
You receive: Report with an executive summary, a timeline of Red Team actions, successful and unsuccessful attack paths, a map of detection gaps, and a prioritized remediation roadmap
ว. 1252/2562 para 2, other banks; สกช. 5/2566 att. 2 ข้อ 6.7
Guideline- What the rule says
- For commercial banks that are neither D-SIBs nor high cyber inherent risk, BOT's circular asks each bank to consider iPentest by its own risk level and readiness. สกช. 5/2566 att. 2 ข้อ 6.7 lets every bank and specialized financial institution apply iPentest to make its pentest more realistic.
- If neither D-SIB nor high cyber inherent risk
- What Reconix testing proves
Red Teaming builds each scenario from threat intelligence, so you can run it toward the iPentest guideline. Whether Reconix testers meet your tester criteria under guideline 1.6 is your bank's decision.
You receive: Report with an executive summary, a timeline of Red Team actions, successful and unsuccessful attack paths, a map of detection gaps, and a prioritized remediation roadmap
สกช. 5/2566 att. 2 ข้อ 6.6
Binding rule- What the rule says
- You must run a vulnerability assessment of every system by risk level. Critical systems: at least once a year and on significant change.
- What Reconix testing proves
Vulnerability Assessment of your critical systems, and of others by risk, finds known CVEs and misconfigurations on the yearly cycle.
You receive: Report stating scope and test dates; each finding with CVSS 4.0 severity and remediation steps
สกช. 5/2566 att. 2 ข้อ 7.2
Binding rule- What the rule says
- You must test a system before go-live, including a security test against the security process set in your technical specification. The clause does not require independent testers.
- What Reconix testing proves
Penetration Testing of your new system before launch shows what an attacker could exploit before your users can reach it. It is evidence toward the security test your technical specification sets, which stays your duty.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
IT Risk Management Guideline 2.7.2
Guideline- What the rule says
- The guideline says that, before go-live, security testing should include a vulnerability assessment, plus a pentest by external experts where the system connects to external networks. It also lists an independent source code review each time you develop or change the part of a system that handles important transactions.
- What Reconix testing proves
Vulnerability Assessment and external Penetration Testing of your system before go-live show which flaws exist and which an attacker can exploit. Secure Code Review by Reconix engineers, who are independent of your developers, checks the code behind important transactions.
You receive: Vulnerability Assessment report with CVSS 4.0 severity and remediation steps per finding; Penetration Testing report with CVSS 4.0 severity and a PoC per finding, plus one retest of every Critical and High finding; Secure Code Review report with line-specific references for developers
สกช. 5/2566 ข้อ 10.5
Binding rule- What the rule says
- You must send BOT your assessment of compliance with this notification within 30 days of calendar year end. It is a compliance self-assessment, not a test.
- What Reconix testing proves
No Reconix assessment covers this duty.
Group service from BAYCOMS (opens in a new tab) and ECOP (opens in a new tab): governance, risk and compliance (GRC)
สกช. 5/2566 att. 2 ข้อ 9.5
Binding rule- What the rule says
- You must review and test your IT contingency plan at least once a year and on every significant change.
- What Reconix testing proves
No Reconix assessment covers this duty.
Group service from BAYCOMS (opens in a new tab) and ECOP (opens in a new tab): business continuity planning and tabletop exercises
สกช. 5/2566 att. 5 ข้อ 1.4 para 2, 2.1, 2.2
Binding rule- What the rule says
- You must audit significant IT work at least once a year and after every significant abnormal IT event, and audit to the set plan and scope at least once a year. BOT may order you to appoint an external auditor when it finds your audit results incomplete or unclear, or deems it necessary; that duty applies only once BOT orders it. This is an audit, not a test.
- What Reconix testing proves
No Reconix assessment covers this duty.
Payment operator duties by clause
| Clause | What the rule says | What Reconix testing proves | Source |
|---|---|---|---|
| สนช. 1/2564 ข้อ 5.1.6 | Binding rule Every operator must have independent experts pentest its Internet-facing applications and networks at least once a year and on every significant change, such as a significant change to systems, risks, or international IT standards. The clause does not say whether the experts are internal or external. | Penetration Testing of your Internet-facing applications and networks, by testers external to and independent of your organization, shows which flaws an attacker can exploit. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification สนช. 1/2564 on IT Risk Governance under the Payment Systems Act, with cover letter and Q&A, p. 9 (opens in a new tab) |
| สนช. 1/2564 ข้อ 5.1.6 para 2 | Binding rule BOT may order you to appoint an independent external expert to run an additional pentest when it finds your results incomplete, finds the scope or method misses generally recognized significant vulnerabilities, or deems it necessary. Your duty applies only once BOT orders it. If BOT orders it | Reconix testers are external to your organization and independent of it, the kind of expert BOT can order you to appoint. You receive: Report naming each tester and stating their independence from your system owners | BOT Notification สนช. 1/2564 on IT Risk Governance under the Payment Systems Act, with cover letter and Q&A, p. 9 (opens in a new tab) |
| สนช. 1/2564 Q&A ข้อ 2 | Guideline BOT's Q&A says pentest experts should be independent. For competence, it points to past pentest work and practitioner certifications, such as OSCP, OSWP, OSCE, OSEE, or OSWE, and says the test should follow an international scope, method, and tools, such as OWASP. | The report names each tester, so you can weigh their competence against BOT's Q&A. Reconix testers hold certifications including OSCP. You receive: Report naming each tester | BOT Notification สนช. 1/2564 on IT Risk Governance under the Payment Systems Act, with cover letter and Q&A, p. 32 (opens in a new tab) |
| สนช. 1/2564 ข้อ 5.1.6, VA | Binding rule Every operator must run a vulnerability assessment of every system by risk level, at least once a year and on significant change, as part of the Cyber Hygiene baseline. | Vulnerability Assessment of your systems, scoped by risk, finds known CVEs and misconfigurations on the yearly cycle. You receive: Report stating scope and test dates; each finding with CVSS 4.0 severity and remediation steps | BOT Notification สนช. 1/2564 on IT Risk Governance under the Payment Systems Act, with cover letter and Q&A, p. 9 (opens in a new tab) |
| สนช. 1/2564 att. 2 ข้อ 7.2 | Binding rule If the IT risk management part (ข้อ 3.2) applies to you, you must test a system before go-live, including a security test against the security process set in your technical specification. If 1/2564 IT risk management applies | Penetration Testing of your new system before launch shows what an attacker could exploit before your users can reach it. It is evidence toward the security test your technical specification sets, which stays your duty. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification สนช. 1/2564 on IT Risk Governance under the Payment Systems Act, with cover letter and Q&A, p. 24 (opens in a new tab) |
| สนช. 11/2561 guideline 2.2(1) | Guideline The guideline asks for a vulnerability assessment and pentest by external experts of critical systems connected to public networks, before launch. BOT calls the guideline a general framework, and where สนช. 1/2564 covers the same matter, สนช. 1/2564 applies instead. | Vulnerability Assessment and Penetration Testing of your critical system that connects to public networks, run before launch by testers external to your organization, show which flaws exist and which an attacker can exploit. You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding | BOT Notification สนช. 11/2561 on Policies and Measures on Security of IT Systems (payment systems), with guideline, p. 7 (opens in a new tab) |
| สนช. 1/2564 ข้อ 3.2, 7.3; cover letter ว. 150/2564 | Binding rule You must send BOT your IT risk self-assessment within 30 days of calendar year end. System operators and significant service operators file the Cyber Hygiene and IT risk management parts; other service operators file Cyber Hygiene only. Service operators must also check the ข้อ 3.2 tests yearly and notify BOT within 30 days of year end if they meet all three. Operators below the tests keep the check on file (Q&A ข้อ 4), and BOT's cover letter asks your IT risk or compliance and internal audit executives to sign off. | No Reconix assessment covers this duty. Group service from BAYCOMS (opens in a new tab) and ECOP (opens in a new tab): governance, risk and compliance (GRC) | BOT Notification สนช. 1/2564 on IT Risk Governance under the Payment Systems Act, with cover letter and Q&A, p. 13 (opens in a new tab) |
| สนช. 1/2564 att. 2 ข้อ 9.5 | Binding rule If the IT risk management part (ข้อ 3.2) applies to you, you must review and test your IT contingency plan at least once a year and on every significant change. If 1/2564 IT risk management applies | No Reconix assessment covers this duty. Group service from BAYCOMS (opens in a new tab) and ECOP (opens in a new tab): business continuity planning and tabletop exercises | BOT Notification สนช. 1/2564 on IT Risk Governance under the Payment Systems Act, with cover letter and Q&A, p. 25 (opens in a new tab) |
| สนช. 11/2561 guideline 3.5(5) | Guideline The guideline says you should test and review the plan for critical operations at least once a year or when factors affecting risk change. Where สนช. 1/2564 covers the same matter, สนช. 1/2564 applies instead (ข้อ 10). | No Reconix assessment covers this duty. Group service from BAYCOMS (opens in a new tab) and ECOP (opens in a new tab): business continuity planning and tabletop exercises | BOT Notification สนช. 11/2561 on Policies and Measures on Security of IT Systems (payment systems), with guideline, p. 11 (opens in a new tab) |
| สนช. 11/2561 ข้อ 4.2.2 | Binding rule You must have an IT security audit carried out regularly, at least once a year. This is an audit, not a pentest. Where สนช. 1/2564 covers the same matter, สนช. 1/2564 applies instead (ข้อ 10). | No Reconix assessment covers this duty. | BOT Notification สนช. 11/2561 on Policies and Measures on Security of IT Systems (payment systems), with guideline, p. 3 (opens in a new tab) |
| สนช. 1/2564 att. 4 ข้อ 3, 5 | Binding rule If the IT risk management part (ข้อ 3.2) applies to you, you must have an independent external auditor audit IT to the approved plan and scope; payment service operators may use an independent internal or external auditor. Significant IT work should be audited at least once a year and after significant abnormal IT events. You must report results to the audit committee and send BOT a copy within 45 days of completing the audit. For payment service operators only, BOT may order an external audit; that duty applies only once BOT orders it. This is an audit, not a test. If 1/2564 IT risk management applies | No Reconix assessment covers this duty. | BOT Notification สนช. 1/2564 on IT Risk Governance under the Payment Systems Act, with cover letter and Q&A, p. 29 (opens in a new tab) |
| สนช. 11/2561 guideline s.4 | Guideline The guideline asks you to send BOT a copy of your IT security audit results within 45 days of completing the audit. It covers operators outside the สนช. 1/2564 IT risk management part. If 1/2564 IT risk management does not apply | No Reconix assessment covers this duty. | BOT Notification สนช. 11/2561 on Policies and Measures on Security of IT Systems (payment systems), with guideline, p. 11 (opens in a new tab) |
สนช. 1/2564 ข้อ 5.1.6
Binding rule- What the rule says
- Every operator must have independent experts pentest its Internet-facing applications and networks at least once a year and on every significant change, such as a significant change to systems, risks, or international IT standards. The clause does not say whether the experts are internal or external.
- What Reconix testing proves
Penetration Testing of your Internet-facing applications and networks, by testers external to and independent of your organization, shows which flaws an attacker can exploit.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
สนช. 1/2564 ข้อ 5.1.6 para 2
Binding rule- What the rule says
- BOT may order you to appoint an independent external expert to run an additional pentest when it finds your results incomplete, finds the scope or method misses generally recognized significant vulnerabilities, or deems it necessary. Your duty applies only once BOT orders it.
- If BOT orders it
- What Reconix testing proves
Reconix testers are external to your organization and independent of it, the kind of expert BOT can order you to appoint.
You receive: Report naming each tester and stating their independence from your system owners
สนช. 1/2564 Q&A ข้อ 2
Guideline- What the rule says
- BOT's Q&A says pentest experts should be independent. For competence, it points to past pentest work and practitioner certifications, such as OSCP, OSWP, OSCE, OSEE, or OSWE, and says the test should follow an international scope, method, and tools, such as OWASP.
- What Reconix testing proves
The report names each tester, so you can weigh their competence against BOT's Q&A. Reconix testers hold certifications including OSCP.
You receive: Report naming each tester
สนช. 1/2564 ข้อ 5.1.6, VA
Binding rule- What the rule says
- Every operator must run a vulnerability assessment of every system by risk level, at least once a year and on significant change, as part of the Cyber Hygiene baseline.
- What Reconix testing proves
Vulnerability Assessment of your systems, scoped by risk, finds known CVEs and misconfigurations on the yearly cycle.
You receive: Report stating scope and test dates; each finding with CVSS 4.0 severity and remediation steps
สนช. 1/2564 att. 2 ข้อ 7.2
Binding rule- What the rule says
- If the IT risk management part (ข้อ 3.2) applies to you, you must test a system before go-live, including a security test against the security process set in your technical specification.
- If 1/2564 IT risk management applies
- What Reconix testing proves
Penetration Testing of your new system before launch shows what an attacker could exploit before your users can reach it. It is evidence toward the security test your technical specification sets, which stays your duty.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
สนช. 11/2561 guideline 2.2(1)
Guideline- What the rule says
- The guideline asks for a vulnerability assessment and pentest by external experts of critical systems connected to public networks, before launch. BOT calls the guideline a general framework, and where สนช. 1/2564 covers the same matter, สนช. 1/2564 applies instead.
- What Reconix testing proves
Vulnerability Assessment and Penetration Testing of your critical system that connects to public networks, run before launch by testers external to your organization, show which flaws exist and which an attacker can exploit.
You receive: Report stating scope, test dates, and method; each finding with CVSS 4.0 severity and a PoC; one retest of every Critical and High finding
สนช. 1/2564 ข้อ 3.2, 7.3; cover letter ว. 150/2564
Binding rule- What the rule says
- You must send BOT your IT risk self-assessment within 30 days of calendar year end. System operators and significant service operators file the Cyber Hygiene and IT risk management parts; other service operators file Cyber Hygiene only. Service operators must also check the ข้อ 3.2 tests yearly and notify BOT within 30 days of year end if they meet all three. Operators below the tests keep the check on file (Q&A ข้อ 4), and BOT's cover letter asks your IT risk or compliance and internal audit executives to sign off.
- What Reconix testing proves
No Reconix assessment covers this duty.
Group service from BAYCOMS (opens in a new tab) and ECOP (opens in a new tab): governance, risk and compliance (GRC)
สนช. 1/2564 att. 2 ข้อ 9.5
Binding rule- What the rule says
- If the IT risk management part (ข้อ 3.2) applies to you, you must review and test your IT contingency plan at least once a year and on every significant change.
- If 1/2564 IT risk management applies
- What Reconix testing proves
No Reconix assessment covers this duty.
Group service from BAYCOMS (opens in a new tab) and ECOP (opens in a new tab): business continuity planning and tabletop exercises
สนช. 11/2561 guideline 3.5(5)
Guideline- What the rule says
- The guideline says you should test and review the plan for critical operations at least once a year or when factors affecting risk change. Where สนช. 1/2564 covers the same matter, สนช. 1/2564 applies instead (ข้อ 10).
- What Reconix testing proves
No Reconix assessment covers this duty.
Group service from BAYCOMS (opens in a new tab) and ECOP (opens in a new tab): business continuity planning and tabletop exercises
สนช. 11/2561 ข้อ 4.2.2
Binding rule- What the rule says
- You must have an IT security audit carried out regularly, at least once a year. This is an audit, not a pentest. Where สนช. 1/2564 covers the same matter, สนช. 1/2564 applies instead (ข้อ 10).
- What Reconix testing proves
No Reconix assessment covers this duty.
สนช. 1/2564 att. 4 ข้อ 3, 5
Binding rule- What the rule says
- If the IT risk management part (ข้อ 3.2) applies to you, you must have an independent external auditor audit IT to the approved plan and scope; payment service operators may use an independent internal or external auditor. Significant IT work should be audited at least once a year and after significant abnormal IT events. You must report results to the audit committee and send BOT a copy within 45 days of completing the audit. For payment service operators only, BOT may order an external audit; that duty applies only once BOT orders it. This is an audit, not a test.
- If 1/2564 IT risk management applies
- What Reconix testing proves
No Reconix assessment covers this duty.
สนช. 11/2561 guideline s.4
Guideline- What the rule says
- The guideline asks you to send BOT a copy of your IT security audit results within 45 days of completing the audit. It covers operators outside the สนช. 1/2564 IT risk management part.
- If 1/2564 IT risk management does not apply
- What Reconix testing proves
No Reconix assessment covers this duty.
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
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).
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.
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)
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.
Official References
Consult the original regulatory documents for full requirements.
Related Services
Security services that support your BOT duties.
Penetration Testing
Full-scope penetration testing for enterprise infrastructure and applications.
Learn MoreMobile App Penetration Testing
Specialized security testing for iOS and Android banking applications.
Learn MoreNetwork Penetration Testing
Infrastructure and network segmentation validation for financial systems.
Learn MoreBOT Penetration Testing FAQs
Answers to the most common questions about BOT penetration testing, iPentest, and compliance timelines.
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.