> For the complete documentation index, see [llms.txt](https://community.peerplays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.peerplays.com/risk-register/introduction/bunker-issue/hypervisor-compromised.md). # Hypervisor Compromised ## Description If the attacker has the control over the hypervisor, then the full access to VMs will be under threat. In order to overcome this situation, the following plans and ideas can be helpful. The document outcome is the ideas discussed among the SMEs. ## Mitigation Ideas 1. Limit the access to admin 2. PEN Testing the accounts to evaluate the security. Example: Brute force test on password. 3. Having Backups of Hypervisor and nodes for Fallback/re-deployment 4. Performing Audits periodically ## Response Plan 1. Updated backups that can be written over the compromised systems. 2. A Kill-switch to stop the process. ## Responder Team In order to find the solution/ to know in details about the risk that has happened, responder team is one to be communicated first. ### First Responder Team **Point of Contact:** Rily and/or Robert ### Second Responder Team **Point of Contact:** Kyle and Haxhi --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://community.peerplays.com/risk-register/introduction/bunker-issue/hypervisor-compromised.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.