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!

Splunk Observability Cloud | Unified Identity - Now Available for Existing Splunk ...

Raise your hand if you’ve already forgotten your username or password when logging into an account. (We can’t ...

Index This | How many sides does a circle have?

February 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

Registration for Splunk University is Now Open!

Are you ready for an adventure in learning?   Brace yourselves because Splunk University is back, and it's ...