Secure Change: Security Engineering for Lifelong Evolvable Systems

Software systems in practice are becoming increasingly long-lived, often without this being planned for from the outset. An example of this is the Y2K problem, which arose because developers did not expect their software to be used beyond the year 2000. At the same time, software systems are continuously evolving, even after their initial deployment. This raises the question of how to organize this evolutionary process to ensure that the originally required critical requirements are not invalidated by the evolutionary process. The "Secure Change" project has developed an approach that solves this problem, especially for the fulfillment of IT security requirements. The contribution of TU Dortmund University focused on the model-based security analysis of security requirements for evolving systems.