Cisco Security Analytics and Logging (SaaS) licenses come with a default data retention period of 90 days. This retention period allows organizations to store and analyze their security event data for up to 90 days, providing sufficient time for security monitoring and forensic investigations.

When packet capture is used on a Cisco Secure Firewall Threat Defense (FTD) device and the packet flow is waiting on the malware query, the Snort verdict appears as " retry. " This indicates that the device is still processing the malware analysis and has not yet determined the final action for the packet.

The " retry " verdict signifies that the packet is in a holding state while awaiting the result of the malware inspection, which helps in maintaining the security posture until a definitive decision is made.

Cisco Firepower uses FlexConfig objects to send NetFlow data. Here ' s the key point:

NetFlow_Set_Parameters object: Defines the parameters of the NetFlow data being exported (e.g., version, sampling rate).

NetFlow_Add_Destination object: Specifies the IP address and port of the flow collector (in this case, your Cisco Stealthwatch appliance) where the NetFlow data should be sent.

To configure an isolated bridge group for Integrated Routing and Bridging (IRB) mode on a Cisco Secure Firewall device, the action to take is to leave the BVI (Bridge Virtual Interface) interface name empty. This ensures that the bridge group operates in an isolated manner, where Layer 3 routing is not applied to the bridged interfaces, effectively isolating the traffic within the bridge group.

Steps:

Access the firewall ' s configuration interface.

Configure the bridge group interfaces.

Ensure that the BVI interface name is left empty to isolate the bridge group.

This configuration prevents Layer 3 routing for the isolated bridge group, ensuring that traffic remains contained within the bridge group.

When replacing a Cisco Secure Firewall high-availability (HA) device due to a failure, the first step the engineer must take is to unregister the secondary (failed) device from the Cisco Secure Firewall Management Center (FMC). This action separates the HA pair and ensures that the new replacement device can be registered and configured correctly.

Steps:

Access the FMC and navigate to the device management section.

Unregister the failed secondary device to remove it from the HA pair.

Register the replacement device to the FMC.

Reconfigure the HA settings to restore the high-availability configuration.

By unregistering the failed device first, the engineer ensures a clean setup for the replacement device, avoiding potential conflicts or issues in the HA configuration.

To create a malware and file policy on a Cisco Secure Firewall Threat Defense (FTD) device that ensures PDF, DOCX, and XLSX files are not sent to Cisco Secure Malware Analytics, the security engineer must configure local malware analysis. Local malware analysis allows the FTD to inspect and analyze files locally without sending them to the cloud-based Cisco Secure Malware Analytics.

Steps to configure local malware analysis:

In FMC, navigate toPolicies > Access Control > Malware & FilePolicies.

Create a new malware and file policy or edit an existing one.

Define rules to inspect specific file types, ensuring that PDF, DOCX, and XLSX files are handled locally.

Set the action for these file types to " Local Analysis. "

Apply the policy to the relevant access control policy.

This configuration ensures that the specified file types are analyzed locally, meeting the requirement to avoid sending them to Cisco Secure Malware Analytics.