Scan Configuration
Additional settings and information related to scans.
Last updated
Was this helpful?
Additional settings and information related to scans.
Last updated
Was this helpful?
Scan frequency allows you to configure how often scans will be performed. This setting defaults to a value of once per week. The following options are also available: Day, Month, and Quarter.
In addition to configuring the frequency, you may select the time that scans are performed or have them performed at a random time.
To change the scan frequency or time, visit the Target Settings or Domain > Network > Settings page.
You can select the scan policy per target.
For customers using our , it's possible to specify AWS instance IDs for resources that are discovered by the integration. If a target has been assigned an instance ID and the target is an IP address without a hostname, then the target IP will be updated whenever the integration is run. This feature can be useful for AWS assets utilizing dynamic IPs that may change periodically between scans.
To specify an AWS Instance ID, visit the "Advanced Settings" page of the target.
Halo Security uses several unique network ranges, user agents, and other identifiers to perform scanning, crawling, and other network-related functions. In some cases, this information may be useful to identify traffic, add us to the allowlist, or filter out traffic from certain services (such as Google Tag Manager).
The following network ranges specify the IP addresses of scanners in use:
Additionally, webshots (used to generate previews of the web application) originate from the following IP address: 54.187.125.96
For scans that access web applications, Halo Security appends a custom string to the User-Agent header to allow you to distinguish our traffic. This string is vuln_scan_by_trustedsite_com_halo_security. The full User-Agent header will appear like the following: