Splunk Enterprise Security

Splunk Enterprise Security: Expected Host Not Reporting finds hosts that are reporting with a different name. How to fix this?

edonze
Path Finder

Expected Host Not Reporting finds results for hosts that are reporting with a different name; for instance, the short DNS name rather than the fqdn, or the IP address rather than the hostname.
Is there a way to fix this?

sshres5
Communicator

what does your hostname -f return?

Add your FQDN on the /etc/hosts, that should provide you the FQDN.

Also, you can add "host = hostname" field in the inputs.conf on the forwarder

0 Karma

syahiya
Engager

I think @edonze is looking for a solution to the Correlation Rule "Expected Host Not Reporting " in Enterprise Security App. We are also facing the same issue and thus we are getting lot of false positive alerts.

0 Karma

hardikJsheth
Motivator

Check out asset table on your ES app.
This table contains field called "is_expected" which determines if host is going to be reported by the mentioned correlation search. If you are getting incorrect values as hostname check the asset table and update it as required.

0 Karma
Get Updates on the Splunk Community!

Upcoming Webinar: Unmasking Insider Threats with Slunk Enterprise Security’s UEBA

Join us on Wed, Dec 10. at 10AM PST / 1PM EST for a live webinar and demo with Splunk experts! Discover how ...

.conf25 technical session recap of Observability for Gen AI: Monitoring LLM ...

If you’re unfamiliar, .conf is Splunk’s premier event where the Splunk community, customers, partners, and ...

A Season of Skills: New Splunk Courses to Light Up Your Learning Journey

There’s something special about this time of year—maybe it’s the glow of the holidays, maybe it’s the ...