- Knowledge base
- Network & System Security
- Scanning techniques
-
Security updates
-
Product news
-
Next-Gen Vulnerability Management
-
Getting started
-
General
-
Operating status
-
Network & System Security
-
Web Application Security
-
Cloud Security
-
API Security
-
Phishing Simulation & Awareness Training
-
Attack Surface Management
-
Scanner Appliance
-
Device Agent
-
On-premise platform deployment
-
Asset management
-
Vulnerability manager
-
Reports
-
Digest reports
-
Organizer
-
Continuous monitoring
-
Integrations
-
Platform API
-
Remediation
-
Users
-
PCI DSS
-
Terms & conditions
-
Dashboard
What type of devices can be disrupted by scans?
Normally devices are not disrupted by a scan as the scan is adapted to avoid being too aggressive and also controls its flow of traffic dynamically.
However, in some IT environments, certain devices may experience brief disruptions during the scanning process. These disruptions can be triggered by specific tests, leading to unintended side effects that may affect not only the device being scanned but also other connected devices.
It is important to note that the devices causing disruptions may not be the same ones that are affected by the scan. For instance, scanning Domain Controllers has inadvertently led to brief downtimes for connected Backup units.
In such cases, simply excluding the Backup units from the scan is insufficient; instead, it is crucial to exclude the scanning of the Domain Controllers themselves. Additionally, you should identify which specific tests are causing these disruptions and disable those tests.
This allows you to continue scanning the Domain Controllers while avoiding the tests that lead to negative impacts on other devices.