HARD KEEL
Sample report

Harbor Shop: what a scan finds, and the order to fix it in.

Harbor Shop is a made-up online shop we built with the mistakes we see most often, planted on purpose. Its keys and passwords are fake. Below is the report Hard Keel Quantum Scan 0.2.0 wrote for it on November 20, 2026, unedited apart from the layout. We will refresh it when the next version is out.

QUANTUM READINESS · 0 / 100 · HARD KEEL METHOD V1

A leaked key or password holds the grade at D or lower until it is revoked and removed. How the score works

3leaked keys or passwords
6uses of weak encryption
6exposed infrastructure settings
2uses of encryption quantum computers will break

Migration plan

NIST's final transition plan (IR 8547, October 2026) deprecates today's public-key algorithms (RSA, elliptic curve, Diffie-Hellman) after 2030 and disallows them after 2035. Key exchange comes first, because encrypted traffic recorded today can be decrypted once a large quantum computer exists.

OrderWhatUsesFilesWhenMove to
1AWS access key1app/settings.pyNowRevoke it and issue a new one, then load it from a secret store. Deleting it from the code leaves it in git history.
2Database password in URL1app/settings.pyNowRevoke it and issue a new one, then load it from a secret store. Deleting it from the code leaves it in git history.
3Private key1deploy/tls.keyNowRevoke it and issue a new one, then load it from a secret store. Deleting it from the code leaves it in git history.
4Public storage4infra/main.tfNowBlock public access. Share files through signed links or a CDN with access control.
5TLS 1.0/1.12deploy/nginx.conf, gateway/server.goNowRequire TLS 1.2 or later, ideally TLS 1.3.
6RSA1app/payments.pyNowUse 3072-bit keys or larger now, then plan the move to post-quantum methods.
7ECB mode1app/payments.pyNowSwitch to AES-256-GCM.
8MD51app/payments.pyNowSwitch to SHA-256 or SHA-3, unless it is only a non-security checksum.
9Weak TLS ciphers1deploy/nginx.confNowAllow only AES-GCM and ChaCha20 cipher suites.
10Open to the internet1infra/main.tfNowLimit the source to known addresses or a VPN, or put it behind a private network.
11Encryption at rest off1infra/main.tfNowTurn on encryption at rest, ideally with a customer-managed key.
12ECDH1api/auth.tsBy 2030Move key exchange to ML-KEM (FIPS 203), or hybrid X25519 + ML-KEM-768 for TLS.
13ECDSA1api/auth.tsBy 2030 to 2035Move to ML-DSA (FIPS 204) or SLH-DSA (FIPS 205) signatures.

This report lists what the scanner found in source code and infrastructure config in the repository. It does not cover compiled dependencies, running services or certificates in use. Hard Keel can assess those separately.

Beyond the code

A clean scan is one layer. Most breaches start with a person: a phished password, a shared admin account, a step skipped because nobody wrote it down. Keep tools that touch production sandboxed, give each account only the access it needs, teach people to spot social engineering, and write down the procedures your team follows. For data in the cloud, use end-to-end encryption, so the provider only ever holds data it can't decrypt.

Files from this scan

Run it on your own code with npx @hardkeel/quantum-scan.