{'fraction_non_alphanumeric': 0.014285714285714285, 'fraction_numerical': 0.0, 'mean_word_length': 5.5703125, '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}}
Safety Critical Systems Formal Verification Using Execution Traces

Data breaches usually involve financial information such as credit card or bank details. Automated formal verification of safety critical systems has been mostly focused on analysing high-level abstract models which, however, are significantly different from real implementations written in programming languages. In this paper we propose a technique that links model checking verification closer to real implementations, with particular regard to financial environment, in order to identify possible causes of data breaches. A formal model starting from execution traces is retrieved. Thus, the discovered model can be analysed to verify it respects the defined properties. A real safety critical system has been used as a case study to evaluate the proposed methodology.