Proof-of-Control\u2122 Certificate
Every CMMC assessor asks the same question: prove your controls were working on a specific date. MDRwatchdog Proof-of-Control\u2122 Certificate answers with a cryptographically sealed record, signed with Ed25519 + ML-DSA-87, independently verifiable by your C3PAO without any MDRwatchdog access.
Certificate format
| Technique | Description | Verdict | Control | Timestamp | Signature |
|---|---|---|---|---|---|
| T1059.001 | PowerShell execution | DETECTED | SI.L2-3.14.2 | 2026-09-08 06:00:12 UTC | ML-DSA-87 ✓ |
| T1055 | Process injection | DETECTED | SI.L2-3.14.6 | 2026-09-08 06:00:14 UTC | ML-DSA-87 ✓ |
| T1078 | Valid account abuse | DETECTED | AC.L2-3.1.1 | 2026-09-08 06:00:16 UTC | ML-DSA-87 ✓ |
| T1486 | Data encryption/ransomware | DETECTED | SI.L2-3.14.2 | 2026-09-08 06:00:18 UTC | ML-DSA-87 ✓ |
| T1003 | Credential dumping | DETECTED | IA.L2-3.5.1 | 2026-09-08 06:00:20 UTC | ML-DSA-87 ✓ |
36 probes per cycle
Every 6 hours, 36 synthetic attack probes run against your live detection engine — the same function that evaluates real events.
Every 6 hours
Continuous cadence. A 12-month certificate contains 1,460 sealed verification records per technique.
Independently verifiable
Your C3PAO verifies with a public key and URL. No MDRwatchdog access required. Math, not attestation.
Common questions
What does the Proof-of-Control™ Certificate prove?+
It proves that your live detection engine evaluated specific attack techniques on specific dates and produced verifiable detection verdicts. Each certificate entry is sealed with Ed25519 + ML-DSA-87 signatures and appended to the Quantum Audit Chain™. An assessor with your public key can verify every entry independently.
Which CMMC controls does this satisfy?+
CA.L2-3.12.1 (periodically assess the effectiveness of the security controls) is the primary control. The certificate also contributes evidence for AU.L2-3.3.1 (audit logging) because every probe result is sealed to the audit chain, and SI.L2-3.14.2 (provide protection from malicious code) because the probes test malware-related detection rules.
How often is the certificate updated?+
Every 6 hours. 36 probes run automatically against the live detection engine and results are sealed. A 12-month certificate contains 1,460 sealed verification records per detection technique.
Can my C3PAO verify this without contacting MDRwatchdog?+
Yes. The certificate includes your public key and verification URL. Your C3PAO opens the URL, queries the chain for control test events, and verifies the cryptographic signatures. No MDRwatchdog access required.
Related compliance forms
Plain-language answers to the questions buyers ask most — readiness and evidence, not certification or legal advice.
Give your C3PAO a certificate, not a conversation.
MDRwatchdog Proof-of-Control\u2122 seals 36 detection verifications every 6 hours. Book a 15-minute review.
Schedule your 15-minute review