-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Security Solution] [Bug] Rules and alerts are available in second space if user re-create the space with same name again. #216158
Comments
Pinging @elastic/security-solution (Team: SecuritySolution) |
Pinging @elastic/security-threat-hunting (Team:Threat Hunting) |
Reviewed and Assigned to @vgomez-el |
Hi @muskangulati-qasource! REC-20250327152007.mp4I will check with @PhilippeOberti and Threat hunting investigations team, if the bug belongs to them, or to the team that owns spaces. |
Pinging @elastic/security-threat-hunting-investigations (Team:Threat Hunting:Investigations) |
Pinging @elastic/kibana-security (Team:Security) |
I reproduced this using stack rules + alerts: spaces_bug.mov |
Similar bug on Entity Analytics side here, a similar solution should be able to be used for both Alerts/Rules and EA. We may need a way to hook into the "Delete Space" code to remove additional resources. |
Describe the bug
Rules and alerts are available in second space if user re-create the space with same name again.
Kibana/Elasticsearch Stack version
Pre Conditions
Mus1
)Steps
Mus1
)Security
->Rules
Security
->Alerts
Mus1
)Create Space
button.Mus1
)Mus1
)Security
->Rules
andSecurity
->Alerts
Expected Result
The data previously deleted should not be available for the newly re created space as it can expose private data
Screen Recording
Alerts.mp4
The text was updated successfully, but these errors were encountered: