To participate in this event, please use the button to ask your questions
This topic is a chance to clarify your questions about the best practices and required elements to migrate your Cisco Adaptive Security Appliance (ASA) to Firepower Threat Defense (FTD).
Because of the continuous evolution of cybersecurity threats, it is always important to stay updated and protected. Firepower Threat Defense (FTD) is a next-generation firewall that is able to respond to existing or unknown threats. Its firewall features include access control through network conditions, user names, ports, inclusive applications or protocols, and the ability to establish VPN remote access or inter-site communication.
Ask questions from Wednesday 29th of January to Friday 14th of February, 2020
Osvaldo Garcia is a presale engineer for global customers at Cisco Global Virtual Engineering (GVE). He works the entire Cisco Security portfolio, from FTD, AMP, Cloudclock, Cisco Umbrella, ESA, WSA and ISE to Meraki, among others. Osvaldo holds a Bachelor’s degree in Computer Technology from the Technical Institute of Monterrey. He holds a CCNP Security and a CCNP R&S certification. Osvaldo is currently pursing a CCIE certification.
Osvaldo might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the Firewalls community.
Let's say that I have a few Sourcefire 3D Sensors (8130) and a Sourcefire Management Center that are on an OS that is before 5.4, one of them being on a version that's a bit older. What are the suggested upgrade paths for these devices? I know that I can'...
Hi - We currently have a slew of public facing email addresses that route to our internal mail server for agents to handle. We're going to move this process to the salesforce cloud and were provided one-to-one new address to redirect to: examp...
We have the Endpoint purge to delete any thing over 365 days, but this wasn't working as standard since in was installedSo disabled and enabled again and this seem to fix it, as had just under 200k endpoints captured. But it removed all clients that ...
I need to remove the "a=crypto:" part from my SDP header to my ISP SDP header from PureCloud via TLSContent-Type: application/sdpUser-Agent: ININ-EDGE/188.8.131.5258Content-Length: 351v=0o=- 2580238779 3812407684 IN IP4 172.24.22.90s=-c=IN IP4 172.24.22....
I activated the securityk9 license on the next boot on 2 x 4331 routers and it changed to "EvalRightToUse" so i could configure TLS and so forth.I just want to confirm the below statement with Cisco, but to my knowledge this should be fine for us in other...