base on Digging Deeper.... # Velociraptor - Endpoint visibility and collection tool. Velociraptor is a tool for collecting host based state information using The Velociraptor Query Language (VQL) queries. To learn more about Velociraptor, read the documentation on: https://docs.velociraptor.app/ ## Quick start If you want to see what Velociraptor is all about simply: 1. Download the binary from the release page for your favorite platform (Windows/Linux/MacOS). 2. Start the GUI ```bash $ velociraptor gui ``` This will bring up the GUI, Frontend and a local client. You can collect artifacts from the client (which is just running on your own machine) as normal. Once you are ready for a full deployment, check out the various deployment options at https://docs.velociraptor.app/docs/deployment/ ## Training We have our complete training course (7 sessions x 2 hours each) https://docs.velociraptor.app/training/ The course covers many aspects of Velociraptor in detail. ## Running Velociraptor via Docker To run a Velociraptor server via Docker, follow the instructions here: https://github.com/weslambert/velociraptor-docker ## Running Velociraptor locally Velociraptor is also useful as a local triage tool. You can create a self contained local collector using the GUI: 1. Start the GUI as above (`velociraptor gui`). 2. Select the `Server Artifacts` sidebar menu, then `Build Collector`. 3. Select and configure the artifacts you want to collect, then select the `Uploaded Files` tab and download your customized collector. ## Building from source To build from source, make sure you have: - a recent Golang installed from https://golang.org/dl/ (Currently at least Go 1.23.2) - the `go` binary is in your path. - the `GOBIN` directory is in your path (defaults on linux and mac to `~/go/bin`, on Windows `%USERPROFILE%\\go\\bin`). - `gcc` in your path for CGO usage (on Windows, [TDM-GCC](https://jmeubank.github.io/tdm-gcc/about/) has been verified to work) - `make` - Node.js LTS (the GUI is build using [Node v18.14.2](https://nodejs.org/en/blog/release/v18.14.2)) ```bash $ git clone https://github.com/Velocidex/velociraptor.git $ cd velociraptor # This will build the GUI elements. You will need to have node # installed first. For example get it from # https://nodejs.org/en/download/. $ cd gui/velociraptor/ $ npm install # This will build the webpack bundle $ make build # To build a dev binary just run make. # NOTE: Make sure ~/go/bin is on your path - # this is required to find the Golang tools we need. $ cd ../.. $ make # To build production binaries $ make linux $ make windows ``` In order to build Windows binaries on Linux you need the mingw tools. On Ubuntu this is simply: ```bash $ sudo apt-get install mingw-w64-x86-64-dev gcc-mingw-w64-x86-64 gcc-mingw-w64 ``` ## Getting the latest version We have a pretty frequent release schedule but if you see a new feature submitted that you are really interested in, we would love to have more testing prior to the official release. We have a CI pipeline managed by GitHub actions. You can see the pipeline by clicking the actions tab on our GitHub project. There are two workflows: 1. Windows Test: this workflow builds a minimal version of the Velociraptor binary (without the GUI) and runs all the tests on it. We also test various windows support functions in this pipeline. This pipeline builds on every push in each PR. 2. Linux Build All Arches: This pipeline builds complete binaries for many supported architectures. It only runs when the PR is merged into the master branch. To download the latest binaries simply select the latest run of this pipeline, scroll down the page to the "Artifacts" section and download the *Binaries.zip* file (Note you need to be logged into GitHub to see this). If you fork the project on GitHub, the pipelines will run on your own fork as well as long as you enable GitHub Actions on your fork. If you need to prepare a PR for a new feature or modify an existing feature you can use this to build your own binaries for testing on all architectures before send us the PR. ## Supported platforms Velociraptor is written in Golang and so is available for all the platforms [supported by Go](https://github.com/golang/go/wiki/MinimumRequirements). This means that Windows XP and Windows server 2003 are **not** supported but anything after Windows 7/Vista is. We build our releases using the MUSL library (x64) for Linux and a recent MacOS system, so earlier platforms may not be supported by our release pipeline. We also distribute 32 bit binaries for Windows but not for Linux. If you need 32 bit Linux builds you will need to build from source. You can do this easily by forking the project on GitHub, enabling GitHub Actions in your fork and editing the `Linux Build All Arches` pipeline. ## Artifact Exchange Velociraptor's power comes from `VQL Artifacts`, that define many capabilities to collect many types of data from endpoints. Velociraptor comes with many built in `Artifacts` for the most common use cases. The community also maintains a large number of additional artifacts through the [Artifact Exchange](https://docs.velociraptor.app/exchange/). ## Knowledge Base If you need help performing a task such as deployment, VQL queries etc. Your first port of call should be the Velociraptor Knowledge Base at https://docs.velociraptor.app/knowledge_base/ where you will find helpful tips and hints. ## Getting help Questions and feedback are welcome at [email protected] (or https://groups.google.com/g/velociraptor-discuss) You can also chat with us directly on discord https://docs.velociraptor.app/discord File issues on https://github.com/Velocidex/velociraptor Read more about Velociraptor on our blog: https://docs.velociraptor.app/blog/ Hang out on Medium https://medium.com/velociraptor-ir Follow us on Twitter [@velocidex](https://twitter.com/velocidex) ", Assign "at most 3 tags" to the expected json: {"id":"7399","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"