Reporting

What is reporting?

Reporting converts technical evidence into reusable views for engineers, security leaders, auditors and migration owners without losing traceability to the underlying finding.

Different stakeholders need different levels of detail. Strong reporting preserves provenance while making migration status and residual risk understandable.

Questions to ask a vendor

1. Can every summary trace back to evidence?
2. Are technical and executive views consistent?
3. Can data be exported in open formats for governance and audit?

What this edition actually supports

Weight 2 of 19. Can technical and executive readers inspect and reuse the result?

The criterion considers understandable findings, exportable detail, provenance and decision limits. QScout scores 9 in edition 2026.7. A polished dashboard is not itself an accurate inventory: readers need access to source records and explicit unknowns. The public index publishes the matrix, CSV, product rationales and a dated source-access screen.

How to investigate this criterion

Try to reproduce the score from the raw matrix, follow a material claim to its original source and identify what is inaccessible.

Primary and original inputs: pqc-index.org · pqc-index.org · pqc-index.org. Review all dated cell source checks and the 1 October per-cell limits.

The 2026.7 cells below are public-evidence scores. A vendor page documents a claim; an artifact check tests only its stated scope. Missing product execution and inaccessible sources remain explicit unknowns. The score snapshot has not been recomputed from later pages.