> For the complete documentation index, see [llms.txt](https://docs.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vectra.ai/deployment/ndr-virtual-cloud-appliances/kvm-brain/licensing-and-brain-deployment-overview.md). # Licensing and Brain deployment overview How licensing works for KVM Brains and an overview of the KVM Brain deployment process. ## Licensing Overview Appliance code has been encrypted to protect Vectra’s intellectual property and a license is required to enable successful decryption of the file system and complete deployment. The licensing for Vectra NDR (formerly Detect for Network) running on KVM Brains also governs the ability of the system to create Detections. {% hint style="warning" %} **Please Note:** After deployment, if your Vectra NDR license expires, Detection algorithms will cease operation until a valid license is applied. Recall and Stream operation are unaffected if your Vectra NDR license expires and your Recall and/or Stream license is valid. {% endhint %} ## Licensing Enforcement Vectra NDR (Detect for Network) supports licensing functionality regardless of the type of deployment (physical appliance, cloud IaaS, KVM, etc). All versions will be able to see license status and enable requests for and application of licenses. Enforcement of NDR licensing is only enabled on KVM, VMware, and Nutanix Brains. Any other Brain type does NOT currently have licensing for NDR enforced. Vectra does plan to add licensing enforcement for other Brain types in the future. It is recommended that all customers work with their account teams to ensure their licensing is up to date. Please refer to the following table for additional detail:
ProductDeployment TypeLicense Enforcement
NDR (Detect for Network)

VMware Brain

KVM Brain
Nutanix Brain

Algorithms stop producing Detections when expired.
NDR (Detect for Network)Physical or Cloud BrainsNot currently enforced. Planned for future (timing TBD).
Other Vectra products are also licensed but enforcement of the license is a matter of contract compliance between sales teams and customers or partners. ## KVM Brain Deployment Overview Deployment of a Brain appliance in KVM environments can be done in Proxmox, Libvirt and other KVM-based virtual machine managers (VMMs) as discussed in [KVM deployment details and considerations](/deployment/ndr-virtual-cloud-appliances/kvm-brain/kvm-deployment-details-and-considerations.md). {% hint style="info" %} **Please Note:** The general steps below provide options in [Step 2](#deploy-the-.ova-or-qcow2-images) that point to different deployment instructions depending on what environment you are deploying a KVM Brain into. Each specific deployment environment page has instructions for which specific KVM compatible Brain image to download in Step 1. Follow the instructions for your environment and then move on to: * [Initial startup and licensing](/deployment/ndr-virtual-cloud-appliances/kvm-brain/initial-startup-and-licensing.md) * [Post deployment guidance](/deployment/ndr-virtual-cloud-appliances/kvm-brain/post-deployment-guidance.md) {% endhint %} {% stepper %} {% step %} ### Download the .OVA or QCOW2 images * Download the .OVA or QCOW2 Brain appliance images from * To see the download option, you must be logged into your Vectra Support Portal account. * The deployment instructions linked in Step 2 below contain additional instruction on which image to choose from the support portal. {% endstep %} {% step %} ### Deploy the .OVA or QCOW2 images Deploy OVA in KVM and power on the appliance using one of the below methods: * [Brain deployment in Proxmox](/deployment/ndr-virtual-cloud-appliances/kvm-brain/brain-deployment-in-proxmox.md) - Uses .OVA image. * [Brain deployment in other KVM Virtual Machine Managers](/deployment/ndr-virtual-cloud-appliances/kvm-brain/brain-deployment-in-generic-kvm.md) * Can use the .OVA image if your virtual machine manager supports it. * Can also manually create the VM from the provided .qcow2 disk images. * Essentially, if you are not using Proxmox or Libvrt, follow these instructions for all other KVM Brain deployments. * [Brain deployment in Libvirt](/deployment/ndr-virtual-cloud-appliances/kvm-brain/brain-deployment-in-libvirt.md) - Uses .qcow2 disk images {% endstep %} {% step %} ### License the Brain These instructions summarize the steps. Additional detail is provided in [Initial startup and licensing](/deployment/ndr-virtual-cloud-appliances/kvm-brain/initial-startup-and-licensing.md). * Browse to the IP assigned to the Brain’s management interface to see the initial boot status messages. The status message screen will update but a manual refresh is required to display any new information. * When you are able to see the **System Setup and Provisioning** screen, enter proxy information if required for your environment and then enter the **License configuration** screen. * Copy the licensing request code from the Vectra UI. * Back on the Vectra customer portal, paste the license request code into the Licensing Request form in the **Enter Authorization Code** box available at . * Copy the license once generated and paste it into the Vectra UI **Licensing Information** box. * Select the virtual machine management software you are using from the dropdown menu. This is currently used for research purposes only and does not change the behavior of the Brain. {% hint style="warning" %} **Please Note:** If your Brain deployment will not be online (connected to Vectra’s provisioner/updater system, this is only supported for Quadrant UX deployments), check the **Offline** box to enable an offline deployment. This means all licensing functions will be done manually offline. * If the **Offline** box is not checked prior to hitting the **Save** button, the deployment will fail and will need to be started over with a fresh deployment of the OVF template. * [Offline updates](/operations/readme-1/offline-updates-v89.md) mode is automatically enabled when selecting the offline deployment mode. * KVM Brains deployed in offline mode can **never** be updated online. {% endhint %} * Click **Save** on the licensing configuration screen. {% endstep %} {% step %} #### Complete Provisioning These instructions summarize the steps. Additional detail is provided in [Initial startup and licensing](/deployment/ndr-virtual-cloud-appliances/kvm-brain/initial-startup-and-licensing.md). * After the license is validated, the file system will be decrypted, a performance test will be run, the Brain will reboot, and the Brain will reach out to the Vectra provisioning server and complete provisioning (if the deployment is in online mode). * Offline Brains follow a similar process but do not need to communicate with the provisioning server and can validate the license locally. * Finally, a success message will be presented with a button to redirect to the main UI login screen. * For RUX deployments, please see the deployment process in the [Vectra Respond UX Deployment Guide](/deployment/getting-started/respond-ux-deployment-guide.md). {% hint style="warning" %} **Please Note:** When doing a RUX deployment, you should **NOT** login and configure anything in the Quadrant UX (which would be available at this point) before Vectra connects your Brain to the Vectra cloud. Once the Brain is connected to the Vectra Cloud, the UI for your deployment (Respond UX) will be served from Vectra's cloud and the local UI (Quadrant UX) will no longer be available. {% endhint %} * For QUX deployments only: * Initial login credentials for the UI: * `admin` / `changethispassword` * Initial login credentials for the SSH access to the CLI: * `vectra` / `changethispassword` * You will be asked to change the password after the initial login. * Complete your configuration using instructions available in the [Vectra Respond UX Deployment Guide](/deployment/getting-started/respond-ux-deployment-guide.md) or [Vectra Quadrant UX Deployment Guide](/deployment/getting-started/quadrant-ux-deployment.md). {% endstep %} {% endstepper %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.vectra.ai/deployment/ndr-virtual-cloud-appliances/kvm-brain/licensing-and-brain-deployment-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.