Skip to content

[REQUEST]: Add note to endpoint docs clarifying how Defend protection works #1326

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

Open
caitlinbetz opened this issue Apr 30, 2025 · 0 comments
Assignees
Labels
Team:Security Issues owned by the Security Docs Team

Comments

@caitlinbetz
Copy link

Description

We continuously see in support cases where customers have a misunderstanding of how Endpoint solution works vs classic Antivirus program.

Here was a thread about this and a very good answer in my opinion from Joe:
https://elastic.slack.com/archives/CEV9CFY8H/p1745238832190549?thread_ts=1745226563.493329&cid=CEV9CFY8H

Elastic Defend has many layers of protections that work in tandem to detect and eliminate threats. Some layers, like malware protection, operate before execution as soon as a threat is introduced to the file system. However, most layers operate after the threat is launched or executed. This includes malicious behavior protection and memory protection. In a realistic attack scenario where a user clicks on this threat, Elastic Defend would comprehensively detect and stop the attack in its tracks.

We'd like to document this somewhere so that we can refer customers to it. Perhaps as an addition to a page like this:
https://www.elastic.co/docs/solutions/security/configure-elastic-defend/elastic-defend-requirements
or
https://www.elastic.co/docs/solutions/security/configure-elastic-defend/configure-an-integration-policy-for-elastic-defend (where most protections are documented today)

Resources

related thread: https://elastic.slack.com/archives/CEV9CFY8H/p1745226563493329

Which documentation set does this change impact?

Elastic On-Prem and Cloud (all)

Feature differences

N/A

What release is this request related to?

N/A

Collaboration model

Other (please describe below)

Point of contact.

Main contact: @caitlinbetz

Stakeholders:
@111andre111 @joe-desimone

@caitlinbetz caitlinbetz added the Team:Security Issues owned by the Security Docs Team label Apr 30, 2025
@github-actions github-actions bot added needs-team Issues pending triage by the Docs Team and removed needs-team Issues pending triage by the Docs Team labels Apr 30, 2025
@natasha-moore-elastic natasha-moore-elastic self-assigned this May 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Security Issues owned by the Security Docs Team
Projects
None yet
Development

No branches or pull requests

2 participants