Skip to content
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

[Entity Analytics] Make risk engine APIs public #188197

Closed
hop-dev opened this issue Jul 12, 2024 · 2 comments
Closed

[Entity Analytics] Make risk engine APIs public #188197

hop-dev opened this issue Jul 12, 2024 · 2 comments
Labels
Team:Entity Analytics Security Entity Analytics Team

Comments

@hop-dev
Copy link
Contributor

hop-dev commented Jul 12, 2024

In v9 internal APIs will not be able to be called other than from Kibana itsself, we have found the risk engine init and status APIs useful for diagnosing and solving SDHs we should make public versions of them and then eventually delete the internal ones, the same way we have with asset criticality APIs.

@hop-dev hop-dev added the Team:Entity Analytics Security Entity Analytics Team label Jul 12, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-entity-analytics (Team:Entity Analytics)

@jaredburgettelastic
Copy link
Contributor

Closing in favor of duplicate (private) issue here: https://github.com/elastic/security-team/issues/11164

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Entity Analytics Security Entity Analytics Team
Projects
None yet
Development

No branches or pull requests

3 participants