Splunk Security Essentials Setup

Prerequisites

Tool or access	Purpose	Verify
Bash and Python 3	Run bundled setup and validation helpers	bash --version && python3 --version
Required product/platform access	Inspect or configure the selected target	Complete the documented preflight
Credential files for live modes	Keep secrets out of chat	Verify paths only

Workflow Overview

┌───────────┐   ┌───────────────┐   ┌───────────────┐   ┌─────────────────┐
│ Preflight │ → │ Render/review │ → │ Apply/handoff │ → │ Validate evidence │
└───────────┘   └───────────────┘   └───────────────┘   └─────────────────┘

When to Activate

• A user asks to set up SSE, Security Essentials, MITRE/Kill Chain content exploration, Security Content recommendations, or starter security posture dashboards.
• Preview and review the splunk security essentials setup workflow before any live apply phase.
• Diagnose failed prerequisites, generated assets, configuration, or validation evidence.

Scope

Follow the documented read-only or render-first path whenever it is available. This skill does not imply permission to mutate live systems. Require explicit apply flags, protected credentials, and operator review for state changes.

Examples

Inspect the supported setup modes before selecting one:

bash skills/splunk-security-essentials-setup/scripts/setup.sh --help

Expected output: usage, supported modes, and required arguments are displayed without changing the target environment.

Inspect validation modes before running completion checks:

bash skills/splunk-security-essentials-setup/scripts/validate.sh --help

Expected output: offline, live, and completion options are displayed when the skill supports them; help exits without mutation.

Troubleshooting

Issue	Cause	Resolution
Preflight fails	A required tool or access path is missing	Resolve it before rendering or applying
Rendered assets are incomplete	Required non-secret inputs are absent	Complete intake and render again
Apply is blocked	Review, credentials, or explicit acceptance is missing	Use the documented handoff
Validation is incomplete	Live evidence is unavailable	Record the gap and keep completion open

Shared add-on completion gate

Whenever this workflow installs, configures, or hands off SSE, follow the shared completion gate. Package delivery alone is not success; validate security-data prerequisites and shipped dashboards against data.

Use this skill to install and validate Splunk Security Essentials (SSE).

Primary Commands

Preview:

bash skills/splunk-security-essentials-setup/scripts/setup.sh --dry-run

Machine-readable preview (emits a single JSON object; useful for agents):

bash skills/splunk-security-essentials-setup/scripts/setup.sh --dry-run --json

Install and validate:

bash skills/splunk-security-essentials-setup/scripts/setup.sh

Validate only:

bash skills/splunk-security-essentials-setup/scripts/validate.sh

Agent Behavior

• Install Splunk_Security_Essentials from Splunkbase app 3435, or use --file for an already-downloaded package.
• Keep SSE on the search tier or search head cluster deployer path.
• Do not treat SSE as an Enterprise Security replacement. It can safely coexist with ES and includes content references from ES, ES Content Update, and UBA.
• Splunkbase lists SSE through platform 10.5. Treat that entry as the repository's Splunk Cloud compatibility target; it does not change the self-managed Enterprise default from 10.4.1 or certify Enterprise 10.5.
• After install, guide operators through the setup checklist: Data Inventory Introspection, Content Mapping, app configuration review, and optional posture dashboards.

Read reference.md for compatibility notes and source links.