Skip to main content
User guide

Baseline checks

Host-configuration baseline and OS end-of-life compliance patrol. A rule library, manual or daily runs, results and trends per host. Data from the CIM Endpoint and Change data models.

Baseline checks express the expected configuration of every host as rules, judge them against the endpoint data already in Splunk, and produce a score and failed items. Available in every edition.

Results

Data source

Judgements run over the CIM Endpoint (Processes, Services, Ports, Registry, Filesystem) and Change data models with tstats. An osquery TA's sourcetypes work directly. Hosts are enumerated from Endpoint.Processes by default; without CIM data a run can be given an explicit hosts=.

OS end-of-life dates come from a bundled catalogue (copilot_eol_catalog), refreshable with eol_sync.py.

Tabs

TabContent
RulesThe library: id, platform (linux, windows), collection SPL fragment, judgement (equals, contains, threshold), severity, enabled. Import defaults loads a CIS starter pack; a rule can be dry-run to see what it collects
RunsEach run's time, hosts, pass, fail, error and score. Run now runs manually; [baseline] schedule_enabled = 1 runs daily
ResultsHost and rule judgements with evidence on failures; a score trend line

Rules

Field map

Field map shows which data-model field each rule field resolves to on this instance. Without CIM a built-in minimal table applies.

Limits

ItemNotes
tstatsCovers index-time fields and accelerated data models only. Search-time extractions need | stats
No CIM Endpoint dataNo hosts are enumerated and Run now reports 0. Pass hosts= or onboard endpoint data first

On this page