Splunk Enterprise
Customer-managed platform for ingesting, indexing, searching and visualizing machine data.
6 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Splunk Enterprise installation package on supported Linux or Windows hosts; Docker is limited to supported standalone and single-server topologies.
Runs in
Documented customer environment
Standalone or distributed customer-operated search heads, indexers and management components, with local storage or optional SmartStore object storage
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- AWS
- Azure
- Google Cloud
Servers / containers
Operated by
Your team
Customer manages compute, networking, storage, data inputs, certificates, clustering, capacity, backups, license configuration, monitoring and upgrades.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Splunk Enterprise reference hardware for AWS, Azure and Google Cloud ↗ · Source checked 2026-11-16
Customer-managed Splunk Enterprise BYOL architecture ↗ · Source checked 2026-11-16
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Splunk Enterprise reference hardware for AWS, Azure and Google Cloud ↗ · Source checked 2026-11-16
Customer-managed Splunk Enterprise BYOL architecture ↗ · Source checked 2026-11-16
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Splunk Enterprise reference hardware for AWS, Azure and Google Cloud ↗ · Source checked 2026-11-16
Customer-managed Splunk Enterprise BYOL architecture ↗ · Source checked 2026-11-16
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Splunk Enterprise installation package on supported Linux or Windows hosts; Docker is limited to supported standalone and single-server topologies. |
|---|---|
| Infrastructure | Servers / containers Splunk Enterprise runs persistent standalone or distributed search, indexing and management services on customer-managed hosts. SmartStore can move indexed data to customer object storage, but the search and indexing tiers remain long-running server workloads. |
| Licensing model | Commercial Only Splunk Enterprise is proprietary software. Production customers purchase commercial end-user licenses based on indexed data volume or licensed infrastructure. Trial, developer and Free licenses are restricted alternatives and do not establish an open-source edition. |
| License | Commercial end-user license based on data volume or infrastructure; limited trial, developer and Free licenses have separate restrictions. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
10 of 12 fields researched (83%) · 10 documented · 0 unresolved. Evidence coverage is not a feature score.
- Marketplace delivery
AvailableEvidence and scope for Marketplace delivery
Splunk publishes an AWS AMI with a 60-day Enterprise trial. Continued paid software use requires an external license; the AMI is not a paid Enterprise subscription or proof of software-spend commitment credit. Verify its packaged version separately from upstream releases.
Vendor-published AWS offer; procurement and application hosting are distinct · Source ↗ · Offer prodview-l6oos72bsyaks ↗ — Splunk; EC2 AMI with trial; commercial license purchased outside Marketplace · Reviewed 2026-11-16
Documented · Editor reviewed.
- Single sign-on
AvailableEvidence and scope for Single sign-on
Enterprise 10.6 documents SAML 2.0 SSO, supported IdP connectivity, role/realName/mail attributes and administrator change_authentication capability. Encrypted assertions can be decrypted when configured; this does not establish SCIM provisioning.
Customer-managed Splunk Enterprise 10.6 SAML configuration · Source ↗ · Reviewed 2026-11-16
Documented · Editor reviewed.
- SCIM provisioning
DocumentedEvidence and scope for SCIM provisioning
Enterprise 10.6 documents SCIM-based deletion of SAML users with a compatible Okta integration. Its release notes identify Entra ID de-provisioning as controlled availability. These sources establish scoped de-provisioning, not unrestricted SCIM user creation, updates or group synchronization.
Splunk Enterprise 10.6 SAML user-removal workflow; identity-provider and availability conditions apply · Source ↗ · 10.6 controlled-availability Entra ID feature ↗ · Reviewed 2026-11-16
Documented · Editor reviewed.
- Compliance attestations
DocumentedEvidence and scope for Compliance attestations
Splunk’s 10.6 guide identifies OpenSSL FIPS Provider certificate 4985 for FIPS 140-3. NIST lists that module as active, with sunset 2030-03-10 and approved-mode conditions. This is a cryptographic-module validation; deployment OS, mode, TLS and app prerequisites remain essential and it is not a blanket Splunk deployment attestation.
Splunk 10.6 documented module plus NIST validation status checked 2026-11-16 · Source ↗ · NIST CMVP certificate 4985 ↗ · Reviewed 2026-11-16
Documented · Editor reviewed.
- Security controls
DocumentedEvidence and scope for Security controls
FIPS mode requires a supported x86-64 OS running in FIPS mode, TLS 1.2+ between nodes and compatible apps. The guide lists the older FIPS 140-2 certificate as expired in September 2026; select the supported 140-3 path and validate the full configuration.
Enterprise 10.6 FIPS configuration prerequisites; not automatic security or regulatory compliance · Source ↗ · Reviewed 2026-11-16
Documented · Editor reviewed.
- Air-gapped operation
AvailableEvidence and scope for Air-gapped operation
Splunk explicitly offers Enterprise for private-cloud/on-premises deployment, including air-gapped environments. This establishes the vendor’s deployment option; the selected apps, license delivery, updates, trust material and data integrations still need a disconnected operating procedure.
Commercial Splunk Enterprise deployment option; not Splunk Cloud or every add-on · Source ↗ · Reviewed 2026-11-16
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
Splunk supplies operating-system-specific Enterprise installers. Select the required platform/version and verify the published checksum. The installation guide limits Docker to supported standalone and single-server uses; a download is not a complete distributed infrastructure template.
Splunk Enterprise 10.6 installation guidance; topology and platform determine the artifact · Source ↗ · Enterprise packages and checksums ↗ · Reviewed 2026-11-16
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The Enterprise 10.6 single-instance reference specifies 12 physical cores or 24 vCPU at 2 GHz+, 12 GB RAM and a 1 Gb NIC. Storage, search concurrency, ingest volume and distributed roles require separate sizing.
S1 single-instance production reference; not a multi-tier total or operating-cost estimate · Source ↗ · Reviewed 2026-11-16
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
Splunk Enterprise is proprietary software. Production customers purchase commercial end-user licenses based on indexed data volume or licensed infrastructure. Trial, developer and Free licenses are restricted alternatives and do not establish an open-source edition.
Splunk Enterprise: software license terms; infrastructure and operating costs are separate · Source ↗ · Edition and license conditions ↗ · Reviewed 2026-11-16
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
Splunk Enterprise 10.6.1 was released October 16, 2026. The release page warns against Universal Forwarder 10.6.0, while SVD-2026-1101 names 10.6.1 and maintained parallel branches as forthcoming November fix targets.
Splunk Enterprise 10.6 release line; advance notice is not a final CVE matrix · Source ↗ · November 2026 advance notice ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
Show all fields (2 not researched)
- Cloud commitment eligibility
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
This entry covers customer-managed Splunk Enterprise, not Splunk Cloud Platform. Splunk documents customer-managed BYOL architectures on AWS, Azure and Google Cloud. Current installation documentation limits supported container deployments to standalone and single-server topologies, so distributed production deployments should follow supported package-based validated architectures. Confirm supported operating systems, instance types, object-store throughput, cache sizing and clustering requirements. Splunk advance notice SVD-2026-1101 says forthcoming November disclosures are fixed in Enterprise 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 and strongly recommends those or later releases. Final CVE-specific disclosures were not live during this review; 10.6.0 Universal Forwarder users should move to 10.6.1 or later.
Category fit
- Observability
- Ingests, indexes and searches machine data for operational monitoring, troubleshooting, dashboards and alerting.
- Data & analytics
- Provides search, dashboards, reports and statistical analysis over indexed machine-generated data.
Compare within Observability
- AVEVA PI System (BYOL)Commercial industrial data collection, historian and visualization system with an AWS architecture.
- AWS
- Cloud Carbon FootprintOpen-source cloud-usage, energy and carbon-estimation application.
- Google Cloud
- Coroot Community EditionSelf-hosted application observability with service maps, logs, metrics, traces and continuous profiling.
- AWS
- Azure
- Google Cloud
- Oracle Cloud
- Datadog BYOC LogsDatadog log processing, indexing and storage in the customer's cloud, with search through Datadog Log Explorer.
- AWS
- Azure
- Google Cloud
- Elastic Cloud EnterpriseCommercial self-managed orchestration platform for Elastic Stack deployments across customer cloud hosts.
- AWS
- Azure
- Google Cloud
- Elastic Cloud on KubernetesElastic's Kubernetes operator for deploying and operating Elasticsearch, Kibana and related Elastic Stack resources in customer clusters.
- AWS
- Azure
- Google Cloud
- Grafana OSS Self-HostedSelf-hosted dashboards, visualization and alerting for operational data.
- AWS
- Langfuse Self-HostedSelf-hosted LLM observability, evaluations and prompt-management platform.
- AWS
- Azure
- Google Cloud
- Railway
- Render
Showing 8 of 20 other listings in Observability. These products address related workflows; read their category-fit notes before comparing scope. See all of Observability →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Splunk Enterprise installation overview ↗help.splunk.com
- Splunk Enterprise reference hardware ↗help.splunk.com
- Customer-managed BYOL SmartStore architectures ↗help.splunk.com
- Splunk Enterprise license types ↗help.splunk.com
- Splunk November 2026 advance notice ↗advisory.splunk.com
- Splunk Enterprise 10.6 release notes ↗help.splunk.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Splunk Enterprise reference hardware for AWS, Azure and Google Cloud ↗ · AWS, Azure, Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
Splunk explicitly states that Splunk Enterprise can be deployed on Amazon Web Services, Microsoft Azure and Google Cloud Platform, including named government, local and distributed variants. Customers must still select supported host specifications and size each deployment for its workload.
- Customer-managed Splunk Enterprise BYOL architecture ↗ · AWS, Azure, Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
Splunk describes customer-managed cloud deployments as BYOL on AWS, Google Cloud or Azure and provides provider-specific SmartStore architecture guidance. This evidence concerns customer-operated Splunk Enterprise, not Splunk Cloud Platform; validate instance, network, object-store and cache requirements for the selected topology.
- Splunk Enterprise reference hardware for AWS, Azure and Google Cloud ↗ · AWS, Azure, Google Cloud
- Infrastructure evidenceChecked
- Licensing evidenceChecked