Ingest Traps ESM Logs on Panorama

Visibility is a critical first step in preventing and reducing the impact of an attack. To help you meet this challenge, Panorama provides an integrated view of firewall logs (events on the network) and Traps™ ESM Server logs (security events on the endpoints) so that you can trace any suspicious or malicious activity.
For awareness and context on the events observed on the network and on your endpoints, forward security events that the Traps agents report to the ESM Server on to Panorama. Panorama can serve as a Syslog receiver that ingests these logs from the Traps ESM components using Syslog over TCP, UDP, or SSL. Then, Panorama can correlate discrete security events that occur on the endpoints with what’s happening on the network and generate match evidence. This evidence gives you more context on the chronology and flow of events to investigate issues and fix security gaps in your network.
  1. Define the log ingestion profile on Panorama and attach it to a Collector Group.
    Panorama virtual appliance in legacy mode cannot ingest Traps logs.
    1. Select PanoramaLog Ingestion Profile, and click Add.
    2. Enter a Name for the profile.
    3. Click Add and enter the details for the ESM Server. You can add up to four ESM Servers to a profile.
      1. Enter a Source Name.
      2. Specify the Port on which Panorama will be listening for syslog messages. The range is 23000 to 23999.
      3. Select the Transport layer protocol—TCP, UDP, or SSL.
      4. Select Traps_ESM for External Log type and 3.4.0 from the Version drop-down.
        As Traps log formats are updated, the updated log definitions will be available through content updates on Panorama.
    4. Select PanoramaCollector GroupsLog Ingestion and Add the log ingestion profile so that the Collector Group can receive logs from the ESM Server(s) listed in the profile.
      If you are enabling SSL for secure syslog communication between Panorama and the ESM Server(s), you must attach a certificate to the Managed Collectors that belong to the Collector Group (PanoramaManaged CollectorsGeneral, and select the certificate to use for Inbound Certificate for Secure Syslog).
    5. Commit changes to Panorama and the Collector Group.
  2. Configure Panorama as a Syslog receiver on the ESM Server.
    1. From the ESM Console, select SettingsESMSyslog, and Enable Syslog.
    2. Enter Panorama hostname or IP address as the Syslog Server and the Syslog Port on which Panorama is listening.
    3. Select the Transport layer protocol: TCP, TCP with SSL, or UDP. If you select TCP with SSL, the ESM Server requires a server certificate to enable client authentication.
      From Panorama, you must export the root CA certificate for the Inbound Certificate for Secure Syslog, and import the certificate in to the trusted root certificate store of the host on which you have installed the ESM Server.
    4. In the Logging Events area, select one or more of the events. At a minimum, you must enable sending of security events for prevention, notification, and provisional incidents that the Traps agents report. For details on the other forwarding settings, refer to the Traps 3.4 Administrator’s Guide.
  3. View ESM logs and correlated events.
    1. Select MonitorExternal LogsTraps ESM to view the logs ingested in to Panorama.
      ESM Logs and Correlated Events
    2. Select MonitorAutomated Correlation EngineCorrelated Events, and filter on the Wildfire and Traps ESM Correlated C2 correlation object name to find correlated events. Panorama generates correlated events when a host on your network exhibits command and control activity that matches the behavior observed for a malicious file in the WildFire virtual environment. This correlated event alerts you to suspicious activity that a Traps agent and the firewall have observed from one or more infected hosts on your network.

Related Documentation