[Security Solution] Update SentinelOne integration README with info. on configuring response actions

[paul-tavares]

Proposed commit message

• Adds information to the SentinelOne (S1) integration README file about the ability for sending Response Actions to S1 hosts
  • Changes goes along with Feature being implemented in Security Solution that supports sending isolate and release response actions.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

Author's Checklist

• none

How to test this PR locally

• Start the stack using --version=8.12.0-SNAPSHOT:

elastic-package stack up -v -d --version=8.12.0-SNAPSHOT

• Navigate to the SentinelOne integration page
  • Note that the version at the top is 1.20.0
  • Note the updated integration description that includes a link to Documentation
• Click the documentation link
  • You will (until v8.12.0 is GA'd) received a 404 "Page not found". This is expected since v8.12 has not yet been released. The page is accessible however by changing the /current/ in the URL with /master/:

Related issues

• none

Screenshots

[paul-tavares]

Am I doing this right? or should this be 1.20.0-next?

[kush-elastic]

It should be 1.20.0 only. the current change is correct.

[ebeahan]

Since we're only updating docs, maybe we do a patch release for 1.19.1 instead of a new minor?

[paul-tavares]

🤷
hi @ebeahan - I'm not sure if that is the best way - this is the my first time making such changes. If you believe that is best I can change it. Please let me know

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-11-29T18:30:22.522+0000

• Duration: 21 min 7 sec

Test stats 🧪

Test	Results
Failed	0
Passed	31
Skipped	0
Total	31

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[paul-tavares]

/test

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (5/5)	💚
Files	100.0% (5/5)	💚
Classes	100.0% (5/5)	💚
Methods	100.0% (71/71)	💚 75.0
Lines	96.387% (3175/3294)	👎 -3.613
Conditionals	100.0% (0/0)	💚

[efd6]

I think it would be worth waiting until 8.12 is released before this change is made.

[paul-tavares]

Hi @efd6 - thanks for the quick feedback. I'll follow up with our team to see if that is ok. I'm thinking its fine given the nature of the change I'm introducing.

[mrodm]

Hi @paul-tavares, please update your branch with the latest contents from main branch. There was an important PR merged updating the CI pipelines. Thanks!

[elasticmachine]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[paul-tavares]

Taking this out of draft as we are approaching the GA for v8.12.0.

[joepeeples]

New content LGTM, and I added some extra edits in 74b731e which have already been incorporated. Thanks!

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 7cd0c59

cc @paul-tavares

[elasticmachine]

Package sentinel_one - 1.19.1 containing this change is available at https://epr.elastic.co/search?package=sentinel_one