finding-draft

Drafting a security finding requires structuring vulnerability observations into a standard format with frontmatter, severity estimation, and remediation recommendations. A guided workflow gathers context to produce a complete finding draft ready for review and audit traceability.

Standard security vulnerability reports use a structured format enforcing frontmatter schema, severity scale conventions, and dedicated sections. This structure ensures consistency across reports, enables clear remediation planning, and provides audit traceability for identified risks.

No, the drafting workflow cannot review or deduplicate existing security findings. It specifically applies to authoring new findings based on vulnerability observations, guiding the end-to-end process from initial context gathering through title construction to the final draft.

Ensuring consistency across security findings requires applying a repeatable frontmatter schema and section structure during report generation. Standardizing title construction and severity estimation through a guided workflow maintains uniform quality for remediation planning.

Estimating severity when authoring a vulnerability finding involves applying the defined severity scale and conventions from the standard format. The guided workflow integrates severity estimation alongside context gathering and recommendation generation to produce an accurate risk assessment.