Skip to content

Bits AI Security Analyst docs#35322

Merged
janine-c merged 7 commits intomasterfrom
janine/docs-13713-bits-ai-sec-analyst
Mar 19, 2026
Merged

Bits AI Security Analyst docs#35322
janine-c merged 7 commits intomasterfrom
janine/docs-13713-bits-ai-sec-analyst

Conversation

@janine-c
Copy link
Copy Markdown
Contributor

@janine-c janine-c commented Mar 17, 2026

What does this PR do? What is the motivation?

New documentation for Bits AI Security Analyst.

Merge instructions

Please hold off on merging until I have approval from the PM. Thanks! Got approval over Slack; this can go out anytime!

Merge readiness:

  • Ready for merge

For Datadog employees:

Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.

AI assistance

Additional notes

@janine-c janine-c requested a review from a team as a code owner March 17, 2026 01:06
@github-actions github-actions Bot added Architecture Everything related to the Doc backend Images Images are added/removed with this PR labels Mar 17, 2026
@github-actions
Copy link
Copy Markdown
Contributor

Comment thread content/en/bits_ai/bits_ai_security_analyst.md
@iadjivon iadjivon added the editorial review Waiting on a more in-depth review label Mar 17, 2026
@iadjivon
Copy link
Copy Markdown
Contributor

Added an Editorial Review card: DOCS-13727

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 556cb7b75b

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".


### Key capabilities

Bits AI Security Analyst investigations are autonomous. If a detection rule is enabled, Bits AI autonomously investigates signals associated with it.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Qualify that only eligible rules are auto-investigated

This overview sentence says any enabled detection rule is investigated, but the setup section below narrows that to eligible rules above the configured severity and notes that some custom rules are not eligible (content/en/bits_ai/bits_ai_security_analyst.md:68-75). Readers who enable a low-severity rule, apply a query filter, or use an ineligible custom rule will expect Bits AI to run and will interpret the missing investigation as a product failure.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can't enable an ineligible rule.


Bits AI Security Analyst investigations are autonomous. If a detection rule is enabled, Bits AI autonomously investigates signals associated with it.

In the [Cloud SIEM Signals Explorer][5], you can click the **Bits AI Security Analyst** tab to only show signals that Bits AI investigated. In the Severity column, a Bits AI status displays as Investigating, Benign, or Suspicious.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use the actual Signals Explorer state labels

This line documents the list view as showing Investigating, Benign, or Suspicious in the Severity column, but the screenshot added in the same commit shows an Investigated badge alongside the verdict badges. As written, the page tells users to look for a state that the UI does not display, making the instructions inconsistent with the screenshot and harder to follow during triage.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor

@rtrieu rtrieu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

overall a solid PR! left a few suggestions and questions for your consideration.

Comment thread content/en/bits_ai/bits_ai_security_analyst.md Outdated
Comment thread content/en/bits_ai/bits_ai_security_analyst.md Outdated
Comment thread content/en/bits_ai/bits_ai_security_analyst.md Outdated
Comment thread content/en/bits_ai/bits_ai_security_analyst.md Outdated
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3cebdc94fe

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".


Bits AI Security Analyst investigations are autonomous. If a detection rule is enabled, Bits AI autonomously investigates signals associated with it.

In the [Cloud SIEM Signals Explorer][5], you can click the **Bits AI Security Analyst** tab to only show signals that Bits AI investigated. In the Severity column, a Bits AI status displays as Investigating, Benign, or Suspicious.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Document the Inconclusive investigation outcome

The linked launch blog for this feature (updated December 18, 2025) still describes three Bits AI conclusions: benign, suspicious, and inconclusive. This sentence only documents the benign/suspicious outcomes, so when an investigated signal comes back inconclusive, readers have no matching explanation here and will likely assume the UI is inconsistent or the investigation failed.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this blog post is outdated and will be updated Monday. We no longer have an inconclusive status.

Statuses will be updated in the future and we'll update docs accordingly.

Comment on lines +43 to +47
Bits AI can run investigations on the following Security log sources:
- AWS CloudTrail
- Azure
- GCP
- Kubernetes
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Limit supported sources to the integrations Datadog documents

This section currently presents Kubernetes, Microsoft Entra ID, Snowflake, SentinelOne, and Email phishing as supported sources, but the linked Bits AI Security Analyst blog (updated December 18, 2025) still scopes its domain expertise to AWS CloudTrail, Google Cloud, Azure, Google Workspace, M365, Okta, and GitHub. Customers will enable the feature on these extra source types and expect autonomous investigations that the current product docs do not promise.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blog post will be updated on Monday.

Copy link
Copy Markdown
Contributor

@rtrieu rtrieu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

love it!

@janine-c janine-c merged commit e6d0e20 into master Mar 19, 2026
19 of 20 checks passed
@janine-c janine-c deleted the janine/docs-13713-bits-ai-sec-analyst branch March 19, 2026 17:57
genesor pushed a commit that referenced this pull request Apr 19, 2026
* Bits AI Security Analyst docs

* Make explorer screenshot more readable

* Apply edits

* Apply Rosa's edits

* Update status wording

* Add details on eligibility
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Architecture Everything related to the Doc backend editorial review Waiting on a more in-depth review Images Images are added/removed with this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants