Skip to content

Commit e2645f7

Browse files
More updates
1 parent 0f49e71 commit e2645f7

File tree

1 file changed

+16
-2
lines changed

1 file changed

+16
-2
lines changed

solutions/security/ai/attack-discovery.md

Lines changed: 16 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,13 @@ You need the `Attack Discovery: All` privilege to use Attack Discovery.
2626

2727
![attack-discovery-rbac](/solutions/images/security-attck-disc-rbac.png)
2828

29+
{applies_to}`stack: ga 9.1` Your role must also have the following privileges:
30+
31+
| Action | Indices | {{es}} privileges |
32+
|---------|---------|--------------------------|
33+
| Read Attack Discovery alerts | - `.alerts-security.attack.discovery.alerts-<space-id>`<br>- `.internal.alerts-security.attack.discovery.alerts-<space-id>`<br> - `.adhoc.alerts-security.attack.discovery.alerts-<space-id>`<br>- `.internal.adhoc.alerts-security.attack.discovery.alerts-<space-id>`| `read` and `view_index_metadata` |
34+
| Read and modify Attack Discovery alerts. This includes:<br>- Generating discovery alerts manually<br>- Generating discovery alerts using schedules<br>- Sharing manually created alerts with other users<br>- Updating a discovery's status |- `.alerts-security.attack.discovery.alerts-<space-id>`<br>- `.internal.alerts-security.attack.discovery.alerts-<space-id>`<br>- `.adhoc.alerts-security.attack.discovery.alerts-<space-id>`<br>- `.internal.adhoc.alerts-security.attack.discovery.alerts-<space-id>`| `all` |
35+
2936
## Set up Attack Discovery
3037

3138
By default, Attack Discovery analyzes up to 100 alerts from the last 24 hours, but you can customize how many and which alerts it analyzes using the settings menu. To open it, click the settings icon next to the **Run** button.
@@ -117,8 +124,7 @@ stack: ga 9.1
117124
You can define recurring schedules (for example, daily or weekly) to automatically generate attack discoveries without needing manual runs. For example, you can generate discoveries every 24 hours and send a Slack notification to your SecOps channel if discoveries are found. Notifications are sent using configured [connectors](/deploy-manage/manage-connectors.md), such as Slack or email, and you can customize the notification content to tailor alert context to your needs.
118125
119126
:::{note}
120-
* Scheduled discoveries are shared by default with all users in a {{kib}} space. Once shared, the visibility of shared discoveries cannot be changed.
121-
* You can still generate discoveries manually at any time, regardless of an active schedule.
127+
You can still generate discoveries manually at any time, regardless of an active schedule.
122128
:::
123129
124130
To create a new schedule:
@@ -152,6 +158,14 @@ You can set a discovery's status to indicate that it's under active investigatio
152158

153159
You can choose to change the status of only the discovery, or of both the discovery and the alerts associated with it.
154160

161+
### Share attack discoveries
162+
163+
By default, scheduled discoveries are shared with all users in a {{kib}} space. Manually generated discoveries are private by default. To share them, change **Not shared** to **Shared** next to the discovery's name.
164+
165+
:::{note}
166+
Once a discovery is shared, its visibility cannot be changed.
167+
:::
168+
155169
### Take bulk actions
156170

157171
You can take bulk actions on multiple discoveries, such as bulk-changing their status or adding them to a case. To do this, select the checkboxes next to each discovery, then click **Selected *x* Attack discoveries** and choose the action you want to take.

0 commit comments

Comments
 (0)