Configuration review
When a firewall or network device integration collects a configuration backup or NAT rules, the CyberOptix CTEM Platform reviews what it collected against the checks below. Anything a check finds is raised as a vulnerability on the device. You can promote it to a finding and work it like any other.
The review is analysis of data already collected, so it adds no load on the device. Turn it on with the integration's Configuration review sync. It runs after each Configuration backup and Exposure correlation sync.
Checks
Every check runs on every vendor whose data can answer it (Palo Alto, Fortinet, Cisco, Meraki, Juniper, ExtremeCloud IQ and F5 BIG-IP). Rule and NAT checks use the normalized rules each integration collects, and published service checks the virtual servers a load balancer serves. Configuration checks read the device's configuration, which is redacted before it is stored, and are vendor specific.
Firewall rules
| Check | Raised when | Severity |
|---|---|---|
| Any source to any destination on any service | An enabled allow rule matches everything | High |
| Sensitive service from any source | An allow rule permits SSH, Telnet, RDP, SMB, database, VNC, SNMP, LDAP and similar services from any source | High |
| Any service allowed | An allow rule permits every port between named sources and destinations | Medium |
| Any application allowed (PAN-OS) | An allow rule does not restrict applications | Medium |
| Shadowed rule | An earlier rule matches everything the rule matches, so it never takes effect | Medium |
| Allow rule without logging (PAN-OS, FortiOS, Meraki) | An allow rule does not log the traffic it permits | Low |
| Rule never matched (PAN-OS) | An enabled rule has a hit count of zero | Low |
| Disabled rule | A disabled rule is still configured | Informational |
NAT
| Check | Raised when | Severity |
|---|---|---|
| NAT publishes a sensitive service | A destination NAT or port forward publishes an administration, file sharing or database port to any source | High |
| Static NAT publishes every port | A one-to-one NAT maps an outside address to an internal host for all ports | Medium |
Published services
| Check | Raised when | Severity |
|---|---|---|
| Service accepts TLS 1.0 or 1.1 | A virtual server's client TLS profile still negotiates a deprecated protocol version | Medium |
| Expired certificate | The certificate a virtual server serves has passed its expiry date | Medium |
| Certificate expires within 30 days | The certificate a virtual server serves expires within the next 30 days | Low |
| Sensitive port published | A virtual server or published port exposes an administration, file sharing or database port at an outside address | High |
These read what the F5 BIG-IP integration collects: each virtual server with its pool, client SSL profile and the certificate the profile serves.
Device configuration
| Check | PAN-OS | FortiOS | Cisco IOS/IOS-XE | Cisco NX-OS | Cisco ASA | JunOS | Extreme Switch Engine | Extreme Fabric Engine | BIG-IP | Severity |
|---|---|---|---|---|---|---|---|---|---|---|
| Management allows Telnet or HTTP | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | High | |
| SNMPv1 or SNMPv2c in use | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Medium | ||
| SSH version 1 accepted | Yes | Yes | Yes | Medium | ||||||
| Local passwords stored with weak encoding | Yes | Medium | ||||||||
| Management not restricted to trusted sources | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Medium | ||
| No remote log collector | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Low |
| Clock not synchronized with NTP | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Low |
Meraki's Dashboard configuration has no management plane settings to review, so Meraki
devices get the rule and NAT checks only. A BIG-IP has no Telnet and serves its
management plane over HTTPS only, so cleartext management is not assessed on it; its
httpd and sshd allow lists, SNMP communities, NTP servers and remote syslog servers
are, beside the published service checks above.
Extreme switch configurations come from ExtremeCloud IQ. SNMP is not
assessed on them: Switch Engine leaves the factory communities out of its configuration on
upgraded switches, and Fabric Engine never stores communities in its configuration, so the
configuration cannot show whether SNMPv1 or v2c is in use. Switch Engine has Telnet on by
default, so a configuration without disable telnet is reported. Access point
configurations are not collected.
Cisco ASA configurations come from the Cisco integration, IOS and IOS-XE from Cisco IOS / IOS-XE and NX-OS from Cisco NX-OS, the latter two under Network.
How findings open and close
- A vulnerability is raised once per check and per rule (or per device, for configuration checks). Re-running the review updates it rather than adding another.
- When a later review no longer finds it, because the rule was fixed or removed or the setting changed, the vulnerability is marked fixed and any finding on it moves to pending retest.
- A vulnerability you have accepted or marked as a false positive stays that way.
- A check that cannot assess a device (for example SSH version on FortiOS) never raises or closes anything there.