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
KevinGallaugher's avatar
KevinGallaugher
Icon for Employee rankEmployee
Aug 21, 2020

Hi Piotr, great question. This is an error on may part. The only key here is the connection passing thru SSL Orchestrator, internet bound or not, so the Protect VS can enforce the block. I would not consider this to be a best practices guide. This is merely a demonstration of some very cool capabilities.