Docs fix — frontmatter: path /solutions/security/ai — 14 pages

Generated by `gh-aw-docs-frontmatter-sweep` for `elastic/docs-content` on 2026-W25.

Path /solutions/security/ai · 18 total in scope · subtree corpus 18 pages.

## Findings (16)

```yaml
- file: solutions/security/ai/ai-assistant-knowledge-base.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Configure and add content to AI Assistant Knowledge Base to provide context that improves AI Assistant response quality in Elastic Security."

- file: solutions/security/ai/ai-assistant.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Elastic AI Assistant for Security provides a chat interface for alert investigation, incident response, query generation, and contextual insights within Elastic Security."

- file: solutions/security/ai/attack-discovery.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Attack Discovery uses large language models to analyze alerts, identify related threats, and surface connections between alerts, users, hosts, and MITRE ATT&CK techniques."

- file: solutions/security/ai/ease/ease-alerts.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "View, track, and analyze ingested alerts from the Alert summary page in Elastic AI SOC Engine."

- file: solutions/security/ai/ease/ease-intro.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Elastic AI SOC Engine (EASE) is a serverless project type providing AI-powered tools to augment existing SIEM and EDR platforms, deployable in minutes using agentless integrations."

- file: solutions/security/ai/ease/ease-upgrade.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Upgrade an Elastic AI SOC Engine serverless project to the Security Analytics Essentials or Security Analytics Complete feature tiers for a full set of SOC capabilities."

- file: solutions/security/ai/ease/ease-value-report.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Review the Value report to measure AI-powered SOC performance and efficiency metrics in Elastic Security and Elastic AI SOC Engine."

- file: solutions/security/ai/generate-customize-learn-about-esorql-queries.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Use AI Assistant to generate, customize, troubleshoot, and learn about ES|QL queries for Elastic Security investigations."

- file: solutions/security/ai/identify-investigate-document-threats.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Step-by-step tutorial for using Attack Discovery and AI Assistant together to identify threats, investigate incidents, and generate incident reports."

- file: solutions/security/ai/large-language-model-performance-matrix.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Performance matrix comparing large language models across Elastic Security AI chat and AI-powered feature use cases, based on internal test results."

- file: solutions/security/ai/triage-alerts.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Use AI Assistant to assess multiple alerts in Elastic Security, interpret alert context, and get actionable recommendations for alert triage."

- file: solutions/security/ai/use-cases.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Guides describing example workflows for AI Assistant and Attack Discovery in Elastic Security, covering alert triage, threat investigation, and ES|QL query generation."

- file: solutions/security/ai/usecase-knowledge-base-walkthrough.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Step-by-step tutorial for ingesting data from various sources into AI Assistant Knowledge Base and using it to improve incident response quality."

- file: solutions/security/ai/agent-builder/agent-builder.md
line: 9
category: weak-description
severity: medium
evidence: "description opens with 'Learn how', a generic teaching phrase; not action-oriented or value-focused"
suggested_fix: |
description: "Elastic Agent Builder provides a natural language chat interface with built-in agents, tools, and support for custom agents to automate Elastic Security workflows."

- file: solutions/security/ai/large-language-model-performance-matrix.md
line: 1
category: missing-navigation-title
severity: medium
evidence: "H1 'Large language model performance matrix for Elastic Security' is ~58 characters with no navigation_title set"
suggested_fix: |
navigation_title: LLM performance matrix

- file: solutions/security/ai/usecase-knowledge-base-walkthrough.md
line: 1
category: missing-navigation-title
severity: medium
evidence: "H1 'Use AI Assistant's Knowledge Base to improve response quality' is 59 characters with no navigation_title set"
suggested_fix: |
navigation_title: Knowledge Base walkthrough
```

## Done when
- All listed pages have a non-empty, <=200-character `description` field and required frontmatter keys present per the repo's frontmatter schema.
- A PR addressing this issue is merged.

## Notes
- `ease-value-report.md` description suggestion is based on partial content (page body is an include snippet); verify accuracy before committing.

> Generated by [Docs frontmatter sweep agent](https://github.com/elastic/docs-content/actions/runs/27855796529) · 196.3 AIC · ⌖ 13.5 AIC · ⊞ 27K · [◷](https://github.com/search?q=repo%3Aelastic%2Fdocs-content+is%3Aissue+%22gh-aw-workflow-call-id%3A+elastic%2Fdocs-content%2Fgh-aw-docs-frontmatter-sweep%22&type=issues)

Start by reading the repository's frontmatter schema, then inspect the 14 listed Markdown files under solutions/security/ai and verify the suggested descriptions against each page, especially ease-value-report.md. Add the required non-empty descriptions and navigation titles, keeping descriptions within 200 characters; done means all listed pages satisfy the schema and a PR is merged.

Written by the indexing model from the issue text.