[EDR Workflows][Endpoint Exception move] Remove endpoint exceptions from detections pages by gergoabraham · Pull Request #258556 · elastic/kibana

gergoabraham · 2026-03-19T14:36:20Z

Summary

This PR removes Endpoint exceptions from the Detections/Rules pages, and shows callouts to the user.

Note

Hidden behind feature flag (as part of the Endpoint exception move effort):

xpack.securitySolution.enableExperimental:
 - endpointExceptionsMovedUnderManagement

Shared lists page

Endpoint Exceptions list removed
direct url cannot be accessed
a banner is shown

Rule details pages

Endpoint Exceptions tab removed
Endpoint Exceptions tab cannot be accessed by url
Rule exceptions tab shows a persistent banner for Endpoint security rules
The same banner is also used for Rules that used Endpoint exceptions, but user hasn't opted in to use per-policy Endpoint exceptions

When user opted in for per-policy Endpoint Exceptions, a different (dismissible) message is shown for rules that used Endpoint exceptions

Rule create page

Rule edit page

If the user has opted in for per-policy Endpoint exceptions, and the rule used Endpoint exceptions, this banner is shown:

If not opted in, or it's a rule without endpoint exceptions, the general 'moved' banner is shown:

Note

Per-policy opt-in feature is coming up in a follow-up PR. In that PR will all code (including these banners, and the removal of 'Add Endpoint exceptions to this rule' toggle) related to per-policy opt-in updated.
Until then, this PR handles the banners as if the user has already opted in, in case the FF is enabled of course.

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
Unit or functional tests were updated or added to match the most common scenarios

elasticmachine · 2026-03-19T14:59:56Z

Pinging @elastic/security-defend-workflows (Team:Defend Workflows)

…ages

denar50

Tested it locally, left a couple of comments, but overall LGTM!

…ages

maximpn

@gergoabraham The changes overall looks good 👍

However, I've noticed you added callouts to rule create and edit pages. Users don't have options to add or edit endpoint exceptions in rule create and edit pages. In this case it's better to refrain from showing the callout on those pages.

maximpn · 2026-03-23T15:55:13Z

+                      {isEndpointExceptionsMovedFFEnabled && (
+                        <EndpointExceptionsMovedCallout
+                          id="ruleCreation"
+                          dismissable
+                          title="cannotBeAddedToRules"
+                        />
+                      )}
+


Endpoint exceptions can't be added upon rule creation. There are 3 pages were it could be done and it's reflected in the docs

Rule details page

Alerts table

Shared Exception Lists page

It makes sense to omit the callout here.

the callout is about adding the endpoint exception list to the rule:

the docs mention it under a 'Note':

The Endpoint Security Exception List is automatically created. By default, it's associated with endpoint protection rules and any rules with the Elastic Endpoint exceptions option selected.

additional info: the checkbox is already hidden when the FF is enabled, by this PR:

[Security Solution] [Detection Engine] Conditionally hides checkbox to add endpoint exceptions to rule execution #242480

Got it. This explains why I didn't see the checkbox.

Did you discuss with @approksiu the callout will be shown for any rule creation? My concern is that only some rules require Endpoint exceptions. Add existing Endpoint exceptions to the rule is under advanced expandable panel. However, the callout telling about moved out endpoint exceptions will appear for workflows not related to the endpoint exceptions.

the callout for rule creation is in the design (you can find it in the linked issue's description), and I think @approksiu was part of defining the design. @approksiu could you please confirm if we're good with this callout?

@gergoabraham @maximpn the behaviour is implemented as expected.
The banner is dismissable for all rules.
The new users should not get the banners if they never used rule-attached endpoint exceptions.

…ages

gergoabraham · 2026-03-23T16:55:18Z

@gergoabraham The changes overall looks good 👍

However, I've noticed you added callouts to rule create and edit pages. Users don't have options to add or edit endpoint exceptions in rule create and edit pages. In this case it's better to refrain from showing the callout on those pages.

thanks a lot @maximpn for the thorough review! 🙌 updated the code based on your findings, will update the text based on @natasha-moore-elastic 's feedback

maximpn

@gergoabraham Thanks for addressing my comments 🙏

The only concern I have is described in #258556 (comment). Besides that the changes LGTM.

natasha-moore-elastic

Left some copy suggestions and questions, thanks!

…ages

natasha-moore-elastic

Thanks for the copy updates, LGTM!

elasticmachine · 2026-03-24T17:14:03Z

💚 Build Succeeded

Buildkite Build
Commit: b5f12c6

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
`securitySolution`	9248	9249	+1

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
`securitySolution`	11.4MB	11.4MB	+3.3KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
`securitySolution`	173.6KB	173.6KB	-1.0B

History

💛 Build #414868 was flaky ff52599

cc @gergoabraham

…rom detections pages (elastic#258556) ## Summary This PR removes Endpoint exceptions from the Detections/Rules pages, and shows callouts to the user. > [!note] > Hidden behind feature flag (as part of the Endpoint exception move effort): > ``` > xpack.securitySolution.enableExperimental: > - endpointExceptionsMovedUnderManagement > ``` ### Shared lists page - Endpoint Exceptions list removed - direct url cannot be accessed - a banner is shown <img width="1282" height="503" alt="image" src="https://github.com/user-attachments/assets/d4201863-efcf-47e5-9a2f-4f1fbe842272" /> ### Rule details pages - Endpoint Exceptions tab removed - Endpoint Exceptions tab cannot be accessed by url - Rule exceptions tab shows a persistent banner for Endpoint security rules - The same banner is also used for Rules that used Endpoint exceptions, but user hasn't opted in to use per-policy Endpoint exceptions <img width="1288" height="832" alt="image" src="https://github.com/user-attachments/assets/9a4a192d-5e82-48b9-be85-7448c69edf7b" /> - When user opted in for per-policy Endpoint Exceptions, a different (dismissible) message is shown for rules that used Endpoint exceptions <img width="1162" height="649" alt="image" src="https://github.com/user-attachments/assets/f2b1fde4-387b-4998-be33-47d15b682704" /> ### Rule create page <img width="1161" height="517" alt="image" src="https://github.com/user-attachments/assets/237a068d-cb79-4365-a507-df2d8e74de2b" /> ### Rule edit page - If the user has opted in for per-policy Endpoint exceptions, and the rule used Endpoint exceptions, this banner is shown: <img width="1153" height="538" alt="image" src="https://github.com/user-attachments/assets/0dc6cf8c-4115-45af-a160-c0ed5cba06c2" /> - If not opted in, or it's a rule without endpoint exceptions, the general 'moved' banner is shown: <img width="1164" height="520" alt="image" src="https://github.com/user-attachments/assets/90bb29b5-d390-4ab0-8903-58ef276255e9" /> > [!note] > Per-policy opt-in feature is coming up in a follow-up PR. In that PR will all code (including these banners, and the removal of 'Add Endpoint exceptions to this rule' toggle) related to per-policy opt-in updated. > Until then, this PR handles the banners as if the user has already opted in, in case the FF is enabled of course. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios

…icy Endpoint Exceptions (#259598) ## Summary This PR adds an opt-in mechanism that allows using the so far global-only Endpoint Exceptions on a per-policy basis. > [!note] > Hidden behind feature flag (as part of the Endpoint exception move effort): > ``` > xpack.securitySolution.enableExperimental: > - endpointExceptionsMovedUnderManagement > ``` ### Behavior in short - new deployments are automatically opted in. they also won't see the 'Endpoint exceptions moved' and 'Endpoint exceptions not evaluated on rules anymore' callouts (from #258556). - upgraded environments will see a new callout on the Endpoint exceptions page that suggests to enable per-policy behavior - superuser role (ESS) or admin role (serverless) users are able to perform the opt-in - other users will see a message to contact their administrators - after manually opting in - Endpoint exceptions can be assigned to package policies, like other endpoint artifacts - but, they won't be evaluated during rule execution anymore (see #233289) - and they cannot be added to detection rules anymore (see #242480) ### Data Opt-in status is stored in the `ReferenceDataClient`, and it's defaulted during plugin start phase either to: - `{ status: false }`, in case endpoint exception list exists (i.e. upgrade, it's created every time), - `{ status: true, reason: 'newDeployment' }`, in case the list does not exist. ### API 2 new API endpoints are added: - `GET /internal/api/endpoint/endpoint_exceptions_per_policy_opt_in` to receive the opt-in status on the UI, - `POST /internal/api/endpoint/endpoint_exceptions_per_policy_opt_in` to perform the opt-in, that sets the status to `{ status: true, reason: 'userOptedIn' }` ### UI #### empty page is... empty <img width="400" height="793" alt="image" src="https://github.com/user-attachments/assets/e7b72ab9-2a42-49ca-b2e9-2447e3ff9dd3" /> #### callout for non-superusers <img width="1280" height="516" alt="image" src="https://github.com/user-attachments/assets/f88a04a6-b8bb-46be-8f5f-ece5f1d89cf2" /> #### callout for superusers / admins <img width="1215" height="554" alt="image" src="https://github.com/user-attachments/assets/e2552d27-ac9d-4dfe-84da-48012fdf57fc" /> #### menu action for superusers / admins in case the callout is dismissed. although, it will come up again as it's only dismissed for the session. <img width="335" height="204" alt="image" src="https://github.com/user-attachments/assets/5d7a23e6-2428-4f8f-b941-0f97e8bd7750" /> #### modal <img width="925" height="564" alt="image" src="https://github.com/user-attachments/assets/0cbc4573-b052-4e1f-82c5-13298532f7fe" /> ### recording #### opt-in process and endpoint exceptions pages https://github.com/user-attachments/assets/de8204bd-72d2-4a99-b51c-b86771c577c3 ### hiding stuff behind opt-in status - endpoint exception related per-policy activities are available only after opt-in, like - per-policy assignment in the form, - assigning exceptions to policies in the Policy details page Endpoint exceptions tab, - `ManifestManager` also uses per-policy EE after opt-in only. - 'endpoint exceptions moved' informative callouts are shown without opting in (due to the FF enabled), or after _manual_ opt-in (i.e. are hidden on new deployments) - see the details in the previous PR: #258556 - 'endpoint exceptions are not evaluated on rules' informative callouts are shown only after _manually_ opting in (i.e. it needs opt-in, but isn't shown on new deployments) - see the details in the previous PR: #258556 ## Testing To test this, - either add some data (endpoint exceptions), and then turn on the feature flag `xpack.securitySolution.enableExperimental.endpointExceptionsMovedUnderManagement`, to simulate an 'upgrade' scenario, - or start with the feature flag turned on, to simulate a 'new deployment' scenario. ### Reading opt-in status dev console: ``` GET .kibana_security_solution/_doc/security:reference-data:ENDPOINT-EXCEPTIONS-PER-POLICY-OPT-IN-STATUS ``` ### Deleting opt-in status you can also delete the opt-in status, so you're back to the 'upgrade' scenario. for this, you need a `system_indices_superuser`, here's a quick console command to create one: ``` POST kbn://internal/security/users/testuser { "password": "changeme", "username": "testuser", "full_name": "", "email": "", "roles": [ "system_indices_superuser", "superuser" ] } ``` and then delete like this: ``` DELETE .kibana_security_solution/_doc/security:reference-data:ENDPOINT-EXCEPTIONS-PER-POLICY-OPT-IN-STATUS ``` ## todo docs ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios

…icy Endpoint Exceptions (elastic#259598) ## Summary This PR adds an opt-in mechanism that allows using the so far global-only Endpoint Exceptions on a per-policy basis. > [!note] > Hidden behind feature flag (as part of the Endpoint exception move effort): > ``` > xpack.securitySolution.enableExperimental: > - endpointExceptionsMovedUnderManagement > ``` ### Behavior in short - new deployments are automatically opted in. they also won't see the 'Endpoint exceptions moved' and 'Endpoint exceptions not evaluated on rules anymore' callouts (from elastic#258556). - upgraded environments will see a new callout on the Endpoint exceptions page that suggests to enable per-policy behavior - superuser role (ESS) or admin role (serverless) users are able to perform the opt-in - other users will see a message to contact their administrators - after manually opting in - Endpoint exceptions can be assigned to package policies, like other endpoint artifacts - but, they won't be evaluated during rule execution anymore (see elastic#233289) - and they cannot be added to detection rules anymore (see elastic#242480) ### Data Opt-in status is stored in the `ReferenceDataClient`, and it's defaulted during plugin start phase either to: - `{ status: false }`, in case endpoint exception list exists (i.e. upgrade, it's created every time), - `{ status: true, reason: 'newDeployment' }`, in case the list does not exist. ### API 2 new API endpoints are added: - `GET /internal/api/endpoint/endpoint_exceptions_per_policy_opt_in` to receive the opt-in status on the UI, - `POST /internal/api/endpoint/endpoint_exceptions_per_policy_opt_in` to perform the opt-in, that sets the status to `{ status: true, reason: 'userOptedIn' }` ### UI #### empty page is... empty <img width="400" height="793" alt="image" src="https://github.com/user-attachments/assets/e7b72ab9-2a42-49ca-b2e9-2447e3ff9dd3" /> #### callout for non-superusers <img width="1280" height="516" alt="image" src="https://github.com/user-attachments/assets/f88a04a6-b8bb-46be-8f5f-ece5f1d89cf2" /> #### callout for superusers / admins <img width="1215" height="554" alt="image" src="https://github.com/user-attachments/assets/e2552d27-ac9d-4dfe-84da-48012fdf57fc" /> #### menu action for superusers / admins in case the callout is dismissed. although, it will come up again as it's only dismissed for the session. <img width="335" height="204" alt="image" src="https://github.com/user-attachments/assets/5d7a23e6-2428-4f8f-b941-0f97e8bd7750" /> #### modal <img width="925" height="564" alt="image" src="https://github.com/user-attachments/assets/0cbc4573-b052-4e1f-82c5-13298532f7fe" /> ### recording #### opt-in process and endpoint exceptions pages https://github.com/user-attachments/assets/de8204bd-72d2-4a99-b51c-b86771c577c3 ### hiding stuff behind opt-in status - endpoint exception related per-policy activities are available only after opt-in, like - per-policy assignment in the form, - assigning exceptions to policies in the Policy details page Endpoint exceptions tab, - `ManifestManager` also uses per-policy EE after opt-in only. - 'endpoint exceptions moved' informative callouts are shown without opting in (due to the FF enabled), or after _manual_ opt-in (i.e. are hidden on new deployments) - see the details in the previous PR: elastic#258556 - 'endpoint exceptions are not evaluated on rules' informative callouts are shown only after _manually_ opting in (i.e. it needs opt-in, but isn't shown on new deployments) - see the details in the previous PR: elastic#258556 ## Testing To test this, - either add some data (endpoint exceptions), and then turn on the feature flag `xpack.securitySolution.enableExperimental.endpointExceptionsMovedUnderManagement`, to simulate an 'upgrade' scenario, - or start with the feature flag turned on, to simulate a 'new deployment' scenario. ### Reading opt-in status dev console: ``` GET .kibana_security_solution/_doc/security:reference-data:ENDPOINT-EXCEPTIONS-PER-POLICY-OPT-IN-STATUS ``` ### Deleting opt-in status you can also delete the opt-in status, so you're back to the 'upgrade' scenario. for this, you need a `system_indices_superuser`, here's a quick console command to create one: ``` POST kbn://internal/security/users/testuser { "password": "changeme", "username": "testuser", "full_name": "", "email": "", "roles": [ "system_indices_superuser", "superuser" ] } ``` and then delete like this: ``` DELETE .kibana_security_solution/_doc/security:reference-data:ENDPOINT-EXCEPTIONS-PER-POLICY-OPT-IN-STATUS ``` ## todo docs ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios

gergoabraham added 6 commits March 19, 2026 12:19

add EndpointExceptionsMovedCallout component

5889fb5

[shared lists] hide endpoint exceptions

82a37dd

[shared lists / details] hide endpoint exceptions url

f1a9771

[shared lists] show callout to user

19c0b27

[rule details] hide endpoint exceptions tab

5de08a6

[rule details] hide endpoint exceptions tab URL

8b3b887

gergoabraham self-assigned this Mar 19, 2026

gergoabraham added release_note:skip Skip the PR/issue when compiling release notes backport:skip This PR does not require backporting Team:Defend Workflows “EDR Workflows” sub-team of Security Solution labels Mar 19, 2026

gergoabraham added 3 commits March 19, 2026 15:45

[rule details / exceptions tab] show callout

56175cd

[rule creation] show EE moved callout

292f126

[rule edit] show EE moved/not evaluated callout

1c5ae8a

gergoabraham marked this pull request as ready for review March 19, 2026 14:59

gergoabraham requested review from a team as code owners March 19, 2026 14:59

gergoabraham requested review from denar50 and sdesalas March 19, 2026 14:59

gergoabraham force-pushed the remove-endpoint-exceptions-from-detections-pages branch from 4273027 to 1c5ae8a Compare March 19, 2026 15:05

gergoabraham requested review from a team, ashokaditya and tomsonpl and removed request for a team March 19, 2026 15:42

Merge branch 'main' into remove-endpoint-exceptions-from-detections-p…

78c3cee

…ages

denar50 reviewed Mar 20, 2026

View reviewed changes

Comment thread .../solutions/security/plugins/security_solution/public/exceptions/pages/shared_lists/index.tsx

denar50 approved these changes Mar 20, 2026

View reviewed changes

Comment thread x-pack/solutions/security/plugins/security_solution/public/rules/routes.tsx

Comment thread .../public/detection_engine/rule_exceptions/components/all_exception_items_table/index.test.tsx

gergoabraham added a commit to gergoabraham/kibana that referenced this pull request Mar 20, 2026

remove obsolete test (see elastic#258556)

d69858c

gergoabraham added 2 commits March 20, 2026 18:58

assert if callout is dismissible or not

87f632d

Merge branch 'main' into remove-endpoint-exceptions-from-detections-p…

bfd9b12

…ages

maximpn self-requested a review March 23, 2026 08:43

maximpn mentioned this pull request Mar 23, 2026

[Detections & Response] RBAC - Add Detection Alerts kibana feature #244637

Merged

10 tasks

maximpn requested changes Mar 23, 2026

View reviewed changes

gergoabraham added 3 commits March 23, 2026 17:39

simplify condition

b3e195f

change the calculation of isEndpointSecurityRule

6161502

Merge branch 'main' into remove-endpoint-exceptions-from-detections-p…

ff52599

…ages

gergoabraham requested a review from maximpn March 23, 2026 16:53

maximpn approved these changes Mar 24, 2026

View reviewed changes

natasha-moore-elastic reviewed Mar 24, 2026

View reviewed changes

gergoabraham requested a review from natasha-moore-elastic March 24, 2026 13:00

gergoabraham added 3 commits March 24, 2026 16:14

update texts

6bc5ce9

Merge branch 'main' into remove-endpoint-exceptions-from-detections-p…

31fce73

…ages

Merge branch 'main' into remove-endpoint-exceptions-from-detections-p…

b5f12c6

…ages

natasha-moore-elastic approved these changes Mar 24, 2026

View reviewed changes

gergoabraham merged commit 79de608 into elastic:main Mar 24, 2026
18 checks passed

kibanamachine added the v9.4.0 label Mar 24, 2026

gergoabraham mentioned this pull request Mar 27, 2026

[EDR Workflows][Endpoint Exception move] Opt-in mechanism for per-policy Endpoint Exceptions #259598

Merged

3 tasks

gergoabraham added a commit to gergoabraham/kibana that referenced this pull request Mar 31, 2026

remove obsolete test (see elastic#258556)

4aba229

gergoabraham added a commit to gergoabraham/kibana that referenced this pull request Apr 1, 2026

remove obsolete test (see elastic#258556)

2237453

gergoabraham added a commit to gergoabraham/kibana that referenced this pull request Apr 2, 2026

remove obsolete test (see elastic#258556)

65a7f1f

gergoabraham added a commit to gergoabraham/kibana that referenced this pull request Apr 2, 2026

remove obsolete test (see elastic#258556)

975ceb9

gergoabraham added a commit to gergoabraham/kibana that referenced this pull request Apr 7, 2026

remove obsolete test (see elastic#258556)

f506ac0

gergoabraham added a commit to gergoabraham/kibana that referenced this pull request Apr 8, 2026

remove obsolete test (see elastic#258556)

a564391

gergoabraham deleted the remove-endpoint-exceptions-from-detections-pages branch April 10, 2026 10:56

Conversation

gergoabraham commented Mar 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Shared lists page

Rule details pages

Rule create page

Rule edit page

Checklist

Uh oh!

elasticmachine commented Mar 19, 2026

Uh oh!

Uh oh!

denar50 left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

maximpn left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

maximpn Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

gergoabraham Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

gergoabraham Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

maximpn Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

gergoabraham Mar 24, 2026

Choose a reason for hiding this comment

Uh oh!

approksiu Mar 24, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

gergoabraham commented Mar 23, 2026

Uh oh!

maximpn left a comment

Choose a reason for hiding this comment

Uh oh!

natasha-moore-elastic left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

natasha-moore-elastic left a comment

Choose a reason for hiding this comment

Uh oh!

elasticmachine commented Mar 24, 2026

💚 Build Succeeded

Metrics [docs]

Module Count

Async chunks

Page load bundle

History

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

gergoabraham commented Mar 19, 2026 •

edited

Loading

maximpn left a comment •

edited

Loading

natasha-moore-elastic left a comment •

edited

Loading