Skip to main content

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​

CheckRaised whenSeverity
Any source to any destination on any serviceAn enabled allow rule matches everythingHigh
Sensitive service from any sourceAn allow rule permits SSH, Telnet, RDP, SMB, database, VNC, SNMP, LDAP and similar services from any sourceHigh
Any service allowedAn allow rule permits every port between named sources and destinationsMedium
Any application allowed (PAN-OS)An allow rule does not restrict applicationsMedium
Shadowed ruleAn earlier rule matches everything the rule matches, so it never takes effectMedium
Allow rule without logging (PAN-OS, FortiOS, Meraki)An allow rule does not log the traffic it permitsLow
Rule never matched (PAN-OS)An enabled rule has a hit count of zeroLow
Disabled ruleA disabled rule is still configuredInformational

NAT​

CheckRaised whenSeverity
NAT publishes a sensitive serviceA destination NAT or port forward publishes an administration, file sharing or database port to any sourceHigh
Static NAT publishes every portA one-to-one NAT maps an outside address to an internal host for all portsMedium

Published services​

CheckRaised whenSeverity
Service accepts TLS 1.0 or 1.1A virtual server's client TLS profile still negotiates a deprecated protocol versionMedium
Expired certificateThe certificate a virtual server serves has passed its expiry dateMedium
Certificate expires within 30 daysThe certificate a virtual server serves expires within the next 30 daysLow
Sensitive port publishedA virtual server or published port exposes an administration, file sharing or database port at an outside addressHigh

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​

CheckPAN-OSFortiOSCisco IOS/IOS-XECisco NX-OSCisco ASAJunOSExtreme Switch EngineExtreme Fabric EngineBIG-IPSeverity
Management allows Telnet or HTTPYesYesYesYesYesYesYesYesHigh
SNMPv1 or SNMPv2c in useYesYesYesYesYesYesYesMedium
SSH version 1 acceptedYesYesYesMedium
Local passwords stored with weak encodingYesMedium
Management not restricted to trusted sourcesYesYesYesYesYesYesYesMedium
No remote log collectorYesYesYesYesYesYesYesYesYesLow
Clock not synchronized with NTPYesYesYesYesYesYesYesYesYesLow

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.