Skip to content

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

@rtpt-romankarwacik

Description

@rtpt-romankarwacik

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestticketed(automation only) Ticket has been created internally for tracking

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions