-
Notifications
You must be signed in to change notification settings - Fork 195
[Security] Memory dump response action - Windows #4511
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
✅ Vale Linting ResultsNo issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
🔍 Preview links for changed docs |
florent-leborgne
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM from a docs / consistency standpoint
|
|
||
| ### `memory-dump` [memory-dump] | ||
| ```yaml {applies_to} | ||
| stack: ga 9.3+ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🫶
Summary
Resolves #4028 by documenting the new
memory-dumpresponse action for Windows endpoints.Note
Do not merge before 9.3 is released. This feature is currently behind a feature flag and requires a new version of Elastic Defend, so it will only be released into serverless after 9.3 is GA.
Preview
Endpoint response actions >
memory-dumpGenerative AI disclosure
Tool(s) and model(s) used:
Cursor, gemini-3-flash