Skip to main content

Cisco switch and router patch scan policy using Nessus

There are a few caveats to scanning Cisco switches with Nessus.


First: I recommend scanning only specific management IP addresses of devices rather than network ranges. The reason for that is that someone could set up a rogue SSH server and intercept the credential you use for scanning. You  can export to the list of IPs from CiscoWorks or use NMAP scan and import result to Nessus.


Second: Nessus supports only SSH authentication for Cisco devices. 


Third: our policy will include checks for IOS, CatOS and Linksys devices.


Fourth: Probably the most important one. You may be running version of IOS that has known vulnerabilities but your device may not be vulnerable. For example if there is a vulnerability in http server but your device doesn't have it enabled you are not vulnerable. Furthermore there are different feature sets of the same IOS version. You may be running "IP Base" set  which doesn't support MPLS but Nessus will show MPLS vulnerability.


To perform this scan an IOS user with privilege 1 is sufficient. Nessus uses output of "show version". 


There are a number of approaches to creating Nessus scanning policies.

1. enable whole "Cisco" family.  This policy would however include checks specific to ASA, Aironet etc - This is Tenable recommended approach. 

2. create a filter (plugin name - contains - cisco) and enable all plug-ins. This policy would include things like CSA agent detection on Windows, VPN client software, etc. Lot of checks not applicable to switches or routers. 

3.use Nessus plugin filtering feature and selectively enable only switch/router applicable plugins - this is my proffered method as it reduces the risk of potential adverse effects the scan could have. Even though this should not happen (Nessus should not fire a plugin that's not applicable), last thing we'd like would be to bring a core switch down.

Here we go: 

1. Configure General settings:
  • disable both Netstat  SSH & WMI
  • disable SNMP Scan
  • enable UDP Scan
  • set port range to 1-65535
  • leave remaining settings on defaults
You may want to enable Network Congestion handling features depending on your network.  You may also want to limit number of maximum hosts scanned simultaneously (Max Hosts Per Scan). 






2. Configure Credentials:
  • Specify SSH User name




3. Select Plugins:

  • All plugins are enabled by default so click "Disable All"
  • Enable Cisco plugin family
  • Enable Settings family



Comments

Popular posts from this blog

x.509 Certificates - Critical vs non-critical extensions

Extensions are used to associate additional information with the user or the key.  Each certificate extension has three attributes - extnID, critical, extnValue extnID - Extension ID - an OID that specifies the format and definitions of the extension critical - Critical flag - Boolean value extnValue - Extension value  Criticality flag specifies whether the information in an extension is important. If an application doesn't recognize the extension marked as critical, the certificate cannot be accepted. If an extension is not marked as critical (critical value False) it can be ignored by an application. In Windows, critical extensions are marked with a yellow exclamation mark,  View certificate extensions using OpenSSL: # openssl x509 -inform pem -in cert.pem -text -noout (output abbreviated)         X509v3 extensions:             X509v3 Key Usage: critical                 Digital Signature, Key Encipherment             X509v3 Subject Key Identifier

Cisco ASA Certificate Revocation Checking

ASA supports status verification using CRLs and OCSP. CRL can be retrieved using HTTP, LDAP or SCEP. Revocation checking using CRL: Over HTTP: ciscoasa(config)# crypto ca trustpoint ASDM_TrustPoint2 ciscoasa(config-ca-trustpoint)# revocation-check crl ciscoasa(config-ca-crl)# protocol http By default ASA will use address listed in CDP extension of the certificate that is being validated.  To override default behaviour we need to add the following in the CRL configuration context. ciscoasa(config-ca-crl)# policy static ciscoasa(config-ca-crl)# url 1 http://cdpurl.kp.local/crl.crl Over LDAP: Certificate I'm using for this lab, doesn't have LDAP address in its CDP extension. Therefore I'm using "policy static"  to specify LDAP URL where CRL can be retrieved.  ciscoasa(config)# crypto ca trustpoint ASDM_TrustPoint2 ciscoasa(config-ca-trustpoint)# revocation-check crl ciscoasa(config-ca-trustpoint)# crl configure ciscoasa

Count number of lines - 'findstr'

How do I count number of lines in a command output? findstr /r/n "^" | find /c ":" Above commands will display number of lines output by whatever command (well, nearly whatever) you specify in the front.  For example:  C:\>ping localhost | findstr /r/n "^" | find /c ":" FINDSTR: // ignored 12 This comes handy if you want to find out how many OUs you have in Active Directory: dsquery ou  -limit 0 | findstr /r/n "^" | find /c ":" How many user accounts there are: dsquery user -limit 0 | findstr /r/n "^" | find /c ":" Computers: dsquery computer -limit | findstr /r/n "^" | find /c ":"