Jump to Content
Bright-docs
DocsSamplesChangelog
Log InBright-docs
Docs
Log In
DocsSamplesChangelog

Welcome

  • What is Bright DAST?
  • About Docs
  • Support
  • Accessibility
  • Privacy Policy
    • Terms of Use

DEPLOYMENT OPTIONS

  • Overview
  • SaaS Deployment
  • Private Cloud Deployment

Getting Started

  • Quickstart
  • Create a first Project

ONboarding your targets

  • Authentication
    • Add an Authentication Object
    • Bright Authentication Recorder
    • Google Chrome DevTools
    • Testing Authentication
  • Discovery
    • Add Entrypoints to your Project
    • Create a Single Entrypoint
    • Crawler
    • .HAR file
    • API Schema: scanning, configuring
      • How to Validate Uploaded File: OpenAPI, Swagger, Postman
      • API Schema Troubleshooting
  • Entrypoints
    • Adding a single Entrypoint
    • Overview Entrypoints
  • API Schema Troubleshooting
  • How to Add Bright to the WAF Allowlist

TESTING YOUR TARGETS

  • Overview
    • Modern Scan
    • Legacy Scan
  • Managing Scans
    • Creating a Scan
    • Creating a Legacy Scan
    • Retesting a Scan
    • Deleting a Scan
    • Managing Scan Templates
    • Troubleshooting Scans
  • Reviewing Scan Results
    • Scans Summary
    • Issues Summary
    • Reviewing Scan Details
    • Reviewing Scan History
    • Modifying Future Scan Settings
    • Exporting a Scan Report

Advanced Setup

  • Managing Organization
    • Managing Organization Users
    • Managing Organization Groups
    • Managing Custom Roles
  • Managing Access Scopes
  • Managing Personal Account
  • Managing Projects
  • Managing Bright File Storage
  • Managing Activity Log
  • Baseline Values

Bright Repeater

  • Overview
    • Prerequisites before installation
    • Install as standalone
    • Install as Docker
    • Install as NPM / Yarn
    • Install as Windows installer (MSI)
    • Supported Versions
  • Scanning with Repeater
    • Scanning at the Enterprise Level
    • Scanning as Part of CI Pipeline
  • Managing Repeaters
  • Using Repeater Scripts
    • HMAC Use Cases
    • Managing Repeater Scripts
  • Troubleshooting
    • Standalone executables
    • Docker
    • NPM / Yarn
    • Windows Installer (MSI)

Bright CLI

  • Overview
  • Setup & Installation Guide
  • Command List
    • Command Language Syntax
    • Running a Scan
    • Stopping a Scan
    • Retesting a Scan
    • Checking Scan Status
    • Running a Discovery
    • Stopping a Discovery
    • Rerunning a Discovery
    • Polling a Discovery
    • Uploading an Archive
    • Generating an Archive
    • Initializing the Repeater
    • Testing Network Connectivity
    • Listing Entrypoints
    • Integrating with an On-Premise Ticketing Service (legacy)
  • Configuration Files

Bright REST API

  • Overview
  • Response Status Codes

Integrations

  • Overview
    • Jira
    • GitHub
    • Slack
    • Azure Boards
    • GitLab Boards
    • Snyk Validation Integration
  • Adding Integration to a Project
  • Integrating a Project with Webhooks
  • Sending Detected Issues from CI/CD Pipelines to Jira
  • Configuring Single Sign-On
    • Okta SSO and Provisioning
    • Google SSO
    • Azure AD: Service Provider initiated SSO and Provisioning
    • Azure AD: Identity Provider initiated SSO
  • CI Pipeline Integrations
    • GitHub Actions
    • CircleCI
    • Jenkins
    • Azure Pipelines
    • Travis CI
    • JFrog
    • GitLab
    • TeamCity
  • CI Pipeline Integration Examples
    • Jenkins Integration Examples
    • Travis CI Integration Examples
    • GitLab Integration Examples

Knowledge base

  • Vulnerability Guide
  • FAQs
Powered by 

Target Authorization

Suggest Edits

As a precaution, Bright only allows to scan trusted or authorized hosts. There are two ways to authorize a host:

  • Connect a Repeater - learn more on how to add a Repeater to your Project
  • Add a .nex file to the application root directory - learn more on how to do it with your Organization

Updated 8 months ago


What’s Next
  • Repeater
  • Managing Organization