Skip to main content
BUSINESS-RESOURCE • 6 min read

SOC Readiness for Financial Services: How to Train and Assess Your Analysts

An insurer's SOC receives an alert about an unusual sign-in to its claims management platform. The employee's credentials were recently reset by the help desk, and the account has since accessed several customer records.

The analyst needs to establish whether the activity is legitimate, what the account accessed and whether any data was exposed. That means connecting identity events, help desk records and application logs before deciding what happens next.

For financial institutions, this is what SOC readiness should measure: whether analysts can investigate suspicious activity, establish its potential impact and produce findings the response team can act on.

What SOC Readiness Looks Like in Financial Services

A bank might have experienced analysts, established playbooks and comprehensive monitoring, yet still struggle to investigate threats involving its most important services.

A compromised identity could expose payment infrastructure, while suspicious activity in an insurer's claims platform might require both technical investigation and business context.

SOC readiness depends on whether analysts can establish what happened, identify the affected systems and make supported decisions using available evidence.

For security leaders, the challenge is assessing those capabilities consistently and identifying where additional training or technical improvements are needed.

The Bank of England's 2025 CBEST thematic review, covering 13 assessments, identified weaknesses involving identity security, detection and response, network protection and staff practices.

These findings provide useful direction for training, particularly around compromised credentials, lateral movement and third-party access.

However, each institution should prioritise scenarios according to its own systems, incident history and unresolved findings.

Hands-on training
Build SOC Readiness With TryHackMe

Give your analysts the experience to investigate confidently and the skills to make every escalation count.

Explore TryHackMe's SOC Simulator

Four Investigations Financial Services SOC Teams Should Practise

1. Account Compromise and Suspicious Authentication

Let's assume an employee's authentication credentials are reset, followed by a login from an unfamiliar device and unusual activity in the claims platform.

The analyst needs to establish who requested the reset, whether the help desk followed its verification procedure and how the account was used afterwards.

Give participants the relevant identity events, help desk records and application logs. Include legitimate activity so the investigation requires judgement.

The completed investigation should identify the suspicious sequence, the account's access and any evidence of unauthorised activity.

If the analyst recommends revoking access, they should explain the potential impact and provide enough information for the identity or response team to act.

2. Lateral Movement Through Privileged Accounts

A compromised administrator account can give an attacker access to several systems, including infrastructure supporting important financial services.

Build an exercise using authentication and endpoint records showing the account connecting to multiple servers. Include ordinary administrative activity alongside suspicious access.

Analysts should identify the source and destination systems, reconstruct the sequence and determine which connections require further investigation. They also need to understand the consequences of restricting the account.

For example, disabling shared administrative credentials may interrupt legitimate applications.

The SOC should explain the security risk and affected dependencies so authorised service owners can make an informed containment decision.

3. Unusual Access to Financial or Customer Data

An attacker using valid credentials may access sensitive information through a legitimate application without triggering a malware alert.

For a bank, that could involve customer transaction records. For an asset manager, it might be portfolio information or investment reports.

Give analysts a scenario involving unusual application activity, such as a large data export or access outside an employee's normal responsibilities.

Their investigation should establish which account performed the action, what information was accessed and whether the records support an authorised business purpose. The application owner may need to explain what particular events mean or whether a similar export is part of normal operations.

The final report should distinguish confirmed access from suspected data theft.

An unusually large export deserves investigation, but it doesn't automatically establish that information was stolen.

4. Suspicious Third-Party Access

Financial institutions depend on external providers for applications, infrastructure and operational services.

When suspicious activity involves a supplier-managed account, the SOC may have only part of the evidence.

Consider a payment institution investigating unusual access through an integration maintained by an external provider. The analyst can review activity within the institution's environment but needs the supplier to establish how the account was accessed.

The exercise should assess whether the analyst can identify the relevant events, prepare a specific evidence request and escalate through the appropriate supplier contact.

It should also establish what response options remain available while the provider investigates.

If the SOC cannot obtain essential records, the institution may need to review its logging arrangements or supplier agreements.

Include Benign Activity in the Assessment

A useful training programme should also assess whether analysts can close alerts correctly. For example, an unusual administrator login might be explained by an approved maintenance window.

The analyst should verify that explanation, check for conflicting evidence and document why escalation isn't required. This is important because unnecessary escalations increase the workload of incident responders.

Assessments should reward accurate reasoning, whether the correct outcome is escalation, further investigation or closure.

Hands-on training
Build SOC Readiness With TryHackMe

Give your analysts the experience to investigate confidently and the skills to make every escalation count.

Explore TryHackMe's SOC Simulator

Measure Investigation Quality

A fast response means little if the analyst misses important evidence or passes an incomplete case to another team.

Agree the assessment criteria before running an exercise.

Assessment Area What to Measure
Investigation accuracy Whether the analyst correctly identifies malicious or benign activity
Incident scope Whether affected accounts, systems and relevant services are identified
Evidence quality Whether conclusions are supported and uncertainty is documented
Escalation quality Whether another responder can continue using the case report
Investigation time How long the analyst takes to reach a supported decision

Review how participants reached their conclusions. Two analysts may identify the same threat, but one might have correlated the relevant evidence while the other relied on assumptions.

Record assistance provided during the exercise, since completing a task independently demonstrates a different level of capability from completing it with guidance.

Timing should also reflect the work performed. Initial triage and a complete escalation are separate activities and may require different measures.

Check Whether the Handoff Works

An investigation is only useful if the receiving team understands what happened and what needs attention.

Compare these two escalations:

Possible account compromise. Unusual login detected. Please investigate.

Following an MFA reset, the affected account authenticated from an unfamiliar device and accessed the claims platform.

The help desk hasn't confirmed who authorised the reset.

Application logs show access to customer records, but data export remains unverified.

The second report identifies the evidence and outstanding questions, allowing the next responder to continue the investigation.

You can assess this through a shift-handover exercise. Give another analyst the completed case without a verbal explanation. Ask them to establish the incident scope, current findings and outstanding actions.

If they cannot, the report may need clearer reasoning or additional context.

Use Assessment Results to Guide Training

Start with a few scenarios connected to the institution's priorities: For example, a bank concerned about privileged account compromise could assess how analysts investigate unusual authentication activity.

Review the results to identify specific weaknesses: Some analysts may struggle to correlate identity events. Others may investigate accurately but produce incomplete escalations.

Assign targeted practical learning: Then repeat the assessment using a different scenario that tests the same skills. Changing the accounts, applications and sequence of events shows whether analysts can apply what they've learned.

Not every finding requires more training: Missing telemetry needs technical attention, while unclear escalation responsibilities may require changes to procedures.

Overall, SOC leaders should be able to connect each finding to the appropriate corrective action and establish whether it worked.

Build SOC Readiness With TryHackMe

TryHackMe's SOC Simulator gives analysts hands-on experience investigating alerts, identifying true and false positives, and producing case reports.

Scenarios use familiar SIEM environments, including Splunk, Elastic and Microsoft Sentinel, allowing analysts to practise investigations with tools relevant to their work.

For financial institutions, these exercises provide an opportunity to develop investigation skills, assess performance and identify where analysts need further practice.

Hands-on training
Build SOC Readiness With TryHackMe

Give your analysts the experience to investigate confidently and the skills to make every escalation count.

Explore TryHackMe's SOC Simulator
Ayomide Joseph A.
Nov 17, 2026

Recommended

Get more insights, news, and assorted awesomeness around cyber training.

Business • 9 min read

How security teams are preparing for Agentic AI

In the space of about two years, enterprise AI has moved from chatbots that answer questions to agents that take actions. They read email, browse the web, call internal tools, hold credentials and hand work to other agents. Most of that change has happened outside the security team's line of sight.

Business • 10 min read

How Banks Can Prioritise Cybersecurity Exercises Using NIST CSF 2.0

The NIST Cybersecurity Framework (CSF) 2.0 offers a useful way to make that decision. By connecting cybersecurity outcomes to existing evidence, banks can identify capability gaps, prioritise exercises and demonstrate whether their teams are improving.

Business • 9 min read

How to Run a Ransomware Tabletop Exercise for Banks

A ransomware tabletop exercise gives banks an opportunity to work through those situations before a real incident. By introducing realistic developments and examining how participants respond, security leaders can identify gaps in their procedures, decision-making and recovery arrangements.

Join over 640 organisations upskilling their
workforce with TryHackMe