Regarding Detection Status messages:
Using the word "Blocked" is misleading as it seems to by itself indicate we kept the malware from running. But that is until you learn about "Prevented". I think this article needs a chart that breaks these out like this (better wording of course):
Blocked - Process was running, we stopped it and blocked it from running again.
Prevented - File wasn't able to run because we prevented it.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Thank you @jmmowrer for the feedback! We'll look into this.
Phrasing suggestion:
(Alternate phrasing may be just as useful, feel free to pick and choose.)
@jmmowrer @illfated In my opinion, these 3 options "Blocked, prevented, detected" do not cover the full spectrum of actions that Defender for Endpoint does.
An automated EDR investigation can yield 3 verdicts: Malicious, Suspicious, or No threats found
and can results in one or more of the following remediation actions:
More details here.
In my opinion, it's a matter of semantics in which of the 3 categories (Blocked,Prevented,Detected) you wish to put the above remediation actions (one or more of them).
@e0i Could we ask the author to check if an article update is needed in this case?
Good & fair point. Thank you for weighing in with your views. I agree. There are several important semantic choices to make.
@e0i : Did you close this ticket based on any recent changes or other work being pushed recently by any of the MS Docs team members?
Most helpful comment
Phrasing suggestion:
(Alternate phrasing may be just as useful, feel free to pick and choose.)