Add Request Headers step to SentinelOne connection setup

[chi-dd]

What does this PR do? What is the motivation?

Adds a missing step to the Configure SentinelOne HTTP connection setup in the Bits Security Analyst doc.

When creating the SentinelOne HTTP connection, users must configure request headers under Token Auth > Headers before confirming access:

• Authorization: Bearer + the inserted Token Value
• Content-Type: application/json

Without these headers, the connection to the SentinelOne Management Console API fails. This step is inserted between "Add the following information" and "Click Next, Confirm Access".

Merge instructions

Merge readiness:

• Ready for merge

Additional notes

🤖 Generated with Claude Code

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/chi/sentinelone-request-headers/bits_ai/bits_security_analyst

[janine-c]

Thanks so much for submitting this, Chi! I applied some formatting changes to make this play a little more nicely with some limitations we have with that many levels of nesting. This is what it looks like now:

If you're okay with that, feel free to merge when the checks pass! Let me know if you have any questions 🙂

[chi-dd]

Thanks so much for submitting this, Chi! I applied some formatting changes to make this play a little more nicely with some limitations we have with that many levels of nesting. This is what it looks like now:

If you're okay with that, feel free to merge when the checks pass! Let me know if you have any questions 🙂

@janine-c thanks for the improvement. looks good