Configuring Cisco Talos Intelligence for FTD and WSA
An organization wants to improve its cybersecurity processes and to add intelligence to its data. The organization wants to utilize the most current intelligence data for URL filtering, reputations, and vulnerability information that can be integrated with the Cisco FTD and Cisco WSA. What must be done to accomplish these objectives?
Community Insight
The core concept tested is identifying the primary vendor-specific threat intelligence feed integrated natively with Cisco security appliances, avoiding third-party or irrelevant standards bodies.
This question addresses the integration of threat intelligence into Cisco Secure Firewall (FTD) and Web Security Appliance (WSA). It establishes that Cisco Talos is the native, most current source for URL filtering, reputation data, and vulnerability information required for these objectives.
Candidates often select pxGrid (Option D) because it is a valid mechanism for sharing intelligence, but they fail to recognize that NIST is not the direct provider of real-time operational threat feeds for FTD/WSA configuration in this context.
Community Discussion (6 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Cisco Talos Intelligence Group is Cisco's dedicated threat intelligence team responsible for collecting, analyzing, and disseminating real-time security data. As noted by user Alizade, Talos provides the specific URL filtering, reputation, and vulnerability data that can be directly ingested by Cisco Firepower Management Center (FMC), which then pushes policies to FTD and WSA. The official documentation confirms that FDM/FMC utilizes Talos feeds for Security Intelligence policies.Why the Other Options Are Wrong
Option B is incorrect because the IETF defines internet standards (RFCs) and does not provide dynamic operational threat feeds for firewalls. Option C refers to the Internet Storm Center, which is part of Kaspersky Labs; while useful, it is not the native 'most current' solution integrated out-of-the-box with Cisco appliances compared to Talos. Option D suggests using pxGrid to connect to NIST; as user haiderzaid clarified, pxGrid is a protocol for sharing intelligence between platforms, but NIST publishes static databases (like CVEs) rather than the real-time actionable threat feeds needed for immediate firewall blocking.Community Comment Notes
User iluvmicrosoft highlights that FDM primarily relies on Talos, reinforcing the exclusivity of the answer. User XBfoundX correctly points out that Security Intelligence policies use Talos feeds to drop unwanted traffic before access control evaluation. User Premium_Pils provided the official Cisco configuration guide link validating Talos integration.Official Reference
Exam Strategy
When configuring Cisco security appliances, always prioritize native vendor integrations for core functions like threat intelligence. Remember that Cisco Talos is the proprietary engine powering URL filtering and reputation services across the Cisco security portfolio.
Frequently Asked Questions
Can FTD use third-party threat feeds instead of Talos?
Yes, via FMC you can add third-party feeds, but Talos is the native, pre-integrated source specifically mentioned for 'current intelligence' in this exam context.
What is the role of pxGrid in this scenario?
pxGrid is a protocol for sharing telemetry and intelligence between different security platforms, but it is not the direct method for importing NIST data into FTD/WSA for URL filtering.