Rerunning a Discovery
Request to start a new discovery using the same configuration as an existing discovery, by discovery ID.
Example: bright-cli discovery:rerun [options] <discoveryId>
discoveryId ID of an existing discovery which you want to re-run.
General options
| Option | Description |
|---|---|
--config | Path to the file with configuration |
--log-level | What level of logs to report. Any logs of a higher level than the setting are shown. [choices: 0, 1, 2, 3, 4, 5, "silent", "error", "warn", "notice", "verbose", "trace"] Default: --log-level 3 |
--hostname | Bright application name (domain name). Default: --hostname app.brightsec.com |
--proxy=socksProxyUrl | Specify a proxy URL to route all traffic through. This should be an HTTP(S), SOCKS4, or SOCKS5 URL. Can be read also from environment param PROXY. Default: If you specify SOCKS://, then SOCKS5h is applied. |
--proxy-bright | Specify a proxy URL to route the traffic to Bright. |
--proxy-target | Specify a proxy URL to route the traffic to the targets. |
--timeout | Request timeout in seconds or a duration string (e.g. 10s, 1m, 1h, 10h, 1y). Default: --timeout 30 |
--insecure | Allows CLI to proceed and operate even for server connections otherwise considered insecure. Default: --insecure false |
--token=apiKey, -t=apiKey | The unique identifier used to authenticate a user. The token (API key) can be issued in your organization’s dashboard. Required option. |
Discovery options
| Option | Description |
|---|---|
--project, -p | Allows specifying the Bright project for a scan using the project ID. You can find the project ID in the Projects section in the Bright app. |
Updated 17 days ago