SEC Cybersecurity Compliance for Capital Markets & Digital Assets
SEC Notification สธ. 38/2565, as amended by สธ. 33/2567, sets penetration testing, vulnerability assessment, and secure development duties for capital market and digital asset operators. Your Risk Level Assessment tier decides how often you test.
Understanding SEC Cybersecurity Requirements
The SEC sets IT security duties for capital market and digital asset operators in Notification สธ. 38/2565, as amended by สธ. 33/2567. Appendix 3 holds the testing duties and Appendix 4 the IT audit duties. Your Risk Level Assessment tier sets how often you test.
- Appendix 3 of สธ. 38/2565 holds the binding testing duties; frequency and scope depend on your tier (small, low, medium, or high)
- นป. 6/2567 is the SEC guideline: following it in full counts as compliance, and an operator that departs from it must prove it still meets สธ. 38/2565
- Penetration testers must be independent of the system owner, and in-house or external experts both qualify
- Digital asset businesses that hold client assets also follow สธ. 44/2565, which adds yearly wallet incident tests and duties after a custody-system incident
- SEC IT rules do not require a smart contract audit before launch, or red teaming
Who Needs to Comply?
สธ. 38/2565 ข้อ 2, as amended by สธ. 33/2567, covers these SEC-licensed and approved operators. Banks and life insurers holding SEC licenses are covered too.
Securities & Derivatives Firms
Licensed securities and derivatives businesses. Duties scale with the Risk Level Assessment tier you file each year.
Fund Managers & Advisers
Fund managers, and investment or derivatives advisers that use technology to serve clients.
Digital Asset Exchanges
Licensed digital asset exchanges. An exchange that holds client assets also follows the custody rules in สธ. 44/2565.
Digital Asset Brokers & Dealers
Licensed digital asset businesses that transact for clients. The custody rules in สธ. 44/2565 apply when they hold client assets.
ICO & Crowdfunding Portals
SEC-approved ICO portals and crowdfunding portals.
Capital Market Infrastructure
Clearing houses, depositories, and derivatives exchanges.
SEC Testing Duties by Rule
Binding duties come from สธ. 38/2565 Appendices 3 and 4. Items from นป. 6/2567 are marked as guidance. Check your tier first: small operators carry fewer duties.
| Clause | What the rule says | What Reconix testing proves | Source |
|---|---|---|---|
| App. 3 ข้อ 8.10.1 | Binding rule You must pentest Internet-facing applications and networks at least once a year and on every significant change. Small operators: at least every 3 years and on significant change. Frequency by RLA tier | Penetration Testing of your Internet-facing applications and networks, run on your tier cycle and after each significant change, 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 | Appendix 3 to สธ. 38/2565 (IT Security), current version, p. 7 (opens in a new tab) |
| App. 3 ข้อ 8.10.1(2) | Binding rule For other systems, you must assess intrusion risk through the internal network, set the pentest scope, and pentest as appropriate. | Internal Network Penetration Testing of the systems your intrusion-risk assessment puts in scope shows how far an attacker inside your network can reach. 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 | Appendix 3 to สธ. 38/2565 (IT Security), current version, p. 7 (opens in a new tab) |
| App. 3 ข้อ 8.10.2 | Binding rule Your testers must be independent of the system owner, in-house or external; this applies to small operators too. | Reconix testers are external to your organization and independent of your system owners. You receive: Report naming each tester and stating their independence from your system owners | Appendix 3 to สธ. 38/2565 (IT Security), current version, p. 7 (opens in a new tab) |
| App. 3 ข้อ 8.10.3 to 8.10.5 | Binding rule You must fix findings promptly, keep all pentest records at least 2 years from the date made, and send pentest reports to the SEC without delay on request. | The retest shows whether your Critical and High fixes hold. The report is the pentest record you keep for 2 years and send to the SEC on request. You receive: Report updated after the retest, recording which Critical and High fixes held and the residual risk that remains | Appendix 3 to สธ. 38/2565 (IT Security), current version, p. 7 (opens in a new tab) |
| นป. 6/2567 App. ข้อ 8.9, 8.10.1 | Guideline You should rate each VA and pentest finding by risk, set a fix deadline that matches the risk, report findings to the system owner, compliance, and internal audit, and report fix progress to the board or senior management. | Every finding comes with a CVSS 4.0 severity you can set fix deadlines against. Setting the deadlines and the internal reporting stay with you. You receive: Report opening with an executive summary for your board and senior management, then severity and remediation steps per finding | SEC Guideline นป. 6/2567 on Implementing IT Systems, appendix, p. 45 (opens in a new tab) |
| นป. 6/2567 App. ข้อ 8.10.2 | Guideline High tier: testers of critical systems should hold recognized certifications, such as CREST, OSCP, GPEN, or an equivalent. High tier | The report names each tester, so you can match their certifications to this guideline. Reconix testers hold certifications including OSCP. You receive: Report naming each tester | SEC Guideline นป. 6/2567 on Implementing IT Systems, appendix, p. 46 (opens in a new tab) |
| App. 3 ข้อ 8.9 | Binding rule You must run a vulnerability assessment of critical and all Internet-facing systems at least once a year and on significant change; this applies to small operators too. | Vulnerability Assessment of your critical and Internet-facing systems 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 | Appendix 3 to สธ. 38/2565 (IT Security), current version, p. 7 (opens in a new tab) |
| App. 3 ข้อ 8.1 | Binding rule You must review system configuration regularly; this applies to small operators too. | Vulnerability Assessment flags insecure configurations on the systems in scope. It is evidence toward your own regular configuration review, which stays your duty. You receive: Report stating scope and test dates; each finding with CVSS 4.0 severity and remediation steps | Appendix 3 to สธ. 38/2565 (IT Security), current version, p. 6 (opens in a new tab) |
| App. 3 ข้อ 10.3(4) | Binding rule You must have a process or tool that controls secure code development. Not small operators | Secure Code Review tests whether code your process approved still holds security flaws. Running the process or tool is your duty. You receive: Report with line-specific references for developers, CVSS 4.0 severity per finding, and a summary for management | Appendix 3 to สธ. 38/2565 (IT Security), current version, p. 9 (opens in a new tab) |
| App. 3 ข้อ 10.3(5), 10.4(3) | Binding rule You must test developed or changed systems before production. Not small operators | Penetration Testing or Vulnerability Assessment of a new or changed system before go-live shows what an attacker could exploit before your users can reach it. 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 | Appendix 3 to สธ. 38/2565 (IT Security), current version, p. 9 (opens in a new tab) |
| นป. 6/2567 App. ข้อ 10.3(4) | Guideline You should review source code, automated or manual by someone other than the developer, when you build or change a critical system with security risk, and fix findings before go-live. High tier: a manual review by an expert independent of your developers. Not small operators | Secure Code Review pairs SAST tools with manual review by Reconix engineers, who are independent of your developers. You receive: Report with line-specific references for developers, CVSS 4.0 severity per finding, and a summary for management | SEC Guideline นป. 6/2567 on Implementing IT Systems, appendix, p. 54 (opens in a new tab) |
| นป. 6/2567 App. ข้อ 10.3(5) | Guideline Before go-live, a new system that connects to critical systems should get a security test: a vulnerability assessment, plus a pentest where needed. Not small operators | Vulnerability Assessment and Penetration Testing of the new system before launch 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 | SEC Guideline นป. 6/2567 on Implementing IT Systems, appendix, p. 55 (opens in a new tab) |
| App. 3 ข้อ 11.6 | Binding rule You must test and review the IT incident plan at least once a year, including a cyber security drill, and report results to the board or its delegated committee. Not small operators | No Reconix assessment covers this duty. Group service from BAYCOMS (opens in a new tab) and ECOP (opens in a new tab): cyber drill and incident response planning | Appendix 3 to สธ. 38/2565 (IT Security), current version, p. 10 (opens in a new tab) |
| App. 3 ข้อ 8.6, 12.5 | Binding rule You must test backup and restore, and review and test the IT contingency plan, each at least once a year and when needed, and report contingency results to the board. Not small operators | 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, and backup solutions | Appendix 3 to สธ. 38/2565 (IT Security), current version, p. 6 (opens in a new tab) |
| App. 4 ข้อ 1, 2, 3.1, 5 | Binding rule You must have an IT audit by an auditor independent of the first and second lines; for audits from 1 Jan 2024 the auditor holds CISA, CISM, CISSP, ISO/IEC 27001 Lead Auditor, or another certificate the SEC lists. Review the audit plan and scope at least yearly. Full scope at least yearly for medium and high tiers; at least every 3 years on the SEC cycle for small and low tiers, and within the year of a significant IT security incident (or report the reason and an audit plan to the board and the SEC within 4 months). Board-reviewed report and remediation plan to the SEC within 3 months after the calendar year end of the audit year; digital asset operators file under กธ. 19/2561, whose deadline this page does not cover; banks and life insurers holding only debt-securities or securities lending licenses do not file Frequency by RLA tier | No Reconix assessment covers this duty. | Appendix 4 to สธ. 38/2565 (IT Audit), current version, p. 1 (opens in a new tab) |
| สธ. 38/2565 ข้อ 4 | Binding rule You must file the Risk Level Assessment with the SEC within Q1 of each calendar year after board or delegate review; the result sets your tier. | No Reconix assessment covers this duty. Group service from BAYCOMS (opens in a new tab) and ECOP (opens in a new tab): risk assessment and governance, risk and compliance (GRC) | SEC Notification สธ. 33/2567 amending สธ. 38/2565, p. 3 (opens in a new tab) |
| สธ. 44/2565 ข้อ 7(3) to 7(5) | Binding rule You must test wallet incident procedures at least once a year, have someone independent of the incident owners evaluate them, and report results to the board yearly. | No Reconix assessment covers this duty. Group service from BAYCOMS (opens in a new tab) and ECOP (opens in a new tab): cyber drill and incident response planning | SEC Notification สธ. 44/2565 on Detailed Requirements for Digital Asset Wallet and Key Management Systems, p. 4 (opens in a new tab) |
| สธ. 44/2565 ข้อ 7(7), 7(8) | Binding rule After a security incident on wallet or key management systems that materially affects client assets, you must engage without delay an independent, certified external expert to review security and run digital forensics; send an interim report to the SEC within 30 days and a final report within 90 days of signing the expert's contract; send a remediation and prevention plan within 10 days of receiving the final report; and send progress reports every Friday until the plan is complete. After a material custody-system incident | No Reconix assessment covers this duty. Group service from BAYCOMS (opens in a new tab) and ECOP (opens in a new tab): digital forensics and incident response | SEC Notification สธ. 44/2565 on Detailed Requirements for Digital Asset Wallet and Key Management Systems, p. 4 (opens in a new tab) |
App. 3 ข้อ 8.10.1
Binding rule- What the rule says
- You must pentest Internet-facing applications and networks at least once a year and on every significant change. Small operators: at least every 3 years and on significant change.
- Frequency by RLA tier
- What Reconix testing proves
Penetration Testing of your Internet-facing applications and networks, run on your tier cycle and after each significant change, 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
App. 3 ข้อ 8.10.1(2)
Binding rule- What the rule says
- For other systems, you must assess intrusion risk through the internal network, set the pentest scope, and pentest as appropriate.
- What Reconix testing proves
Internal Network Penetration Testing of the systems your intrusion-risk assessment puts in scope shows how far an attacker inside your network can reach.
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
App. 3 ข้อ 8.10.2
Binding rule- What the rule says
- Your testers must be independent of the system owner, in-house or external; this applies to small operators too.
- What Reconix testing proves
Reconix testers are external to your organization and independent of your system owners.
You receive: Report naming each tester and stating their independence from your system owners
App. 3 ข้อ 8.10.3 to 8.10.5
Binding rule- What the rule says
- You must fix findings promptly, keep all pentest records at least 2 years from the date made, and send pentest reports to the SEC without delay on request.
- What Reconix testing proves
The retest shows whether your Critical and High fixes hold. The report is the pentest record you keep for 2 years and send to the SEC on request.
You receive: Report updated after the retest, recording which Critical and High fixes held and the residual risk that remains
นป. 6/2567 App. ข้อ 8.9, 8.10.1
Guideline- What the rule says
- You should rate each VA and pentest finding by risk, set a fix deadline that matches the risk, report findings to the system owner, compliance, and internal audit, and report fix progress to the board or senior management.
- What Reconix testing proves
Every finding comes with a CVSS 4.0 severity you can set fix deadlines against. Setting the deadlines and the internal reporting stay with you.
You receive: Report opening with an executive summary for your board and senior management, then severity and remediation steps per finding
นป. 6/2567 App. ข้อ 8.10.2
Guideline- What the rule says
- High tier: testers of critical systems should hold recognized certifications, such as CREST, OSCP, GPEN, or an equivalent.
- High tier
- What Reconix testing proves
The report names each tester, so you can match their certifications to this guideline. Reconix testers hold certifications including OSCP.
You receive: Report naming each tester
App. 3 ข้อ 8.9
Binding rule- What the rule says
- You must run a vulnerability assessment of critical and all Internet-facing systems at least once a year and on significant change; this applies to small operators too.
- What Reconix testing proves
Vulnerability Assessment of your critical and Internet-facing systems 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
App. 3 ข้อ 8.1
Binding rule- What the rule says
- You must review system configuration regularly; this applies to small operators too.
- What Reconix testing proves
Vulnerability Assessment flags insecure configurations on the systems in scope. It is evidence toward your own regular configuration review, which stays your duty.
You receive: Report stating scope and test dates; each finding with CVSS 4.0 severity and remediation steps
App. 3 ข้อ 10.3(4)
Binding rule- What the rule says
- You must have a process or tool that controls secure code development.
- Not small operators
- What Reconix testing proves
Secure Code Review tests whether code your process approved still holds security flaws. Running the process or tool is your duty.
You receive: Report with line-specific references for developers, CVSS 4.0 severity per finding, and a summary for management
App. 3 ข้อ 10.3(5), 10.4(3)
Binding rule- What the rule says
- You must test developed or changed systems before production.
- Not small operators
- What Reconix testing proves
Penetration Testing or Vulnerability Assessment of a new or changed system before go-live shows what an attacker could exploit before your users can reach it.
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
นป. 6/2567 App. ข้อ 10.3(4)
Guideline- What the rule says
- You should review source code, automated or manual by someone other than the developer, when you build or change a critical system with security risk, and fix findings before go-live. High tier: a manual review by an expert independent of your developers.
- Not small operators
- What Reconix testing proves
Secure Code Review pairs SAST tools with manual review by Reconix engineers, who are independent of your developers.
You receive: Report with line-specific references for developers, CVSS 4.0 severity per finding, and a summary for management
นป. 6/2567 App. ข้อ 10.3(5)
Guideline- What the rule says
- Before go-live, a new system that connects to critical systems should get a security test: a vulnerability assessment, plus a pentest where needed.
- Not small operators
- What Reconix testing proves
Vulnerability Assessment and Penetration Testing of the new system before launch 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
App. 3 ข้อ 11.6
Binding rule- What the rule says
- You must test and review the IT incident plan at least once a year, including a cyber security drill, and report results to the board or its delegated committee.
- Not small operators
- 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): cyber drill and incident response planning
App. 3 ข้อ 8.6, 12.5
Binding rule- What the rule says
- You must test backup and restore, and review and test the IT contingency plan, each at least once a year and when needed, and report contingency results to the board.
- Not small operators
- 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, and backup solutions
App. 4 ข้อ 1, 2, 3.1, 5
Binding rule- What the rule says
- You must have an IT audit by an auditor independent of the first and second lines; for audits from 1 Jan 2024 the auditor holds CISA, CISM, CISSP, ISO/IEC 27001 Lead Auditor, or another certificate the SEC lists. Review the audit plan and scope at least yearly. Full scope at least yearly for medium and high tiers; at least every 3 years on the SEC cycle for small and low tiers, and within the year of a significant IT security incident (or report the reason and an audit plan to the board and the SEC within 4 months). Board-reviewed report and remediation plan to the SEC within 3 months after the calendar year end of the audit year; digital asset operators file under กธ. 19/2561, whose deadline this page does not cover; banks and life insurers holding only debt-securities or securities lending licenses do not file
- Frequency by RLA tier
- What Reconix testing proves
No Reconix assessment covers this duty.
สธ. 38/2565 ข้อ 4
Binding rule- What the rule says
- You must file the Risk Level Assessment with the SEC within Q1 of each calendar year after board or delegate review; the result sets your tier.
- 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): risk assessment and governance, risk and compliance (GRC)
สธ. 44/2565 ข้อ 7(3) to 7(5)
Binding rule- What the rule says
- You must test wallet incident procedures at least once a year, have someone independent of the incident owners evaluate them, and report results to the board yearly.
- 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): cyber drill and incident response planning
สธ. 44/2565 ข้อ 7(7), 7(8)
Binding rule- What the rule says
- After a security incident on wallet or key management systems that materially affects client assets, you must engage without delay an independent, certified external expert to review security and run digital forensics; send an interim report to the SEC within 30 days and a final report within 90 days of signing the expert's contract; send a remediation and prevention plan within 10 days of receiving the final report; and send progress reports every Friday until the plan is complete.
- After a material custody-system incident
- 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): digital forensics and incident response
What Reconix Tests
Reconix service scope. Match each service to your own SEC duties above.
Entire IT Infrastructure
Vulnerability Assessment: Systematic discovery of CVEs and misconfigurations across all systems and environments.
Trading Platforms & APIs
Penetration Testing: Proving whether vulnerabilities in web apps, mobile apps, and APIs can be exploited by real attackers.
Application Source Code
Secure Code Review: Catching logic flaws and OWASP Top 10 vulnerabilities before they reach production.
People, Processes & Tech
Red Teaming (Reconix service, not an SEC requirement): Stress-testing incident response, SOC detection, and organizational cyber resilience end to end.
Web3 Tokens & ICOs
Smart Contract Audit (Reconix service, not an SEC requirement): Finding vulnerabilities in on-chain code before investor funds are at stake.
e-KYC & Onboarding
Validating the security of identity verification, document handling, and client onboarding workflows.
Filings and Records the SEC Expects
This page does not cover SEC penalties. These are the filing and record duties in the rules.
- Pentest reports sent to the SEC without delay when it asks (App. 3 ข้อ 8.10.3 to 8.10.5)
- Pentest records kept at least 2 years from the date made (App. 3 ข้อ 8.10.3 to 8.10.5)
- Risk Level Assessment filed within Q1 of each calendar year after board or delegate review (สธ. 38/2565 ข้อ 4)
- Board-reviewed IT audit report and remediation plan filed within 3 months after the calendar year end of the audit year; digital asset operators file under กธ. 19/2561 (App. 4)
- Proof that you still meet สธ. 38/2565 wherever you depart from นป. 6/2567 (นป. 6/2567 ข้อ 4)
How a Reconix Pentest Runs the SEC Cycle
Four steps come from สธ. 38/2565 Appendix 3 ข้อ 8.10: scope, independent test, prompt fixes, and records. The CVSS 4.0 and PoC report and the retest of every Critical and High finding are what Reconix adds.
SEC Compliance Checklist
Core duties from สธ. 38/2565 Appendix 3. Confirm your tier first.
- Risk Level Assessment filed with the SEC within Q1, and your tier on record
- Internet-facing pentest done within your tier's cycle (yearly, or every 3 years for small operators) and after each significant change
- Testers independent of the system owner, whether in-house or external
- Vulnerability assessment of critical and Internet-facing systems at least once a year
- Findings fixed promptly and pentest records kept at least 2 years
- Secure development process or tool in place, and systems tested before production (not required of small operators)
Official References
Every document cited in the requirements table, linked to the issuer. The rules (สธ. 38/2565, สธ. 33/2567, นป. 6/2567, สธ. 44/2565) are published on sec.or.th.
Related Services
Specialized security services to support your SEC compliance.
Vulnerability Assessment
Systematic vulnerability discovery and risk scoring across your infrastructure and applications.
Learn moreWeb Application Penetration Testing
In-depth security testing for trading platforms, portals, and client-facing web applications.
Learn moreSmart Contract Audit
Rigorous security audits for DeFi protocols, tokens, and ICO smart contracts.
Learn moreSEC Compliance FAQ
Common questions about SEC Thailand cybersecurity requirements for capital markets and digital assets.
Test Against Your SEC Duties
Protect your license and your investors with security assessments built for SEC Thailand requirements.
Reconix is the proof-first offensive security specialist for digital businesses in Thailand where a breach ends the business.