Qualysec
Blog

Securities and Futures Act 2001 Cybersecurity Requirements: MAS Notices, Penetration Testing & Compliance in Singapore

Securities and Futures Act 2001 cybersecurity rules in Singapore, including MAS notices, TRM Guidelines, penetration testing and incident reporting.

Published on November 17, 2026
Read Time: 14 min
CONNECT WITH US

Summarize this blog post with

The Securities and Futures Act 2001 contains rules and guidelines on licensing and conduct for capital markets firms in Singapore, while the cybersecurity responsibilities are contained in separate MAS notices and guidelines. A number of searchers land at this point, and those looking for guidance are here for what they can find now.

The known facts:

  • The cyber hygiene notice for capital markets firms (FSM-N22) was issued on 9th May 2024 and took effect on 10th May 2024.
  • FSM-N21: the Technology Risk notification for the same group, which came into effect on the same date.
  • Incident reporting: the MAS circular of 16 December 2025 came into effect on 1 February 2026, and reports are sent via MAS-Tx.
  • There are six control requirements specified in FSM-N22. It doesn’t mention penetration testing.

So why is testing important? The examiner and counterparties read the control evidence and not the intentions. This guide provides an instrument map, a clause-by-clause test method, the reporting clocks and a finding template.

Meet with Qualysec’s security professionals to discuss testing your systems for trading or advisory: Schedule a meeting!

What are the requirements of the Securities and Futures Act 2001 in relation to Cybersecurity?

The Act is a licensing and conduct piece of legislation. It determines who can trade in capital market products, give advice about them, and be in charge of a market. Cyber duties are derived from the notices issued under the Financial Services and Markets Act 2022 (FSMA) and from MAS guidelines.

Both notices include capital markets entities. MAS lists the groups under FSM-N21, which include:

  • Engaging in the trading of capital markets products
  • Companies that include licensed and venture capital fund management
  • Corporate finance advisory
  • Providing custodial services
  • Product financing
  • REIT management
  • Markets and exchanges
  • Clearing houses
  • Trade repositories
  • Credit rating agencies
  • Securities crowdfunding
  • Central securities depositories

For all other matters, refer to the scope of FSM-N22, under section 1.1 of the Securities and Futures Act 2001. Who is covered is determined by the wording of each notice.

Which of the Securities and Futures Act Regulations and Notices apply?

Think of a ladder. The top item is the Act, followed by the Securities and Futures Act Regulations under the Act, followed by MAS notices, followed by guidelines. Notices bind firms. Guidelines establish expectations that are to be judged by supervisors.

Table 1 lists the sources of cyber duties for a capital markets firm under the Securities and Futures Act 2001.

Instrument Basis Applies to Cyber content
FSM-N22 Binding notice under the FSMA Capital markets financial institutions The six cyber hygiene controls are identified below:
FSM-N21 Binding notice under the FSMA Capital markets financial institutions The reliability, availability and recoverability of critical IT systems and IT controls to protect customer information.
TRM Guidelines (January 2021) Guidelines Financial institutions Vulnerability Assessment, Black and Grey Box Testing, Scenarios, Red Team, Remediation
MAS incident circular (16 December 2025) Circular, effective 1 February 2026 Financial institutions Incident Report – MAS-Tx template
PDPA breach notification Law Organisations that have personal data Inform PDPC within 72 hours after the assessment.

The rules are also on the move. In 2026, MAS consulted on amendments to technology risk notices. This feedback will close on 31 July 2026. The proposals cover:

  • An up-to-date list of all IT assets, including third-party parts
  • A risk register with owners and key risk indicators
  • Pre-release testing of all changes to significant systems
  • The continuous monitoring of critical systems is crucial.
  • Immutable or offline backups
  • Partial or intermittent disruption that counts towards downtime.

A 12-month transition would be provided after the final notices. These are recommendations, not regulations.

Rajah & Tann also explains the current downtime rule and cites it as: “The total unscheduled downtime for each critical system shall not exceed 4 hours over any 12 months.”

What is the Cyber Hygiene Notice asking for?

There are six controls on FSM-N22. Each one is shown with the test to determine it and the evidence to retain in Table 2.

Section Requirement How it is tested Evidence
4.1 Administrative user accounts are secured and restricted. Account review, then test use of dormant/shared admin accounts List of accounts and access logs.
4.2 Security patches applied, with timeframes “commensurate with the risks” Patch scan of Internet-facing and internal systems for missing patches Identify and document the patch details.
4.3 Security standards are in written form for systems Compare running configurations to standard Policy, configuration review
4.4 Network perimeter defence Test firewalls, remote access and exposed services Penetration test report
4.5 Malware protection Check coverage and try benign test payloads Report on coverage, results of tests
4.6 Multi-factor authentication for admin accounts of critical systems and for the internet access to customer information. Attempt to log on using just a password. Configuration export and test capture.

Note that there is an exemption in Section 3.1 for systems not under direct control of the firm or its provider or where the firm can switch provider. Take care to read it before using it.

MAS does not have any attestation obligation in the notice. Be sure to read the specific language of each section of the notice.

Is there a need for Financial Services Penetration testing for MAS?

Not by name. It is not mentioned in FSM-N22. The language for the testing is contained in the TRM Guidelines, not in a notice.

As summarised by the law firms:

They did not set a frequency or an independence rule. Firms make a decision according to risk.

It still has a “real world” use. Risk-based patching is requested in FSM-N22 section 4.2. A new company with no track record of testing would have a hard time demonstrating how vulnerabilities rank. Financial services penetration testing comes into its own when that happens. It is used to verify the functionality of controls.

Get Your Free Pentesting Quote

Our expert-led penetration testing helps secure your applications, networks, and infrastructure.

Get a Quote→

Table 3 provides a mapping of each of the requirements under the Securities and Futures Act 2001 to what the test can prove.

Control What it asks What a test proves Evidence
Patching (4.2) Correct mistakes identified on a risk-based time frame. The exposed systems are free of known flaws. Scan and retest reports
Perimeter (4.4) Protect the network perimeter All services are accessible only by intended ones. Penetration test report
MFA (4.6) This is the second factor for in-scope accounts. Admin console requires both name and password to unlock it. Configuration export and test capture.
Admin accounts (4.1) Restrict and control the use of privileged accounts Unused accounts and shared accounts are not susceptible to misuse. Account review, logs

How to Test a Capital Markets Environment?

A firm passes a test of a notice control under the Securities and Futures Act 2001 if it can demonstrate that the control works. One lap for each component:

  1. Record normal behaviour
  2. Change one input
  3. If it doesn’t work, take an alternate route to a similar solution
  4. Inspect the response
  5. Capture the evidence
  6. Retest after the patch.

Trading, Order Management and Client APIs

For order entry, amendment, cancellation and account endpoints, the scope is: scope:order_entry, scope:order_amendment, scope:order_cancel, scope: account.

Test: Request replays using a different client’s token, different quantities and different account numbers
Pass: All requests are denied, and no data across the client is returned.
Evidence: captures of evidence in the form of requests and responses

Client Portals and Mobile Apps

Target audience: Customers, mobile users, login, statements and transfers.

Test: credential stuffing, session reuse, hard-coded keys and weak local storage.
Pass: there is no secret to recover, and it is impossible to hijack sessions.
Evidence: logs and traffic captures.

Market Connectivity and Gateways

Parties involved: remote access gateways, VPNs, exchanges and clearing houses

Test: version checks for known flaws, authentication bypass attempts and exposed management pages.
Pass: The internet cannot reach any unpatched gateway.
These will serve as evidence.

Privileged Accounts and MFA

Avoid using the same password for any of the following accounts: scope: administrator, service and break-glass accounts.

Test: a password-only login to each admin console and role changes without approval.
Pass: Second factor enforced and revoked accounts are not allowed to log in.
Evidence: screenshots and access logs

Cloud or Third-Party Providers

Scope: storage permissions, build pipelines and vendor-hosted tools.

Test: open storage, shared credentials and scripts loaded from outside the firm.
Pass: no information is leaked that wasn’t intended to be exposed.
Evidence: permission exports and file comparisons.

Backup, Recovery and Monitoring

The scope includes backup and restore procedures, and alerting.

Test: restore a sample, then trigger a test alert.

Pass: The system returns the data unaltered, and the system sends the alert to an individual.

Evidence: logs and alert records

What measures are put in place to ensure financial data protection in Singapore?

There are two sources of financial data protection, namely from the MAS and the PDPC.

MAS: FSM-N21 requires companies to implement IT safeguards to prevent the disclosure or access of a customer’s information without authorisation. Incidents are passed through MAS-Tx from 1st February 2026.

PDPC: Report to the PDPC, within 72 hours after assessment, a breach that is likely to cause serious harm or involves 500 or more people. A data intermediary tells the organisation within 24 hours. See the PDPC guide.

Review the time requirements for MAS reports in the notice and in MAS’ reporting instructions. These are not the PDPC clock’s.

The MAS report should be the first part of a runbook followed by the PDPC assessment.

On 8 November 2023, ransomware hit ICBC Financial Services (FS), a US-based unit of the Industrial and Commercial Bank of China. According to Help Net Security, ICBC claimed the attack “disrupted certain FS systems”. FS was able to isolate and disconnect the affected systems.

According to Financial Times and Bloomberg, the LockBit gang is responsible for it. The sources report, but do not confirm. ICBC told us it had cleared trades with the U.S. Treasury on 8 November, and repo trades on 9 November.

The relevant portion is the patching. Security researcher Kevin Beaumont reported that an ICBC-owned Citrix NetScaler device remained unpatched for CVE-2023-4966 (Citrix Bleed). Citrix patched the bug on 10 October 2023, a month earlier, according to The Register. This bug isn’t confirmed as an entry point in either case.

ICBC FS is not a Singapore company, and the case is not a MAS case. Let’s see how it maps for a capital markets firm.

  • Control: FSM-N22 section 4.2, security patches installed within a reasonable time period based on the risks.
  • Test that finds it: a vulnerability scan of all Internet-facing gateways for vulnerabilities
  • Pass condition: No gateway is running a version that has a known and patched bug
  • Paperwork: scan report, patch record and retest result

Speak with Qualysec’s security professionals about testing your remote access gateways: Schedule a call!

Prepare for Your Next Cybersecurity Audit with Qualysec

Choose a partner that helps you identify and fix real security risks before attackers do. We are here to help.

Talk to an Expert→

Talk to a Cybersecurity Expert

What is included in a Financial Security Finding?

An examiner or counterparty reads the artefacts from a Securities and Futures Act 2001 file. The following should come with each finding:

  • Identify a problem, system and criticality
  • The instrument and section it relates to
  • Interface, preconditions and steps
  • Expected and observed behaviour
  • Evidence
  • Data regarding severity and customers disclosed
  • Remediation owner
  • Examine the results of the previous test and note the date.

Ensure that the steps are easy to replicate. A third party who is not a member of the build team should be able to do the same and get the same result.

Why Qualysec is useful for Capital Markets Firms

Qualysec’s MAS TRM penetration testing page explains penetration testing in web, API, cloud, network, and mobile testing modes, both black box and grey box. Findings have severity level, reproduction steps, and remediation information.

Application and API Penetration Testing

  • Endpoints for ordering, account, and client underwent testing for broken authorisation and injection.
  • Business logic issues with transfers and statements
  • Steps used to reproduce each finding

Penetration Tests for Financial Services in Cloud & Network Environments

  • The entire process of building pipelines and network segments for cloud storage underwent testing as a single chain.
  • The different types of remote access gateways and exposed services underwent review.
  • This involves checking how the mobile applications handle weak storage and/or sessions.
  • Each of these will undergo re-testing and be reported in a Notice-Mapped report.
  • Evidence of retesting verifies each fix and closes the findings.
  • You can place the sections of Table 2 next to each finding.

Testing is not a form of certification. The responsibility remains with the firm.

Keep your cloud infrastructure secure and compliant.

We catch cloud flaws before hackers do, clear your compliance hurdles, and keep your dev team moving fast.

Speak with a Cloud Security Expert→

Talk to a Cloud Security Expert

Conclusion

The Securities and Futures Act 2001 provides for the licensing of persons. The cyber duties derive from FSM-N22, FSM-N21 and the TRM Guidelines. FSM-N22 includes six controls and zero testing duty. The guidelines provide the yardstick for testing.

A firm that conducts tests, logs the owners, and retests each control will prepare for the supervisory question.

Determine your testing scope with the Qualysec experts: Organise a meeting!

FAQs(Frequently Asked Questions.)

Are there any cybersecurity rules codified into the Securities and Futures Act 2001?
The Act prescribes the rules for licensing and conduct. MAS prescribes the cyber duties in a notice in accordance with the Financial Services and Markets Act 2022 (FSM Notices 21 and 22). The notices contain the requirements for cyber hygiene; therefore, firms must read the notices and the TRM Guidelines together with the Act.

Who is the target audience for the cyber hygiene notice?
The notice does not define the scope of this section of the financial market, but rather it is defined by the financial institutions to which this section is applicable, which are the capital markets financial institutions as set out in section 1.1 of the notice. That means dealers, fund managers, exchanges and clearing houses, custodians and more. If the entity, its provider, or the provider-change option does not allow direct control of a system, please refer to Section 3.1, which exempts these systems from management. Look at the Act and the regulations to the Securities and Futures Act for the categories of licences.

Do Singapore Capital Markets Firms need to do penetration testing?
FSM-N22 does not have any named duty. The TRM Guidelines include Vulnerability Assessment and Black and Grey Box Testing as guidance. However, when it comes to risk-based patching under section 4.2, the advantage would be that most firms would back the controls with test records, and therefore that would be easier to defend. Retain the reports in the file.

When is a data breach reportable?
Two clocks apply. When a breach is likely to cause significant harm or impact 500 or more individuals, the PDPC expects a notice within 72 hours of assessment. A data intermediary must tell the organisation within 24 hours. MAS-Tx processes incidents reportable to MAS. Financial data protection Singapore rules dictate that companies should have plans in place for both.

Do third-party and cloud systems fall within scope?
Yes, in practice. Only systems that the firm cannot control itself, its provider or via the provider are exempt from FSM-N22 section 3.1. The firm has control over or can replace third-party gateways, cloud tools and vendor-hosted systems that it uses, which remain in scope. Test them and keep records on file to give an examiner proof of each provider’s tests.

What is the periodicity needed for the capital markets systems testing?

Test before launch, before significant changes, and regularly for critical systems. In addition, record a reason for the cycle and be able to tell MAS if they ask. Furthermore, critical systems typically require a shorter cycle than low-risk systems.

Pabitra Kumar Sahoo

About Pabitra Kumar Sahoo

Pabitra Kumar Sahoo is the Co-Founder and Chief Operating Officer (COO) at Qualysec. With a deep commitment to elevating global cybersecurity standards, he directs corporate operations and service strategy, helping enterprises mitigate compliance debt and defend their digital infrastructure through elite, human-led penetration testing.

Leave a Comment.

Your email address will not be published. Required fields are marked *

Related Blogs

Subscribe to Newsletter

Get the latest cybersecurity insights, compliance tips, and vulnerability reports delivered directly to your inbox.