Glossary
Allowlist
A list of IP addresses that your firewall or web application firewall (WAF) lets through. Also called a whitelist, an older term that some tools still use. You allowlist XBOW’s IP addresses so that XBOW can reach your asset. See Access requirements.
API
The programming interface of a web application. You can test an API together with its web application. Testing standalone APIs is available in private preview. Talk to your XBOW contact.
For details on the XBOW API, see API reference.
Assessment
One security test of an asset by XBOW, from the configuration check to the results. See Define an assessment type.
Asset
What you ask XBOW to test: a web application, an API (private preview), or a web application together with its API. You set up an asset once and run assessments against it. Also see Target, Web application, and Choosing an asset to test.
Attack credits
The allowance that assessments use while XBOW is attacking your asset. An assessment does not use attack credits while XBOW only monitors the health of your asset.
Attack methods
The ways XBOW tests an asset. They include checks for:
- Common weaknesses (CWEs)
- Flaws such as business logic errors and race conditions
- Technology-specific weaknesses
- Common misconfigurations
- Known vulnerabilities (CVEs)
- Dynamic application security testing (DAST)
See Attack methods.
Attackable, Allow Visit, and Blocked
The three scope settings for a domain.
- Attackable: XBOW can load and attack the domain.
- Allow Visit: XBOW can load the domain but does not attack it.
- Blocked: XBOW cannot reach the domain.
See Scope configuration.
Canary token
A secret that you hide in your asset and challenge XBOW to retrieve. A canary token proves vulnerabilities that XBOW cannot otherwise demonstrate, such as business logic flaws. See Validate with canaries.
Comprehensive assessment
The default assessment type. XBOW tests your asset using the generally available attack methods for it, plus any preview methods you enable. See Comparing different types of assessment and Choose preview stages.
Configuration check
The checks XBOW runs before an assessment starts, also called the preflight phase. They confirm that XBOW can connect to the asset and, when required, authenticate. For authenticated tests, they also check support for concurrent sessions unless you enable Sequential mode. See Checking your configuration.
Credential set
A test account that XBOW authenticates with. An assessment can use up to five credential sets. XBOW uses the primary set for discovery and all attack methods. See Work with multiple credential sets. Also see Test account.
CVE
Common Vulnerabilities and Exposures. A public catalog of known vulnerabilities in specific products and versions, each with an identifier such as CVE-2021-44228. XBOW includes checks for CVEs among its attack methods.
CWE
Common Weakness Enumeration. A standard catalog of software weakness types, such as CWE-79 for cross-site scripting. Where possible, XBOW reports each finding with the top-level CWE for its weakness. See Vulnerability classification.
Detection
One occasion when XBOW detects an issue during an assessment. XBOW often detects the same issue more than once, and groups the detections into a single finding.
Discovery
How XBOW finds the domains and endpoints that make up your asset. During the configuration check, XBOW identifies the domains your asset uses and proposes scope rules. During an assessment, discovery agents search for more endpoints to attack, unless you turn on Focus testing on the listed endpoints. See Provide asset context.
Finding
One unique vulnerability or informational issue that XBOW detected in an asset. XBOW groups repeated detections of the same issue into one finding. You triage and fix the finding, not each detection. See Findings.
Gray-box testing
Testing that uses some inside knowledge of an asset, such as source code and documentation that you upload. White-box testing uses full knowledge of the asset’s internals. Black-box testing uses none. See Guiding XBOW testing.
Guardrails
The protections that XBOW applies around an assessment, such as scope, protected URLs, and target protection. XBOW sets initial guardrails during the configuration check, and you can add more. See Trust and safety.
Impact demonstration
An investigation into how an attacker could exploit a significant finding. You choose the level, from Off to Deep, when you run the assessment. See Impact demonstration.
Pause
What XBOW does when it detects a disruptive event during an assessment, for example when the asset becomes unavailable. XBOW pauses to avoid worsening the problem and spending attack credits. You usually need to fix the cause and resume the assessment manually; some pauses, such as a model provider outage, recover automatically. Health-only “Monitoring” is a separate state that resumes testing automatically when the asset recovers. See Monitor an assessment.
Preflight
Another name for the configuration check: the checks XBOW runs before an assessment starts. An asset shows “Preflight successful” when the checks pass and users with the Developer role or higher can run assessments. See Checking configurations before assessment.
Primary detection
The detection that supplies a finding’s details and reproduction steps. It is usually the first detection. See Findings.
Protected URLs
Endpoints that XBOW does not attack, to prevent an assessment pausing if the test account cannot authenticate or is damaged. XBOW protects many sensitive endpoints automatically, and you can protect more. Auth-only lets XBOW contact an endpoint but not attack it. See Protected URLs.
Release phase
How mature a feature is: private preview, public preview, or generally available (GA). For attack methods, for example, the phase reflects XBOW’s confidence in the precision of the results.
Retest
An assessment that checks whether you have fixed findings. XBOW tries to reproduce the original exploit for each finding you select. If the exploit is blocked, XBOW looks for ways to bypass the fix. See Explore and fix XBOW results.
Risk score
A severity rollup for an asset: a single number that summarizes its open findings, weighted by severity. Use it as a relative signal for triage, not as a measure of business risk. See Risk score.
Scope
The network boundary of an assessment: which domains XBOW can reach and which it can attack. See Scope configuration and Attackable, Allow Visit, and Blocked.
Sequential mode
An option for assets that do not support multiple concurrent authenticated sessions. XBOW tests with one session at a time, so assessments take longer. See Asset types.
Severity
How serious a finding is in technical terms: “Critical”, “High”, “Medium”, “Low”, or “Informational”. XBOW sets severity from the Common Vulnerability Scoring System (CVSS). See Severity levels.
Target
The asset that an assessment is testing. See Asset.
Target protection
A setting that limits what XBOW may do to your asset during an assessment. Choose Standard, the default, or Permissive. Both levels block actions that resemble a denial-of-service attack. See Target protection.
Test account
An account that XBOW uses to log in to your asset. XBOW uses only the credentials you provide. See Define authentication. Also see Credential set.
Unauthenticated test
An assessment of an asset that does not require authentication. XBOW tests without logging in. See Publicly accessible targets.
Verify fix
See Retest.
Web application
A website with interactive features, such as forms, dashboards, or user accounts. A web application is one kind of asset. See Asset types.