Splunk Enterprise Security

What is the best way to build searches and alerting in a Hyper-V environment in which VMs pull MAC address ?

gg74
Engager

What is the best way to deal with building searches and alerting in a Hyper-V environment in which VMs pull MAC address from a pool controlled by the cluster nodes?  Is setting all of my VMs to use static MAC addresses best practice (this is a large undertaking and would require maintenance) or is there a better way to do this?  Should I rely on another variable to track these assets?

Labels (2)
0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

If you want a deterministic way to track assets, don't use a non-deterministic way of identifying the assets.

0 Karma

gg74
Engager

Is there a better variable to use than the MAC address?  Something that doesn't rely on manual intervention to set?  Is the GUID or device name the standard?  Just looking options I may not be aware of.

0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

It depends how your assets are set up - often a qualified host name is unique (enough) in your environment to distinguish between different hosts.

Get Updates on the Splunk Community!

Routing logs with Splunk OTel Collector for Kubernetes

The Splunk Distribution of the OpenTelemetry (OTel) Collector is a product that provides a way to ingest ...

Welcome to the Splunk Community!

(view in My Videos) We're so glad you're here! The Splunk Community is place to connect, learn, give back, and ...

Tech Talk | Elevating Digital Service Excellence: The Synergy of Splunk RUM & APM

Elevating Digital Service Excellence: The Synergy of Real User Monitoring and Application Performance ...