Scan Profiles (also referred to as Scan Configurations) define how a scan is executed.
They describe the technical behavior of a scan rather than what is scanned.A scan profile controls parameters such as:Which vulnerability tests are executed
Scan intensity and performance tuning
Network and port scanning behavior
Detection depth and accuracy
Scan profiles allow the same target (host, IP range, or asset) to be scanned using different strategies, depending on security requirements, compliance needs, or performance constraints.Relationship to Scans#
When creating a scan via the API:A scan profile is referenced, not embedded.
The profile determines scan behavior at runtime.
List available scan profiles via /v2/scans/profiles/activeted
Select the appropriate profile ID
Create a scan referencing that profile
Product-Specific Scan Profiles & Restrictions#
Scan Profiles are product-specific. Each scanning product (e.g. PCI, VRMS, Penetration Testing, etc.) exposes its own set of available scan profiles, aligned with the technical and regulatory requirements of that product.End users cannot create, modify, or update scan profiles through the API or the UI. All scan profiles are system-defined and maintained to ensure scan integrity, consistency, and compliance.PCI Product – Special RestrictionFor the PCI Compliance (ASV) product, the scan profile is:Not configurable or replaceable
Mandatory for all PCI scans
This restriction exists due to ASV PCI DSS requirements, which mandate a specific scanning configuration. Allowing profile changes would invalidate compliance and certification requirements. Other Products#
For all non-PCI products (e.g. VRMS, Penetration Testing, Dark Web):Multiple scan profiles may be available
Different profiles can be selected instead of the default
Profiles allow flexibility in scan depth, performance, and coverage
However, even for these products, profiles remain read-only for end users and can only be selected, not modified. Modified at 2026-01-02 14:04:00