Your security team has completed its assigned training. The dashboard shows strong participation, certifications are up to date, and everyone has finished their required modules.
But can the people responsible for your payment systems investigate a compromised account? Can your incident response team contain an attack without disrupting critical services?
These are the questions financial institutions need to answer when assessing their security capabilities.
Regulatory frameworks and supervisory guidance provide expectations for cyber security training, risk management and operational resilience. Turning those expectations into effective workforce development requires a clear understanding of what people need to do and how their performance will be assessed.
A security skills mapping framework helps connect those responsibilities to practical training and evidence.
This guide explains how financial institutions can map security capabilities to DORA, NIST CSF and FFIEC guidance, identify meaningful skills gaps and build a training programme that supports internal oversight and regulatory readiness.
What Do DORA, NIST CSF and FFIEC Expect From Security Training?
Financial institutions often use several frameworks to guide security operations and workforce development.
Each serves a different purpose, so understanding those differences is important before building a skills map.
DORA: Training That Reflects Operational Responsibilities
The EU's Digital Operational Resilience Act (DORA) establishes requirements for managing information and communication technology (ICT) risks across covered financial entities.
Article 13(6) requires ICT security awareness programmes and digital operational resilience training as compulsory elements of staff training schemes.
The training must cover employees and senior management, with complexity appropriate to their functions. Relevant ICT third-party providers should also be included where appropriate under the Regulation.
For a financial institution, this means training should reflect the responsibilities people hold.
A SOC analyst needs the skills to investigate suspicious activity, while an incident commander may need to evaluate containment decisions and coordinate the wider response.
The European Insurance and Occupational Pensions Authority (EIOPA) has also clarified that training frequency should reflect employees' roles and responsibilities.
NIST CSF 2.0: Defining Role-Based Security Capabilities
The NIST Cybersecurity Framework (CSF) 2.0 provides a structured approach to understanding and managing cybersecurity risk.
Its Awareness and Training category includes PR.AT-02, which addresses the knowledge and skills people in specialised roles need to perform their security responsibilities.
Financial institutions can use this outcome to identify relevant tasks, organise development programmes and assess whether staff have the required capabilities.
NIST CSF is a voluntary framework unless adopted through an applicable requirement or obligation. Mapping training to it does not automatically establish regulatory compliance.
FFIEC: Connecting Training to Security Responsibilities
For US financial institutions, the Federal Financial Institutions Examination Council (FFIEC) provides guidance through its Information Technology Examination Handbook.
The Information Security booklet addresses the importance of training personnel to understand their security responsibilities and perform their roles effectively.
This includes maintaining awareness of relevant threats and adapting training as risks change.
Explore customised learning paths, training assignments and progress reporting
How to Build a Regulatory Security Skills Map
A useful skills map connects three things:
- the expectations relevant to your institution,
- the responsibilities assigned to your security teams, and
- the evidence that demonstrates their capability.
1. Identify the Business Service and Security Responsibilities
Let's assume a retail bank that wants to strengthen its response to suspicious activity affecting customer payments.
Several roles may contribute to that response. The SOC analyst investigates the initial activity, an identity engineer can restrict compromised access, and an incident commander coordinates the response.
The payment service owner may also need to assess whether a proposed security action could interrupt legitimate transactions.
Each role requires different skills. Rather than assigning everyone the same general incident response course, define what each person should be able to do.
For example, the SOC analyst should be able to identify the affected account, investigate related transactions and prepare an actionable escalation.
The incident commander should be able to use those findings to assess the threat and authorise the appropriate response. These tasks give the institution something specific to assess.
2. Connect Each Task to a Relevant Expectation
Once responsibilities are clear, identify the applicable regulatory obligations, guidance and internal policies that inform them.
Record the source, relevant section and reason for the mapping. For example, a bank may use NIST CSF to structure role-based training while separately considering its obligations under applicable law and supervisory expectations.
One exercise can provide useful evidence for several purposes, but each relationship needs to be explained.
3. Define How the Capability Will Be Assessed
The next step is deciding what evidence would demonstrate that someone can perform the task.
- A knowledge assessment may establish that an analyst understands an incident response process.
- A hands-on investigation can show whether they can examine evidence and make an appropriate decision.
- A team exercise can assess how responders coordinate actions and communicate with business owners.
Choose the assessment based on the responsibility being evaluated.
Explore customised learning paths, training assignments and progress reporting
Example: A Security Skills Mapping Matrix for a Bank
The following is an illustrative mapping for a payment-related incident. It connects selected expectations and internal responsibilities to tasks and possible evidence.
In a working version, include the exact source reference and the institution's applicability rationale for each entry. You should also record when the assessment took place, which scenario was used and whether participants needed assistance.
Explore customised learning paths, training assignments and progress reporting
How to Measure Security Skills Beyond Course Completion
Training completion shows that someone participated in assigned learning.
For critical security responsibilities, institutions may also need to understand whether employees can apply that knowledge in practice.
Consider a SOC analyst investigating suspicious access to a payment application. The analyst receives authentication logs and application activity indicating that an account may have been compromised.
A practical assessment can examine whether they correctly identify the affected identity, investigate related activity and communicate the findings.
The outcome should be based on observable behaviour.
For example:
- Independent performance: The analyst investigates the available evidence and produces an accurate escalation without assistance.
- Assisted performance: The analyst completes the investigation after receiving guidance.
- Incomplete performance: The analyst cannot establish the required findings or communicate the appropriate next action.
This makes the development need easier to understand. An analyst who struggles to interpret authentication records may benefit from further technical investigation practice.
Someone who identifies the threat but cannot communicate the next action may need additional reporting and escalation exercises.
Separate Skills Gaps From Operational Problems
Not every unsuccessful assessment means the employee lacks knowledge.
An analyst may understand which evidence they need but lack permission to retrieve it. In the same case, an incident commander may identify the correct response but have no clear process for obtaining approval.
Those are operational weaknesses that training alone cannot resolve. Record the underlying cause so the appropriate owner can address it. When the issue is resolved, repeat the assessment using a comparable scenario to establish whether performance has improved.
Build Role-Based Security Capabilities With TryHackMe
Financial institutions need to understand whether their security teams have the skills to protect critical services and respond effectively when incidents occur.
Connecting security responsibilities to recognised frameworks, practical assessments and targeted development gives leaders a clearer view of where their teams are prepared and where further investment is needed.
TryHackMe's Management Dashboard helps organisations structure and manage role-based security training.
Security leaders can map learning content to frameworks such as NIST, MITRE ATT&CK and ISO 27001, or organise it around their own requirements.
Explore customised learning paths, training assignments and progress reporting
Ayomide Joseph A.