Velociraptor is a tool for collecting host based state information using Velocidex Query Language (VQL) queries.
Velociraptor is loosely based on Google's GRR technologies but is a re-implementation and redesign focusing on ease of use, scalability and flexibility.
To learn more about Velociraptor, read about it on our blog:
https://velociraptor-blog.velocidex.com
-
Download the binary from the release page.
-
You need to generate a server config file. This will generate new key material:
$ velociraptor config generate > /etc/velociraptor.config.yaml
-
Edit the config file and update any settings. In particular you would probably need to update the following:
-
Client.server_urls - the public-facing URLs to connect to the server.
-
Datastore.location and Datastore.filestore_directory - where to store files on the server.
-
-
To be able to log into the GUI you will need to make a user account with password.
$ velociraptor --config /etc/velociraptor.config.yaml user add my_user_name
-
Start the server:
$ velociraptor --config /etc/velociraptor.config.yaml frontend
-
Point a browser at the GUI port that you set in the config file. You should be able to log in with the password set earlier.
-
Generate a client config (this is just the client part of the server config you made before - it contains no secrets and can be installed on clients.):
$ velociraptor --config /etc/velociraptor.config.yaml config \ client > client.conf.yaml
-
Launch the client on any system with this client config file.
$ velociraptor --config client.conf.yaml client
-
You should be able to search for the client in the GUI, browse VFS, download files etc.
NOTE: You may omit the --config flag if you include the location to the config file in the VELOCIRAPTOR_CONFIG environment variable.
To create a windows executable:
-
Embed the client config in the binary. This makes the binary self contained for your particular installation. It is therefore very easy to install:
$ velociraptor config repack --exe velociraptor_windows.exe \ client.config.yaml my_velociraptor.exe
Where velociraptor_windows.exe is the Windows binary release for Velociraptor.
-
On a windows system you can now install the service:
$ my_velociraptor.exe service install INFO:2018/08/28 00:18:19 Stopped service Velociraptor INFO:2018/08/28 00:18:20 Copied binary to C:\Program Files\Velociraptor\Velociraptor.exe INFO:2018/08/28 00:18:20 Installed service Velociraptor INFO:2018/08/28 00:18:21 Started service Velociraptor
This will copy the binary into the install_dir specified in the config file, create and start the service.
Velociraptor is also useful as a local triage tool. In particular you might find Velociraptor's artifacts especially useful for quickly capturing important information about a running system. You can collect artifacts by using the "artifacts collect" command:
$ velociraptor artifacts list
INFO:2018/08/20 22:28:56 Loaded 18 built in artifacts
INFO:2018/08/20 22:28:56 Loaded 18 artifacts from artifacts/definitions/
Linux.Applications.Chrome.Extensions
Linux.Applications.Chrome.Extensions.Upload
Linux.Applications.Docker.Info
Linux.Applications.Docker.Version
Linux.Debian.AptSources
$ velociraptor artifacts list -v Linux.Debian.AptSources
.... displays the artifacts
$ velociraptor artifacts collect Linux.Debian.AptSources
... Collects all the named artifacts
Explore more of Velociraptor's options using the -h flag.
To build from source, make sure you have a recent Golang installed: ```bash $ go get -u www.velocidex.com/golang/velociraptor $ cd $GO_PATH/go/src/www.velocidex.com/golang/velociraptor/
# This will download go dependencies.
$ dep ensure
# This will build the GUI elements:
$ cd gui/static/
$ npm install
$ gulp compile
$ cd -
# This builds a release (i.e. it will embed the GUI files in the
# binary). If you dont care about the GUI a simple "make" will
# build a bare binary.
$ make release
$ make windows
```
Questions and feedback are welcome at velociraptor-discuss@googlegroups.com
File issues on https://gitlab.com/velocidex/velociraptor
Read more about Velociraptor on our blog: