Enrichment
Enrichment
Enrichment enhances raw logs by automatically adding meaningful context that makes events easier to understand, correlate, and investigate. Rather than relying solely on basic log data such as timestamps and error messages, enrichment supplements logs with diverse contextual information including asset details (hostname, IP address, operating system), user information (identity, roles, permissions), geolocation data (country, city, network location), threat intelligence (known malicious indicators, threat actor attribution), and risk context (severity scores, compliance implications, business impact). By layering this metadata onto raw logs, security teams gain the visibility required to assess the true significance of each event.
Supported Enrichment Types
Static: Applied at data ingestion, either during collection or storage. Static enrichment is indexed, which makes queries over large datasets run faster.
Dynamic: Applied during analysis, or when a query runs. Useful for lookups that are only possible long after logs are received (for example from threat intelligence). Dynamic enrichment uses less storage and collection load and is good for small datasets and short time ranges. Dynamic enrichment metadata is not stored.
Enrichment Sources
Logpoint provides a set of enrichment sources that add contextual information to logs during ingestion and processing. These enrichment sources provide additional data, such as asset details, user and identity information, geolocation data, network context, and threat intelligence that is automatically associated with events via matching fields such as IP addresses, hostnames, or usernames.
Logpoint Enrichment Sources
Enrichment Policies
An Enrichment Policy is made up of a set of enrichment specifications, a set of 5 or less enrichment rules. Enrichment rules define which normalized, event log key-value pairs in the message fields are matched against an enrichment source. When there is a match, the additional information from the Enrichment Source is added to the event.
When an Enrichment Policy is configured on a device, each log from the device is matched against all the enrichment rules in ascending order. You can create multiple enrichment policies, but only one can be applied to a single device.
Last updated
Was this helpful?