Every security event MDRwatchdog detects is sealed into a SHA-256 hash chain and dual-signed with Ed25519 and ML-DSA-87—the NIST FIPS 204 post-quantum standard. Hand your CMMC assessor, SOC 2 auditor, or cyber-insurance underwriter a public key and a URL. They verify your full security history independently. No MDRwatchdog login. No infrastructure access. No trust required.
Each audit record contains the SHA-256 hash of the previous record. Editing, deleting, or reordering any record changes its hash — which breaks every hash that follows. Tampering is detectable at the exact sequence number where it occurred.
Hourly, MDRwatchdog seals a block of records with both Ed25519 (classical) and ML-DSA-87 (NIST FIPS 204 post-quantum). The block proves the chain was intact at that moment. Both signatures are stored and independently verifiable.
The public key and verification endpoint are published. Any party — assessor, insurer, attorney — can verify your entire chain using cryptographic math. They need only the public key. They do not need to trust MDRwatchdog.
A CMMC assessment you complete today produces evidence that may be reviewed in a contract dispute, litigation, or follow-on audit years from now. If quantum computers break Ed25519 in that window, evidence signed only with classical algorithms becomes mathematically suspect.
MDRwatchdog dual-signs every audit block with both Ed25519 and ML-DSA-87. The Ed25519 signature is efficient and compatible with every tool today. The ML-DSA-87 signature is based on the hardness of lattice problems — a mathematical structure that Shor's algorithm, the primary quantum attack on classical cryptography, cannot exploit.
NIST standardized ML-DSA (Module Lattice-based Digital Signature Algorithm) as FIPS 204 in August 2024 — the first post-quantum signature standard the US government has published. MDRwatchdog implemented ML-DSA-87, the highest-security variant, on every audit block.
No other managed detection and response platform at any price point currently signs customer audit evidence with a NIST post-quantum standard. MDRwatchdog does it on every hourly block, automatically, for every customer, at no additional cost.
Verify AU.L2-3.3.1 and AU.L2-3.3.2 with a cryptographic proof rather than a vendor attestation. The chain integrity check is a one-line API call. No log review required.
Receive a shareable verification link unique to your organization. Open it, see chain intact, record count, date range, and signed blocks. No broker call, no questionnaire follow-up.
CC7.2 requires that security events are detected and logged. A tamper-evident, independently verifiable chain is the strongest possible evidence that the log is complete and unaltered.
Security events are often central to breach litigation. A cryptographically sealed, timestamped, hash-chained record is admissible evidence. A database printout is not.
DFARS 252.204-7012 and NIST 800-171 both require audit log retention and integrity. The hash chain satisfies the integrity requirement; the quantum-resistant signature future-proofs it.
When a board asks whether the company has records of its security posture at a specific date, the answer is a URL and a public key. The verification takes seconds.
Included in all plans at no additional cost.
A quantum-resistant audit chain is a sequence of security event records where each record contains the cryptographic hash of the previous one, forming a chain. Any alteration, deletion, or reordering of any record breaks the chain at that point and is immediately detectable. MDRwatchdog signs each batch of records with both Ed25519 (classical) and ML-DSA-87 (NIST FIPS 204 post-quantum standard), so the chain remains verifiable even after quantum computers can break classical signatures.
ML-DSA-87 is the highest-security variant of Module Lattice-based Digital Signature Algorithm, standardized by NIST as FIPS 204 in August 2024 — the first post-quantum digital signature standard the US government has published. Classical signatures like Ed25519 can in theory be broken by a sufficiently powerful quantum computer running Shor's algorithm. ML-DSA-87 is based on the hardness of lattice problems, which Shor's algorithm cannot attack. MDRwatchdog signs every audit block with both, so your evidence is protected today and in the quantum era.
MDRwatchdog publishes its Ed25519 and ML-DSA-87 public keys and a verification endpoint. Any auditor, assessor, cyber-insurance underwriter, or opposing counsel can fetch your signed audit blocks from that endpoint, verify the cryptographic signatures using the public keys, and confirm the hash chain is intact — without logging in, without contacting MDRwatchdog, and without access to our infrastructure. The verification is a mathematical proof, not a statement from us.
A standard security log is a file or database table. Any administrator can edit, delete, or reorder entries after the fact. There is no way to prove the log was not altered. A hash chain makes retrospective alteration cryptographically detectable — editing any past record changes its hash, which breaks every subsequent hash in the chain. The dual signature proves the chain existed and was intact at the moment of signing. No conventional log provides this guarantee.
The hash-chained, cryptographically signed audit trail directly supports CMMC AU.L2-3.3.1 (create and retain system audit logs) and AU.L2-3.3.2 (ensure actions can be traced to users), and the corresponding NIST SP 800-171 controls. It also supports SOC 2 CC7.2 and HIPAA § 164.312(b) audit control requirements. The independent verifiability means auditors can confirm the log's integrity without relying on MDRwatchdog's attestation.
Signed blocks are stored in your Postgres database on Railway and are independently verifiable using only the public key — which anyone can hold. If MDRwatchdog ceased to exist, any party with the public key and the signed blocks (which can be exported at any time) could still verify the full chain. The evidence is not dependent on MDRwatchdog's continued operation.
Yes. MDRwatchdog generates a unique, unauthenticated verification link for each tenant. You paste that link into your cyber-insurance application or hand it to your underwriter. They open it and see your full chain verification result, record count, date range, and signed blocks — without any login or special access.
Plain-language answers to the questions buyers ask most — readiness and evidence, not certification or legal advice.
Every MDRwatchdog plan includes the quantum-resistant audit chain. Book a 15-minute review and we'll show you the verification endpoint live.
Schedule your 15-minute review