Financial services

Pen testing for wealth and investment managers: five attack paths to test first

Wealth and investment managers hold high-value client assets and sensitive data, move money on instruction, and often run lean IT teams that rely on platforms and outsourced providers.

If your annual pen test is “scan the website”, it’s probably testing the least likely way in. These are the five paths to look at first.

1. Client and adviser portals

Portals hold client data and instructions. The highest-impact issues are usually authorisation failures: one client seeing another’s valuations or documents by changing an ID, an adviser reaching clients outside their book, or a download that skips the access check. Scanners are poor at finding these. A tester with one test account per role finds them reliably.

2. Microsoft 365 and email

Payment instruction fraud and business email compromise are among the most damaging attacks a wealth manager can suffer. The typical route: a phished mailbox, mail rules that hide replies, then a convincing change of bank details. Testing should cover:

  • conditional access and MFA coverage, including legacy authentication;
  • which users can create forwarding rules or register applications;
  • email authentication (SPF, DKIM, DMARC) and resistance to spoofing;
  • how far a compromised user could reach in SharePoint and Teams.

3. Payment and instruction workflows

Every process where a client or adviser can change a bank account, request a withdrawal or authorise a transfer should be tested as business logic. Can a step be skipped? Can an instruction be replayed? Is the call-back check enforced by the system, or only by policy? These are the findings that link most directly to client harm.

4. Platform and third-party integrations

Firms connect to investment platforms, custodians, CRM, open banking and document services. Common issues include API keys stored in the wrong place, overly broad integration accounts and unauthenticated webhook endpoints. Test the integrations you own, and check what each supplier connection could do if it were compromised.

5. The internal network and Active Directory

Assume one laptop is compromised. How long until domain administrator, and what’s reachable — back-office systems, client document shares, backups? An internal or assumed-breach test answers the question boards actually care about: if someone gets in, how bad is it?

Making the results useful

For FCA-regulated firms, each finding should map to an important business service and a client-harm scenario. “IDOR on documents API” means little to a board. “Any logged-in client can download another client’s statements” gets fixed quickly.

The bottom line

Scope your test around how money and client data actually move through the firm. That’s where attackers focus — and where the regulator will expect assurance.

Frequently asked questions

What should a wealth management pen test include?

Client and adviser portals with multi-role authorisation testing, Microsoft 365 and email security, payment and instruction workflows, third-party integrations, and an internal or assumed-breach test.

Want a test scoped around your client journeys?

Fixed-price testing, scoped and delivered by a senior tester, with live findings on the SMARTSEC client platform.