{'fraction_non_alphanumeric': 0.025477707006369428, 'fraction_numerical': 0.0, 'mean_word_length': 5.044871794871795, '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}}
Towards a trusted immutable kernel extension (TIKE) for self-healing systems: a virtual machine approach

The conventional method to restore a compromised system is to wipe the system clean, install from known good media, and patch with the latest updates: a costly, restrictive, and inefficient method. An alternative method is to monitor the host and restore trust if a compromise occurs. When this method is automated, the system is said to be self-healing. One critical requirement of a self-healing system is that the self-healing mechanism itself must not be compromised. Our solution to this requirement is a trusted immutable kernel extension (TIKE) by way of a virtual machine. Using a host operating system as a trusted platform, we discuss a self-healing system that uses existing intrusion detection systems and corresponding self-healing mechanisms to automatically heal the guest operating system once a compromise has occurred.