{'fraction_non_alphanumeric': 0.01644736842105263, 'fraction_numerical': 0.0008223684210526315, 'mean_word_length': 4.58256880733945, '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}}
Preventing and unifying threats in cyberphysical systems

Although there are numerous works on the security of CPSs only a few address general aspects of their threats. A good amount of the security work on CPS is about attack detection; their methods of analyzing threats and their effects on CPSs can characterize them but not provide ways to prevent them. System approaches take an input/output view, we detect the inputs and we correct the outputs. However, a complex system has a large number of inputs, physically distributed, where a large number of threats can be applied. We need to know the location of specific threats and stop them in their point of entrance in the system. We are intending to do just that by relating our identified threats to a Security Reference Architecture such as the one we built for cloud systems [2]; Reference Architectures have been used to trace the propagation of attacks but not to find where to stop them. There is also an enormous variety of threats, specific to each type of system; we intend to show that many of them are similar in effect and can be prevented in similar ways. Finally, we believe that threat patterns are a better attack description than other models.