{'fraction_non_alphanumeric': 0.022585669781931463, 'fraction_numerical': 0.001557632398753894, 'mean_word_length': 5.237864077669903, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
K-binID: Kernel binary code identification for Virtual Machine Introspection

Virtual Machine Introspection (VMI) techniques generally employ kernel symbols to obtain addresses of kernel data and functions of interest to monitor guest OS states and activities. However, employing kernel symbols in an Infrastructure as a Service (IaaS) cloud presumes perfect knowledge of what kernel version and customization is running in an introspected VM. Moreover, existing kernel fingerprinting techniques are limited in precision and usability due to insufficient coverage of kernel code. So they are not suitable for IaaS cloud. In this paper, we present K-binID, a set of new automatic and OS-independent techniques based on static binary code analysis that enables the hypervisor to precisely identify version and customization of VM main kernel binary code (among a set of known kernels). K-binID achieves this in black-box regardless of challenges presented by compiler optimizations and kernel base address randomization. We designed and implemented our prototype of K-binID on KVM hypervisor. K-binID evaluation on a variety of Linux kernel binary code versions shows that, in 1 to 5 seconds, K-binID identifies precisely both the kernel version and customization of all tested kernels.