{'fraction_non_alphanumeric': 0.023833167825223437, 'fraction_numerical': 0.0, 'mean_word_length': 5.904109589041096, '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}}
Identifying Security Issues with MBSE while Rebuilding Legacy Software Systems

in this paper, we introduce how Model-based System Engineering (MBSE) could be leveraged in order to tackle security issues while recreating legacy software systems. Originally, MBSE was dedicated to managing the complex system creation in terms of system requirements, design, analysis, verification and validation activities leaving security aspects aside. However, previous research shows that security analysis activity could be integrated into MBSE activity and powerful MBSE tools such as change impact analysis, simulation, validation, and verification could be successfully applied in cross-cutting disciplines. The paper presents guidelines on how and when to apply various security techniques (e.g. security requirements, misuse cases, attack scenarios) in the MBSE environment. The case study demonstrates and proves the adaptability of the security guidelines on the realworld software system modernization project.