Documents new D4C capabilities

[benironside]

Fixes elastic/docs-content-internal/issues/536

The Defend for Containers integration will be available in 9.3+. This PR adds several new pages to document the 9.3+ functionality.

Docs team reviewers, a couple areas to focus on, please:

• Make sure terminology and support levels are consistent. The feature is called Cloud Workload Protection for Kubernetes, but the integration that implements that feature is called Defend for Containers. This is admittedly confusing — most of the docs I am trying to stick to just referring to D4C (the nuts and bolts thing-that-exists-in-Kibana), but let me know if that needs clarification anywhere.
• Do you have any remaining conceptual questions after your review? Anything you're confused about?
• I would prefer not to do a deep copy edit, but of course if you see issues please point them out. Most of the content was pulled from the 8.x docs.

@mjwolf, thanks for creating this issue and providing a bunch of helpful info. Please just review for technical accuracy.

Generative AI disclosure

1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?

• Yes
• No

[github-actions]

Vale Linting Results

Summary: 7 suggestions found

💡 Suggestions (7)

File	Line	Rule	Message
solutions/security/cloud/_snippets/kubernetes-dashboard.md	5	Elastic.Versions	Use 'or later' instead of 'or higher' when referring to versions.
solutions/security/cloud/d4c/d4c-overview.md	53	Elastic.FutureTense	'will result' might be in future tense. Write in the present tense to describe the state of the product as it is now.
solutions/security/cloud/d4c/d4c-policies.md	35	Elastic.FutureTense	'will select' might be in future tense. Write in the present tense to describe the state of the product as it is now.
solutions/security/cloud/d4c/d4c-policies.md	66	Elastic.Wordiness	Consider using 'to' instead of 'In order to'.
solutions/security/cloud/d4c/d4c-policies.md	80	Elastic.FutureTense	'will only' might be in future tense. Write in the present tense to describe the state of the product as it is now.
solutions/security/cloud/d4c/get-started-with-d4c.md	17	Elastic.Versions	Use 'or later' instead of 'or higher' when referring to versions.
solutions/security/cloud/d4c/get-started-with-d4c.md	18	Elastic.Versions	Use 'or later' instead of 'or higher' when referring to versions.

---

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

[github-actions]

🔍 Preview links for changed docs

• solutions/security/cloud/d4c/d4c-overview.md
• solutions/security/cloud/d4c/d4c-policies.md
• solutions/security/cloud/d4c/get-started-with-d4c.md
• solutions/security/cloud/d4c/kubernetes-dashboard.md
• solutions/security/dashboards/kubernetes-dashboard.md
• solutions/security/cloud.md
• solutions/security/get-started/elastic-security-ui.md
• solutions/security/investigate/session-view.md

[bmorelli25]

@natasha-moore-elastic can you please review this

[nastasha-solomon]

Overall, it looks great! I left some suggestions on organization, terminology, and structure. Feel free to take what you like and discard the rest!

[natasha-moore-elastic]

Left a few suggestions, but looks good otherwise!