SNP-CERT-01: SEV-SNP report is signed by genuine AMD hardware¶
| Property | Value |
|---|---|
| Severity | critical |
| Platform | Hardware fleets (collector) |
| Lifecycle stage | hardware |
| Policy | P-04: Attestation evidence is fresh and fully verified |
| Evaluated from | Evidence sent to the service (collector bundles or registry scans), not from a cloud API scan. |
What it checks¶
It passes when:
- Report signed by the … of this chip; chain to AMD's pinned ARK-… verified; ASK not revoked.
How to fix¶
- Treat this host as untrusted: the report does not chain to AMD's root or its signing certificate is revoked.
- Verify these hosts with AMD's tools; an unrecognized CPUID family or model is never assumed to be supported.
- Use a collector that reads the extended report (configfs-tsm auxblob), which carries the VLEK.
After the fix, scan again: the check should report PASS.
Related¶
- Runtime detection
DET-H4(Hardware fleets): Collector stopped reporting or moved hardware - Other checks for policy P-04: CCA-CERT-01, CSPACE-ATT-01, CSPACE-ATT-02, CSPACE-ATT-03, GPU-CERT-01, GPUCC-ATT-01, NITRO-ATT-02, NITRO-ATT-03, SE-CERT-01, SGX-CERT-01, TDX-CERT-01
Evidence recorded¶
Keys in the finding's evidence: product, revocation, signing_key
Generated from untrust 1.3.0 (commit 7ef462d9a0c3).