> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zentitle2-docs/use-cases/use-case-directory/virtualized-environments.md). # Virtualized Environments Stop license abuse from cloned VMs using Zentitle's nonce-based validation, which detects duplicated instances and denies a refresh request from the clone. ### Stop license abuse on VMs {% embed url="" %} Stop revenue leakage from casual and intentional license abuse when VMs are duplicated with your software installed. Turn this into the additional license sales required. Virtualized environments are everywhere—whether it's full VMs, Docker containers, or individual desktops. Many desktops running Windows 11+, for example, present themselves as being virtualized and are indeed virtualized environments under the hood. We wanted to build excellent support for virtualized image detection and cloning protection to ensure you get properly paid for every license seat you sell to customers. We accomplish this using a technique called the nonce—think of it as a transient secret. Every time the application communicates with the Zentitle Cloud during license refresh, we generate a new nonce from the search server registered to that individual instance. When that instance stores the nonce and makes a subsequent request, it must provide that same nonce. We validate this nonce to authenticate using that license seat, then generate a new nonce to send back to the client. If a process receives its nonce and clones itself, Process One and Process Two will have the same secret. The first process to make a refresh request will have its seat validated by the Zentitle Cloud and receive a new nonce. However, the other process will no longer know the current nonce, so its request will be denied when it attempts a refresh. When this happens, that process realizes it has lost its seat to a clone. At this point, the application can decide whether to try checking out another seat against the license—it's up to you as the vendor to define what policy to enforce when we detect that a clone has claimed that seat. See more in the [Virtual Machine Control](/zentitle2-docs/developers/virtual-machine-control.md) topic. {% hint style="success" %} Let's jump on a call and discuss how we can help, get in touch with your account manager today → [Setup a 1:1 discussion](https://www.nalpeiron.com/get-a-11-demo.html) {% endhint %} --- # 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.nalpeiron.com/zentitle2-docs/use-cases/use-case-directory/virtualized-environments.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.