Essentials
£249/mo
or £199/mo billed annually
compliance, plus automation
Start free →Capability Gap Analysis
Compliance as capabilities, not a thousand controls
A control-by-control checklist tells you what to prove. It doesn't tell you what actually delivers the protection. 786 Cyber maps your frameworks down to the security capabilities they depend on — MFA, cloud posture, web and vulnerability scanning, patching — evidences each one from your own activity, and routes every gap to the fix that closes it.
What it does
A capability-level view
Instead of a control-by-control checklist, see the handful of security capabilities — MFA, cloud posture, web scanning, vulnerability scanning, patching — that your frameworks actually depend on, and how many controls each one carries.
Evidenced by your own platform
A cloud scan evidences CSPM. A web scan evidences WAF coverage. Your people data evidences MFA. 786 Cyber reads its own signals, so a capability is marked evidenced from real activity — not a questionnaire.
Honest by default
No signal means "unknown", never a false "covered". A detected tool marks the capability evidenced; the underlying control stays in review until you confirm it — the same discipline as the cross-map.
Every gap routed to a fix
Each gap is routed the right way: documentation gaps to policy templates, in-platform gaps to the module that closes them, and third-party gaps to a partner who can.
Reverse opportunities
When a capability you have already evidenced also covers controls in a framework you have not started, 786 Cyber surfaces it — progress toward your next standard that you have already earned.
How it works
786 Cyber joins the frameworks you're assessing to their controls, to the canonical controls those map to, and finally to the security capabilities that deliver them. For each capability it reports how many of your controls depend on it, whether your own platform signals evidence it, and — where it's missing — whether the gap is a documentation, in-platform or third-party fix. Capabilities you've already evidenced are then checked against frameworks you haven't started, surfacing coverage you've earned but not yet claimed.
Why 786 Cyber
Fewer things to prove. A dozen capabilities, not a thousand controls.
Evidence you already have. Signals from your own scans and data, not another questionnaire.
Honest coverage. Unknown stays unknown; nothing is marked covered without proof.
Cross-framework leverage. One capability counts across every framework it satisfies.
Frequently asked questions
What is capability gap analysis?
It reframes compliance around security capabilities — the kinds of tools and controls that deliver protection (MFA, cloud posture, web scanning, and so on) — and shows, per capability, which controls across your frameworks depend on it, whether it is in place, and how to close any gap.
How does 786 Cyber know a capability is in place?
It reads its own signals: a cloud misconfiguration scan evidences cloud posture management, a web scan evidences web-application protection, your people data evidences MFA coverage. Where there is no signal, the capability is reported as unknown — never assumed present.
Does detecting a tool mark my control as met?
No. A detected capability is marked evidenced, but the underlying control stays in review until you confirm it. Automated detection informs the assessment; it never auto-completes it.
See how your controls connect across standards in the Compliance Universe.
Start a 14-day free trial
No card required. See which capabilities carry your compliance on day one.