Industries · Public sector

Public sector cybersecurity: answers a tender can accept

Public bodies do not buy on a demonstration. They buy on a document, scored against requirements written months earlier, and the supplier who cannot evidence a claim loses the point. QS-WAN is built so the evidence already exists, and so the whole platform can run on your own infrastructure.

What a tender actually asks
01
Evidence, not assurances
02
Where the data and console live
03
Which languages the product speaks

Each of those is a scored line, and each has a short factual answer here.

The constraint

The buyer is a process, not a person

In the public sector the person who needs the product rarely decides alone. A specification is written, responses are scored against it, and anything that cannot be evidenced is treated as absent, however true it is.

That rewards a very particular kind of supplier: one whose claims come with artefacts. An inventory of the cryptography used, per subsystem. Assessment results with a scale that includes not tested. A deployment model that can be described precisely rather than as a diagram with a cloud in it.

There is also a plain practical requirement that catches suppliers out: language. If the people using the console work in another language, the product either supports it or the line is lost.

What cannot be evidenced is scored as if it did not exist.
Where responses usually fall down
01

Hosting cannot be negotiated late

If the requirement says the management plane stays on your infrastructure, an exception request is a lost point rather than a conversation.

02

Claims without artefacts

Saying a product is quantum ready is worth nothing. Naming the standards it aligns with and producing the inventory is worth the line.

03

Language is a hard requirement

Interfaces that only exist in English are excluded in some competitions, and nobody tells you afterwards.

How QS-WAN answers a specification

Three answers that are usually scored

QS-WAN runs a private network from one console, and QNova Client puts it on the device. For a public body, three of its properties carry most of the scoring weight.

01

It can run entirely on your infrastructure

License the control plane onto your own hardware, physical or virtual, inside your own boundary. Or take a gateway we ship configured, or let us host it: the choice is yours and it is written down, not implied.

02

The cryptography is documented, not asserted

Key establishment and signatures between device, gateway and control plane are post-quantum by default, aligned with FIPS 203, FIPS 204 and CNSA 2.0, and hybrid by design. The inventory is documented by subsystem, which is the artefact an evaluator can attach.

03

Evidence with an honest scale

Assessments return pass, fail, partially satisfied or not tested, and the compliance crosswalk keeps missing evidence out of the denominator instead of scoring it as failure.

Two facts a tender usually asks for

15 languages in the console

QS-WAN is available in 15 languages, which answers a line that excludes a surprising number of suppliers.

Kernel drivers attested by Microsoft

Our kernel drivers are attested by Microsoft. That is the scope of the claim, and we keep the evidence to hand because this buyer checks.

What goes in the response

Four requirements, four places the answer lives

These four appear in almost every specification, and none of them need an exception request.

R1

Access control and separation

Gateways, VLANs and the edges between them, plus one certificate per gateway membership per device, exportable as CSV.

R2

Cryptographic assurance

Post-quantum by default, hybrid by design, with the inventory documented by subsystem and the standards named.

R3

Deployment and data location

Licensed on your infrastructure, shipped as a configured gateway, or hosted by us, stated plainly rather than sketched.

R4

Continuous assurance

Assessment results per gateway with a risk score built from 19 indicators, and a detection history kept rather than summarised.

The sentence worth putting in the response. A green confirmation means the intention was recorded; a gateway that was offline applies it on reconnect. Evaluators trust suppliers who write that down before being asked.

Where it stops

What we will not claim in a tender

It is cheaper to be exact here than to be corrected at clarification stage.

No certification claims

The platform helps you meet and evidence requirements. It does not certify you, and we do not describe ourselves as approved by any authority.

Not a managed service

QuantumNova is a product. Nobody here monitors your network or handles your incidents.

Platform coverage differs

Windows is the complete implementation, Linux is a genuine port with gaps we declare, and macOS and iOS are planned. We answer that line by column, not with a tick.

Remote support is in integration

It exists inside the signed agent and it is not fully productised yet. We say so rather than let a scoring sheet assume otherwise.

Send us the requirement you cannot get answered

Usually it is hosting, cryptography or language. Bring that line to a free demonstration and we will show you where the evidence for it comes from.

NEWSLETTER

Get weekly tips, product news and early access, straight to your inbox.

Scroll to Top