Skip to content
Black Fox Security

03 / Governance and risk

Probability versus severity, written down and owned

We assess the risks to your infrastructure, network and applications, rank them in plain terms and help you decide what to treat, what to transfer and what to accept.

Overview

What a risk assessment gives you

Every security decision is a bet on two things: how likely something is to happen, and how bad it would be if it did. A risk assessment makes that bet explicit, so the budget goes to the risks that matter instead of the ones that are loudest.

We identify what you need to protect, what threatens it and which weaknesses make the threat real. Each risk gets a probability, a severity, an owner and a decision. The method follows established guidance such as ISO/IEC 27005 and NIST SP 800-30, scaled to your size.

The result is a risk register that your people can maintain, not a heat map that fades on a slide. It also feeds the obligations that ask for a risk-based approach, such as ISO/IEC 27001, NIS2 and DORA.

Who it is for

Organisations that need a documented risk assessment for ISO/IEC 27001, NIS2, DORA, a client or an insurer, and teams that have to decide where the next security budget goes. Also useful before a major change: a migration, a new product or a new supplier.

The work, from scoping to evidence.

What we do

  1. Asset and context mapping

    The systems, data, processes and suppliers that matter, who owns them and what the business needs from them.

  2. Infrastructure and network

    Risks in your network design, servers, endpoints, cloud services and remote access, assessed from architecture and configuration.

  3. Application risk

    Risks in the applications you build or rely on: authentication, data handling, integrations and the way they are deployed.

  4. Threats and vulnerabilities

    Realistic threat scenarios matched against the weaknesses we find, including results from tests you already have.

  5. Risk register

    Each risk with its probability, severity, owner, existing controls and residual rating, in a format you can keep up to date.

  6. Treatment options

    For each risk, a recommendation to reduce, avoid, transfer or accept it, with the controls and effort involved.

How the engagement runs

  1. Kickoff

    We agree the scope, the risk criteria and the people involved, and sign an NDA first if you need one.

  2. Proposal

    A business proposal with the method, the scope and the contract type that suits you.

  3. Discovery

    Workshops with owners, document and architecture review, and technical checks where the scope calls for them.

  4. Analysis

    Risks scored for probability and severity, compared with your risk criteria and ranked.

  5. Results handover

    The register, a business report for management and a technical report for the teams who treat the risks.

  6. Closing

    Project close with feedback, and optional consultation as you work through the treatment plan.

What you receive

  • Risk assessment method and risk acceptance criteria
  • Asset inventory for the assessed scope
  • Risk register with owners and ratings
  • Risk treatment plan with recommended controls
  • Business report for management
  • Technical report for the teams doing the work

Questions

Is a risk assessment the same as a penetration test?

No. A penetration test shows how specific weaknesses can be exploited. A risk assessment looks across the whole scope and asks which risks matter most. Test results are good input to a risk assessment, and a risk assessment tells you where testing is worth it.

Which method do you use?

One that fits your size and any standard you report against, typically following ISO/IEC 27005 or NIST SP 800-30. If you already have a method, we work with it.

Can we accept a risk instead of fixing it?

Yes, if it falls within your acceptance criteria and the owner signs off. Accepting a risk is a legitimate decision. Forgetting about it is not.

How often should it be repeated?

At planned intervals and whenever something significant changes. ISO/IEC 27001, for example, expects both. We can help you set a cadence that matches your rate of change.

Put your risks on one page

Tell us what you run and what keeps you up. We will help you weigh it.

Request a meeting

Send us a request to arrange a meeting, so you can tell us about your project and we can introduce ourselves and our experience properly.

§ A

Reading preferences

Adjust how this site looks and reads. Your choices apply at once and are kept on this device only.

Specimen

Good engineering is shown, not claimed. Read this line to judge your settings.

§ A.1Text

Text size
Line height
Letter and word spacing
TypefaceAtkinson Hyperlegible was designed for low vision; OpenDyslexic for some readers with dyslexia.
Align text leftRemoves justified text and hyphenation.

§ A.2Reading aids

Reading aidFollows your pointer to help you keep your place.
Highlight links
Highlight headings
Stronger focus outlineFor keyboard navigation.

§ A.3Colour and contrast

Contrast
Colour saturation
Hide decorative patternsRemoves the engraved line patterns behind content.

§ A.4Motion and pointer

Stop animationsAnimations are already reduced when your system asks for it.
Large pointer