WHO THIS HELPS

A business view of cyber risk.

For business owners, IT managers and leadership teams planning security investment, supplier assurance or a wider governance programme.

THE PROBLEM TO SOLVE

A technical issue is only part of a business risk. Critical dependencies, likely impact, existing controls and the ability to recover all influence what deserves attention.

What you receive

Receive a documented risk register, a leadership summary and a treatment roadmap. We distinguish verified evidence from assumptions and identify areas needing deeper technical assessment.

A DEFINED ENGAGEMENT

What the work can cover.

01

Business context, important assets and service dependencies.

02

Threat and control review supported by interviews and available evidence.

03

Risk evaluation using an agreed method and clear assumptions.

04

Prioritised treatment options, ownership and review criteria.

How delivery works

We agree scope and risk criteria, gather evidence, assess scenarios and discuss realistic treatment choices with the people accountable for the business.

After delivery

Risk owners track treatment and formally accept residual risks where appropriate. Revisit the assessment after major changes or incidents.

What shapes scope and price

Business units, systems, suppliers, evidence quality, interview needs and assessment depth influence effort. Technical testing and detailed legal analysis are separate unless specified.

Your proposal sets out the deliverables, assumptions, exclusions and responsibilities before work begins. No fixed price or contractual inclusion is implied by this page.

Questions worth asking.

Can this support UK GDPR security work?

It can inform technical and organisational security measures. A security assessment alone does not establish complete data protection or legal compliance.

Can you assess suppliers?

Supplier dependencies can be included through evidence review and targeted questions. Scope and access determine the assurance possible.

What do we receive from a risk assessment?

The output should explain important business risks, the evidence and assumptions behind them, and a prioritised treatment plan with owners. The aim is to support decisions about controls and investment, rather than produce an unowned list of technical issues.

How are proposed treatments followed up?

Your team agrees the treatment decisions and accountable owners. Progress can be reviewed against evidence of change, with residual risk recorded where appropriate. Implementation and specialist technical validation are separately scoped when needed.

What affects the depth and cost of the assessment?

Business services, systems, supplier dependencies, available evidence and stakeholder access affect the work. The proposal should distinguish a broad risk review from detailed testing or legal analysis, and explain the assessment boundaries.

LET’S DEFINE THE RIGHT SCOPE

Turn cyber risks into an owned treatment plan

Outline the business services, systems and decisions the assessment should inform. We can agree evidence needs, stakeholder involvement and a risk treatment plan your team can own.

Virtual CISO →
Cloud Security Assessments →
Incident Readiness and Tabletop Exercises →