How are certificate enrollment and attestation claims verified?

A capability is established by a dated primary source and a located excerpt, not by a protocol name or a vendor label.

Evidence and verification

Each claim records its primary source, cited location, attributed excerpt, conditions and evidence status. An inference is labeled as such. Vendor documentation does not establish an independently reproduced test result.

How to read this reference

not documented by the vendor
The vendor has not documented this property; it is not proof of absence.
none (documented absence)
The cited documentation establishes that this property is absent.
depends on a documented setting
The result depends on the configuration described in the prerequisites and evidence.
supported
Vendor documentation establishes the capability under the listed conditions.
partial
Only part of the workflow is established, or documented limits or conflicts remain.
unknown
The documentation does not establish support. This is not a supported claim.
unsupported / roadmap
Documented as unavailable, or announced but not currently available.
vendor_documented / inferred
Explicit primary documentation, or a qualified inference. Independent test-report classes are not enabled in this release.
Read the evidence and verification methodology

Owner review and publication

Content begins as draft. The owner verifies evidence before publication. Consequential changes require a human decision. A confirming evidence recheck changes neither the material-update date nor sitemap lastmod.

Review cadence and suspension

The specified cadence is daily source monitoring and weekly evidence rechecks, enabled in the monitoring checkpoint. Scenarios receive owner review when linked evidence changes. Missing or materially changed tier B evidence suspends affirmative capabilities until resolved.

Corrections and access to data

Corrections are reviewed by the owner, not emailed automatically. RSS includes published changes and scenario answers. Workflow JSON and change JSON expose public data, not internal source snapshots. Test-report submissions are not enabled in this release.