External vulnerability scanning is a quick, easy and automated way to assess your network for the kinds of weaknesses hackers will look to exploit when assessing a target.
To get the best possible results, we recommend whitelisting va.scanner.defense.com/74.220.28.142 in any network security products you have in place (e.g. firewalls, IDS).
Log in to your Defense.com account and select Scanning from the navigation on the left-hand side.
From the expanded menu, select Vulnerability Scanning.
Next, click Add Group in the top right.
Each scan can be configured to be run on one or more assets (or hosts). Enter a Name for your Scan Group, then enter a list of assets you'd like to be scanned. These can be domain names, IP addresses, or IP ranges.
Please Note:If you're scanning multiple assets, separate each one with a comma (e.g: example.com,178.18.119.22).Click Start date and set the date and time the scan is to start.
Set the frequency you'd like the test to run, and check the Enable Schedule box.
Once you're happy, click Add Group and you'll be taken back to the Vulnerability Scan overview.
If you'd like to run a scan straight away, click on your Group name, then Scan now.
Once your scan has been run, click on the View scans button to view your report.
What kinds of vulnerabilities do we report on - and what do we ignore?
We report on findings with real, actionable confidence behind them where the pattern evidence is strong enough to be worth your attention.
Every finding we detect carries an internal confidence rating that determines whether and how it's reported. Understanding these helps explain why our results won't always match another vendor's:
Description | Reported? |
Vulnerable, exploited - confirmed via active exploitation or asset-specific testing | Always - highest confidence |
Vulnerable version - the service/software version is known-vulnerable | Reported |
Vulnerable, potential - flagged from patterns or indirect evidence, not confirmed | Reported, but at lower confidence |
Overridden, version check - a version match was positive, but other evidence showed it doesn't actually apply | Not reported |
Excluded, version check - a version-based finding excluded by policy or manual exception | Not reported |
Skipped due to DoS settings - the check was skipped to avoid risking a Denial of Service | Not reported |
And that's it! You now know how to configure and run vulnerability scans. đ