Rename High/Standard/Low Priority

[storbeck]

Description

The current terms for priority levels are confusing and do not clearly convey their actual function.

Problem

Users without prior knowledge find it difficult to understand the terms without consulting the documentation. The terms should be self-explanatory and intuitive.

Preferred Solution

High Priority -> Aggressive Standard Priority -> Normal Low Priority -> Asset Discovery

Alternatives Considered

High Priority

1. Intensive Scan - Emphasizes the rigorous nature of the scan, suggesting a high level of activity and potential impact, including frequent scans and web crawling.
2. Enhanced Scan - Highlights the increased frequency, web crawling, and further detections, suggesting a highly detailed and thorough scan.

Standard Priority

1. Balanced Scan - This term implies a middle-ground approach, balancing asset discovery and vulnerability scanning.
2. Moderate Scan - Indicates a moderate level of scanning, balancing asset discovery and vulnerability assessment.

Low Priority

1. Exploratory Scan - Suggests a focus on finding new assets using the provided domain without performing vulnerability scans.
2. Basic Asset Scan - Suggests a foundational level of scanning that focuses on asset discovery only, without vulnerability assessments.

Additional Information The goal is to ensure users can easily understand the implications of each priority level without needing additional documentation.

Preferred solution terms were chosen to shamelessly copy the tried-and-true nmap options.

(Renamed Host Discovery to Asset Discovery to match our existing nomenclature)

[privateducky]

agreed (aggressive, normal, asset discovery)