Skip to content

Commit 6174fbf

Browse files
natasha-moore-elasticmergify[bot]
natasha-moore-elastic
authored and
mergify[bot]
committed
[Serverless bug bash] Removes outdated content (#6188)
(cherry picked from commit 6247f6c) # Conflicts: # docs/serverless/edr-install-config/configure-endpoint-integration-policy.asciidoc
1 parent 16d772c commit 6174fbf

File tree

2 files changed

+285
-2
lines changed

2 files changed

+285
-2
lines changed

‎docs/getting-started/configure-integration-policy.asciidoc‎

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -207,8 +207,7 @@ image::images/install-endpoint/event-collection.png[Detail of event collection s
207207
[[register-as-antivirus]]
208208
== Register {elastic-sec} as antivirus (optional)
209209

210-
With {elastic-defend} version 7.10 or later on Windows 7 or later, you can
211-
register {elastic-sec} as your hosts' antivirus software by enabling **Register as antivirus**.
210+
You can register {elastic-sec} as your hosts' antivirus software by enabling **Register as antivirus**.
212211

213212
NOTE: Windows Server versions are not supported. Antivirus registration requires Windows Security Center, which is not included in Windows Server operating systems.
214213

‎docs/serverless/edr-install-config/configure-endpoint-integration-policy.asciidoc‎

Lines changed: 284 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,284 @@
1+
[[security-configure-endpoint-integration-policy]]
2+
= Configure an integration policy for {elastic-defend}
3+
4+
// :description: Configure settings on an {elastic-defend} integration policy.
5+
// :keywords: serverless, security, how-to
6+
7+
8+
After the {agent} is installed with the {elastic-defend} integration, several protections features — including
9+
preventions against malware, ransomware, memory threats, and malicious behavior — are automatically enabled
10+
on protected hosts (most features require the Endpoint Protection Essentials or Endpoint Protection Complete <<elasticsearch-manage-project,project feature>>). If needed, you can update the
11+
integration policy to configure protection settings, event collection, antivirus settings, trusted applications,
12+
event filters, host isolation exceptions, and blocked applications to meet your organization's security needs.
13+
14+
You can also create multiple {elastic-defend} integration policies to maintain unique configuration profiles. To create an additional {elastic-defend} integration policy, go to **Project settings** → **Integrations**, then follow the steps for <<add-security-integration,adding the {elastic-defend} integration>>.
15+
16+
.Requirements
17+
[NOTE]
18+
====
19+
You must have the appropriate user role to configure an integration policy.
20+
====
21+
22+
////
23+
/* Commented out because APIs are not exposed in initial serverless release. We can uncommment this and add a link to API docs once APIs are available.
24+
<DocCallOut title="Tip">
25+
In addition to configuring an {elastic-defend} policy through the {elastic-sec} UI, you can create and customize an {elastic-defend} policy through the API.
26+
</DocCallOut>
27+
*/
28+
////
29+
30+
To configure an integration policy:
31+
32+
. Go to **Assets** → **Endpoints** → **Policies** to view the **Policies** page.
33+
. Select the integration policy you want to configure. The integration policy configuration page appears.
34+
. On the **Policy settings** tab, review and configure the following settings as appropriate:
35+
+
36+
** <<malware-protection,Malware protection>>
37+
** <<ransomware-protection,Ransomware protection>>
38+
** <<memory-protection,Memory threat protection>>
39+
** <<behavior-protection,Malicious behavior protection>>
40+
** <<attack-surface-reduction,Attack surface reduction>>
41+
** <<event-collection,Event collection>>
42+
** <<register-as-antivirus,Register {elastic-sec} as antivirus (optional)>>
43+
** <<adv-policy-settings,Advanced policy settings (optional)>>
44+
** <<save-policy,Save the general policy settings>>
45+
. Click the **Trusted applications**, **Event filters**, **Host isolation exceptions**, and **Blocklist** tabs to review the endpoint policy artifacts assigned to this integration policy (for more information, refer to <<security-trusted-applications,trusted applications>>, <<security-event-filters,event filters>>, <<security-host-isolation-exceptions,host isolation exceptions>>, and <<security-blocklist,blocklist>>). On these tabs, you can:
46+
+
47+
** Expand and view an artifact — Click the arrow next to its name.
48+
** View an artifact's details — Click the actions menu (image:images/icons/boxesHorizontal.svg[Actions menu]), then select **View full details**.
49+
** Unassign an artifact — Click the actions menu (image:images/icons/boxesHorizontal.svg[Actions menu]),
50+
then select **Remove from policy**. This does not delete the artifact; this just unassigns it from the current policy.
51+
** Assign an existing artifact — Click **Assign _x_ to policy**,
52+
then select an item from the flyout. This view lists any existing artifacts that aren't already assigned to the current policy.
53+
+
54+
[NOTE]
55+
====
56+
You can't create a new endpoint policy artifact while configuring an integration policy.
57+
To create a new artifact, go to its main page in the {security-app} (for example,
58+
to create a new trusted application, go to **Assets** → **Endpoints** → **Trusted applications**).
59+
====
60+
. Click the **Protection updates** tab to configure how {elastic-defend} receives updates from Elastic with the latest threat detections, malware models, and other protection artifacts. Refer to <<security-protection-artifact-control>> for more information.
61+
62+
[discrete]
63+
[[malware-protection]]
64+
== Malware protection
65+
66+
{elastic-defend} malware prevention detects and stops malicious attacks by using a <<machine-learning-model,machine learning model>>
67+
that looks for static attributes to determine if a file is malicious or benign.
68+
69+
By default, malware protection is enabled on Windows, macOS, and Linux hosts.
70+
To disable malware protection, turn off the **Malware protections** toggle.
71+
72+
.Requirements
73+
[NOTE]
74+
====
75+
Malware protection requires the Endpoint Protection Essentials <<elasticsearch-manage-project,project feature>>.
76+
====
77+
78+
Malware protection levels are:
79+
80+
* **Detect**: Detects malware on the host and generates an alert. The agent will **not** block malware.
81+
You must pay attention to and analyze any malware alerts that are generated.
82+
* **Prevent** (Default): Detects malware on the host, blocks it from executing, and generates an alert.
83+
84+
These additional options are available for malware protection:
85+
86+
* **Blocklist**: Enable or disable the <<security-blocklist,blocklist>> for all hosts associated with this {elastic-defend} policy. The blocklist allows you to prevent specified applications from running on hosts, extending the list of processes that {elastic-defend} considers malicious.
87+
* **Scan files upon modification**: By default, {elastic-defend} scans files every time they're modified, which can be resource-intensive on hosts where files are frequently modified, such as servers and developer machines. Turn off this option to only scan files when they're executed. {elastic-defend} will continue to identify malware as it attempts to run, providing a robust level of protection while improving endpoint performance.
88+
89+
Select **Notify user** to send a push notification in the host operating system when activity is detected or prevented. Notifications are enabled by default for the **Prevent** option.
90+
91+
[TIP]
92+
====
93+
Endpoint Protection Complete customers can customize these notifications using the `Elastic Security {action} {filename}` syntax.
94+
====
95+
96+
[role="screenshot"]
97+
image::images/configure-endpoint-integration-policy/-getting-started-install-endpoint-malware-protection.png[Detail of malware protection section.]
98+
99+
[discrete]
100+
[[manage-quarantined-files]]
101+
=== Manage quarantined files
102+
103+
When **Prevent** is enabled for malware protection, {elastic-defend} will quarantine any malicious file it finds (this includes files defined in the <<security-blocklist,blocklist>>). Specifically {elastic-defend} will remove the file from its current location, encrypt it with the encryption key `ELASTIC`, move it to a different folder, and rename it as a GUID string, such as `318e70c2-af9b-4c3a-939d-11410b9a112c`.
104+
105+
The quarantine folder location varies by operating system:
106+
107+
* macOS: `/System/Volumes/Data/.equarantine`
108+
* Linux: `.equarantine` at the root of the mount point of the file being quarantined
109+
* Windows - {elastic-defend} versions 8.5 and later: `[DriveLetter:].equarantine`, unless the files are from the `C:` drive. These files are moved to `C:\Program Files\Elastic\Endpoint\state.equarantine`.
110+
* Windows - {elastic-defend} versions 8.4 and earlier: `[DriveLetter:].equarantine`, for any drive
111+
112+
To restore a quarantined file to its original state and location, <<security-add-exceptions,add an exception>> to the rule that identified the file as malicious. If the exception would've stopped the rule from identifying the file as malicious, {elastic-defend} restores the file.
113+
114+
You can access a quarantined file by using the `get-file` <<response-action-commands,response action command>> in the response console. To do this, copy the path from the alert's **Quarantined file path** field (`file.Ext.quarantine_path`), which appears under **Highlighted fields** in the alert details flyout. Then paste the value into the `--path` parameter. This action doesn't restore the file to its original location, so you will need to do this manually.
115+
116+
[NOTE]
117+
====
118+
Response actions and the response console UI are Endpoint Protection Complete <<elasticsearch-manage-project,project features>>.
119+
====
120+
121+
[discrete]
122+
[[ransomware-protection]]
123+
== Ransomware protection
124+
125+
Behavioral ransomware prevention detects and stops ransomware attacks on Windows systems by
126+
analyzing data from low-level system processes. It is effective across an array of widespread
127+
ransomware families — including those targeting the system’s master boot record.
128+
129+
.Requirements
130+
[NOTE]
131+
====
132+
Ransomware protection requires the Endpoint Protection Essentials <<elasticsearch-manage-project,project feature>>.
133+
====
134+
135+
Ransomware protection levels are:
136+
137+
* **Detect**: Detects ransomware on the host and generates an alert. {elastic-defend}
138+
will **not** block ransomware. You must pay attention to and analyze any ransomware alerts that are generated.
139+
* **Prevent** (Default): Detects ransomware on the host, blocks it from executing,
140+
and generates an alert.
141+
142+
When ransomware protection is enabled, canary files placed in targeted locations on your hosts provide an early warning system for potential ransomware activity. When a canary file is modified, Elastic Defend immediately generates a ransomware alert. If **prevent** ransomware is active, {elastic-defend} terminates the process that modified the file.
143+
144+
Select **Notify user** to send a push notification in the host operating system when activity is detected or prevented. Notifications are enabled by default for the **Prevent** option.
145+
146+
[TIP]
147+
====
148+
Endpoint Protection Complete customers can customize these notifications using the `Elastic Security {action} {filename}` syntax.
149+
====
150+
151+
[role="screenshot"]
152+
image::images/configure-endpoint-integration-policy/-getting-started-install-endpoint-ransomware-protection.png[Detail of ransomware protection section.]
153+
154+
[discrete]
155+
[[memory-protection]]
156+
== Memory threat protection
157+
158+
Memory threat protection detects and stops in-memory threats, such as shellcode injection,
159+
which are used to evade traditional file-based detection techniques.
160+
161+
.Requirements
162+
[NOTE]
163+
====
164+
Memory threat protection requires the Endpoint Protection Essentials <<elasticsearch-manage-project,project feature>>.
165+
====
166+
167+
Memory threat protection levels are:
168+
169+
* **Detect**: Detects memory threat activity on the host and generates an alert.
170+
{elastic-defend} will **not** block the in-memory activity. You must pay attention to and analyze any alerts that are generated.
171+
* **Prevent** (Default): Detects memory threat activity on the host, forces the process
172+
or thread to stop, and generates an alert.
173+
174+
Select **Notify user** to send a push notification in the host operating system when activity is detected or prevented. Notifications are enabled by default for the **Prevent** option.
175+
176+
[TIP]
177+
====
178+
Endpoint Protection Complete customers can customize these notifications using the `Elastic Security {action} {rule}` syntax.
179+
====
180+
181+
[role="screenshot"]
182+
image::images/configure-endpoint-integration-policy/-getting-started-install-endpoint-memory-protection.png[Detail of memory protection section.]
183+
184+
[discrete]
185+
[[behavior-protection]]
186+
== Malicious behavior protection
187+
188+
Malicious behavior protection detects and stops threats by monitoring the behavior
189+
of system processes for suspicious activity. Behavioral signals are much more difficult
190+
for adversaries to evade than traditional file-based detection techniques.
191+
192+
.Requirements
193+
[NOTE]
194+
====
195+
Malicious behavior protection requires the Endpoint Protection Essentials <<elasticsearch-manage-project,project feature>>.
196+
====
197+
198+
Malicious behavior protection levels are:
199+
200+
* **Detect**: Detects malicious behavior on the host and generates an alert.
201+
{elastic-defend} will **not** block the malicious behavior. You must pay attention to and analyze any alerts that are generated.
202+
* **Prevent** (Default): Detects malicious behavior on the host, forces the process to stop,
203+
and generates an alert.
204+
205+
Select whether you want to use **Reputation service** for additional protection. Elastic's reputation service leverages our extensive threat intelligence knowledge to make high confidence real-time prevention decisions. For example, reputation service can detect suspicious downloads of binaries with low or malicious reputation. Endpoints communicate with the reputation service directly at https://cloud.security.elastic.co[https://cloud.security.elastic.co].
206+
207+
Select **Notify user** to send a push notification in the host operating system when activity is detected or prevented. Notifications are enabled by default for the **Prevent** option.
208+
209+
[TIP]
210+
====
211+
Endpoint Protection Complete customers can customize these notifications using the `Elastic Security {action} {rule}` syntax.
212+
====
213+
214+
[role="screenshot"]
215+
image::images/configure-endpoint-integration-policy/-getting-started-install-endpoint-behavior-protection.png[Detail of behavior protection section.]
216+
217+
[discrete]
218+
[[attack-surface-reduction]]
219+
== Attack surface reduction
220+
221+
This section helps you reduce vulnerabilities that attackers can target on Windows endpoints.
222+
223+
.Requirements
224+
[NOTE]
225+
====
226+
Attack surface reduction requires the Endpoint Protection Essentials <<elasticsearch-manage-project,project feature>>.
227+
====
228+
229+
* **Credential hardening**: Prevents attackers from stealing credentials stored in Windows system process memory. Turn on the toggle to remove any overly permissive access rights that aren't required for standard interaction with the Local Security Authority Subsystem Service (LSASS). This feature enforces the principle of least privilege without interfering with benign system activity that is related to LSASS.
230+
231+
[role="screenshot"]
232+
image::images/configure-endpoint-integration-policy/-getting-started-install-endpoint-attack-surface-reduction.png[Detail of attack surface reduction section.]
233+
234+
[discrete]
235+
[[event-collection]]
236+
== Event collection
237+
238+
In the **Settings** section, select which categories of events to collect on each operating system.
239+
Most categories are collected by default, as seen below.
240+
241+
[role="screenshot"]
242+
image::images/configure-endpoint-integration-policy/-getting-started-install-endpoint-event-collection.png[Detail of event collection section.]
243+
244+
[discrete]
245+
[[register-as-antivirus]]
246+
== Register {elastic-sec} as antivirus (optional)
247+
248+
You can register {elastic-sec} as your hosts' antivirus software by enabling **Register as antivirus**.
249+
250+
[NOTE]
251+
====
252+
Windows Server is not supported. Antivirus registration requires Windows Security Center, which is not included in Windows Server operating systems.
253+
====
254+
255+
By default, the **Sync with malware protection level** is selected to automatically set antivirus registration to match how you've configured {elastic-defend}'s <<malware-protection,malware protection>>. If malware protection is turned on _and_ set to **Prevent**, antivirus registration will also be enabled; in any other case, antivirus registration will be disabled.
256+
257+
If you don't want to sync antivirus registration, you can set it manually with **Enabled** or **Disabled**.
258+
259+
[role="screenshot"]
260+
image::images/configure-endpoint-integration-policy/-getting-started-register-as-antivirus.png[Detail of Register as antivirus option.]
261+
262+
[discrete]
263+
[[adv-policy-settings]]
264+
== Advanced policy settings (optional)
265+
266+
Users with unique configuration and security requirements can select **Show advanced settings**
267+
to configure the policy to support advanced use cases. Hover over each setting to view its description.
268+
269+
[NOTE]
270+
====
271+
Advanced settings are not recommended for most users.
272+
====
273+
274+
This section includes:
275+
276+
* <<security-endpoint-diagnostic-data,Turn off diagnostic data for {elastic-defend}>>
277+
* <<security-self-healing-rollback,Configure self-healing rollback for Windows endpoints>>
278+
* <<security-linux-file-monitoring,Configure Linux file system monitoring>>
279+
280+
[discrete]
281+
[[save-policy]]
282+
== Save the general policy settings
283+
284+
After you have configured the general settings on the **Policy settings** tab, click **Save**. A confirmation message appears.

0 commit comments

Comments
 (0)