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

Feature: More nuanced deletion of Data (specifically HasSession) #853

Open
rtpt-romankarwacik opened this issue Sep 11, 2024 · 1 comment
Labels
enhancement New feature or request ticketed (automation only) Ticket has been created internally for tracking

Comments

@rtpt-romankarwacik
Copy link

Feature Description

Database Management management was introduced in #423 . In cases where current data about logged in users for an attack is needed, we currently have to delete the whole database (Collected graph data), and import all other data besides the HasSession Edges. A way to only delete specific typed of data could be useful in this case.

Are you intending to implement this feature?

No

Current Behavior

Only all collected graph data can be deleted, not specific types of data.

Desired Behavior

Add more options to the /clear-database endpoint and add UI elements too.

Use Case

Updating user sessions without keeping the old user session data.

Implementation Suggestions

Maybe a deleteHasSessionsEdges option for POST api/v2/clear-database which executed something akin to:

match (c:Computer)-[e:HasSession]->(u:User) delete e
@rtpt-romankarwacik rtpt-romankarwacik added enhancement New feature or request triage This issue requires triaging labels Sep 11, 2024
@Acebond
Copy link

Acebond commented Sep 14, 2024

This is still in the old Bloodhound, it has clear sessions, and also you can right click and delete individual edges/nodes. I wish the new one had these features too.

@StephenHinck StephenHinck added ticketed (automation only) Ticket has been created internally for tracking and removed triage This issue requires triaging labels Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request ticketed (automation only) Ticket has been created internally for tracking
Projects
None yet
Development

No branches or pull requests

3 participants