For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Incident Remediation with Cisco Firepower and F5 SSL Orchestrator

SSL Orchestrator Configuration steps This guide assumes you have a working SSL Orchestrator Topology, either Incoming or Outgoing, and you want to add a Cisco Firepower TAP Service. Both Topology ty...
Published Aug 18, 2020
Version 1.0
BIG-IP
cisco
firepower
integration
iRules
remediation
security
sslo
KevinGallaugher's avatar
Icon for Employee rankEmployee
Technical Marketing Engineer for SSL Orchestrator. I have over 25 years experience in Cybersecurity, with over 15 years spent as a Technical Marketing Engineer. Prior to F5 I worked at Blue Coat, Gigamon and Fortinet.
View Profile
KevinGallaugher's avatar
Icon for Employee rankEmployee
Technical Marketing Engineer for SSL Orchestrator. I have over 25 years experience in Cybersecurity, with over 15 years spent as a Technical Marketing Engineer. Prior to F5 I worked at Blue Coat, Gigamon and Fortinet.
View Profile
dragonflymr's avatar
dragonflymr
Icon for Cirrostratus rankCirrostratus
Aug 25, 2020

Hi,

 I wonder how this should be implemented in cease we need to protect outbound traffic to the Internet. To intercept such traffic FTD-Protect VS will have to be full wildcard, the same as Ingress VS created by Topology wizard (sslo_Outbound-in-t-4 if I Am not wrong) so there will be conflict, no way to configure two VSs with the same settings.

Should then FTD-Protect iRule be added in Interception Rule section of the Topology in iRules property?

Piotr