Skip to main content

Scan Profiles Overview

​
Overview

Scan Profiles make WAS scanning flexible and repeatable.
They allow teams to:
  • Define global request headers
  • Apply authentication values
  • Maintain reusable configurations across multiple projects
  • Enable consistent security testing rules
  • Avoid duplicating configuration during every scan
Profiles are especially useful when scanning:
  • Staging vs Production environments
  • APIs requiring tokens / session identifiers
  • Applications with custom headers or tenant routing

​
Creating a Scan Profile

Create a New Scan Profile

​
1. Profile Details

Profile Name

Enter a unique name to identify this scan profile.

Description

(Optional) Add context or usage instructions for your team.

​
Custom Headers

Profiles support adding custom HTTP headers that will be included with all scan requests.

Header Name

Define the name of the header (e.g., Authorization, X-Tenant-ID).

Header Value

Specify the value to be applied during scanning.
Users can add multiple headers—for API tokens, session cookies, or routing identifiers.

Adding Custom Headers

​
Managing Scan Profiles

All created profiles appear under Existing Scan Profiles.

Existing Scan Profiles

Each profile supports:

Edit

Modify name, headers, or configuration at any time.

Delete

Remove outdated profiles to maintain clean workspace organization.

Reusable

Profiles can be applied to any scan across WAS.

​
Why Use Scan Profiles?

Consistency Across Scans

Apply identical configuration across all projects.

Faster Setup

Reduce repetitive configuration when creating new scans.

Team Collaboration

Shared settings ensure standardized security testing across teams.

​
Next Steps

Run a Scan Using This Profile

Learn how scan profiles integrate with the scanning workflow.