Skip to main content

Cisco IOS configuration compliance auditing using Nessus

To use this feature you need to be a Nessus professional feed subscriber. Tebnable provides a  number of audit policy files. They are available for download from support portal. 

You can download CIS benchmark for both IOS devices and ASA firewalls as well as DISA switch and perimeter router audit files.

Setting up a policy is straight forward. It requires that plugin 46689 "Cisco IOS Compliance Checks" is enabled. I generally keep scans separate for sake of report clarity so I enable only this plugin. 

I normally enable SYN & UDP scans on all ports as well. As always with UDP, it makes scans much longer. On top of that I find that Nessus UDP scanner is not as reliable as NMAP. 

Next we configure credentials. We configure user/pass in "SSH Settings" on "Credentials" tab. Nessus supports only SSH for Cisco audits and requires a user with privileges sufficient to get a full output of "show running-config" or "show startup-config" (you can choose which one you want to audit). (Option "Save(show config)" has been deprecated). "Show running-config" requires a user with privilege 15 as only then  it is possible to get full output.

I tired creating "views" (using Cisco role based CLI) to no avail, I also tried lowering privilege level required to execute "sh run" which didn't work either. The problem here is that "show run" invokes a number of other commands (and sub commands) in the background. 

By default "show startup-config" requires privilege 15 too. Here we can work around by lowering privilege requires to execute this command.

To do so at the IOS prompt:

#conf t
#privilege exec level 1 show startup-config

This will allow any priv 1 (and higher) user to execute sh start. This user will then be able to see SNMP strings and passwords (if not encrypted), so the implications should be considered. 

If your security policy disallows SSHing directly with priv 15 accounts you can use 'standard' account and then use "enable" to elevate permissions instead. 

Last step is to import .audit file downloaded from Tenable's site. This is done in "Preferences" Tab. 

 To summarize:
  • download desired audit policy from Tenable
  • disable all plugins
  • enable 46689 "Cisco IOS Compliance Checks" plugin
  • specify credentials
  • import audit policy file
To create a privilege 15 user in Cisco IOS:

#conf t
#username auditor privilege 15 password somepass


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

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 ":"

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 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