[SEC-31445] severity modifiers doc

[BusyBeaver-42]

What does this PR do? What is the motivation?

A new type of automation pipelines is being added (see the RFC). This PR adds the relevant documentation.

Merge instructions

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

Used for generating a first draft, proof-reading and phrasing improvements.

Additional notes

[github-actions]

Preview links (active after the build_preview check completes)

New or renamed files

• https://docs-staging.datadoghq.com/romain.ageron/add-doc-for-severity-modifiers/security/automation_pipelines/modify_severity

Modified Files

• https://docs-staging.datadoghq.com/romain.ageron/add-doc-for-severity-modifiers/security/automation_pipelines/

[rtrieu]

Created DOCS-14617 for docs review.

[hugoqnc]

Overall looks good! One thing missing is a header for your page in the table of contents on the left:

You can add it by updating config/_default/menus/main.en.yaml (example PR)

[janine-c]

Looks great! I just have a few really minor wording suggestions. If you need help applying any other edits, like modifying the main.en.yaml file Hugo mentioned, just let me know!

[janine-c]

Looks great! Just a couple of small writing edits here. Happy to give the final stamp once the screenshots are ready!

[janine-c]

Suggested change

	- link: "/security/automation_pipelines/mute"
	tag: "Documentation"
	text: "Mute Rules"
	- link: "/security/automation_pipelines/security_inbox"
	tag: "Documentation"
	text: "Add to Security Inbox Rules"
	- link: "/security/automation_pipelines/set_due_date"
	tag: "Documentation"
	text: "Set Due Date Rules"
	- link: "/security/automation_pipelines/create_ticket"
	tag: "Documentation"
	text: "Ticket Creation Rules"
	- link: "/security/automation_pipelines/modify_severity"
	tag: "Documentation"
	text: "Severity Modifier Rules"

I noticed that these links are otherwise in the same order that they appear in the sidebar, so I thought I would apply that here too for parallelism's sake. We could also consider moving the position in the sidebar, if you'd rather this new page appear higher in all these other places, of course; I just care about them matching so these links are easier to navigate.

[BusyBeaver-42]

Thanks for catching the ordering inconsistencies. I've reordered these, but kept Severity Modifiers first rather than moving it to match the old sidebar order.

Reason: these automation rules types are executed in order (severity modifiers -> mute -> due date -> inbox -> ticketing), and the UI already lists them in that execution order.

So I reordered the sidebar/menu instead to match the pipeline order, rather than reordering _index.md to match a sidebar order that was really just chronological-by-ship-date.

Dismissing review while todos are still visible on the page, but on deck for re-review when they're replaced with screenshots 🙂