There are a few use cases where you need to migrate data from an instance to another. It could be for educational purpose to provide pre-filled labs, or to provide a third party with the exact insights you had during your investigation. Event for archiving, being able to reload a dataset in Velociraptor to review what was done if something went amiss, being able to export and import an organization dataset could prove useful.
Everything related to an organization is stored in a directory under <file store>/orgs
. There is:
<orgId>.json.db
We need to transfer both to the destination server.
Server.Orgs.ListOrgs
Artifact or scrolling down the Velociraptor root org home page.json.db
file (mind the star)tar czf transport-<org name>.tar.gz <file store>/orgs/<org id>*
<file store>/orgs
directory.The orgs
directory is created with the first organization. After a fresh install of Velociraptor, it doesn’t exist until you create an org. You may also simply create the directory.
Upon startup, Velociraptor will run the workers linked to the organization, so you can find a trace of it in the logs, but you may only see it in GUI if you are granted permissions on it. Just edit with your favorite text editor: <file store>/orgs/<org id>/acl/<username>.json.db
to give the access rights to an existing user (or create a user with the name of a user who was allowed to see the org),