[REQUEST]: Update Agentless Integrations doc with latest supported integrations

[smriti0321]

Description

We will extend the support for Agentless (public beta) for following integrations:

1. Okta
2. SentinelOne
3. CrowdStrike
4. AbuseCH
5. Microsoft 365 Defender
6. Microsoft Defender for Endpoint
7. Google Security Command Center
8. Zscaler ZIA
9. Google Workspace
10. Tenable IO
11. Wiz
12. Qualys VMDR
13. Microsoft Sentinel
14. Google SecOps

We should update the following doc with this list and call out public beta support. And CSPM agentless will be GA.

https://www.elastic.co/guide/en/security/current/agentless-integrations.html

Resources

https://www.elastic.co/guide/en/security/current/agentless-integrations.html

Latest list of integarions can be found here- https://docs.google.com/spreadsheets/d/1zdsaE3WKzKCbdmY3ibXK2gAT6RTssmpItJpy9zB1KFc/edit?gid=1385062052#gid=1385062052

Which documentation set does this change impact?

Elastic Cloud (Hosted and Serverless) only

Feature differences

NA

What release is this request related to?

8.18

Collaboration model

The documentation team

Point of contact.

Main contact: @benironside

Stakeholders: @smriti0321 @qcorporation

[kpollich]

@lucabelluccini - I want to summarize your specific ask here to make sure I understand.

You suggested that we should have some field here in the docs that explains the level of support for different deployment modes, right?

e.g. we'd have some section along the lines of

Supported deployment modes
- Agent-based: Generally available
- Agentless (learn more): Beta

If we want to update the package manifests to have this information it'd require a new version the package spec to be generated and a new version of every integration to be published that makes use of the new fields. That would be the only way we can update both the integration docs content and the docs that appear within Kibana at the same time, but it would be the most correct thing to do.

As a stop gap, we could update this data by hardcoding into the public docs directly for now.

Right now, each agentless integration includes a rather prominent notice at the top of its README indicating its support for agentless and the beta status of agentless deployment. Is this sufficient to meet support's needs here or do we need the actual "support matrix" content above with certainty here?

[lucabelluccini]

Hello @kpollich

I think that the stop-gap solution to hardcode it in the integration docs is fine as from customer side will be there. The wording used should be the typical one of Beta (not subject to SLA and breaking changes can happen).

If the fact of having it in the package spec is also valuable for the future plans of agentless, it would be nice to have a follow up item to have it as a manifest entry.