U.S. flag   An unofficial archive of your favorite United States government website
Dot gov

Official websites do not use .rip
We are an unofficial archive, replace .rip by .gov in the URL to access the official website. Access our document index here.

Https

We are building a provable archive!
A lock (Dot gov) or https:// don't prove our archive is authentic, only that you securely accessed it. Note that we are working to fix that :)

This is an archive
(replace .gov by .rip)

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

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.

Related Topics

Security and Privacy: vulnerability management

Technologies: cloud & virtualization

Applications: forensics

Created June 05, 2019, Updated June 22, 2020