Skip to content

Decide what to fix first

Risk
Assessment

We identify the threats that could realistically hurt your business, rate how likely and how damaging each one is, and hand you a register that ranks what to treat first. It follows NIST SP 800-30 and gives auditors the documented assessment that SOC 2, ISO/IEC 27001 and HIPAA expect.

From assets to decisions

What could hurt you,
and how much.

We follow NIST SP 800-30 Rev. 1, and report in ISO/IEC 27005 terms if you hold or want ISO/IEC 27001 certification. Ratings come from evidence and from interviews with the people who own each system, and every rating shows its reasoning so you can challenge it.

Phase 01 · Scope & context

Agree what is in scope and what matters most.

A scope statement naming the business processes, systems and data the assessment covers.

  • Business processes and the systems behind them listed with their owners.
  • Risk appetite discussed with leadership, in their words.
  • Regulatory and contract obligations that shape the assessment noted.

Phase 02 · Assets & threats

Name what an attacker or an accident could reach.

An asset and threat inventory tied to real scenarios rather than a generic catalog.

  • Crown jewel data and systems identified with the business.
  • Threat scenarios drawn from MITRE ATT&CK and your own incident history.
  • Accidents included too: outages, human error, supplier failure.

Phase 03 · Likelihood & impact

Rate each scenario with the evidence in view.

A rating for every scenario, with the reasoning written down so anyone can question it.

  • Existing controls checked, not assumed, before likelihood is set.
  • Impact scored across money, operations, legal exposure and reputation.
  • Ratings reviewed with system owners before they are final.

Phase 04 · Treatment

Decide what to fix, transfer, accept or avoid.

A treatment plan with owners, so accepted risks are accepted on purpose.

  • Treatment options costed in rough terms for each top risk.
  • Risk acceptance written up for leadership approval.
  • Quick wins separated from projects that need budget.

Phase 05 · Register & readout

Hand over a register your team keeps current.

A ranked risk register and a leadership readout your auditor can sample.

  • Register delivered in a format your team will maintain.
  • Top risks presented to leadership first.
  • Method documented so the next assessment compares like with like.

Agree what is in scope and what matters most.

A scope statement naming the business processes, systems and data the assessment covers.

  • Business processes and the systems behind them listed with their owners.
  • Risk appetite discussed with leadership, in their words.
  • Regulatory and contract obligations that shape the assessment noted.

Key benefits

Spend on the risks that matter.

Priorities you can defend

Each rating shows the evidence and reasoning behind it. When someone asks why one project beat another, the answer is in the register, not in someone's memory.

The assessment auditors ask for

SOC 2, ISO/IEC 27001 and the HIPAA Security Rule all expect a documented risk assessment. Ours follows NIST SP 800-30, so it answers that request directly.

A shared language for leadership

Risks are written as business scenarios with business impact. Your CFO and general counsel can weigh them against other spending without a security translator in the room.

What you get

What lands on
your desk.

Each handoff is written for the person who has to decide or act on it.

The document

The risk assessment report

Scope, method, threat scenarios and ratings with reasoning, plus a treatment plan for the top risks. Written so an auditor can trace each rating back to its evidence.

The working file

The risk register

One row per risk: scenario, owner, likelihood, impact, current controls, treatment and status. Built for your team to keep current after we leave, in a spreadsheet or your GRC tool.

The conversation

The treatment session

A working session with leadership to agree treatment and record risk acceptance. You leave with decisions made and owners named, rather than a document waiting for a meeting.

Client case studies

Real engagements.
Documented outcomes.

YHB | CPAs & Consultants testimonial

In their words

"ForgePath has become a trusted security partner for YHB. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."

Cyrus Kapadia
Chief Technology & Information Officer, YHB | CPAs & Consultants

Trusted by industry leaders.

Practical questions

Before the
first interview.

Straight answers from the practitioners who do the work. If yours is not here, ask us directly.

A program review asks how well security is run. A risk assessment asks what could go wrong and how badly. The two fit together: the risk register often decides the order of the program roadmap.

A sponsor in leadership, the owners of your most important systems and data, and the IT or security staff who know how controls are set up. Leadership joins the treatment session too, because accepting risk is their call.

That is what it is written for. The report documents scope, method and reasoning in NIST SP 800-30 terms, which SOC 2 and ISO/IEC 27001 auditors recognize. If your auditor expects a specific format, share it in scoping and we will follow it.

Most standards expect a periodic review and a fresh look after major change, such as an acquisition or a new platform. Because the method is documented, your team can refresh the register themselves, or we can rerun it with you.

Ready?

Bring us
the problem.

One conversation with a senior practitioner who has carried this responsibility before. We will tell you what we would do, and whether it is us.