Service

Security and Assurance

Threat modelling, hardening and control evidence for systems you operate, including incident readiness.

The Perseverance rover and the Ingenuity helicopter on the surface of Mars
Image: NASA/JPL-Caltech/MSSS. NASA library
On this page
  1. When this fits
  2. What the work covers
  3. What you receive
  4. How completion is decided
  5. What you provide
  6. What RJV does not promise
  7. How to start

When this fits

You need to know how a system can be attacked and what evidence shows that its controls work.

What the work covers

  • A threat model across identity, data flow, network design and service boundaries.
  • Hardening of the system to that model.
  • Control checks that produce evidence repeatedly, not once.
  • Incident readiness: escalation paths, evidence handling and a rehearsal.

What you receive

  • A written threat model and the findings against it.
  • The changes made or a plan for those the customer chooses to make.
  • The control checks and their results.

How completion is decided

Each finding is closed, accepted by name or left open with its reason recorded and the control checks are shown to fail when the control is removed.

What you provide

  • Access to the system and its owners, within an agreed scope.
  • Written authority for any testing of live systems.

What RJV does not promise

  • A fixed price or duration before the scope is known.
  • Regulatory approval or a certificate because the customer remains the regulated party.
  • That a system cannot be breached. An assessment states what was examined and what was not.

How to start

Describe the problem on the Work with Us page. Every engagement follows the stages on the engineering page and the commercial terms explain what determines scope and how the work is charged. Ownership at handover is described in deployment and ownership.

On a phone or tablet

Use the browser with a connection to the host.

See what works on your device
Find this offering
Browser (W)
Carry out every authorised operation
Client (C)
Compute on the device itself
Not supported (U)
Use a host you own
Client (C)
Work without the host or the internet
Not supported (U)

Nothing here needs a desktop because every operation that this site offers works in the browser on a screen down to 320 CSS px which is the narrowest width that we test. Where a row reads Not supported the browser is the alternative because we do not install the release on the device and no offline mode exists and the host that you control must be reachable and we do not use device sensors or accelerators.

Published
29 October 2026
Revision
2

Last reviewed 29 October 2026.