Study guide

13.1 Kibana Spaces for SOC Multitenancy & Segmentation

Elastic Certified SIEM Analyst Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Study Strategy

1.1 Elastic Certified SIEM Analyst Exam Facts, Objectives & Study Plan

2 Chapter 2: Elastic Stack Architecture & SIEM Foundations

2.1 Elastic Stack Architecture for Security Operations 2.2 Telemetry Ingestion Architecture & Data Pipelines 2.3 Security Data Storage, Data Streams & ILM

3 Chapter 3: Elastic Common Schema (ECS) & Ingestion Normalization

3.1 ECS Structure, Core Principles & Essential Field Sets 3.2 Ingest Pipelines, Processors & Normalization Workflows 3.3 Fleet Server & Elastic Agent Integration Management

4 Chapter 4: Discover, Data Views & Security Query Languages

4.1 Kibana Discover, Security Data Views & Runtime Fields 4.2 Kibana Query Language (KQL) & Lucene for SecOps 4.3 ES|QL for Multi-Stage Security Analysis

5 Chapter 5: Security Visualizations & Threat Analytics

5.1 Metric, Aggregation & Histogram Visualizations for SOC 5.2 Data Tables, Heatmaps & Specialized Security Charts 5.3 Elastic Maps & Geospatial Telemetry Analysis

6 Chapter 6: Kibana Lens for Security Workflows

6.1 Lens Architecture & Multi-Layer Telemetry Visualizations 6.2 Lens Formulas, Ratios & Anomaly Baseline Metrics 6.3 Operationalizing Lens in SOC Triage & Drilldowns

7 Chapter 7: Security Dashboards & SOC Operations

7.1 Security Dashboard Architecture & SOC Layout Design 7.2 Interactive Controls, Time Sync & Cross-Filtering 7.3 Dashboard Exporting, Reporting & Spaces Sharing

8 Chapter 8: The Elastic Security App: Capabilities, Explore & Dashboards

8.1 Security App Capabilities & the Explore Pages (Hosts, Network, Users) 8.2 Monitoring with the Security App Dashboards

9 Chapter 9: Elastic Security Detection Engine & Core Rules

9.1 Detection Engine Architecture & Prebuilt Rule Management 9.2 Custom Query & Threshold Detection Rules 9.3 Event Correlation Rules with Event Query Language (EQL)

10 Chapter 10: Advanced Detection Rules, ML & Rule Tuning

10.1 Threat Intelligence & Indicator Match Rules 10.2 New Terms, ES|QL & Machine Learning Detection Rules 10.3 Detection Rule Tuning, Exceptions & Alert Suppression

11 Chapter 11: Alert Triage, Timelines & Investigation Workflows

11.1 Alert Triage Workflow & the Alert Details Flyout 11.2 Elastic Security Timeline & Timeline Templates 11.3 Visual Event Analyzer & Session View Forensics

12 Chapter 12: Case Management, Integrations & AI Assistant

12.1 Elastic Security Case Management & Triage Workflows 12.2 Case Connectors & External Incident Escalation 12.3 Elastic AI Assistant for Security & Attack Discovery

13 Chapter 13: Security Administration, RBAC & Kibana Spaces

13.1 Kibana Spaces for SOC Multitenancy & Segmentation 13.2 Role-Based Access Control, Feature Privileges & Index Security 13.3 Elastic Defend Administration & Endpoint Policy Controls

14 Chapter 14: End-to-End Threat Hunting & Incident Investigation Capstone

14.1 Hypothesis-Driven Threat Hunting & Baselining in Elastic 14.2 Investigating Lateral Movement & Credential Access Campaigns 14.3 Data Exfiltration, C2 Detection & Incident Reconstruction

13.1 Kibana Spaces for SOC Multitenancy & Segmentation

Key Takeaways Explain This Topic AI

Kibana Spaces provide presentation-layer logical isolation for Kibana saved objects—including dashboards, Data Views, detection rules, Timelines, Cases, and alert triage views—enabling multi-tenant SecOps segmentation without deploying multiple physical Kibana instances.

Spaces operate strictly at the Kibana object layer and do not enforce Elasticsearch index-level security; true data tenant isolation requires pairing Spaces with Elasticsearch Role-Based Access Control (RBAC), Document-Level Security (DLS), and Field-Level Security (FLS).

Space routing modifies browser URL paths to the pattern /s/{space_id}/app/{app_name} , while the Default Space (ID default , which cannot be deleted) uses /app/{app_name} with no prefix.

Saved objects move between spaces with NDJSON export and import (overwrite or createNewCopies), Share to spaces for shareable types such as data views, or Copy to spaces; detection rules use the Rules page export and import instead.

Detection Engine rules execute on a per-space basis, registering within each space's saved object namespace and generating alerts that are scoped to that space's operational triage queue.

Last updated: September 2026

In enterprise Security Operations Centers (SOCs) and Managed Security Service Provider (MSSP) environments, a single monolithic monitoring interface quickly becomes unmanageable. Tier 1 triage analysts require streamlined, queue-oriented dashboards; threat hunters need exploratory query interfaces and ad-hoc timelines; internal audit and compliance teams require restricted read-only reporting; and MSSPs must maintain strict separation between customer organizations. Kibana Spaces provide the architectural foundation for multi-tenancy and operational segmentation within the Elastic Stack, allowing administrators to partition saved objects, configure customized application navigation, and establish operational boundaries within a single shared Kibana deployment.

1. Presentation-Layer Isolation vs. Elasticsearch Data-Layer Security

A foundational concept tested on the Elastic Certified SIEM Analyst exam is the strict boundary between Kibana Spaces and Elasticsearch Index Security :

Kibana Spaces operate exclusively at the presentation and saved object layer. A space logically segments Kibana saved objects: Dashboards, Visualizations, Canvas workpads, Maps, Data Views (index patterns), Timelines, Timeline Templates, Detection Rules, Alert Views, and Cases. Spaces also control which Kibana applications appear in the navigation menu.

Kibana Spaces do NOT restrict Elasticsearch index access. A user who is granted access to a specific space is not automatically restricted to any specific Elasticsearch index or data stream. If a user's assigned Elasticsearch role grants read privileges on logs-* , that user can execute queries across all matching documents via Discover, Lens, or the Console, regardless of which space they occupy.

True SecOps Multi-Tenancy = Kibana Spaces (Presentation) + Elasticsearch RBAC / DLS / FLS (Data) \text{True SecOps Multi-Tenancy} = \text{Kibana Spaces (Presentation)} + \text{Elasticsearch RBAC / DLS / FLS (Data)} True SecOps Multi-Tenancy = Kibana Spaces (Presentation) + Elasticsearch RBAC / DLS / FLS (Data)

To achieve true, auditable multi-tenancy, administrators must couple Kibana Spaces with Elasticsearch Role-Based Access Control (RBAC), Document-Level Security (DLS) (such as filtering documents by tenant.id or organization.id ), and Field-Level Security (FLS) (redacting sensitive PII or credentials).

2. Space Routing, URL Architecture, and Space Mechanics

Every Kibana space possesses a unique, URL-safe identifier that dynamically prefixes browser routing:

Default Space: The baseline space built into every Elastic Stack deployment has the fixed identifier default . Its URL does not include a space prefix (e.g., https://kibana.internal.net:5601/app/security ). The default space cannot be deleted. Users see only the spaces their roles grant; there is no automatic fallback into the default space.

Custom Spaces: Created by administrators via Stack Management > Spaces or the Spaces REST API. Custom spaces modify the URL path with the /s/<space_id>/ prefix. For example, a dedicated threat hunting space with the identifier threat-hunting routes to https://kibana.internal.net:5601/s/threat-hunting/app/security .

Space Identifiers and Rules

Immutability: The space identifier ( space_id ) is defined upon creation and cannot be modified. It must consist exclusively of lowercase alphanumeric characters, underscores, and hyphens.

Feature Control: When creating or editing a space, administrators can selectively disable entire Kibana applications (e.g., hiding Dev Tools, Machine Learning, or Stack Management). In a dedicated Tier 1 SOC space, disabling Dev Tools and Management declutters the navigation menu, enforces standard triage workflows, and minimizes human error.

Landing Page Customization: Each space can specify a custom initial landing page (e.g., routing directly to /app/security/alerts rather than the default Kibana home page).

3. Saved Object Lifecycles: Export, Import, and Conflict Resolution

SecOps workflows frequently require migrating detection rules, custom dashboards, and Data Views between development, staging, and production environments, or between tenant spaces. This is managed through the Saved Objects management interface or the Saved Objects API.

Exporting Saved Objects

Dashboards, visualizations, data views and other saved objects are exported as newline-delimited JSON ( .ndjson ) files via Stack Management > Saved Objects or the Saved Objects API: POST /s/soc-staging/api/saved_objects/_export

Content-Type: application/json

  • {
  • "type": ["dashboard", "visualization", "index-pattern"],
  • "includeReferencesDeep": true
  • }

The includeReferencesDeep: true flag guarantees that all dependent objects—such as the data views and visualizations referenced by dashboard panels—are recursively packaged into the NDJSON payload.

Detection rules are handled separately. Export and import them from the Security app's Rules page (or the Detection Engine _export and _import APIs). Rule exports include the rules' exceptions, and imports match existing rules by rule_id . The import dialog offers Overwrite existing detection rules with conflicting "rule_id" and Overwrite existing exception lists (the overwrite and overwrite_exceptions API parameters). Importing rules with actions also needs Actions and Connectors privileges.

Importing Saved Objects and Conflict Resolution

When importing saved objects into a destination space ( POST /s/<space_id>/api/saved_objects/_import ), existing objects may share the same internal UUID. Administrators must select an explicit conflict resolution strategy:

overwrite: true : Overwrites any existing saved object in the target space that has a matching ID. This is standard when pushing updated rule definitions or dashboard revisions from a staging space into production.

createNewCopies: true : Generates brand-new UUIDs for colliding objects, preserving both the original object and the imported copy. References between imported objects are automatically updated to target the newly generated UUIDs.

Fail on Conflict (Default): Halts the import process and reports colliding objects, allowing the engineer to resolve conflicts on an individual object basis.

Cross-Space Saved Object Sharing

Rather than maintaining duplicate copies across spaces, Kibana supports Share to spaces for shareable saved-object types, such as data views. A shared object keeps one ID, and changes made in one space appear in every space it is shared with. Not every type is shareable. For those that are not, Copy to spaces creates an independent copy in the target space.

4. Detection Engine Rules and Alert Scoping Across Spaces

In Elastic Security, the Detection Engine operates within the scope of the active Kibana space:

Space-Scoped Rules: Detection rules are Kibana saved objects that belong to the space in which they were created. Staging spaces can test experimental EQL or threshold rules without executing them against production triage queues.

Prebuilt Rule Installation: When an administrator enables Elastic prebuilt detection rules, they are installed into the currently active space . Installing prebuilt rules in /s/soc-triage/ does not automatically activate them in /s/client-alpha/ .

Alert Segregation: When a detection rule fires, the resulting alert document records the space ID in which the rule executed. In the Elastic Security Alerts table ( /s/<space_id>/app/security/alerts ), analysts only observe alerts generated within that specific space. Cross-space alert aggregation requires building an executive dashboard in a parent space that queries the underlying .alerts-security.alerts* indices directly.

Timelines and Cases: Like detection rules, Cases and Timelines are partitioned by space. An insider-threat investigation initiated in a restricted /s/executive-investigations/ space remains completely invisible to analysts working in the standard /s/soc-triage/ space.

5. Architectural Comparison: Single-Space vs. Multi-Space SOC Models

Architectural Dimension Single-Space SOC Architecture Multi-Space SOC Architecture

Presentation Governance Monolithic; all analysts and auditors share identical dashboard and case listings. Granular; tailored UI, application visibility, and saved objects per operational team.

Saved Object Isolation Zero isolation; high risk of naming collisions, accidental overwrites, and clutter. Strict logical isolation; changes in experimental spaces do not impact production assets.

Detection Rule Operations All rules execute in a single shared engine; staging rules fire into production queues. Rules are partitioned by space; development, canary testing, and production are isolated.

Alert Triage Boundaries Single unified alert queue; requires complex manual KQL filters to segment workflows. Native alert queue filtering; analysts only see alerts relevant to their operational domain.

Administrative Overhead Minimal initial setup; high ongoing overhead managing tag hygiene and permissions. Moderate initial configuration; low ongoing maintenance and clear role boundaries.

Collaboration Model High accidental overlap; cases and timelines easily visible to unauthorized tiers. Secure delegation; sensitive cases kept in restricted spaces, common views shared via object sharing.

Loading diagram... Multi-Tenant SOC Architecture with Kibana Spaces and Index Segregation