{'fraction_non_alphanumeric': 0.013333333333333334, 'fraction_numerical': 0.0, 'mean_word_length': 5.877862595419847, '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}}
Incorporating Service Degradations into a Security Plan

Computer systems invest substantial resources in securing their services. Costs of failure prevention are balanced against those of detection and recovery, both of which typically involve substantial degradations. Most computer users consider degradations of service to be insidious and injurious. Yet, degradations commonly assist in both the prevention and the curtailment of failures. Their toleration enables service continuation following fault activation, during which degradations are monitored for symptoms of security breaches. A systematic approach to degradations should be incorporated into security plans. We propose a template in which service degradations are classified according to their usage and their impact on services within the different stages of a system's lifecycle. Such standardization will promote system security.