Templates

Templates provide consistent structure for public security research artifacts. They are not substitutes for review. A completed template still requires scope confirmation, evidence review, redaction, and release approval before publication.

The templates are intentionally conservative. They favor affected product details, impact summaries, timelines, remediation notes, and reviewer-visible assumptions over exploit walkthroughs. That structure keeps public artifacts useful to defenders while reducing avoidable harm.

Advisory TemplateStructured public advisory format for coordinated publication.Report TemplateResearch report structure for sanitized public findings.

Usage

Use the advisory template when a vulnerability or class of vulnerabilities is being communicated as a public coordination artifact. Use the report template when the artifact is broader than one advisory, such as a method note, aggregate review, or sanitized research summary.

Templates should reduce reviewer discretion by making required fields explicit. They should preserve enough structure for repeatable review while leaving room for case-specific facts.

Template Standard

Templates should reduce reviewer discretion by making required fields explicit. They should preserve enough structure for repeatable review while leaving room for case-specific facts.

A template should prevent omissions without encouraging filler. Each required field should exist because a reviewer, coordinator, vendor, or public reader needs that information to interpret the artifact.

Reader Outcome

A complete page in this section should leave the reader with a clear next action, a clear limitation, and a clear route for follow-up. If the section is an index, it should explain what records will appear here, why they may be absent today, and which adjacent policy or template controls future entries. If it is a template, it should explain how to use the structure without treating the sample as a substitute for review.

Templates are part of the quality system. They reduce missing fields, normalize review language, and keep public artifacts from drifting into ad hoc narratives.