Core concepts
A short glossary of the ideas that show up everywhere in BestDefense. Skim it once and the rest of the docs will read more easily.
Organization
Section titled “Organization”The top-level container for everything you do. An organization owns its targets, reports, members, integrations, and billing. You can belong to more than one organization and switch between them from the menu in the top bar — switching changes which organization’s data and subscription you’re working in.
Site / target
Section titled “Site / target”A thing you scan — usually a web application or an API, identified by its URL or domain. Targets must have their domain ownership verified before they can be scanned. See Managing sites.
Report
Section titled “Report”The result of a scan. A Vortex security scan, a Maelstrom load test, and a network scan each produce a report you can open, explore, and export.
Finding (alert)
Section titled “Finding (alert)”A single issue surfaced by a scan — for example, a missing security header or an injectable parameter. Findings are grouped (so related issues sit together) and ranked by severity. You’ll also see the term alert for an individual finding.
Severity
Section titled “Severity”How serious a finding is. Severity drives prioritization throughout the platform — overview charts, sort order, and which findings you might choose to remediate first. See Severity & scoring for the levels and what they mean.
Remediation
Section titled “Remediation”The act of fixing a finding. BestDefense can generate a fix with AI and open a pull request in your connected repository. Fixes move through the Remediation Queue — a pipeline from finding to reviewed, merged change.
Accepted risk
Section titled “Accepted risk”A formal decision to not fix a finding right now, recorded with a reason and (optionally) an expiration date and supporting document. Accepted risks are kept out of the active remediation pipeline. See Accepted risks.
Members, teams, and roles
Section titled “Members, teams, and roles”People in your organization are members. Members can be grouped into teams, and what each member can do is governed by their role and by allow-rules.
Allow-rules
Section titled “Allow-rules”Fine-grained permissions that gate specific actions — for example, who can trigger remediation, change guardrail policy, or manage integrations. Roles come with sensible defaults; allow-rules let you tune access precisely. See Allow-rules.
Credits and limits
Section titled “Credits and limits”Some actions consume credits (for example, generating an AI remediation pull request), and some resources have caps (for example, how many targets or team members your plan allows). Both are tied to your subscription tier. See Billing & tiers.
Integrations
Section titled “Integrations”Connections to external tools: version control (GitHub, GitLab, Bitbucket) for remediation pull requests, Jira for tickets, SonarQube for code quality, and SSO/OIDC for sign-in. Integrations are configured per organization. See Integrations.