tsjilo.blogg.se - Nessus basic network scan

#NESSUS BASIC NETWORK SCAN HOW TO#
#NESSUS BASIC NETWORK SCAN TRIAL#
#NESSUS BASIC NETWORK SCAN WINDOWS#

The Schedule and Notifications options enable the scan to be performed at certain time and email the results to a list of recipients automatically. , insert the Name, Description, and Targets. Which can be used to fine-tune the compliance checks (credentials are required) and plugins. Be prepared to run lots of scans.Nessus provides a set of ready-to-use templates.

#NESSUS BASIC NETWORK SCAN TRIAL#

In general, after a certain point (following some of the basic guidance here and in the other links in this thread), improving scan performance is highly dependent on the environment being scanned and will require trial and error. For example, if the hardware or network can't handle more than 50 hosts at one time, and you try 100, every target will take longer to scan and bump your overall scan time to more than it would take to do 50 at once. The optimal settings based on targets, scan requirements, network capabilities, etc will vary, but keep in mind that asking the scan to do more than it's capable of can make the whole scan run longer.

Increasing the scan or engine performance settings beyond what the hardware/network/target/engine is capable of.

Nessus will automatically run the correct checks against the correct target while you may see some marginal improvements in disabling say, Amazon Linux Local Checks when scanning on-premise systems, the possibility for user error in using the wrong scan policy, or disabling the wrong plugin family generally outweighs the benefit.

Disabling plugin families in scan policies.

Re-evaluate your scan configurations/procedures at least annually and whenever an environment changes significantly.Consider breaking up large scan jobs into chunks this can help identify targets/subnets that take longer to assess and benefit from being scanned separately.Performing local checks is almost always faster and more efficient than probing network services remotely. Or run said dynamic scan policy weekly, and then run a subsequent scan with normal settings if you do use the informational level data. For example, if you only care about vulnerabilities and don't use scan data for anything else, run a dynamic scan policy and only scan with critical-medium severity plugins. But depending on your environment or scan requirements, you may choose to change the settings.

The default scan policy settings are a good balance of performance and thoroughness in terms of depth of assessment.

Some, like qdb_mem_usage may need to be altered after you increase the amount of RAM to the system.

Review the scan engine performance settings ( ) after ensuring the specs are as high as they can be.

Make sure Nessus meets the recommended specs ( ) - the more CPU and RAM you can give it, the better (it will max out at some point, and you'll hit network, target or network limitations.).

Make sure you're running the latest version of Nessus and the latest plugin set.

If you must run other services, try not to run them when Nessus is scanning and/or exclude Nessus data from on-access programs ( )

Dedicate the server to only running Nessus.

#NESSUS BASIC NETWORK SCAN WINDOWS#

Linux or Windows Server will get better performance.

Make sure Nessus is running on a server grade OS (aka, not Windows 10/11).

Some of these will be generic, because I don't know about your environment. Use other tools to populate a dynamic asset list?

#NESSUS BASIC NETWORK SCAN HOW TO#

but I'm having a hard time finding documentation on how to do this. and then based on those results, create a dynamic asset list to only run the basic scan against the asset list. Create a Host Discovery scan that pings the IP's. Changed "Max simultaneous hosts per scan" to 100 Disabled "Slow down the scan when network congestion is detected" Enabled "Stop scanning hosts that become unresponsive during the scan" However, we don't have to money to spin up another scanner.Īre there setting changes you would all recommend? I started with the Basic Scan, and made the following changes: I understand the typical recommended way of speeding up scans is using more scanners. The actual number of live hosts on these /24's is not near the 128k number of IP's that are scanned. And some of my scans take over 12 hours to scan 21 x /24's. I'm new to nessus and I inherited the product.