Cybersecurity

Hong Kong SFC — Guidelines for Reducing and Mitigating Hacking Risks Associated with Internet Trading

SFC Cybersecurity Guidelines framework badge
Summarize with
ClaudeChatGPTPerplexityGoogle AI Mode
In this article
At a Glance
SFC Guidelines for Reducing and Mitigating Hacking Risks Associated with Internet Trading
  • Classification
    Category
    Cybersecurity
    Domain
    Cybersecurity
    Framework Family
    Other
  • Regulatory Context
    Type
    Guidance
    Legal Instrument
    Guideline
    Sector
    Financial Sector
    Industry
    Financial Services
  • Region / Publisher
    Region
    Asia-Pacific
    Region Detail
    Hong Kong
    Publisher
    Securities and Futures Commission (SFC), Hong Kong
  • Versioning
    Version
    Guidelines for Reducing and Mitigating Hacking Risks Associated with Internet Trading (27 October 2017)
    Effective Date
    April 27, 2018 (two-factor authentication); July 27, 2018 (all other requirements)
    Issue Date
    October 27, 2017
  • Adoption
    Adoption Model
    Regulatory Compliance
    Implementation Complexity
    Medium
  • Official Reference
License Information

License included / downloadable: Yes

The Guidelines are published free of charge by the SFC on its website and are included with the platform for reference.

Framework text is licensed by its publisher and is included only where stated above.

Official Resources
Guidelines for Reducing and Mitigating Hacking Risks Associated with Internet Trading (PDF)
The SFC's full text of the 20 baseline requirements for internet trading cybersecurity.
Key takeaways
  • The SFC's Guidelines for Reducing and Mitigating Hacking Risks set 20 baseline cybersecurity requirements for Hong Kong firms offering internet trading.
  • Issued October 27, 2017, two-factor authentication applied from April 27, 2018 and the other requirements from July 27, 2018.
  • They apply to persons licensed for Type 1, 2, or 3 regulated activity, and Type 9 where funds are distributed through internet trading.
  • A July 9, 2026 circular says one-time passwords are not phishing-resistant and sets July 8, 2027 as the latest date for phishing-resistant login.
  • Delegation is allowed in writing, but overall accountability stays with the responsible officers or executive officers.

Overview

The Securities and Futures Commission (SFC) of Hong Kong published the Guidelines for Reducing and Mitigating Hacking Risks Associated with Internet Trading as baseline cybersecurity requirements for firms whose clients trade over the internet. They apply to persons licensed by or registered with the SFC for Type 1, 2 or 3 regulated activity, and for Type 9 to the extent they distribute funds through internet-based trading facilities. Two-factor authentication took effect on 27 April 2018 and the other requirements on 27 July 2018.

The SFC issued the Guidelines on 27 October 2017 under section 399 of the Securities and Futures Ordinance. They set 20 baseline requirements in three groups: protection of clients' internet trading accounts (1.1 to 1.6), infrastructure security management (2.1 to 2.10) and cybersecurity management and supervision (3.1 to 3.4). They are read with paragraphs 18.4 to 18.7 and Schedule 7 of the Code of Conduct and, although they do not have the force of law, failing to follow their spirit may reflect adversely on a person's fitness and properness (paragraph 4).

Firms treat the SFC's later circulars as the working expectations. The 6 February 2025 thematic review report found gaps in two-factor authentication, patching, encryption and administrator access, and a 9 July 2026 circular says one-time passwords are not phishing-resistant and sets 8 July 2027 as the latest date to adopt phishing-resistant login.

Why does it matter?

The Guidelines are the SFC's minimum standard for protecting clients' internet trading accounts, and the SFC checks them in thematic reviews and cites them in circulars. Senior management cannot hand off accountability: delegation is allowed in writing, but overall accountability stays with the responsible officers or executive officers (3.1).

Key benefits include:

  • Two-factor login comes first

Requirement 1.1 calls for two-factor authentication for login to clients' internet trading accounts, using any two of what a client knows, has or is.

  • Clients are told quickly

Requirement 1.3 requires prompt notices of logins, password resets, trade executions, transfers to unregistered third-party accounts and changes to account information, sent through a channel different from the one used for login.

  • Patches have a clock

Requirement 2.4 says to implement security patches or hotfixes within one month following completion of testing.

  • The SFC tests firms against it

Its February 2025 thematic review reported unqualified two-factor authentication, delayed patching, weak encryption algorithms, excessive administrator access and missing audit trails.

  • Phishing-resistant login is next

The SFC's 9 July 2026 circular says OTP does not meet its expectation for login and device binding, and sets 8 July 2027 as the latest date for the change.

How does it work?

The Guidelines open with a scope statement (paragraphs 1 to 5) and then list the 20 requirements. Group 1 covers client accounts: two-factor authentication, monitoring and surveillance, prompt notification, data encryption, protection of login passwords, and password policies and session timeout. Group 2 covers infrastructure: network, user access, remote connection, patching, end-point protection, unauthorized installation, physical security, backup, contingency planning and third-party providers. Group 3 covers governance, incident reporting, staff training and client alerts.

The SFC says the controls can reduce or mitigate hacking risks but cannot eliminate them, that they are minimum standards and not exhaustive, and that firms should implement measures commensurate with their structure, business operations and needs (paragraph 5). A firm reviews the user access list of critical systems and databases at least yearly (2.2), takes backups in an off-line medium at least daily (2.8) and gives all internal system users cybersecurity awareness training at least yearly (3.3).

The 2025 and 2026 circulars add expectations on top of the text. The 2 June 2026 circular on AI-enabled cyberattacks asks licensed firms to keep an accurate technology asset inventory, expedite patching, apply least-privilege access and review incident response, and holds the Manager-in-Charge of Information Technology ultimately responsible.

Key Elements

  • Account protection (1.1 to 1.6)

Two-factor authentication, monitoring to detect unauthorized access, client notifications, strong encryption of credentials and trade data in transit, system-generated passwords sent through a channel free from staff intervention, and password and session timeout controls.

  • Network and access controls (2.1 to 2.3)

A secure network with a Demilitarized Zone and multi-tiered firewalls around critical systems, need-to-have user access reviewed yearly, and security controls over remote connections.

  • Patching and endpoint control (2.4 to 2.6)

Patches implemented within one month after testing, anti-virus and anti-malware kept current on critical servers and workstations, and controls to prevent unauthorized installation of hardware and software.

  • Physical security, backup and contingency (2.7 to 2.9)

Physical access controls for critical components, daily off-line backups with a roll-back method for major changes, and contingency plans that cover distributed denial-of-service attacks and total loss of records through ransomware.

  • Third-party providers (2.10)

A formal service-level agreement that lets the firm meet Paragraph 18 and Schedule 7 of the Code of Conduct and these Guidelines, reviewed and revised regularly.

  • Cybersecurity management and supervision (3.1 to 3.4)

Responsible officers define the cybersecurity risk management framework, approve policies and budget and run a regular self-assessment. Written incident escalation procedures, yearly staff training and client cybersecurity alerts complete the group.

What does it cover?

The Guidelines apply to persons engaged in internet trading who are licensed by or registered with the SFC for Type 1 (dealing in securities), Type 2 (dealing in futures contracts), Type 3 (foreign exchange trading, licensed traders only) or Type 9 (asset management, only for funds distributed through internet-based trading facilities). Internet trading means order instructions sent through an internet-based trading facility (Code of Conduct paragraph 18.2(f)).

What are its objectives?

The Guidelines pursue three practical aims for internet trading firms.

Protect clients' internet trading accounts with two-factor authentication, monitoring, notifications, encryption and password controls (1.1 to 1.6).

Secure the infrastructure that carries trading and settlement: network, access, patching, backup and third-party arrangements (2.1 to 2.10).

Place cybersecurity oversight with responsible officers, with incident reporting, training and client alerts (3.1 to 3.4).

Framework in Context

The Guidelines sit under the SFC's Code of Conduct framework and were issued after consultation. The Hong Kong Monetary Authority issued a parallel circular to registered institutions on the same day. Later SFC circulars (6 February 2025, 2 June 2026 and 9 July 2026) apply and extend them for internet brokers and virtual asset service providers. The SFC says its controls can reduce but not eliminate hacking risks, so firms add measures that suit their own business.

Common Framework Mappings

Organizations commonly map established international standards and regulatory regimes to the SFC guidance to harmonize controls, demonstrate compliance across jurisdictions, and simplify audits and vendor assessments.

Mapped frameworks include:

EU DORA

ISO 27001:2022

ISO 27002:2022

ISO 27017

ISO 27018

ISO 27701

NIST CSF 2.0

NIST 800-53 Rev.5

SWIFT CSCF

SMARTSUITE

How SmartSuite Supports the SFC Internet Trading Guidelines

SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.

Use Cyber & IT Risk and Third Party Risk Management to hold each of the 20 requirements as an owned control with evidence and review dates, so the responsible officer can show two-factor login, patch timing, access reviews and provider agreements to the SFC.

Authentication and Notification Controls

Record, per trading platform, the two-factor method (1.1) and the five client notification events (1.3), with an owner and test evidence.

Yearly Access Review

Run the yearly review of user access to critical systems and client databases (2.2) with reviewer sign-off and follow-up actions.

Patch Window Tracker

Log each patch or hotfix with its release, test completion and deployment dates against the one-month window in 2.4.

Backup and Contingency Evidence

Keep daily off-line backup records (2.8) and contingency exercises for DDoS and ransomware scenarios (2.9) with open actions.

Third-Party Provider Register

Track outsourced internet trading services, service-level agreements and their review dates (2.10) with the approving officer (3.1(h)).

Incident, Training and Oversight Record

Capture incident escalations (3.2), yearly training completion (3.3), self-assessments and officer approvals (3.1) in one reportable record.

Related frameworks

EU DORA

DORA (Regulation (EU) 2022/2554) requires EU financial entities to manage ICT risk, report major incidents, test resilience and control ICT third-party risk, applying from January 17, 2025.

ISO 27001:2022

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

ISO 27002:2022

ISO/IEC 27002:2022 is the reference set of 93 information security controls in four themes, with attributes and implementation guidance, that supports an ISO/IEC 27001 ISMS.

ISO 27017

ISO/IEC 27017:2026 gives cloud security control guidance for customers and providers, built on ISO/IEC 27002:2022, with four cloud-specific controls; it replaced the 2015 edition.

ISO 27701

ISO/IEC 27701:2025 specifies requirements for a stand-alone privacy information management system (PIMS) for PII controllers and processors, replacing the 2019 edition.

NIST CSF 2.0

NIST CSF 2.0 (CSWP 29, February 26, 2024) is the voluntary cybersecurity framework with six Functions including Govern, 22 Categories, 106 Subcategories, Profiles and Tiers.

NIST 800-53 Rev.5

NIST SP 800-53 Rev. 5 is the NIST catalog of security and privacy controls in 20 families, mandatory for federal systems under OMB A-130 and FISMA; Release 5.2.0 issued August 27, 2025.

SWIFT CSCF

The SWIFT Customer Security Controls Framework (CSCF v2026) sets 32 mandatory and advisory controls that every Swift user attests to each year under the Customer Security Programme.

FAQ

Frequently Asked Questions For Hong Kong SFC — Cybersecurity Guidelines for Internet Trading

Persons licensed by or registered with the SFC who are engaged in internet trading for Type 1, 2 or 3 regulated activity, and Type 9 to the extent they distribute funds through internet-based trading facilities (Introduction, paragraph 3). The Guidelines do not have the force of law, but failing to follow their spirit may reflect adversely on a person's fitness and properness (paragraph 4).

There are 20 baseline requirements in three groups: protection of clients' internet trading accounts (1.1 to 1.6), infrastructure security management (2.1 to 2.10) and cybersecurity management and supervision (3.1 to 3.4). The SFC calls them minimum standards that are not exhaustive (paragraph 5).

The SFC announced the Guidelines on 27 October 2017. Two-factor authentication for client login took effect on 27 April 2018, and all other requirements on 27 July 2018.

Requirement 1.1 calls for two-factor authentication. In its 9 July 2026 circular the SFC says it does not consider an OTP phishing-resistant and expects internet brokers to adopt phishing-resistant login and device binding as soon as practicable and no later than 8 July 2027, with large internet brokers expected to move immediately.

Requirement 2.4 says to monitor and evaluate patches and hotfixes, test them as soon as practicable and implement them within one month following completion of testing. The SFC's 2 June 2026 circular asks firms to expedite patching and to handle urgent fixes outside routine cycles.

Put this framework to work in SmartSuite

Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.