- 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 are potentially dangerous test and tests that perform active break-in attempts?
The potentially dangerous test setting allows the users to enable a set of plugins within the library of vulnerability checks, which may have a negative effect on the network, device, or application being tested.
Tests that perform active break-in attempts should be treated as an extension of Potentially dangerous tests as the main concept remains the same.
Some examples of the impact can be Denial of Service conditions, modification of applications, restarting servers, lock-outs, etc. Therefore, we recommend that the potentially dangerous tests and tests that perform active break-in attempts be used in a pre-production environment.
These categories include around 3000 plugins that aren't automatically performed when running a scan without those settings enabled.
Enable the categories
To activate potentially dangerous tests in Security Center, see the following article: https://support.holmsecurity.com/knowledge/how-do-i-run-a-scan-with-potentially-dangerous-test