KOLM SHIELD
Quantum-safe security for financial services · data in transit and at rest
Provable

Your systems can prove the credential was used.

Not provable

They cannot prove that you used it.

Everything we build lives in that gap.Kolm Shield secures data in transit and at rest against today’s attackers and tomorrow’s quantum computers, and answers the question a valid credential cannot: whether the hands using it are the ones it was issued to.

Protects
Data in transit and at rest
Standards
NIST FIPS 203 · 204 · 205
First sector
Financial services
Status
Patent pending, PCT filed
The gap

The attack looks legitimate.

A stolen credential does not produce a suspicious instruction. It produces a correctly signed one, and every check you own approves it, correctly.

Post-quantum migration ensures a signature cannot be forged. It does nothing about a signature made with a real key, in the wrong hands.

The position

The attack is prepared in the interval no control measures.

Post-quantum migration, access control and incident detection are each necessary, and each answers its own question well. What none of them measures is the interval in which an attack is prepared: a valid credential, in the wrong hands, on a channel that is cryptographically sound, often weeks before anyone classifies an incident.

Post-quantum migration

Can this signature or session be broken?

Not once it is migrated, including by a future quantum computer. It says nothing about who holds the key.

Authentication and access

Is this credential valid?

Yes, and that is the difficulty: a stolen credential is a valid one, and every check approves it, correctly.

Detection and response

Has an incident occurred?

Usually answered after the act. The weeks before it are the interval disclosures and controls were never designed to count.

Kolm Shield

Is an attack being prepared, and are these the hands the credential was issued to?

Answered before the act, with the reasons attached, on cryptography built to outlast the algorithms in use today.

  1. Beside the path, by default.It advises and your systems decide. It can be removed at any stage.
  2. Warnings with their working.Reviewable by your team, your auditors and your regulator.
  3. Built for the failure mode.The whole of financial services first; the same two acts everywhere else.
Why now

The calendar is set by other people.

The window to move early is the current procurement cycle, not the next one. The institutions that migrate last will be the ones whose archives were worth taking first.

The deadlines in plain terms

Aug 2024FIPS 203 · 204 · 205
The standards were published. Waiting for clarity stopped being a defensible position on that date.
Jun 2026EO 14412
The first deadline became binding. US federal systems and, through a contracting rule, their suppliers: post-quantum encryption by the end of 2030, authentication by the end of 2031.
Today
Harvest now, decrypt later is already running. The deadline that matters is how long your data has to stay secret.
Writing

The thinking is public. The build is not.

Current series · Four parts · Weekly from 28 September

The Uncounted

Two measured categories of loss, and a third that neither captures. Four South African cases from the public record, read as one pattern.

3 / 4 published

Next, from NovemberBefore It Becomes Materiala newsletter for boards

  1. IThe three weeks nobody countsDwell time, and the interval financial-sector controls and disclosures were never designed to measure.Read →
  2. IIOne provider, many perimetersThird-party concentration, and why an institution’s own controls cannot see the environment that now holds its clients’ data.Read →
  3. IIIThe request that looked legitimateTrusted channels, and what happens when a process is followed correctly and the request itself is fraudulent.Read →
  4. IVIdentity at the sourceWhat happens to onboarding checks once the documents they depend on are themselves in circulation.19 Oct
Bring the hardest question you have

We would rather be tested early than admired late.

Request a briefing →

briefing@kolmshield.com

Briefings, and our security and compliance documentation, are shared under mutual non-disclosure. Investors and candidates: see Company.