Bank of Thailand Notification สกช. 5/2566: Rules on the Oversight of IT Risk of Financial Institutions and Specialized Financial Institutions — SP 800-53 Coverage
How well do NIST SP 800-53 Rev 5 controls address each BOT IT Risk Notification requirement? This analysis maps from framework clauses back to SP 800-53, with expert coverage weightings and gap identification.
Clause-by-Clause Analysis
Sorted by clauseA1.1 Board's role in overseeing IT risk บทบาทหน้าที่และความรับผิดชอบของคณะกรรมการของสถาบันการเงินและคณะกรรมการของสถาบันการเงินเฉพาะกิจ
Rationale
PM-29 names a senior accountable official for risk and sets up a risk executive function, which carry the oversight of IT risk that the board holds or delegates. PM-28 records the risk tolerance, the acceptable level of risk the board oversees against. PM-09 manages IT and cyber risk as one of the organisation's significant risks, and PM-01's programme plan, approved by an accountable senior official, puts the policies in place (1.2). PM-07's enterprise architecture keeps the use of IT in line with the business strategy and able to take future change, and CP-02 keeps the systems behind critical services running (1.1). AT-02 builds awareness of IT risk among all users, managers and senior executives included (1.3).
Gaps
BOT makes the board accountable for IT risk, and the board stays responsible when it delegates oversight to a committee or to senior management. SP 800-53 gives that accountability to senior officials, so give the board its oversight role in your programme plan. BOT's governance notifications also ask for at least one director with knowledge or experience of IT. The board oversees the risk of significant IT projects and makes sure the management of financial fraud risk is robust (1.2), which SP 800-53 leaves to the organisation. Building awareness among customers and service users (1.3) is a duty to customers outside SP 800-53.
A1.2 Governance structure and head of IT security โครงสร้างการกำกับดูแล
Rationale
PM-01's programme plan sets the roles, responsibilities and coordination of the units that run IT, oversee its risk and compliance, and audit it (2.1). AC-05 separates those duties and keeps the head of IT security apart from IT operations and development. CA-02, with independent assessors under CA-02(01), keeps audit independent of operations and of risk and compliance. PM-29's risk executive function takes the organisation-wide view of IT risk that an IT risk committee holds (2.2.2). PM-02 appoints a senior information security officer with the mission and resources to run the security programme: the head of IT security, and the CISO where one is required. PS-09 writes that role's duties into the position description. Controls carry the duties themselves (2.3.1): PL-08 the security requirements and architecture, PM-09 the management of IT security and cyber threat risk with the organisation's other risks, IR-08 the readiness to respond to cyber threats, and AT-02 staff awareness.
Gaps
SP 800-53 leaves the three lines of defence model and the committees to the organisation. BOT asks for committees that oversee IT operations, IT risk management and IT audit, such as an IT steering committee, an IT risk committee and the audit committee (2.2). The head of IT security needs knowledge or experience of IT, IT security management and responding to cyber threats, and presents IT security and cyber threat risks to the board or the assigned committee as a regular agenda item. Domestic systemically important banks, and institutions with high inherent cyber risk under BOT's Cyber Resilience Assessment Framework (CRAF), also need a CISO (2.3.2). The CISO reports significant problems and incidents directly to the top executive, a committee or the board, and takes part in decisions with a significant impact on IT security.
A1.3 IT security and IT risk management policies นโยบายที่เกี่ยวข้องกับการกำกับดูแลความเสี่ยงด้านเทคโนโลยีสารสนเทศ
Rationale
PM-01's programme plan, written down, approved by an accountable senior official and reviewed at a set frequency and after set events, serves as the IT security policy. PM-09's risk management strategy serves as the IT risk management policy, and RA-01 gives its risk assessment part a written policy and procedures on the same review cycle. SR-01 brings the risk from third parties' services, connections and access to data into the policies (3.1). The policy controls of the other families, such as AC-01 and IR-01, supply the policy for each topic of the IT security policy, under OSA's rule for policy clauses, which follows NIST's crosswalks.
Gaps
BOT asks the board itself to approve both policies, where SP 800-53 has a senior official approve the programme plan. Review them at least once a year and at every significant change, the minimum BOT sets (3.2). Keep them consistent with the strategy for using IT, and fit them to the nature of the business, the transaction volume and the complexity of IT (3.1).
A1.4 Personnel management การบริหารจัดการบุคลากร
Rationale
PS-03 screens people before they get access, and PM-13 sets the knowledge and skills each role needs and the qualifications applicants must meet, which together cover the selection of staff (4.1). AT-02 builds their awareness of IT risk. PS-06 access agreements, such as non-disclosure agreements, PL-04 rules of behaviour and PS-09 position descriptions write each person's IT security responsibilities into contracts and internal rules (4.2). AC-02 ties account changes to transfers and terminations, PS-04 removes access when employment ends, and PS-05 reviews it when someone changes position and tells the people concerned (4.3).
Gaps
BOT asks for enough staff for the volume of IT use, with their workload taken into account (4.1). It also asks for staff in IT operations, risk, compliance and audit chosen for their knowledge or experience. PM-13 sets these for security roles, so extend it to the other roles.
A1.5 Staff awareness of IT risk การส่งเสริมให้บุคลากรตระหนักถึงความเสี่ยงด้านเทคโนโลยีสารสนเทศ (IT risk awareness)
Rationale
AT-02 gives all users security literacy training and awareness, such as how to use computers safely on public networks, with practical exercises under AT-02(01). AT-03 adds role-based training for staff in IT operations, risk, compliance and audit. IR-02 trains staff to respond to cyber attacks with simulated events (IR-02(01)), and IR-03 tests the response plans, the rehearsal BOT names.
Gaps
BOT also says institutions should build awareness of IT risk and cyber threats among customers and service users, regularly and in step with new threats (paragraph two). SP 800-53 writes awareness training for the organisation's own users, so plan customer awareness on its own.
A2.1 IT asset management การบริหารจัดการทรัพย์สินด้านเทคโนโลยีสารสนเทศ (IT asset management)
Rationale
CM-08 keeps a complete, accurate inventory of system components and PM-05 an inventory of the organisation's systems, which together make the asset register. RA-02 categorises systems and the information they hold, so the register sets the security approach for each asset. MA-02 maintains assets on a schedule to the manufacturer's specifications, and MA-06 obtains support and spare parts in time, with preventive maintenance under MA-06(01). SA-22 replaces components once their support ends, or arranges other support.
Gaps
BOT asks for assets nearing the end of their useful life or of support to be managed ahead of time and in step with the risk. SA-22 acts once support has ended, so plan their replacement before then.
A2.2 Data security การรักษาความมั่นคงปลอดภัยของข้อมูล (information security)
Rationale
SC-08 protects data sent over networks and SC-28 data stored on systems, each with encryption under its first enhancement, SC-08(01) and SC-28(01). MP-04 controls and stores media of all kinds. RA-02 categorises information by impact, the basis for classifying it. SI-12 keeps and disposes of information as law and policy require, with disposal techniques under SI-12(03), and MP-06 sanitises media with a strength that matches the classification. SC-12 manages cryptographic keys through their life, and SC-13 sets the type of cryptography each use requires.
Gaps
RA-02 rates impact, and BOT asks for classification levels with rules for storing and destroying data at each level, so set those levels and rules. Choose cryptography that follows generally accepted international standards, as BOT asks. SP 800-53 leaves the choice of standard to the organisation.
A2.3 Access control การควบคุมการเข้าถึง (access control)
Rationale
AC-02 manages accounts and their privileges, with privileged accounts under a role-based scheme (AC-02(07)), dynamic privilege management for check-out (AC-02(06)) and conditions such as time limits on their use (AC-02(11)). AC-03 enforces approved authorisations on operating systems, applications and databases. AC-06 grants least privilege by need, restricts privileged accounts (AC-06(05)), reviews privileges (AC-06(07)) and logs their use (AC-06(09)). AU-06 reviews the records of privileged sessions after use. IA-02 authenticates users, with multi-factor authentication for privileged accounts (IA-02(01)) and for other accounts (IA-02(02)), such as those that reach customer data from a public network. These are the institution's own accounts, the users NIST writes IA-02 for. IA-05 sets the strength of authenticators, the measure for a substitute of equal effect where a system cannot do multi-factor authentication. AC-17 authorises remote access from public networks and sets its conditions (3.2(2)). RA-03 assesses the risk of each approved exception.
Gaps
BOT asks for a process to request and approve an exception where a system or device cannot meet 3.2, with a risk assessment and risk controls for each. Set that process up, with RA-03 for the assessment. BOT names check-out of privileged accounts, a set period of use and review after use as practices of their own. SP 800-53 has them only in enhancements of AC-02 and AC-06, so write them into your procedures.
A2.4 Physical and environmental security การรักษาความมั่นคงปลอดภัยทางกายภาพและสภาพแวดล้อม (physical and environmental security)
Rationale
PE-02 lists and reviews who may enter computer centres and important areas, and PE-03 enforces entry, escorts visitors and keeps access logs. PE-06 monitors physical access, with intrusion alarms and video surveillance under PE-06(01) and PE-06(03). PE-09 protects power equipment and cabling, and PE-11 provides uninterruptible power, with an alternate power supply for long outages under PE-11(01). PE-13 detects and suppresses fire, PE-14 keeps temperature and humidity within set levels, and PE-15 protects against water damage. PE-18 positions equipment to limit damage and unauthorised access, and PE-23 plans sites with natural hazards in mind. MA-02 maintains computer equipment on a schedule.
Gaps
BOT asks for maintenance processes for IT utility systems, such as generators, uninterruptible power supplies and cooling, as well as for computer equipment. MA-02 covers system components, so add the utility systems to your maintenance schedule.
A2.5 Network security การรักษาความมั่นคงปลอดภัยของระบบเครือข่ายสื่อสาร (communications security)
Rationale
SC-07 monitors and controls traffic at the boundary and at key internal points, with public-facing systems in subnetworks of their own, and AC-04 enforces approved flows between network zones and connected systems. SI-04 watches the network for attacks and unauthorised connections, inbound and outbound under SI-04(04). SC-08 protects the data sent over the networks. SC-05 protects against denial-of-service attacks, and CP-08 provides alternate telecommunications services, which keep the networks ready to support services.
Gaps
BOT asks for networks ready to support services continuously. Design them for reliability and for growth in use, which SP 800-53 leaves to the organisation.
A2.6 IT operations security การรักษาความมั่นคงปลอดภัยในการปฏิบัติงานด้านเทคโนโลยีสารสนเทศ (IT operations security)
Rationale
CP-02 plans capacity for processing, telecommunications and environmental support under CP-02(02) (6.1). SI-03 protects servers and endpoints against malicious code and keeps itself up to date, and SI-02 installs tested security patches within set times (6.2, 6.10). CP-09 backs up user and system data at a frequency the recovery objectives set (6.3). AU-02 and AU-12 log events on important servers, systems and network devices, and AU-03 records what happened, when, where and who did it. AU-06 reviews the access and activity logs, AU-09 protects them from change and deletion, and AU-11 keeps them for the period the law sets (6.4). SI-04 monitors systems to detect attacks, SI-05 acts on security alerts and advisories, and PM-16 shares threat intelligence to track new threats (6.5). RA-05 scans for vulnerabilities by risk (6.6), and CA-08 runs penetration tests by an independent team under CA-08(01) (6.7). CM-03 controls changes such as deployments, configuration changes and patches, CM-04 analyses each change's impact before it is made, and CM-05 restricts who can make changes (6.8). CM-02 sets the minimum security baseline, CM-06 applies secure settings and approves deviations from them, and CM-07 hardens systems by turning off unneeded functions, ports and services (6.9).
Gaps
CP-02(02) plans capacity for contingency operations. BOT asks for capacity management in normal operation too, with trends in use assessed and the capacity of digital channels watched closely (6.1). BOT sets minimum frequencies where SP 800-53 lets the organisation choose: assess the vulnerabilities of critical systems, and penetration-test systems that face the Internet, at least once a year and at every significant change (6.6, 6.7). BOT may also order further penetration tests by independent external experts. Where a vendor has no patch yet, put substitute controls in place, and where a patch cannot be installed, approve an exception with a risk assessment (6.10). Keep logs fit to serve as legal evidence of electronic transactions (6.4).
A2.7 System acquisition and development การจัดหาและการพัฒนาระบบ (system acquisition and development)
Rationale
SA-04 writes security requirements and acceptance criteria into acquisition contracts, and SR-06 assesses suppliers, such as their reliability, certification and support (7.1). SA-03 builds security into the development life cycle, with protected preproduction environments (SA-03(01)) and controlled use of live data in testing (SA-03(02)), and SA-08 applies security engineering principles (7.2). For the items of 7.2, SA-17 gives the technical specification its security design and SA-10 controls source code versions. AC-05 separates developers from those who put systems into production, and CM-04 analyses changes in a test environment apart from production (CM-04(01)). SA-11 runs unit, integration, system and security tests, and CP-04 tests that backup systems are ready. PM-25 limits the use of personal data in testing. SA-05 provides administrator and user manuals, and SA-16 trains users and administrators in the security functions.
Gaps
BOT asks for performance and load testing when systems for services or electronic transactions are built or changed. It asks for the flexibility to change providers, technology or strategy later (7.1), and names certification of providers to international standards as a selection criterion. SP 800-53 leaves these to the organisation, so add them to your selection criteria and test plans.
A2.8 IT incident and problem management การบริหารจัดการเหตุการณ์ผิดปกติและปัญหา (IT incident and problem management)
Rationale
IR-04 handles incidents from detection and analysis to recovery, and feeds lessons learned back to stop them recurring. IR-05 records and tracks each incident. IR-06 reports incident information to set recipients, here the assigned committee. IR-08's plan sets the roles, the response structure and which incidents are reported.
Gaps
BOT covers every incident and problem that arises from the use of IT, outages included, and SP 800-53's incident controls aim at security incidents. Run problem management with root-cause analysis as a process of its own, to fix the cause and stop incidents recurring. Report incidents, problems and their resolution to the assigned committee within an appropriate time.
A2.9 IT disaster recovery plan การจัดทำแผนฉุกเฉินด้านเทคโนโลยีสารสนเทศ (IT disaster recovery plan)
Rationale
CP-02 sets out a written plan with roles, recovery objectives and priorities, approved by designated officials, coordinated with related plans (CP-02(01)), and reviewed and updated. CP-10 recovers systems within the times the recovery time and recovery point objectives set. CP-03 trains the staff who carry out the plan, and CP-04 tests it at a set frequency and corrects what fails. CP-07 provides a backup site ready to take over, far enough from the primary site under CP-07(01).
Gaps
BOT asks the assigned committee to approve the plan (9.1). Review and test it at least once a year and at every significant change, the minimum BOT sets (9.5). Take concentration risk and systemic risk into account when preparing it (9.2), and set the maximum tolerable period of disruption (MTPD) alongside the recovery objectives (9.3).
A2.10 Third-party risk management การบริหารจัดการความเสี่ยงจากบุคคลภายนอก (third party risk management)
Rationale
SA-09 holds providers to the institution's security requirements, sets oversight roles and monitors compliance, and SA-09(05) limits where data is processed and stored. SA-04 allocates security responsibilities in the contract, with the return and removal of data at the end under SA-04(12). CA-03 governs each connection with a third party. SR-02 plans the management of third-party risk, SR-06 assesses and reviews providers, and SR-03 deals with weaknesses in the supply chain, with a diverse supply base under SR-03(01) against reliance on one provider (10.2). Where audit rights cannot go into the contract, SR-08 obtains the provider's independent audit results instead (10.1). For public cloud (10.5), RA-03 assesses the risk, with supply chain risk under RA-03(01), and CM-12 records where data is processed and stored. CP-09 backs up the data and tests the backups (CP-09(01)), and CP-06 keeps them at a separate site (CP-06(01)). SC-08 and SC-28 encrypt data in transit and at rest under SC-08(01) and SC-28(01). CM-06 sets and monitors security settings. SI-04 and SI-05 watch cloud-hosted systems for attacks and act on advisories before the provider fixes a flaw. CP-02 coordinates the contingency plan with providers' plans (CP-02(07)), so services continue through a severe event (10.4, 10.5.9).
Gaps
Write the right of BOT and of internal and external auditors to examine a significant IT outsourcing provider into the contract (10.1). Manage concentration risk and lock-in to a single provider, beyond the diverse supply base of SR-03(01) (10.2). For public cloud, weigh the risk of the country where the provider stores or processes data (10.5.1, 10.5.2), and keep backups in Thailand or in a country other than the main service country (10.5.4). At exit, take the data back and make sure the provider's copy is destroyed beyond recovery (10.5.8), which SA-04(12) covers in part. Plan for the worst cases BOT names: the provider's region fails, all its regions fail, or the institution loses every communication line (10.5.9).
A3.1 IT risk management function โครงสร้างองค์กร
Rationale
PM-29's risk executive function, under a senior accountable official, takes an organisation-wide view of IT risk and links it with the institution's other risks (1.1, 1.2). PM-13 sets the knowledge and experience risk management roles need, and AT-03 gives those staff continuous role-based training (1.3).
Gaps
BOT asks for an IT risk management function independent of the first line of defence, with a clear reporting line of its own to the committee that oversees IT risk (1.1, 1.2). SP 800-53 leaves the form of the function and its reporting line to the organisation.
A3.2 Carrying out IT risk management การปฏิบัติงานด้านการบริหารความเสี่ยงด้านเทคโนโลยีสารสนเทศ
Rationale
PM-28 records the risk tolerance, which is the IT risk appetite, and PM-09's strategy is the framework for managing IT risk within it. RA-01 sets the risk assessment policy and procedures. RA-03 identifies threats and vulnerabilities and assesses their likelihood and impact, with third parties under RA-03(01) (2.1). RA-07 responds to the findings so residual risk stays within the appetite (2.2). PM-31 sets the measures to watch, such as key risk indicators, monitors them and reports the risk status at set intervals (2.2 to 2.4).
Gaps
BOT asks the assigned committee to approve the IT risk appetite, and the risk function to build the framework together with the first line of defence. Report the level of risk and the results of managing it to the board or the assigned committee regularly (2.4). SP 800-53 leaves the recipients to the organisation.
A4.1 IT compliance function โครงสร้างองค์กร
Rationale
AT-03 gives compliance staff continuous role-based training on regulations and IT, and PM-13 sets the legal and IT knowledge their roles need (1.3).
Gaps
BOT asks for an IT compliance function, independent enough to do its work in full, with a reporting line through the head of compliance to the relevant committee (1.1, 1.2). SP 800-53 leaves the compliance function to the organisation, so set it up with its reporting line. Its staff need knowledge and experience of the law as well as basic knowledge of IT (1.3).
A4.2 Overseeing compliance with IT laws and rules การปฏิบัติงานด้านการกำกับการปฏิบัติตามกฎเกณฑ์ที่เกี่ยวข้องกับเทคโนโลยีสารสนเทศ
Rationale
CA-02 assesses controls against requirements on a plan and reports the results, the compliance testing BOT names (2.2). AT-02 educates employees on the rules that apply to their use of IT. PM-04 tracks corrective actions for non-compliance and reports them (2.3).
Gaps
BOT asks for compliance risk to be identified and assessed against the IT laws it names, such as the laws on electronic transactions, computer-related offences, cybersecurity, personal data protection and payment systems (2.1). Set an annual compliance programme that follows that assessment (2.2). Report compliance results, breaches, corrective measures and action on the recommendations and orders of BOT and other supervisors to the assigned committee regularly (2.3).
A5.1 IT audit function โครงสร้างองค์กร
Rationale
CA-02 has assessments carried out by independent assessors under CA-02(01), internal or external, which keeps IT audit apart from IT operations and from risk and compliance (1.1, 1.3). PM-13 sets the audit knowledge and expertise the role needs, and AT-03 gives IT auditors continuous training (1.4).
Gaps
BOT asks for an IT audit function, in a unit of its own or within internal audit, reporting to the head of internal audit and directly to the audit committee (1.1, 1.2). SP 800-53 leaves the function and its reporting line to the organisation. BOT may also order an institution to appoint an external auditor and report the results to BOT.
A5.2 Carrying out IT audit การปฏิบัติงานด้านการตรวจสอบเทคโนโลยีสารสนเทศ
Rationale
CA-02 plans each assessment with its scope, has the plan approved before work starts, assesses at a set frequency and reports to set recipients (2.1 to 2.3). CA-05 records the remediation of findings in a plan of action, and PM-04 keeps those plans current and reports them, such as to the audit committee. RA-07 responds to the findings within the risk tolerance.
Gaps
BOT asks the audit committee to approve the audit plan and scope, and to review them at least once a year and at every significant change (2.1). Audit significant IT work at least once a year and after every significant IT incident. Follow audit standards consistent with the law and with generally accepted international standards (2.2). Keep audit reports ready for BOT to examine or request (2.3).
A6.1 Project need, risk and approval ศึกษาความจำเป็นและประโยชน์ที่คาดว่าจะได้รับ
Rationale
RA-03 assesses the risk and impact of the planned system before work starts, and CM-04 assesses its impact on related systems. SA-02 sets security requirements during business planning and funds them through capital planning, one part of approving a project.
Gaps
BOT asks for a study of the project's need and expected benefits before it starts, an appropriate choice of technology, and an assessment of the impact on other departments. Prioritise projects, and submit each for approval to the assigned committee within the set limits of approval authority. SP 800-53 leaves these steps of project management to the organisation.
A6.2 Project management framework กำหนดกรอบการบริหารจัดการโครงการ (project management framework) 20%
Rationale
SA-03 sets a defined system development life cycle, with stages from initiation onward and security built in. It is the nearest SP 800-53 comes to a project management framework.
Gaps
BOT asks for a clear, written project management framework covering project initiation, execution and control, closure and review. Set it up as a framework of its own, with SA-03 for the security steps within it.
Mapped Controls
A6.3 Project governance structure กำหนดโครงสร้างการควบคุมและกำกับดูแลโครงการที่ชัดเจน (project governance) 10%
Rationale
SA-03 defines and assigns the security roles across the system life cycle, a small part of the project governance BOT asks for.
Gaps
BOT asks for at least a committee that oversees projects (3.1), a project management office (3.2) and a project manager for each project (3.3). SP 800-53 leaves project governance to the organisation.
Mapped Controls
S8 Mobile banking availability การดูแลระบบงานที่รองรับช่องทางการให้บริการทางอุปกรณ์เคลื่อนที่ (mobile banking) ของสถาบันการเงินและสถาบันการเงินเฉพาะกิจ
Rationale
CP-02 plans for the mobile banking service to keep running, with recovery objectives the institution can set to BOT's limit. CP-02(05) continues essential functions and CP-02(03) resumes them within a set time. CP-07 provides an alternate processing site, and CP-10 recovers the systems promptly, within a set time under CP-10(04). SI-13 keeps standby components ready to take over (SI-13(05)), and SC-05 protects the channel against denial-of-service attacks.
Gaps
BOT allows mobile banking at most 8 hours of disruption in a calendar year. SP 800-53 leaves availability targets to the organisation, so set yours to that limit and track downtime against it. Count disruptions as BOT's Q&A (item 12) does: each disruption of 15 minutes or more that affects over 10,000 users or over 10% of financial transactions, on the main mobile banking product for retail customers.
S9 Criteria for significance ข้อกำหนดในการพิจารณาความมีนัยสำคัญเพื่อดำเนินการตามประกาศนี้
Rationale
PM-28 records the priorities and risk tolerance that decisions on significance rest on, shares them with the units that apply them and reviews them at a set frequency. PM-09 applies them consistently across the organisation. RA-02 categorises systems and information by impact, with the decision approved by an authorising official, which weighs the impact on the institution (9.2).
Gaps
BOT asks for the criteria to be agreed jointly by the first and second lines of defence and approved by the assigned committee (9.1). Weigh the impact on the whole banking system as well as on the institution (9.2). Check how the criteria are applied, and review the criteria themselves, at least once a year (9.4, 9.5).
S10 Notices, reports and applications to BOT การแจ้ง การรายงาน หรือการขออนุญาต ต่อ ธปท.
Rationale
IR-06 reports incident information to set authorities, here BOT, and IR-08's plan defines which incidents are reported, such as the three cases BOT names (10.3). CA-02 assesses controls against requirements and sends the results to set recipients, the basis of the yearly self-assessment (10.5).
Gaps
Notify BOT at least 15 days before a significant adoption of IT or change to systems. A specialized financial institution, finance company or credit foncier company applies for BOT's permission first (10.1). Notify BOT at least 15 days before relying on a group company's central oversight of IT risk (10.2). Submit BOT's data reports in its formats and on its timetable (10.4), and the yearly self-assessment within 30 days of the end of the calendar year (10.5). SP 800-53 leaves reports to regulators to the organisation.
The Thai titles are the source's own wording, from the Bank of Thailand's Notification สกช. 5/2566 of 16 October 2023, which is not a copyright work under Thailand's Copyright Act B.E. 2537, section 7. OSA wrote the English titles as short summaries, and summarised the requirements in the rationale and gaps, from its working translation of BOT's Thai text. Where BOT gives three items the same title, organisational structure (โครงสร้างองค์กร) in Attachments 3, 4 and 5, the English title names the function. Attachment 6 items have no headings, so their Thai titles are the opening words of each item.
Methodology and Disclaimer
This coverage analysis maps from BOT IT Risk Notification clauses/requirements back to NIST SP 800-53 Rev 5 controls, assessing how well the SP 800-53 control set addresses each framework requirement.
Coverage weighting represents an informed estimate based on control-objective alignment, not a definitive compliance determination. Weightings consider whether SP 800-53 controls address the intent of each framework requirement, even where terminology and structure differ.
This analysis should be validated by qualified assessors for use in compliance or audit activities. The authoritative source for any compliance determination is always the framework itself.