DEFENSESTORM BLOG

From Framework to Risk Assessment: Five Steps to Close the Gap

Friday, November 20th, 2026

VIEW ALL BLOGS

Cyber security risk management solutions from DefenseStorm.

Many banks and credit unions have chosen a cybersecurity framework. For many, the work stopped there. A self-assessment was completed and filed, and the framework has had little to do with the program since.

In a recent DefenseStorm webinar, Jessica Caballero, VP of Banking Strategy, walked through how to get from having a framework to using one. This blog covers the five steps she laid out.

Step 1: Choose with the right criteria

The two frameworks institutions ask about most are NIST CSF 2.0 and the CRI Profile. They are closely related. NIST CSF 2.0 is general-purpose, written for any organization in any sector, and organized into six functions: Govern, Identify, Protect, Detect, Respond, and Recover. The CRI Profile keeps that structure and adapts it for financial institutions. It adds a seventh function, Extend, for third parties and supply chain. It adds diagnostic statements written to be assessed against. And it adds impact tiers that determine how many of those statements apply to a given institution.

A common assumption is that size should drive the choice. It should not, because both frameworks already account for it. NIST was written to fit any organization, and CRI scales by tier.

The better question is how much interpretation the team can absorb. NIST states outcomes and leaves the detail to the institution. CRI has the banking detail built in.

Institutions should also consider where they are today. One whose NIST program is already mapped to its controls has little to gain from switching.

One point applies to either choice. Examiners want to see that an institution uses a framework, but they do not examine against it. Their criteria are their own exam procedures. Progress against the framework needs to be readable in those terms as well.

Step 2: Map your control universe

An institution’s policies and controls are its own. The framework guides which controls are put in place, but it is usually not where the record of those controls lives.

That raises a question every institution should be able to answer: have you mapped your control universe to your framework, or are you self-assessing off of gut? If a framework statement is answered with “yes, we do that” and nobody can point to the specific control, the answer is gut.

A real mapping puts the control at the center and ties it to three things: the policy that requires it, the framework statement it satisfies, and the exam procedure that will ask about it. The evidence that the control operates is attached once and serves all three. Spreadsheets tend to hold one of these relationships at a time, which is why the full picture is hard to see.

Once the mapping exists, it shows which framework statements are covered, which are covered by a single control, and which have no coverage.

Step 3: Look for second-line blind spots

A completed self-assessment can still overstate coverage. There are five places to look.

  • Self-attestation: a statement is marked met because the first line said so, with no evidence attached.
  • Concentrated exceptions: exceptions are approved one at a time, and several end up weakening the same control or the same framework statement.
  • Single-control coverage: a statement is covered, but by one control, so one failure removes the coverage.
  • Evidence in disparate systems: the proof sits in separate tools and reaches the second line as point-in-time screenshots, never aggregated and never current.
  • Operational reality: a control exists in policy, with nothing to show that it is operating.

These share a cause. The second line cannot challenge what it cannot see, and operating evidence lives in technical systems that IT and cybersecurity teams run. The answer is to get that evidence in front of the people responsible for oversight.

Step 4: Track and mature continuously

Many institutions rebuild the self-assessment every cycle. When evidence is collected continuously, that is no longer necessary. The previous cycle’s work becomes the starting point, and attention goes to what changed.

Maturing has two parts. The first is moving up in rigor. NIST describes four tiers, from Partial, where practices are ad hoc, to Adaptive, where the organization improves continuously. The second is raising the institution’s own standard for what “met” requires: from a control that exists, to one with evidence that it operates, to one that has been tested.

Step 5: Connect it to the risk assessment

A framework lists controls. It does not list risks. A risk assessment needs threats, likelihood, impact, and inherent and residual risk, and none of those are in NIST CSF or the CRI Profile. A framework self-assessment is therefore not a substitute for a risk assessment, even though the two are often treated as the same thing.

They work together through the controls. The framework guides which mitigating controls appear in the risk assessment, and those controls are what reduce risk from inherent to residual. When the risk assessment shows that risk is higher than the controls can support, the framework indicates what should fill the gap.

This is also what makes a roadmap defensible. A framework self-assessment can produce a long list of gaps with nothing to rank them. The risk assessment provides the ranking: where risk is high and coverage is thin, that gap goes first.

The result: one story

When the framework, the controls, and the risks are mapped to each other and supported by operating evidence, the institution has one account of its program. The board hears it, the examiner hears it, and the roadmap is built on it.

DefenseStorm Risk Assessment, part of Risk & Governance, builds threat-informed risk assessments on the same platform that runs detection and response. The risk assessment draws on the first line’s real data, and each rating keeps the evidence and rationale behind it, so the story holds up when the board or the examiner asks why.

Watch the on-demand webinar, From Framework to Risk Assessment: Closing the Gap