Getting Data In

Windows TA not extracting key_path as registry_path from registry_type="baseline"

bowesmana
SplunkTrust
SplunkTrust

Is it an omission that the latest Windows TA will only extract registry_path if the registry_type field contains "\w+Key". As a result, registry_path is not set to key_path and therefore in the Endpoint.Registry datamodel, there is no value stored for registry_path in the datamodel and the path comes out as unknown.

Has anyone come across a good reason NOT to add the additional mapping, so that it will pass through the DM correctly.

The consequence is that you can't use tstats on an accelerated DM

Labels (3)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...