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

Permit users to directly access prevention/detection control alerts from the inject user interface #2222

Closed
neutneutneut opened this issue Jan 16, 2025 · 1 comment
Labels
duplicate use to identify issue already existing feature use for describing a new feature to develop

Comments

@neutneutneut
Copy link

Context

When detective collectors such as CrowdStrike are enabled, the detection and prevention verification is shown in the user interface for an inject.

A good to have feature would be the ability for a user to directly click the control box, to be taken to the alert within the security control application.

I.e., if I have a CrowdStrike green, I click the CrowdStrike green button and it takes me to the CrowdStrike console where I can directly review the specifics of the control prevention / detection

Use case

Allow the user to 'click' the control via the user interface to be taken to the relevant alert in the security product console:

Image

Current Workaround

Access the consoles directly and search manually for the detection / prevention activity.

Proposed Solution

Update the OpenBAS UI to include a link to the alert in the associated security product console window.

Additional Information

N/A

If the feature request is approved, would you be willing to submit a PR?

Yes / No

@neutneutneut neutneutneut added feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team labels Jan 16, 2025
@EllynBsc EllynBsc removed the needs triage use to identify issue needing triage from Filigran Product team label Feb 12, 2025
@EllynBsc EllynBsc added this to the Short term candidates milestone Feb 12, 2025
@jborozco
Copy link

Hi @neutneutneut I'm closing this one as duplicate of #564 we are currently working on this feature, stay tuned !

@SamuelHassine SamuelHassine added the duplicate use to identify issue already existing label Feb 19, 2025
@SamuelHassine SamuelHassine removed this from the Short term candidates milestone Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate use to identify issue already existing feature use for describing a new feature to develop
Projects
None yet
Development

No branches or pull requests

4 participants