Skip to content

Commit c24626c

Browse files
Update solutions/security/get-started/get-started-endpoint-security.md
Co-authored-by: natasha-moore-elastic <[email protected]>
1 parent 1db831d commit c24626c

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

solutions/security/get-started/get-started-endpoint-security.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -101,9 +101,9 @@ Here are some other features {{elastic-sec}} provides to help manage host config
101101

102102
* [Endpoint response actions](/solutions/security/endpoint-response-actions.md): Perform response actions on an endpoint using a terminal-like interface. For example, isolating or releasing a host, getting a list of processes, or suspending a running process.
103103

104-
:::{tip}
105-
You can also automate some responses when an event meets the rule's criteria. Refer to [Automated response actions](/solutions/security/endpoint-response-actions/automated-response-actions.md) for more information.
106-
:::
104+
:::{tip}
105+
You can also automate some responses when an event meets the rule's criteria. Refer to [Automated response actions](/solutions/security/endpoint-response-actions/automated-response-actions.md) for more information.
106+
:::
107107

108108
* [Trusted applications](/solutions/security/manage-elastic-defend/trusted-applications.md): Add Windows, macOS, and Linux applications that should be trusted so that {{elastic-defend}} doesn't monitor them.
109109
* [Blocklist](/solutions/security/manage-elastic-defend/blocklist.md): Prevent specified applications from running on hosts to extend the list of processes that {{elastic-defend}} considers malicious. This adds an extra layer of protection by ensuring that known malicious processes aren’t accidentally executed by end users.

0 commit comments

Comments
 (0)