Security Brief
The Security Brief is a project-scoped AI summary: Vygl pre-aggregates the relevant context (recent scans, open findings, dependencies, container vulnerabilities, your organizational memory) and the LLM produces a structured brief with the project’s top risks and recommended next steps. A chat thread is attached to the brief for follow-up questions.
Generating a brief
Section titled “Generating a brief”- Open a project’s detail page.
- Click the Security Brief tab.
- Click Generate on first visit, or open an existing brief if one’s already there.
Vygl pre-aggregates the project’s findings, scans, dependencies, and any matching organizational memory into a structured data_summary, then asks the LLM to produce a sectioned brief from it. The result is persisted as a Consultation row — your team sees the same brief next time.
What’s in the brief
Section titled “What’s in the brief”A typical brief has sections like Top Risks, What changed since last scan, Recommended actions, and an actions block with concrete triage operations the LLM thinks are safe to apply.
Apply suggested triage actions
Section titled “Apply suggested triage actions”When the brief surfaces an action (“8 findings under tests/fixtures/ look like documented placeholders — mark them all false_positive?”), it renders as a one-click button on the brief itself. Clicking Apply runs it via the Consultation Actions API.
The whitelist is narrow:
| Action | What it does |
|---|---|
bulk_triage_rule | Triage every open finding from one rule (with optional triage_status and reason). |
bulk_triage_findings | Triage a specific list of finding IDs (with optional triage_status and reason). |
Default triage_status is false_positive; you can override via the API. Both actions hit the same audited triage path as a manual bulk-triage from the Findings list. Anything outside this whitelist — opening PRs, creating tickets, modifying settings — is intentionally out of reach.
Chat about the brief
Section titled “Chat about the brief”Open the chat panel under the brief to ask follow-up questions. Chat messages stream token-by-token. The chat works against the brief’s data_summary and the prior message history — it doesn’t re-query findings or memories live, so for the freshest context, regenerate the brief.
Useful prompts:
- “Why is the second item on the priority list ranked over the third?”
- “What would removing this dependency cost us in terms of CVE exposure?”
- “Walk me through the remediation steps for the highest-priority item.”
- “Is there a single fix that closes multiple top-risks?”
Brief regeneration
Section titled “Brief regeneration”Vygl tracks a fingerprint over the project’s open findings. When the fingerprint stops matching the brief’s frozen state — typically after a new scan or a meaningful triage shift — the page surfaces a Regenerate button. Regenerating creates a new Consultation row and starts a fresh chat thread; your prior brief and chat history remain in the database, just out of view.
Container images get their own pre-computed AI summary, separate from the project-level brief. See Container AI Analysis.