Risk Assessments
defended on every line.
Vorge replaces the Word documents, copy-pasted spreadsheets and one-off PDFs your team uses today with a structured, multi-user platform — built for refineries, mines, ports, and other critical infrastructure operators"
DESIGNED FOR
Operators of high-consequence facilities
DEPLOYMENT
Single-tenant cloud · onboarded in weeks
EVIDENCE STANDARD
Immutable, time-stamped, defensible line by line
THE ANNUAL SRA, AS IT STANDS TODAY
The Security Risk Assessment defending your facility is a Word file. Scattered across inboxes and shared drives. Nobody sure which version is the one.
PROBLEM 01
Ratings nobody can defend, evidence nobody can find
A 4 turns into a 5 between revisions and nobody remembers why. The "supporting evidence" is in someone's email, on a thumb drive, or in a slide deck two versions out of date.
"We had three different versions of the threat register going around. The Approver signed the wrong one and we didn't catch it until the audit."
- Security Manager, North Sea Operator
PROBLEM 02
Weeks of copy-paste from last year's file
90% of the asset register, threat catalogue and control language is stable year-over-year. But the only way to bring it forward is to open last year's .docx, copy what's still true, and re-key everything else by hand.
"My author spends the first three weeks of the SRA cycle just reformatting last year's document. That is not risk work."
- Head of Security, LNG Terminal
PROBLEM 03
No facility looks like any other facility
Each site uses its own template, its own threat names, its own scoring conventions. HQ can't roll up the data. The Board sees a stack of PDFs and is asked to draw conclusions across them.
"We can't tell our Board whether risk went up or down. The assessments aren't comparable, and they know it."
- Group CISO, Pipeline Operator
01 · HOW VANTAGE WORKS
From last year's PDF to a sealed, evidence-ready
assessment in three stages.
STEP 01 · CLONE & SCOPE
Bring last year forward in one click.
Clone the previous approved version. Vorge carries the structure, asset register, threat catalogue and control language. You change what's actually changed, and Vorge flags the rest as carried-over for explicit review.
Tartan West v2025.1 (Approved)
8 assets · 8 threats · 22 controls
+ contractor laydown (new)
STEP 02 · AUTHOR & REVIEW
Author drafts, Reviewer challenges, Approver signs
The Author drafts. The Reviewer comments line-by-line and locks fields whose ratings must not change without re-review. The Approver signs off, or sends back with a reason. Nothing leaves the system.
STEP 03 · Approve & Execute
Sealed forever. Mitigations tracked to closure.
Approval freezes the version with a cryptographic seal and a complete change history. Approved mitigations land on the responsible owner's dashboard with a target date and a status. Export a single PDF, a structured file, or a board brief — on demand. Errors discovered later create a new version. The sealed one stays untouched.
v2026.1 · sealed 25 Apr 2026
P. Vance (Facility Mgr.)
147 events · immutable
WHY WE BUILT THIS
We've sat on both sides of the SRA table.
Vorge is built by a team of risk assessment practitioners, with decades of combined experience across government, energy, maritime, mining, and other safety-critical industries. We've authored Security Risk Assessments at high-consequence facilities, sat across the table from a Group CISO challenging every line, and signed off on cycles that we knew at the time couldn't really be defended line by line. Vorge is the platform we kept wishing existed. Not a document tool with AI bolted on top. The workflow, the audit trail, and the matrix we needed every cycle.
Solomon Asonye, P.Eng
Vorge Founder
02 . WHO USES IT
Six accountable roles, one shared workflow
Each role sees only what they need, signs only what they own. Permissions, scoping and visibility are configured per-organization by your administrator.
01
Author
Owns the assessment day-to-day. Drafts each section, attaches evidence, responds to sendbacks. One Author per facility per cycle.
Editor
Comments
Evidence upload
02
Reviewer
Independent challenge. Locks contested fields. Threads challenges with required evidence. Cannot approve their own facility.
Field locking
Challenge log
Cross-facility view
03
Approver
Signs the cycle. Reads the reviewer summary, the audit trail and the residual heatmap. One-click structured sendback when needed.
Sealed sign-off
Sendback
Portfolio view
04
Mitigation Owner
Receives approved mitigations on a personal dashboard. Updates status, attaches progress evidence, closes out. Cannot edit the assessment that produced them.
My Mitigations
Status updates
Append-only progress log
05
HQ Executive
Read-only across the entire portfolio. Heatmap, trends, inconsistency flags, exportable board brief. Cannot edit assessments.
Read-only
Board export
Compare
06
Administrator
Manages users, facilities, the risk matrix, threat libraries and AI opt-in. Cannot author or approve assessments.
Users
Risk matrix
AI policy
03 . THE PLATFORM
One assessment system for every facility in your portfolio.
Vorge gives security and risk teams a single, structured workflow from facility data to executive sign-off — and an immutable evidence trail underneath all of it.
[01]
Structured, end-to-end assessments
A connected spine from executive summary through mitigation tracking. Assets, threats and evaluations share one source of truth across every section.
[02]
Enterprise-wide visibility
An executive view aggregates every facility into a comparable heatmap, surfaces inconsistencies, and tracks mitigation status across the cycle.
[03]
Immutable evidence trail
Every field edit, lock, comment, send-back and approval is time-stamped and preserved forever. Approved versions are read-only — by design, not by policy.
[04]
AI assistance
Drafts the slow sections from the structured data your team has already entered, and flags gaps a human reader would miss. Never sets ratings on the Author’s behalf. Every suggestion is logged in the audit trail.
04 . AI-ASSISTED AUTHORING
The blank page, solved. The defensible rating, intact.
Vorge's authoring assistant drafts executive summaries from the structured assessment data the Author has already entered, and surfaces inconsistencies as they write. It never sets ratings on the Author's behalf. Every suggestion is logged in the audit trail.
Drafted, not decided. AI proposes language; the Author accepts, edits, or discards. Every accepted suggestion is logged.
Tags from your library. Suggestions are drawn from your organisation's threat taxonomy — not a generic web model.
Off by default, opt-in per org. No customer data is used for training. AI features can be disabled at the workspace level.
Tartan West/v2026.1/Section 1 · Executive Summary
SAVED · 14:22
EXECUTIVE SUMMARY
147 / 600 words
Tartan West Refinery enters the FY26 review cycle with seven scenarios at Severe (5) or High (4) post-mitigation rating, down from nine in FY25. The dominant residual risk profile is shaped by cyber/OT exposure and persistent terrorism baseline status under critical national infrastructure designation. Two evaluations remain locked pending independent re-validation of pre-mitigation ratings.
SUGGESTED TAGS · DRAWN FROM YOUR LIBRARY
06 . CLONE LAST YEAR
Weeks of reformatting, gone.
Vorge doesn't ask the team to start from a blank page or rebuild structure. Pick last year's approved version, choose what to carry forward, and start from a working draft.
Selective carry-over. Bring forward what’s still true; flag what needs to be re-validated. The team decides; the platform tracks.
Year-over-year diff, built in. Every reviewer sees exactly what changed against last year’s approved version. In line, not in a separate document.
FY25 · Approved
v2025.1 · sealed
Crude Distillation Unit (CDU-1)
Criticality 5 · Primary distillation tower
8 classes carried — terrorism, cyber/OT, organised crime, civil unrest…
11 closed · 0 open
All from FY25 cycle complete
FY26 · Draft (cloned)
v2026.1 · 0d ago
Crude Distillation Unit (CDU-1)
Criticality 5 · carried-over
Contractor laydown (south service road)
Criticality 2 · new this cycle
9 carried-forward to re-evidence
Vendor SBOM programme · expanded scope
Cloned in 4 seconds. 0 assets · 0 threats · 0 controls carried over.
07 . ANOMALY FLAGS & RISK SCORING
The matrix you already use, watching for the things you'd miss.
Bring the matrix your team already uses. Vorge scores rigorously and flags the gaps a human reader would miss: assets without coverage, ratings that contradict last year, overdue or off-target mitigations, and cross-section inconsistencies.
Cross-section consistency. An asset rated Critical (5) with no scenarios mapped to it — flagged. A mitigation that doesn't reduce post-mitigation scoring — flagged.
Year-over-year drift. Severity rating changed by ≥2 levels between cycles? Flagged with last year's evidence trail attached.
Configurable, not hardcoded. Your Admin defines what counts as an anomaly. Vorge doesn't override your conventions; it enforces them.
08 . Evidence Trail
Every rating tells you who, when, and why.
Vorge writes an immutable, time-stamped record of every meaningful action in the system — field edits, comment threads, lock events, send-backs, approvals, AI suggestions accepted or discarded. Approved versions are sealed and addressable forever.
A1
Append-only event log
Every action is hashed and chained , tampering with the historical record is computationally detectable, not just policy-prohibited.
A2
Sealed approved versions
Once an Approver signs a cycle, the version becomes read-only. Future changes start a new version with a full diff against the sealed one.
A3
Per-field provenance
Hover any field to see who set the value, when, and what evidence was attached. Same answer next year. Same answer in five years.
A4
AI actions tagged in the trail
Every AI suggestion is logged, accepted, edited, or discarded, and by whom. No silent automation. No black box.
09 . SECURITY & ARCHITECTURE
Built like the systems you already trust.
[01]
Single-tenant deployment
Your data lives in your tenant. No cross-customer query paths. Optional dedicated cloud account.
[02]
SSO & SCIM
SAML 2.0 and OIDC. SCIM provisioning. MFA enforced at the platform tier — not optional, not configurable away.
[03]
Encryption
AES-256 at rest, TLS 1.3 in transit, customer-managed keys available on the enterprise tier.
[04]
Region pinning
Pin your data to US, EU or AU regions. No cross-region replication without your written approval.
[05]
AI opt-in, per-org
AI features are off by default. When enabled, no customer data is used to train models. Inference logs available.
[06]
Compliance posture
SOC 2 Type II in progress. ISO 27001 mapped controls. Penetration test summaries shared under NDA.
FREQUENTLY ASKED
Questions teams ask before
they switch.
Straight answers on security, deployment, AI, and how Vorge fits alongside the way your team already runs assessments.