Skip to main content
CybeDefend streamlines remediation by letting you update each vulnerability (found by SAST, IAC, or SCA) directly from the dashboard. Whether you’re marking it as “In Progress” or adding a priority label, you can keep the entire team aligned.
Vulnerability Update Popup

​
Steps to Update

  1. Open the Vulnerability
    In the project’s vulnerability list, click a specific item to reveal the Update Popup.
  2. Edit Fields
    • Status: Switch from To Verify → Confirmed.
    • Priority: Assign internal priority tags (e.g., critical, low).
    • Comment: Record progress, decisions made, or references to external tickets.
  3. Confirm & Save
    Changes are immediately visible to all team members, helping them see updated statuses without additional overhead.

​
Dismissing a finding requires a justification

Setting a finding to Ignored — in the dashboard, through the API, or through the Cybe MCP tool — now requires a written reason. A dismissal without one is refused.
Breaking change. Any integration that sets status: "ignored" must now send dismissalReason alongside it. Requests that omit it fail validation with dismissalReason is required when status is "ignored".
The same rule applies to bulk dismissal: each item in a batch update carries its own dismissalReason, so a bulk action stays audited rather than becoming a way around the requirement.
The justification is recorded against the finding and surfaces as dismissal_reason in the Findings Export. Automated triage is held to the same standard — when Cybe Agent dismisses a finding, it records its own reason and is attributed as agent.
After Updating Vulnerability
Use the comment field for quick, contextual notes. This eliminates the need for separate emails or Slack threads where details can get lost.

​
Consistent Management Across Scanners

A critical SAST finding about SQL injection can be handled the same way as a high-severity IAC misconfiguration in Terraform. This uniform approach:
  • Reduces Confusion: No separate tools or flows for each scanner.
  • Speeds Remediation: Everyone uses the same interface, no matter the vulnerability source.
Consider adopting weekly triage sessions where you review newly detected vulnerabilities and update them as a team.