Skip to main content

F5 BIG-IP

The F5 integration reads a BIG-IP through its iControl REST API. It runs on an Integrator inside your network, because the management interface of a load balancer is not something the CyberOptix CTEM Platform should reach over the internet.

It is read-only. The integration never changes configuration, saves it or restarts anything.

What it collects​

SyncCollects
Configuration backupThe LTM, network and system configuration as JSON, with secrets stripped on the Integrator before it leaves your network, versioned whenever it changes
Configuration reviewEvery configuration backup and exposure correlation sync is reviewed against the checks below, and what they find is raised as vulnerabilities on the device
Network discoveryInterfaces with their link state, self IPs with their VLANs, the networks they are addressed into, and static routes
Host discoveryThe ARP table and every pool member: what the BIG-IP has actually seen on the network and what it balances traffic to
Exposure correlationVirtual servers with their destination, pool members and client-side TLS profile and certificate, so an address reachable from outside is tied to the servers behind it

Pointed at one member of a device group, every sync reports that device. Add each member as its own integration.

Configuration review checks​

CheckRaised when
TLS 1.0 or 1.1 permittedA virtual server's client SSL profile does not disable TLS 1.0 or TLS 1.1
Certificate expired or expiringThe certificate a client SSL profile serves has expired or is about to
Management accessThe management HTTPS and SSH services are open to any address, SNMPv1 or v2c communities are configured, or no NTP or remote syslog server is set

Create a read-only user​

  1. Under System > Users > User List, click Create.
  2. Give the user a name (for example inventory) and a strong password.
  3. Set Role to Auditor (or Guest), with All partitions.
  4. Set Terminal Access to Disabled. The integration uses the REST API only and never opens a shell or tmsh.
  5. Click Finished.

Or from tmsh:

create auth user inventory password <password> partition-access add { all-partitions { role auditor } } shell none
save sys config

The Auditor role can read every configuration object and statistic, and nothing else. Local users can use iControl REST by default; if your BIG-IP restricts REST to particular users, add this user under System > Users > User List > REST API access.

The integration logs in against the local (tmos) authentication provider and sends the token it is issued on every request. It never sends the password with each request.

Connect it​

  1. Under Integrations, add F5 BIG-IP with the management address (hostname or IP), the username and the password.
  2. In the integration's settings, assign the Integrator that can reach the management address on port 443.
  3. Enable the syncs you want.

Certificates​

A BIG-IP ships with a self-signed management certificate. The first connection accepts it and records its fingerprint on the integration; every later connection must present the same certificate. If you replace the certificate, clear the pinned fingerprint in the integration's settings so the new one is recorded. A certificate issued by a trusted CA is verified normally and never pinned.

A wrong password fails the sync with an error. It does not report an empty device.