Field names (CIM)
One set of field names for every source, the ones security teams already know from Splunk.
src, dest, user, process, signature_id. When an event is stored, LogPulse adds the CIM name next to the older LogPulse name, such as process_path next to image. Both work in search and detections.How it works
- Parsed fields to Add CIM names
- Add CIM names to Event
- Event to Search and dashboards
- Event to Detections
The CIM names come from the public CIM documentation. A value a parser already set under the CIM name wins; LogPulse only fills names that are missing. That costs a few percent more storage per event and keeps every existing search and rule working.
CIM fields and aliases
The CIM field gets the value of the first LogPulse field in the list that has one.
| CIM field | Filled from | CIM data model |
|---|---|---|
src | src_ip, src_host, src_hostname, client_ip | Network Traffic, Authentication, Intrusion Detection, Web, Network Sessions |
dest | dest_ip, dest_host, dest_hostname, hostname | Network Traffic, Authentication, Endpoint, Intrusion Detection, Web |
dvc | device, device_name, device_ip, devname | Network Traffic, Intrusion Detection, Change |
src_interface | interface | Network Traffic |
src_zone / dest_zone | src_interface / dest_interface | Network Traffic |
tcp_flag | tcp_flags | Network Traffic |
src_mac | mac, src_mac_address, calling_station_id | Network Traffic, Authentication, Network Sessions |
vendor_action | waf_action, pan_action, fortinet_action | Network Traffic |
rule | rule_name, policy, policy_name | Network Traffic, Intrusion Detection |
signature_id | event_code, event_id, EventCode, asa_msgid, ise_code, logid, alert_type | Intrusion Detection, Malware, Authentication, Endpoint |
signature | alert_name, threat_name, rule_name, log_description | Intrusion Detection, Malware, Alerts |
authentication_method | auth_type, auth_protocol, authentication_protocol | Authentication |
reason | failure_reason | Authentication |
src_user | subject_user, actor, event_user, sender | Authentication, Change, Email |
process | command_line, process_cmdline | Endpoint |
process_path | image, process_path_full | Endpoint |
process_name | file name of process_path or image | Endpoint |
process_exec | process_name | Endpoint |
process_integrity_level | integrity_level | Endpoint |
process_current_directory | current_directory | Endpoint |
parent_process_path | parent_image, parent_process (when it is a path) | Endpoint |
parent_process_name | file name of the parent path | Endpoint |
parent_process_id | parent_pid | Endpoint |
registry_value_data | registry_data, registry_value | Endpoint |
registry_key_name | last part of registry_path | Endpoint |
file_name | file name of file_path | Endpoint |
http_user_agent | user_agent | Web |
http_referrer | referer, referrer | Web |
site | vhost, host_header | Web |
reply_code | response_code, rcode | Network Resolution (DNS) |
record_type | query_type, qtype | Network Resolution (DNS) |
recipient | recipients |
Fields that already have the same name in LogPulse and the CIM, such as user, action, src_port, dest_port and query, are not in the table.
Searching
Use the CIM name in new searches and rules. A Splunk search on CIM fields runs as it is:
earliest=-24h index=windows channel="Microsoft-Windows-Sysmon/Operational" signature_id=1
| stats count by dest, user, process_name, parent_process_name
| sort - countSee LPQL syntax for the rest of the language.
Your own data
Sending data over the HTTP API, from Cribl or with your own parser rules? Use the CIM names straight away. The built-in rules and the Sigma rules search on them. The rules from the Detection Hub follow; until then they use the older names, which is why both stay on every event.
parent_process
parent_process holds the path of the parent; in the CIM it is the parent's command line. Use parent_process_path and parent_process_name, which mean the same in both. In a later step parent_process gets the CIM meaning.Frequently asked questions
- Does LogPulse use Splunk CIM field names?
- Yes. The Splunk Common Information Model names are the field standard of LogPulse: src, dest, user, action, process, process_path, signature_id, http_user_agent and so on. Searches, dashboards and detections moved from Splunk find their fields.
- Do my existing LogPulse searches still work?
- Yes. The older LogPulse names, such as src_ip, image and command_line, stay on every event. LogPulse adds the CIM name next to them when an event is stored.
- What happens when a parser already sets a CIM field?
- The parser wins. LogPulse only adds a CIM name that is missing from the event.
- Does old data get the CIM names?
- No. The CIM names are added when an event is stored, so only events stored after the change have them. Search older data with the LogPulse names.