- If the primary requirement is a DAST-first user experience and specialized DAST workflows, and the organization is not already committed to the Tenable ecosystem, dedicated DAST vendors may be more appropriate.
- If the application set includes many complex authentication/MFA/SSO flows and the organization cannot allocate resources to develop and maintain authentication and session handling for scans.
- If procurement requires transparent, self-serve catalog pricing; Tenable’s enterprise pricing is often quote-driven and can require sales engagement.
- If the environment requires very high scan throughput without detailed capacity planning; concurrency and batching behaviors should be validated in proofs of concept.
- If local scanner deployment targets ARM-based hosts (for example, some Apple Silicon hosts), verify current platform compatibility prior to procurement.
**Vendor-documented / product documentation**
- WAS is crawler-based DAST and requires additional configuration for API scan templates; out-of-the-box coverage for all APIs is not automatic.
- Concurrency limits are documented for certain scanner types and configurations and should be validated for planned deployment scale.
- Release notes indicate ongoing work on scan controls, session pattern handling, and related scan behaviors.
**Community-reported limitations**
- Some users report integration and reporting challenges beyond basic scan launching in specific environments.
- Standalone WAS scanners are functionally separate from Nessus network scanners; they are not interchangeable for network scanning use cases.
**Roadmap**
- This report did not include a formal product roadmap. Request the current roadmap or review release notes directly with the vendor for detailed product planning information.