Join our Newsletter — 33% off our NHI Course
Home› Guides› Asset Management Firm Cybersecurity Guide: Trading, Custody and…
Guide Security Leadership & Governance

Asset Management Firm Cybersecurity Guide: Trading, Custody and Regulatory Duties

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 11 November 2026 14 min read
On this page

An asset manager rarely holds client money itself, yet a single forged instruction, a compromised trader account or a breached fund administrator can move or expose millions of pounds or dollars of investor assets in an afternoon. This guide is a security programme for buy-side firms: investment advisers, fund managers, UCITS management companies and alternative investment fund managers. It covers what attackers target in a buy-side firm, the regulatory duties that apply in the US, EU and UK as of November 2026, how to protect trading and cash movement, and how to govern the custodians, administrators and data providers that hold most of the operational risk. It is written for chief operating officers, chief compliance officers, CISOs and heads of operations at small and mid-sized managers who run lean teams and outsource heavily. Bank-wide programmes are covered in the Banking Cybersecurity Programme Guide.

Key takeaways

  • Protect the instruction, not just the data. The most direct path to loss at a manager is a fraudulent instruction to a custodian, administrator or transfer agent, so payment and settlement instruction controls deserve the same weight as data protection.
  • Your providers hold your risk. Fund administrators, custodians, prime brokers and transfer agents run most of the processes regulators examine; contract for notification, test their controls and keep a current register.
  • US advisers now run under amended Regulation S-P. Larger entities had to comply by 3 December 2025 and smaller ones by 3 June 2026, so every SEC-registered adviser now needs a written incident response programme, service provider oversight and 30-day customer notice.
  • Trading access is privileged access. Order management and execution system roles, FIX connections and broker portals can move markets and leak material non-public information; manage them like administrator rights.
  • Machine credentials connect everything. SFTP keys, API tokens and service accounts link the firm to custodians, data vendors and administrators, and are often the least governed access in a small manager.

What attackers target in an asset manager

A buy-side firm's attack surface is shaped by outsourcing. Investor assets sit with custodians, investor records often sit with an administrator or transfer agent, and the firm itself holds the decision rights: who can instruct, who can trade and who can see positions before the market does.

AssetWhere it usually livesWhat an attacker wantsPrimary control
Settlement and payment instructionsCustodian and administrator portals, email, secure file transferRedirect redemptions, capital calls or fees to attacker accountsDual control, independent callback, standing instruction lock
Investor and client recordsAdministrator, transfer agent, CRM, investor portalIdentity data for fraud, account takeover of investorsAccess review, provider oversight, portal MFA
Orders and positionsOrder management system (OMS), execution management system (EMS), broker platformsFront-running, market manipulation, ransom leverageRole-based trading access, information barriers, logging
Research and deal informationFile shares, collaboration tools, data roomsMaterial non-public information for trading or resaleNeed-to-know access, DLP, barrier monitoring
Executive and portfolio manager mailboxesCloud emailImpersonation for payment fraud, insight into dealsPhishing-resistant MFA, forwarding rule alerts
Integration credentialsScripts, SFTP servers, middleware, cloud vaultsSilent, persistent access to provider dataCredential inventory, rotation, vaulting

The fraud path is usually mundane: phishing (MITRE ATT&CK T1566) gives access to a mailbox, an email forwarding rule (T1114.003) lets the attacker watch payment threads, and a well-timed change of bank details produces financial theft (T1657). The Business Email Compromise Response Playbook covers the response.

Regulatory duties as of November 2026

The rules below are those most buy-side firms meet. They are summaries, not legal advice; confirm scope for your entity with counsel.

Jurisdiction and ruleWho it coversCore security dutiesStatus
US: Regulation S-P, as amendedRegistered investment advisers, investment companies, broker-dealers and transfer agentsWritten incident response programme to detect, respond to and recover from unauthorised access to customer information; notice to affected individuals within 30 days of becoming aware of unauthorised access to sensitive customer information; written service provider oversight, with providers notifying within 72 hours; written records documenting complianceAdopted 16 May 2024. Larger entities by 3 December 2025; smaller entities by 3 June 2026
US: Regulation S-ID (Identity Theft Red Flags)Registered advisers that can direct transfers or payments from individuals' accounts to third parties, and other covered firms with covered accountsBoard-approved programme to identify, detect and respond to identity theft red flags and keep the programme updatedIn force since 2013; named in the SEC Division of Examinations fiscal year 2026 priorities, with focus on account takeover and fraudulent transfers
US: proposed adviser cybersecurity ruleAdvisers and fundsWould have added written cyber policies and incident reportingWithdrawn by the SEC on 12 June 2025; Regulation S-P and S-ID remain
EU: Digital Operational Resilience Act (Regulation (EU) 2022/2554)Managers of alternative investment funds (Article 2(1)(k)) and UCITS management companies (Article 2(1)(l)); certain smaller AIFMs under Article 3(2) of the AIFMD are excluded by Article 2(3)(a)ICT risk management framework, major incident reporting, resilience testing, ICT third-party risk and a register of information, applied proportionately under Article 4Applies from 17 January 2025
UK: FCA operational resilience rulesIncludes enhanced scope SM&CR firms, among other firm typesIdentify important business services, set impact tolerances, map and testIn force since 31 March 2022; mapping and testing deadline 31 March 2025; new operational incident and third-party reporting requirements from 18 March 2027

Firms with a New York licence may also fall under the NYDFS Part 500 Guide requirements, and listed managers under the SEC Cybersecurity Disclosure Rules Guide. Detail on each rule sits in the SEC Regulation S-P Amendments Guide, the DORA Guide and the Financial Services Cyber Regulation Map.

Securing trading and investment systems

Trading platforms are business-critical and latency-sensitive, which tempts firms to leave them outside normal access governance. Treat them as privileged systems.

  • Role design: separate portfolio manager, trader, compliance and operations roles in the OMS and EMS. Order entry, order approval and allocation should not sit with one person for the same account.
  • Pre-trade limits as security controls: restricted lists, position limits and fat-finger checks also stop a compromised trader account from doing much damage. Changes to limits should need approval and leave a log.
  • Broker and venue connections: keep an inventory of FIX sessions and broker portals, who can use each, and which credentials or certificates authenticate them. Disable sessions for brokers no longer on the approved list.
  • Information barriers: where the firm holds material non-public information, enforce need-to-know access to research and deal folders and monitor crossings. See the Information barriers and ethical walls guide.
  • Change control: trading system configuration, model code and allocation rules change through a reviewed process, with emergency changes reviewed after the fact.
  • Communications: trading conversations on personal messaging apps create both a records problem and an attack surface. See the Enterprise Messaging Retention and Off-Channel Communications Guide.

Protecting custody and cash movement

Managers instruct; custodians and administrators execute. Attackers exploit that hand-off. The controls below are NHI Mgmt Group recommendations built from common practice; agree them with your providers, because many sit on the provider side.

  1. Standing settlement instructions locked: agree with each custodian and administrator that new or changed beneficiary details need a separate authorised request through a channel other than email, plus a callback to a number already on file.
  2. Dual authorisation: every outbound payment and every change to bank details needs two authorised signatories, with neither able to approve their own request. See the Dual control and four-eyes approval guide.
  3. Investor redemption checks: redemption requests that change the receiving account, arrive soon after a contact detail change, or request full balance payment get extra verification by the administrator or transfer agent.
  4. Capital call and distribution notices: publish bank details only in the investor portal and tell investors you will never change them by email, so a spoofed notice stands out.
  5. Portal hardening: custodian, administrator and bank portals use phishing-resistant MFA, named users and a quarterly user review. Remove leavers on the day they leave.
  6. Reconciliation: daily cash and position reconciliation against the custodian catches unauthorised movements early.

These controls also support a Regulation S-ID programme, since account takeover and fraudulent transfers are exactly the red flags examiners named for 2026. The Account Takeover Prevention Guide covers investor-facing controls.

Governing administrators, custodians and other providers

For most managers, providers carry more operational risk than the firm's own estate. Regulation S-P now requires written oversight of service providers, DORA requires a register of information, and examiners in all three jurisdictions ask how you know your providers are secure.

ProviderWhat they hold or doContract and oversight points
Fund administratorNAV, investor records, payments, anti-money laundering checks72-hour incident notice for customer information, payment verification procedures, SOC 1 and SOC 2 reports, user access lists for your staff
Custodian and prime brokerAssets, settlement, financingInstruction authentication methods, callback rules, portal MFA, notification of suspected fraud
Transfer agentShareholder registers, redemptionsChange of address and bank detail verification, notice duties, recordkeeping
Market data and research vendorsData feeds, terminals, analyticsCredential handling, licence-based user lists, API key scope
Outsourced IT and managed securityYour endpoints, cloud and emailPrivileged access model, logging, right to audit, exit plan

Rank providers by what they can move or expose, review the top tier annually with evidence rather than questionnaires alone, and run at least one joint incident exercise with your administrator. The Third-Party Risk Management Guide and DORA ICT Third-Party Risk and Register of Information Guide cover the programme in depth.

Where identity fits

Small managers often have more machine identities than staff. Daily position files arrive by SFTP with key-based accounts, risk systems pull data with API keys, and reporting scripts log in to custodian portals with shared service accounts. Each is a standing path into investor data. Inventory them with an owner, store secrets in a vault rather than scripts or spreadsheets, scope API keys to read-only where the provider allows it, and rotate on staff departure and on any provider incident. See the Financial Services Identity Security Guide. Human administrator rights to email, cloud and trading platforms belong under the Privileged Access Management Guide approach.

Implementation steps

This sequence is NHI Mgmt Group's recommended order for a small or mid-sized manager starting from an informal programme.

  1. Map critical services: list trading, cash movement, investor servicing and reporting, with the systems and providers behind each. This doubles as the FCA important business service list and DORA critical function view.
  2. Lock down cash movement first: agree callback and dual authorisation rules with every custodian and administrator within the first month, because this is where losses are fastest.
  3. Enforce phishing-resistant MFA: start with executives, finance, operations and traders, then all staff and every provider portal. Pilot with one team, keep a documented break-glass account, and roll back per user if a provider portal fails.
  4. Write the incident response programme: include assessment, containment, the 30-day Regulation S-P customer notice decision, DORA or FCA reporting where relevant, and recordkeeping. Test it with a tabletop that includes the administrator.
  5. Repaper providers: add 72-hour notice, audit rights, access lists and exit terms at renewal, and build the provider register.
  6. Govern trading and machine access: role review in the OMS and EMS, FIX session inventory, and a credential register for SFTP, API and service accounts.
  7. Measure and report: give the board or management committee a quarterly view against the metrics below.

Decision guidance by firm size

QuestionSmall manager (under about 50 staff)Larger manager or fund complex
Build or buy security operationsManaged detection and response with clear escalation to the COOIn-house team or hybrid with a 24x7 provider
Who owns cyberCOO or CCO with an external virtual CISODedicated CISO reporting to the CEO or risk committee
Provider assuranceSOC reports plus a targeted call on payment and notice proceduresOnsite or virtual audits of top-tier providers and joint testing
Trading platformHosted OMS with vendor-managed infrastructure; focus on roles and MFASelf-hosted components need network segmentation and change control
TestingAnnual penetration test and payment fraud tabletopThreat-led testing where regulators require it, plus red teaming of payment paths

Detection and metrics

Log and alert on new mailbox forwarding and inbox rules, sign-ins to email and provider portals from new countries or devices, changes to standing settlement instructions, bulk downloads from research or investor folders, OMS role and limit changes, and use of dormant service accounts. Send logs off the systems that generate them, and keep them long enough to support a Regulation S-P investigation.

  • Payment changes verified: percentage of bank detail changes confirmed by independent callback (target 100 per cent).
  • MFA coverage: share of staff and provider portal accounts on phishing-resistant MFA.
  • Provider assurance: share of top-tier providers with a current assurance review and 72-hour notice clause.
  • Access hygiene: days from leaver date to removal across email, OMS and provider portals.
  • Machine credential age: share of SFTP keys and API tokens with an owner and rotated within policy.
  • Exercise cadence: incident tabletops run with the administrator in the last 12 months.

Framework mapping

Control areaNIST CSF 2.0NIST SP 800-53 Rev. 5Regulatory hook
Provider oversightGV.SC-07SA-9, SR-6Regulation S-P service provider oversight; DORA ICT third-party risk
Trading and admin accessPR.AA-05AC-6Regulation S-P safeguards
Investor data protectionPR.DS-01AC-6Regulation S-P safeguards
MonitoringDE.CM-09IR-6Regulation S-ID red flag detection
RecoveryRC.RP-01CP-10FCA impact tolerances; DORA business continuity
Governance reviewGV.OV-01IR-6Board approval of the S-ID programme

Common failure patterns

  • Trusting email for instructions: a change of bank details accepted on the strength of a reply from a known address, which an attacker controls through a compromised or look-alike mailbox.
  • Assuming the administrator has it covered: the manager stays responsible for Regulation S-P compliance even when a provider sends notices on its behalf.
  • Shared provider logins: one custodian portal account used by the whole operations team, so no one can tell who approved what and leavers keep access.
  • Orphaned machine credentials: SFTP keys and API tokens created by a departed analyst, still live years later.
  • Untested plans: an incident plan that names no one at the administrator and has never been run against the 30-day notice clock.
  • Trading outside governance: OMS roles granted at onboarding and never reviewed, with limit changes made without approval.

Practitioner checklist

  • Critical services mapped to systems and providers, reviewed annually.
  • Callback and dual authorisation agreed in writing with every custodian, administrator and bank.
  • Phishing-resistant MFA on email, cloud, OMS and all provider portals.
  • Written incident response programme covering the Regulation S-P 30-day notice and any DORA or FCA reporting.
  • Provider register with tiering, 72-hour notice clauses and current assurance evidence.
  • Regulation S-ID programme approved by the board, with account takeover and transfer red flags.
  • OMS and EMS roles, limits and FIX sessions reviewed at least quarterly.
  • Machine credential register with owners, vault storage and rotation.
  • Annual tabletop with the fund administrator.

Standards and references

Related NHI Mgmt Group resources: SEC Regulation S-P Amendments Guide · Financial Services Identity Security Guide · Financial Services Incident Response Guide · DORA Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 11 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.