- Help Center
- Platform Overview
- Onboarding
-
Getting Started
-
Platform Overview
-
Scanning & Testing
-
Troubleshooting Asset Blockers
-
Vulnerability Management
-
Attack Surface Management
-
Continuous Threat Exposure Management (CTEM)
-
Integrations
-
Reporting
-
Security Best Practices
-
Advanced Features & Customizations
-
Troubleshooting & FAQs
-
Updates & Announcements
Why do I need to white-list the edgescan source IPs?
White-listing edgescan IPs avoids alert triggers during fast, 'loud' scans, ensuring vulnerabilities are detected to improve security posture.
Version Number: v1.0.1
Published Date: 14 May 2024
____________________________________________________________________________
Real-world attacks are typically slower and more covert than automated vulnerability scans, often evading detection for extended periods. When conducting scans in shorter durations, the process becomes more noticeable and quicker, potentially triggering Intrusion Detection Systems (IDS) or alerts on the client's side.
Failing to whitelist our IPs could hinder our ability to identify vulnerabilities in the client's infrastructure that malicious actors could exploit without detection. Our goal is to uncover as many underlying vulnerabilities as possible to assist the client in enhancing their overall security measures. Keeping our source IPs whitelisted is crucial to prevent any delays in assessments.