Bermward

Findings

Every security issue Bermward detects becomes a finding. Findings are deduplicated across scans, so an issue is one row that opens, stays open, and closes, not a new alert every night.

Anatomy of a finding

  • Severity: critical, high, medium, low, info.
  • Category: email, TLS, DNS, registration, exposure, vulnerability, lookalike, threat intel, web or credentials.
  • Asset: the domain, subdomain, host or address it is about.
  • Explanation and remediation: what was found and how to fix it, in plain language.
  • History: when it was first seen, last seen, who commented, and when it was resolved.

Lifecycle

StatusHow it gets thereWhat happens next
OpenA scan sees the issue.It stays open while later scans still see it, and counts toward your grade.
ResolvedA later scan no longer sees the issue.If it comes back, it reopens as the same finding.
Accepted riskAn analyst or admin accepts it with a reason and an expiry date.It stops counting while accepted. When the date passes, it reopens on its own.

Accepting a risk

Accepting needs two things: a short reason (up to 1,000 characters) and the date the acceptance ends. The date must be in the future and at most a year away. The reason stays visible on the finding as "Accepted because", and the action is written to the audit log. Reopen an accepted risk at any time.

A resolved finding cannot be accepted.

Working a finding

  • Filter by status, severity and domain. Overview severity counts link here with the filter applied.
  • Comment on a finding so the next person knows what has been tried.
  • Run a retest to check a fix without waiting for the next scheduled scan.

Alerts

When a scan opens, reopens or resolves findings, or discovers new subdomains, Bermward can send one summary per scan to chat channels and webhooks (event exposure.findings), and tells you when a scan fails (exposure.scan_failed). Critical findings can page through PagerDuty. See Webhooks and alert channels.

API

MethodPathRoleWhat it does
GET/api/orgs/:orgId/findingsviewerList findings, filterable.
POST/api/orgs/:orgId/findings/:findingId/acceptanalystBody: reason and until (ISO date).
POST/api/orgs/:orgId/findings/:findingId/reopenanalystReopen an accepted risk.
PATCH/api/orgs/:orgId/findings/:findingIdanalystUpdate a finding.
GET/api/orgs/:orgId/findings/:findingId/commentsviewerList comments.
POST/api/orgs/:orgId/findings/:findingId/commentsanalystAdd a comment.
POST/api/orgs/:orgId/findings/:findingId/retestanalystRetest one finding.

With an API token, GET /api/v1/findings returns open findings for read-only integrations. See API.