Reports
Reports are public research artifacts that are broader than a single advisory. They may describe a research method, aggregate observation, sanitized case study, data review, or defensive analysis. The report format is designed for clarity, reproducibility, and restrained public value.
A report should not rely on vague authority. It should make scope, limitations, assumptions, evidence boundaries, and defensive relevance visible. Strong reports tend to be measured: they identify what was found, what was not tested, and what a defender can do with the information.
Publication Standard
A report should help a technical audience understand risk without creating avoidable operational harm. Evidence should be summarized, redacted, and contextualized before publication.
Report Standard
Report pages should preserve analysis quality while removing raw evidence that belongs in private case files. Public readers should be able to understand scope, method, impact, and remediation state without receiving unnecessary operational detail.
Program Model
The report program page defines how reports differ from advisories. Reports can cover methodology, defensive analysis, aggregate findings, tool behavior, and post-publication review. They need the same publication discipline as advisories, but their purpose is broader than issue-specific remediation.