Deep Packet Inspection (DPI) is a fundamental technique used by firewalls to inspect headers and the payload of network packets before passing them down the network subject to security rules. DPI provides information about the source and destination of the packet, the protocol, other IP and TCP/UDP header information, and the actual data. In the Common Information Model, deep packet inspection data is typically mapped to the Network Traffic Data model.
DPI provides raw information of everything transmitted over a network, including things that aren’t necessarily part of or difficult to extract from a log, such as database query results. PCAP data can also be used to provide and identify:
- DNS session analysis for malicious domain communications from each endpoint
- Abnormal amounts of traffic or sessions
- Abnormal amounts of domain and host communications
- Known malicious traffic from a host
- Expired SSL certification analysis
- Abnormal host communications (internal and external)
When your Splunk deployment is ingesting deep packet inspection data, you can use it to accomplish security and compliance and IT Ops use cases.
Guidance for onboarding data can be found in the Spunk Documentation, Getting Data In (Splunk Enterprise) or Getting Data In (Splunk Cloud). In addition, these Splunk Add-Ons and Apps are helpful for working with deep packet inspection data.
Looking for more information on data types? Download the Splunk Essential Guide to Machine Data.