-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[8.x] [Security Solution][Entity Analytics] Scoping the entity store …
…to spaces (#193303) (#193697) # Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution][Entity Analytics] Scoping the entity store to spaces (#193303)](#193303) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tiago Vila Verde","email":"tiago.vilaverde@elastic.co"},"sourceCommit":{"committedDate":"2024-09-23T09:47:48Z","message":"[Security Solution][Entity Analytics] Scoping the entity store to spaces (#193303)\n\n## Summary\r\n\r\nThis PR introduces Kibana Spaces support for the Entity Store.\r\nIt implements https://github.com/elastic/security-team/issues/10530\r\n\r\n\r\n\r\n\r\n### How to test\r\n\r\n1. Add some host/user data\r\n* Easiest is to use\r\n[elastic/security-data-generator](https://github.com/elastic/security-documents-generator)\r\n2. Make sure to add `entityStoreEnabled` under\r\n`xpack.securitySolution.enableExperimental` in your `kibana.dev.yml`\r\n3. Make sure to create a second space other than `default`, either via\r\nthe UI or the spaces API.\r\n4. In the default space kibana dev tools, call the `POST\r\nkbn:/api/entity_store/engines/{entity_type}/init {}` route for either\r\n`user` or `host`.\r\n5. Switch to the other space and call `INIT` again.\r\n6. Check that calling the `GET kbn:api/entity_store/engines` route in\r\neach space returns only one engine.\r\n7. Check that calling `GET\r\n/.kibana*/_search?q=type:entity-engine-status` returns 2 engines, one in\r\neach space.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"16dcfa84c8e54825bd24a89697bb715012791284","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","Theme: entity_analytics","Feature:Entity Analytics","Team:Entity Analytics","8.16 candidate"],"number":193303,"url":"https://github.com/elastic/kibana/pull/193303","mergeCommit":{"message":"[Security Solution][Entity Analytics] Scoping the entity store to spaces (#193303)\n\n## Summary\r\n\r\nThis PR introduces Kibana Spaces support for the Entity Store.\r\nIt implements https://github.com/elastic/security-team/issues/10530\r\n\r\n\r\n\r\n\r\n### How to test\r\n\r\n1. Add some host/user data\r\n* Easiest is to use\r\n[elastic/security-data-generator](https://github.com/elastic/security-documents-generator)\r\n2. Make sure to add `entityStoreEnabled` under\r\n`xpack.securitySolution.enableExperimental` in your `kibana.dev.yml`\r\n3. Make sure to create a second space other than `default`, either via\r\nthe UI or the spaces API.\r\n4. In the default space kibana dev tools, call the `POST\r\nkbn:/api/entity_store/engines/{entity_type}/init {}` route for either\r\n`user` or `host`.\r\n5. Switch to the other space and call `INIT` again.\r\n6. Check that calling the `GET kbn:api/entity_store/engines` route in\r\neach space returns only one engine.\r\n7. Check that calling `GET\r\n/.kibana*/_search?q=type:entity-engine-status` returns 2 engines, one in\r\neach space.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"16dcfa84c8e54825bd24a89697bb715012791284"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/193303","number":193303,"mergeCommit":{"message":"[Security Solution][Entity Analytics] Scoping the entity store to spaces (#193303)\n\n## Summary\r\n\r\nThis PR introduces Kibana Spaces support for the Entity Store.\r\nIt implements https://github.com/elastic/security-team/issues/10530\r\n\r\n\r\n\r\n\r\n### How to test\r\n\r\n1. Add some host/user data\r\n* Easiest is to use\r\n[elastic/security-data-generator](https://github.com/elastic/security-documents-generator)\r\n2. Make sure to add `entityStoreEnabled` under\r\n`xpack.securitySolution.enableExperimental` in your `kibana.dev.yml`\r\n3. Make sure to create a second space other than `default`, either via\r\nthe UI or the spaces API.\r\n4. In the default space kibana dev tools, call the `POST\r\nkbn:/api/entity_store/engines/{entity_type}/init {}` route for either\r\n`user` or `host`.\r\n5. Switch to the other space and call `INIT` again.\r\n6. Check that calling the `GET kbn:api/entity_store/engines` route in\r\neach space returns only one engine.\r\n7. Check that calling `GET\r\n/.kibana*/_search?q=type:entity-engine-status` returns 2 engines, one in\r\neach space.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"16dcfa84c8e54825bd24a89697bb715012791284"}}]}] BACKPORT-->
- Loading branch information
1 parent
9c356e8
commit 05e9b8f
Showing
8 changed files
with
62 additions
and
66 deletions.
There are no files selected for viewing
2 changes: 1 addition & 1 deletion
2
...ver/lib/entity_analytics/entity_store/__snapshots__/entity_store_data_client.test.ts.snap
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters