-
Notifications
You must be signed in to change notification settings - Fork 266
Open
Labels
enhancementNew feature or requestNew feature or requestticketed(automation only) Ticket has been created internally for tracking(automation only) Ticket has been created internally for tracking
Description
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
exploide
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestticketed(automation only) Ticket has been created internally for tracking(automation only) Ticket has been created internally for tracking