Burp Suite - Run Site Scan
- 14 Oct 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Burp Suite - Run Site Scan
- Updated on 14 Oct 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Burp Suite- Run Site Scan runs a Burp Suite scan on all assets retrieved from the saved query supplied as a trigger (or from the assets selected in the asset table).
See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.
Note:
- Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
- See Actions supported for Vulnerabilities.
- See Actions supported for Software.
Required Fields
These fields must be configured to run the Enforcement Set.
- Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
- Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
Use stored credentials from the BurpSuite adapter - Select this option to use credentials from the adapter connection. By default, the first connection is selected.
NOTE- To use this option, you must successfully configure a Burp Suite adapter connection.
- The API key used for the adapter connection must be a user with permissions to create new assets.
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.
Additional Fields
These fields are optional.
- Host Name or IP Address - The hostname or IP address of the Burp Suite server.
- API Key - Enter your Burp Suite API key.
- Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.
- HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.
- HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the HTTPS Proxy.
- HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.
For more details about other Enforcement Actions available, see Action Library.
Was this article helpful?