Skip to main content
U.S. flag

An official website of the United States government

Dot gov

The .gov means it’s official.
Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you’re on a federal government site.

Https

The site is secure.
The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.

A Methodology for Enabling Forensic Analysis Using Hypervisor Vulnerabilities Data: NIST Publishes NIST Internal Report 8221

NIST announces the publication of NISTIR 8221, "A Methodology for Enabling Forensic Analysis Using Hypervisor Vulnerabilities Data."

Hardware/Server Virtualization is a foundational technology in a cloud computing environment and the hypervisor is the key software in that virtualized infrastructure. However, hypervisors are large pieces of software with several thousand lines of code and are therefore known to have vulnerabilities. Hence, a capability to perform forensic analysis to detect, reconstruct and prevent attacks based on vulnerabilities on an ongoing basis is a critical requirement in cloud environments.

To gain a better understanding of recent hypervisor vulnerabilities and attack trends, identify forensic information needed to reveal the presence of such attacks, and develop guidance on taking proactive steps to detect and prevent those attacks, NIST has published NIST Internal Report (NISTIR) 8221, A Methodology for Enabling Forensic Analysis Using Hypervisor Vulnerabilities Data, which outlines a methodology to enable this forensic analysis.

Two open-source hypervisors—Xen and Kernel-based Virtual Machine (KVM)—were chosen as platforms to illustrate the methodology; the source for vulnerability data is NIST’s National Vulnerability Database (NVD).  The methodology is broken into three steps:

  1. Classify the vulnerabilities based on three categories: hypervisor functionality where the vulnerability exists, attack type, and attack source. The outcome of this step is to obtain the relative distribution of recent hypervisor vulnerabilities for the two products in the three categories.
  2. Identify the hypervisor functionality that is most impacted, then build and run sample attacks, along with logging system calls.
  3. Perform an iterative process that identifies gaps in the evidence data required for fully detecting and reconstructing those attacks and to identify techniques required to gather the needed evidence during subsequent attack runs.
Released June 5, 2019, Updated June 7, 2019