HKMA Supervisory Policy Manual TM-E-1: Risk Management of E-banking โ SP 800-53 Coverage
How well do NIST SP 800-53 Rev 5 controls address each HKMA TM-E-1 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 clause1.4 A risk-based approach to e-banking
Rationale
PM-09 sets a risk management strategy and applies it across the organisation, which is the risk-based approach the section asks for. PM-28 frames that approach with the risk tolerance, priorities and constraints it works from, this module and other HKMA guidance among them. RA-03 assesses the threats to each e-banking service and their impact, so the controls follow the risk. PM-01's programme plan records the requirements the institution must meet, compliance included. PL-11 tailors the control baseline, which is how general technology controls are refined for e-banking.
Gaps
The section asks the institution to comply with this module and other HKMA guidance, and to refer to the Code of Banking Practice and banking industry guidelines. SP 800-53 asks for policies consistent with the laws and guidelines that apply, and leaves the choice of those to the organisation. Risk management for the underlying financial services, such as credit and liquidity risk, has no SP 800-53 counterpart.
3.1 Board oversight and resourcing of e-banking
Rationale
PM-29 names a senior accountable official for risk and a risk executive function, which gives each risk a clear owner across the business lines and IT. PM-09's strategy, reviewed as the organisation and its technology change, keeps e-banking risks understood and managed. RA-03 assesses them before a service is introduced or enhanced. PM-03 puts security resources into capital planning, and SA-02 allocates what each system needs for its protection. PM-13 builds the staff and expertise to manage the risk. CA-06 has a senior official authorise each system before it operates, the point at which the institution confirms it has the resources and expertise to run it. PM-01's approved programme plan sets out roles, management commitment and compliance. PM-04 tracks remedial action on material control deficiencies for senior management to follow up.
Gaps
SP 800-53 gives accountability to senior officials, and the module gives oversight to the board or a committee it designates. The section also asks the board and senior management to promote a strong risk culture, and to oversee the reputation, legal and liquidity risks of e-banking as well as its operational risk. It gives the institution primary responsibility for educating and protecting its customers, a customer-facing duty with no SP 800-53 counterpart. Compliance with guidance from the HKMA, other authorities and industry associations is the module's own requirement. For an institution incorporated overseas, local senior management carries the oversight, under the monitoring of its head office (footnote 7).
3.2 Roles and skills across the three lines of defence
Rationale
PS-09 writes security roles into position descriptions, and PM-01's programme plan assigns responsibilities across the organisation, so each line of defence knows what it answers for. AT-03 role-based training gives the first line the competence to assess risks and run controls, and gives the second and third lines the technical knowledge they need. PM-13 develops that competence across the workforce. CA-02 assesses whether controls work, with independent assessors under CA-02(01), which is how the second line evaluates the first line's controls and the third line audits them. PM-29's risk executive function takes the organisation-wide view of risk that a second-line risk function holds.
Gaps
The three lines of defence model itself has no SP 800-53 counterpart. SP 800-53 assigns security roles and responsibilities, and the module asks for accountability set separately for each line, with internal audit as the third. The section also asks the board and senior management to support the second and third lines in building their technical competence.
3.3 Assessing e-banking controls before launch and every year
Rationale
CA-01 sets the policy and accountability for assessment. CA-02 plans each assessment with its scope and assessors and reports the findings. CA-02(01) asks for independent assessors, and CA-02(03) lets the institution rely on recent assessments by others, as 3.3.1(ii) allows. SA-09 brings outsourced systems and processes into scope by monitoring the service providers' compliance. CA-05 records each finding with its remedial actions and target dates. CA-06 has a senior official accept the residual risk before the service operates, and revisit it when the authorisation is updated. CA-08 penetration testing, by an independent team under CA-08(01), meets 3.3.2. RA-03 gives the formal risk assessment of 3.3.3, and RA-07 responds to the findings within the risk tolerance, so material issues are fixed in time.
Gaps
The module sets minimum frequencies, and SP 800-53 lets the organisation choose them. It asks for penetration tests each year of Internet banking and of every service delivered over the Internet or a wireless network, and for a formal risk assessment at least once a year. The independent assessment also checks compliance with HKMA guidance, and the assessors must be free to report directly to the board. Where several assessors share the work, the responsible function makes sure their scopes join up. The rest is the module's own detail: a designated senior officer endorses the risk assessment, the report covers the items in Annex A and goes to the HKMA on request, and penetration tests are planned to keep production systems running.
4.1 Authenticating customers and high-risk transactions
Rationale
SP 800-53 treats customers as users from outside the organisation, so IA-08 identifies and authenticates them when they open or use an e-banking account. IA-12 verifies their identity with validated evidence at account opening. IA-11 re-authenticates the customer before a high-risk transaction, once per session or before each one where the risk warrants. IA-10 asks for supplemental authentication when set conditions arise, which covers step-up authentication for risky transactions and ambush authentication when access looks suspicious. IA-02's enhancements IA-02(01) and IA-02(02) state multi-factor authentication. NIST writes IA-02 for the organisation's own users, and this mapping applies those enhancements to customers for the module's two-factor rule. IA-05 sets password and PIN strength (IA-05(01)) and protects passwords the institution generates, reissues or resets. AC-05 divides those duties so no one member of staff learns a customer's password. AC-07 limits invalid logon attempts and locks the account. AC-02 controls changes to account details and flags atypical use (AC-02(12)). CP-13 keeps alternative authentication methods ready to deploy quickly when fraud defeats the main one.
Gaps
SP 800-53 states multi-factor authentication for the organisation's own users, so two-factor authentication for customers is the HKMA's own rule. So is its list of high-risk transactions, with the exception for small-value transfers (footnote 10). The section also asks for payee registration through secure channels with identity checks, and for due diligence to classify high-risk merchants (footnote 9). Reminders to customers whose passwords are long unchanged, and alerts and calls to customers who fail ambush authentication, are customer-facing duties with no SP 800-53 counterpart.
4.2 Alerts to customers about transactions and unusual activity
Rationale
SI-04 monitoring finds unusual e-banking activity, such as a sudden change of location, a new device or new login behaviour. AC-02(12) flags atypical use of a customer's account. AC-09 shows customers their previous logon each time they log on, and AC-09(01) to AC-09(04) add failed attempts, account changes and other details, so customers can spot some unusual activity themselves.
Gaps
The section is about notices to customers, and customer notifications have no SP 800-53 counterpart. AC-09 informs users when they log on, and the module asks for a notice as soon as a customer starts a higher-risk transaction, sent through an effective channel with the transaction type, part of the payee's details and the amount. It also asks for notices of unusual activity, and for risk-based follow-up of undelivered notices.
4.3 Security advice for customers and action on scams
Rationale
PL-04 sets out the rules of behaviour customers acknowledge before access, including their duty to protect their devices and authentication factors. IA-05(h) asks users to take specific steps to protect their authenticators. AT-02 security awareness, kept up to date and drawing on recent scams, supports the periodic advice to customers. NIST writes AT-02 for the organisation's own users, so it covers customers in part. AT-03 trains the officers who answer customers' questions about security. AU-13 monitors open sources, and AU-13(03) detects copies of the institution's websites and apps. IR-04 handles a scam as an incident through to removing the fake items, with IR-04(15) for press releases and public communication. IR-06 reports it to the Police and the HKMA.
Gaps
Customer education and warnings to the public have no SP 800-53 counterpart. The module asks for security advice that is easy to understand and prominently displayed, sent through several channels, and for the provisions of the Code of Banking Practice. When a scam appears, the institution decides quickly how to warn its customers and the public, and issues any press release within the HKMA's expected timing (footnote 12).
4.4 Tools and terms that protect customers
Rationale
AC-09(02) and AC-09(04) show customers their recent logons with times, locations and devices, which gives part of the activity review in 4.4.1. IR-07 offers a support resource where customers get help with possible unauthorised transactions, and PM-26 runs an accessible complaints process with tracked responses. AC-02 disables an account on request and re-enables it under set conditions, and IA-10 asks for stronger authentication before a suspended account is reactivated. PL-04's rules of behaviour, acknowledged before access, carry the terms that set out business customers' responsibilities and security precautions. PM-18's privacy programme and PT-01's processing policy support compliance with the Personal Data (Privacy) Ordinance and the Privacy Commissioner's codes. PT-03 keeps the use of customers' data to its stated purposes.
Gaps
Liability for unauthorised transactions has no SP 800-53 counterpart. Under the Code of Banking Practice and the Treat Customers Fairly Charter, a personal customer bears a direct loss from an unauthorised transaction only after acting fraudulently or with gross negligence. Business customers need clear terms on disputes and liabilities before the service starts. The section also asks for an activity history customers can search back at least 90 days, and a help channel open at all times. Customers must be able to suspend their own accounts. Check the Ordinance's specific requirements and the Privacy Commissioner's codes against their own text.
5.1 Encryption and integrity of customer data
Rationale
SC-08 protects customer information on external networks and credentials on internal ones, with encryption under SC-08(01), and protects the integrity of data passed between systems. SC-28(01) encrypts highly sensitive information in storage, mainly login credentials. IA-05(01) sends passwords only over protected channels and stores them with a salted key derivation function. SC-13 sets strong, approved cryptography for each use, to be replaced as algorithms weaken, and SC-12 manages the keys. SI-07 integrity checks detect unauthorised changes to the data the Internet banking system processes.
Gaps
The module asks for application checks that reconcile data file balances after transaction updates. Where internationally recognised algorithms are impractical, an alternative must be similarly strong and independently assessed (footnote 13).
5.2 Securing the Internet-facing network
Rationale
PL-08 sets the security architecture of the Internet infrastructure. SC-07 puts public-facing components in a demilitarised zone, with managed interfaces for external connections. AC-04 enforces approved information flows within internal networks and to external systems, and CA-03 governs each connection to an external party with an agreement. CM-02 keeps baseline configurations for the network devices, and CM-06 sets them securely. CM-07 keeps each device to the ports and services it needs. SI-04 runs intrusion detection, with SI-04(01) for a system-wide intrusion detection system. SI-02 gives the patch management procedure for systems and infrastructure.
Gaps
SP 800-53 covers each part of the infrastructure 5.2.1 names. The design of the demilitarised zone is the institution's own.
5.3 Secure development and session controls
Rationale
SA-03 builds security into the life cycle of the Internet banking system and its apps, from design to implementation. SA-08 applies security engineering principles, the sound industry practice the module points to, such as OWASP's (footnote 14). SA-15 names the development standards that code is reviewed against. SA-11 tests the code before launch, with static analysis (SA-11(01)), independent verification (SA-11(03)) and manual review (SA-11(04)). AC-10 limits each account to one session at a time, and SC-23 protects the authenticity of sessions. AU-02 logs additional login attempts, and AU-03 records their IP address, device type and location.
Gaps
The module asks for a code reviewer independent of the developers, which SA-11(03) expresses in part. It accepts a documented peer review assisted by automated tools, and asks the institution to make sure a vendor's code review process is adequate, or to review the vendor's code itself (footnote 15).
5.4 Tracking threats and scanning for vulnerabilities
Rationale
PM-16's threat awareness programme shares threat intelligence with other organisations, and SI-05 brings in security alerts and advisories. Together they give the systematic monitoring of emerging threats. RA-03, with dynamic threat awareness under RA-03(03), relates those threats to the institution's infrastructure and applications. RA-05 scans the Internet infrastructure and banking systems with automated tools at a set frequency. RA-07 responds to the threats and vulnerabilities found in line with the risk tolerance, and SI-02 fixes the flaws.
Gaps
SP 800-53 covers what the section asks. The module adds manual techniques to automated scanning where the institution needs them.
6.1 Limits and authentication for funds transfers
Rationale
IA-08 authenticates the customer, and IA-11 re-authenticates them before each high-risk transfer. IA-02's multi-factor enhancements, IA-02(01) and IA-02(02), state the two-factor rule. NIST writes IA-02 for the organisation's own users, and this mapping applies it to customers. AC-03 enforces the transfer limits, and AC-03(02) dual authorisation gives business customers the dual control the module suggests. AC-02(11) usage conditions keep small-value transfers off until a customer opts in. AC-06 least privilege keeps transfer functions off, or limits at zero, for new accounts, and reviewing privileges (AC-06(07)) removes high limits left unused.
Gaps
The structure of the limits is the HKMA's own, with customers' limits inside a cap the institution sets, and high-value limits reset to zero when unused, normally within 18 months. Customers can lower a default cross-border limit. Telling customers the risk of their limits is a customer-facing duty with no SP 800-53 counterpart. Liquidity risk management for large outflows, intraday and under stress (6.1.3), is a financial risk outside SP 800-53.
6.2 Information and documents customers submit online
Rationale
RA-03 assesses the risks of accepting information over the Internet before the controls are set. SC-08 protects submitted information and documents in transit, using SC-13's approved cryptography, and SC-28 protects them once stored. SI-03 scans files from outside sources in real time to detect and block malware. IA-12, with identity evidence and its validation (IA-12(02), IA-12(03)), supports asking for supporting documents and extra checks on the customer's identity.
Gaps
SP 800-53 covers what the section asks. When to ask for supporting documents is the institution's own judgement.
6.3 Linking customers' accounts at other institutions
Rationale
RA-08's privacy impact assessment before launch shows whether the service needs disclosure to customers or their consent. PT-04 obtains that consent, and PT-05 tells customers how the service processes their data. SA-09 requires the partner institution to meet the institution's security requirements and monitors its compliance. CA-03 documents the interface, security requirements and responsibilities of the connection. SC-07 connects to the partner through managed boundary interfaces only, which limits the risk of intrusion. CA-02 assesses the controls independently (CA-02(01)).
Gaps
Most of the section concerns the business and legal side of the partnership. The institution checks that the business model is acceptable, and observes local and overseas legal requirements, including those on money laundering and terrorist financing. Handling cross-border complaints, sharing liability with the partner for customers' losses, and telling customers the service's risks and limitations are customer-facing duties with no SP 800-53 counterpart.
6.4 Other financial services offered online
Rationale
RA-03 assesses how delivery over electronic channels, including access from outside Hong Kong, shifts or amplifies the security risk of a new online service. SI-10 validity checks on market price inputs help keep the prices shown online accurate.
Gaps
The section is mostly about financial and conduct risk, which has no SP 800-53 counterpart. Under Principle 1 of the Treat Customers Fairly Charter, services must meet customers' needs. The institution assesses credit, market, reputation and legal risk, and keeps online prices timely when markets are volatile. Where a service involves activities the Securities and Futures Commission regulates, the SFC's and the HKMA's requirements apply (6.4.2).
7.1 Mobile banking apps and devices
Rationale
RA-03 identifies and assesses the risks of the mobile channel and its platforms, and PL-02's security plan records the measures that address them. SI-07 integrity checks, with runtime application self-protection under SI-07(17), help the app resist malware and tampering on the customer's phone. AU-13(03) looks for fake Internet banking apps that copy the institution's. AT-02 awareness tailored to mobile use supports customer education. NIST writes AT-02 for the organisation's own users, so it covers customers in part. For a phone that both opens Internet banking and receives or generates one-time passwords, IA-05 protects the authenticators. IA-02(06) takes one factor from a separate device. NIST writes IA-02 for the organisation's own users, and this mapping applies it to customers.
Gaps
Customers' phones sit outside the institution's control, and SP 800-53's mobile device controls cover devices the organisation manages. Customer education built for mobile use, and prompt notice to customers about fake apps, are customer-facing duties with no SP 800-53 counterpart.
7.2 Banking through social media and other platforms
Rationale
SR-06 assesses the platform before the partnership, including its controls and its record on data leakage. RA-08 runs a privacy impact assessment where customer data passes to the platform or is stored there. SA-09 requires the platform to meet the institution's security requirements and monitors its compliance, and CA-03 documents each connection's interface and security requirements. CA-02 gives the rigorous assessment of the connection. SC-07 segregates the institution's network from the platform, and SC-08 protects customer data in transit between them. SI-03 guards against malware arriving through the connection, and SI-04 monitors it for intrusion and data leakage. For banking by chat message, IA-08 authenticates the customer before the institution acts on an instruction, and SI-12 keeps proper records of the instructions. IA-02's multi-factor enhancements state the two-factor rule for high-risk transactions by chat. NIST writes IA-02 for the organisation's own users, and this mapping applies it to customers.
Gaps
The module asks the institution to weigh the platform's financial condition, and to carry out legal due diligence on local and overseas requirements, personal data privacy among them. These sit outside SP 800-53. Arrangements for customer complaints, and for sharing liability with the platform for customers' losses, are customer-facing duties with no SP 800-53 counterpart.
7.3 ATMs and other self-service machines
Rationale
RA-03 assesses the risks of self-service terminals regularly, and RA-05 scans the terminals and their hosts for vulnerabilities. SI-05 alerts and advisories keep the institution informed of emerging attacks on terminals. SR-09's tamper protection programme and SR-10's inspections address skimming devices and physical tampering. SI-03 guards against malware implanted on terminals, and SA-22 replaces end-of-support software or arranges continued support. SC-07 protects the hosts and back-end systems that terminals connect to.
Gaps
Detecting and handling counterfeit banknotes at deposit machines has no SP 800-53 counterpart. The module also asks the institution to prevent disputes with customers caused by confusing transaction processing or by incidents involving banknotes, a customer-facing duty outside SP 800-53.
7.4 Verifying callers to phone banking
Rationale
IA-08 authenticates each caller before the institution gives account details or carries out a transaction. IA-05 sets the strength of phone PINs, biometrics and challenge questions and protects the answers. AC-06 limits which staff and service providers can see customers' answers. AC-05 separates duties, which limits the chance that the people who ask the questions use the answers to act as the customer.
Gaps
The design of challenge questions is the HKMA's own detail. The module warns that static answers, or answers in the public domain, raise the risk of impersonation. It prefers dynamic questions that vary between sessions and keep some questions back each time (footnote 21).
7.5 Contactless payments from mobile devices
Rationale
RA-03 assesses the security risks of a contactless payment service before launch, and PL-02's security plan records the measures. SC-08 protects payment data on the contactless link from eavesdropping and electronic pick-pocketing. CA-02 control assessments review regularly whether the measures still work.
Gaps
Loss or theft of the customer's own phone calls for measures of the institution's own, since SP 800-53's device controls cover devices the organisation manages. The module also asks the institution to follow industry guidance from the relevant authorities.
7.6 Securing card payments and alerting cardholders
Rationale
IA-08 authenticates cardholders for card-not-present transactions. IA-05 makes the authenticator strong enough to resist phishing and malware where merchants use 3-D Secure. SI-04 monitors for unauthorised card-not-present transactions, using data such as IP addresses and phone numbers. IA-10 asks the cardholder for extra confirmation of a suspicious transaction, even one already authenticated.
Gaps
Notifications to cardholders have no SP 800-53 counterpart. The module asks for timely notices of card-not-present transactions, notice when a card is bound to a mobile payment service, and notices of at least the first three transactions after binding. It also asks for a channel where customers turn card-not-present transactions on or off and set a limit for them.
8.1 Detecting and stopping fraud
Rationale
SI-04 gives automated, near real-time monitoring (SI-04(02)) against profiles of normal behaviour (SI-04(13)), adjusted as the risk changes. AC-02(12) flags atypical use of a customer's account. AU-06 reviews and analyses records for unusual activity, and adjusts the review when intelligence or law enforcement information changes the risk. PM-16 brings fraud and scam intelligence from inside and outside the institution into the monitoring rules. IR-04 handles alerts through to containment, such as suspending a transaction, at any hour, and feeds the lessons back.
Gaps
Alerts to customers have no SP 800-53 counterpart. The module asks the institution to warn customers promptly of a "High Risk" result from the Police's anti-fraud search engine, and to contact customers through a reliable channel to verify a transaction. It also asks for enough designated staff with fraud expertise during and after office hours. SP 800-53's monitoring looks for security events, and fraud rules built on each customer's own history and transaction patterns are the module's own.
8.2 Responding to incidents and practising the response
Rationale
IR-01 sets formal incident response policy and procedures, and IR-08's plan defines reportable incidents, responsibilities and information sharing. IR-04 handles breaches, attacks, fraud and service interruptions, and IR-04(15) manages public relations, press releases included. IR-06 reports incidents inside the institution and to the HKMA. IR-07 support resources, such as hotlines, help affected customers with their questions (footnote 24). IR-03 tests the response capability regularly, and IR-02(01) trains staff with simulated events. IR-08(01) covers deciding when to notify affected individuals.
Gaps
The module puts the interests of affected customers first. Senior management sets a communication strategy for everyone affected, customers and the media among them. The institution tells affected customers the key facts and the steps they can take, such as how to claim compensation. It issues a press release for a prolonged disruption of a critical service, and notifies the HKMA under the HKMA's own arrangements. These customer-facing duties have no SP 800-53 counterpart.
9.1 Availability and response times for customers
Rationale
CP-02 plans for continuous service, with capacity planning under CP-02(02) and coordination with service providers' plans under CP-02(07). SA-09 extends the resilience and capacity requirements to service providers and monitors them. SC-06 allocates resources by priority or quota, so time-critical services keep their response times.
Gaps
Service levels and response times set against customers' expectations are the module's own. So is scaling resilience, capacity planning and performance monitoring to time-critical services such as Internet securities trading. SP 800-53 plans capacity for contingency operations, and the module asks for it in everyday operation.
9.2 Capacity reviews and forecasting
Rationale
CP-02(02) plans processing and telecommunications capacity, which SP 800-53 frames for contingency operations. SC-05(02) manages capacity, bandwidth and redundancy, and SC-05(03) monitors whether resources are enough, both aimed at denial of service.
Gaps
SP 800-53 plans capacity for contingencies and denial of service, and the module asks for capacity management as everyday practice. It asks for regular capacity reviews with reports to senior management, utilisation thresholds with precautionary measures, and a forecasting method based on utilisation trends and growth in customers and business. It also suggests a fast-track procurement process for upgrades, and asks for end-to-end stress testing to find bottlenecks.
9.3 Monitoring for performance problems
Rationale
SI-04 gives automated monitoring with near real-time analysis (SI-04(02)) and alerts to designated staff (SI-04(05)), and SC-05(03) watches whether system resources are enough. IR-04 lets designated staff handle a detected interruption promptly. SI-04 and SC-05 aim at security events and denial of service, so performance measures need adding.
Gaps
SP 800-53's monitoring controls aim at security, and the module asks for an automated performance monitoring and alert system covering every critical component of e-banking. Designated staff handle the alerts during and after office hours.
9.4 Removing single points of failure
Rationale
SI-13 provides standby components and failover (SI-13(05)), and SC-36 distributes processing and storage across locations, which removes single points of failure. CP-08(02) chooses alternate telecommunications that lower the chance of sharing a single point of failure with the primary service. CA-09 authorises internal connections and reviews whether each is still needed. CP-04 tests whether the resilience works in practice. CP-02(07) coordinates the contingency plan with service providers' plans, and SA-09 monitors their controls, resilience included.
Gaps
Where an outsourcing agent supports the service, the module asks the institution to assess the agent's resilience controls as part of its own resilience assessment. SA-09 expresses that in part.
9.5 Keeping e-banking running through disruptions
Rationale
CP-02 sets recovery objectives and keeps essential functions running (CP-02(05)), and CP-04 tests the disaster recovery plan in regular drills. CP-07 provides an alternate processing site for switching to back-up systems, and CP-10 recovers the systems within the recovery time objective. MA-02 maintains equipment to suppliers' specifications and service intervals. CM-03 tests and approves changes and fall-back procedures before scheduled maintenance (Annex B). SC-05 protects against denial-of-service attacks, with detection under SC-05(03), and SI-04 detects other attacks that could disrupt e-banking. IR-04 responds to them promptly, and CA-02 validates the DDoS controls and reviews them periodically.
Gaps
The module asks the IT function to agree a service level for availability with the business lines. Advance notice to customers of maintenance outages, and prompt answers to customer and media enquiries (Annex B.4 to B.6), are customer-facing duties with no SP 800-53 counterpart. Alternative channels need the capacity and procedures to serve customers' critical functions while Internet banking is down (9.5.4).
Methodology and Disclaimer
This coverage analysis maps from HKMA TM-E-1 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.