Cybersecurity

Use cases

You probably arrived with a specific need in mind. These are the situations where organisations most often use our products, each one explained from the problem to what changes.

Start here

Find your situation.

Pick the one closest to yours, or filter by need. Each card opens a page with the detail: what changes on your network and what stays as it is.

Remote access

Give people access to internal systems from anywhere

Internal systems must stay reachable off-site. Publishing them creates a permanent attack surface; a classic VPN gives any valid credential network-wide reach.

Isolation

Run a network that never touches the public internet

Isolated networks still need rule changes, device updates and configuration control. Manual management drifts; a cloud console adds the outbound path isolation was meant to exclude.

Remote access

Protect company traffic without routing everything through the office

Full tunnel backhauls all traffic, personal included, through the gateway and degrades video. No tunnel removes control; manual exception lists drift on every device.

Integration

Add QS-WAN to the network you already have

New requirements land on a network built over years. Rip-and-replace stalls on downtime and risk; a parallel network doubles the estate you run and reconcile.

Remote access

Take the network with you

Temporary sites run over ad hoc, untrusted links with no local infrastructure. A consumer VPN secures the link only: no identity, access scope or device-state checks.

Compliance

Stay ready for the audit, not scared of it

Evidence for frameworks such as NIS2 and ISO 27001 sits across separate consoles and spreadsheets, assembled by hand each time an audit or questionnaire arrives.

Endpoint protection

Turn every company device into a protected endpoint

Separate VPN, endpoint protection, password manager and file-transfer tools mean separate consoles, renewals and policies, with coverage gaps between them.

Guidance

None of these?

Start from your network rather than from a template. Bring the topology you actually have and we work through it with you.

Useful to bring
  • 01Your sites, your users and the systems they need to reach
  • 02The equipment you already run and want to keep
  • 03The rules or frameworks you have to answer to
The common ground

One platform, with your team in control

They are one platform, not seven.

Whichever one you arrive through, you get QS-WAN as the console and QNova Client as the agent, with post-quantum encryption by default between them.

None of them is a managed service.

QuantumNova is a product. Nobody here watches your network. The platform produces the risk score and the evidence, and your people read them. That distinction matters more here than anywhere else on the site, because a page about a situation reads like a promise of somebody solving it for you.

A different way to look

By type of organisation

The same seven situations land differently depending on who is asking and what they have to prove.

01

Healthcare

A clinical group with several sites, external suppliers on the network, nobody dedicated to security, and a legal obligation that arrived by decree.

02

Financial services

DORA territory, where the demand is not just that you are secure but that you can demonstrate it on request, including for your own suppliers.

03

Public sector

Procurement rules, formal tender requirements and a preference for evidence over assurances.

See it running on your own network

Bring your sites and your topology, and we walk through how it would fit.

Scroll to Top