Full Description
For ensuring a software system's security, it is vital to keep up with changing security precautions, attacks, and mitigations. Although model-based development enables addressing security already at design-time, design models are often inconsistent with the implementation or among themselves. An additional burden are variants of software systems. To ensure security in this context, we present an approach based on continuous automated change propagation, allowing security experts to specify security requirements on the most suitable system representation. We automatically check all system representations against these requirements and provide security-preserving refactorings for preserving security compliance. For both, we show the application to variant-rich software systems. To support legacy systems, we allow to reverse-engineer variability-aware UML models and semi-automatically map existing design models to the implementation. Besides evaluations of the individual contributions, we demonstrate the approach in two open-source case studies, the iTrust electronics health records system and the Eclipse Secure Storage.
Contents
Introduction.- Running Example: iTrust.- State of the Art in Secure Software Systems Development.- A Walkthrough of the Proposed Development Approach.- Program Model for Object-oriented Languages.- Model-Synchronization and Tracing.- Application to Legacy Projects using Reverse-Engineering.- Static Security Compliance Checks.- Verification and Enforcement of Security at Run-time.- Specification of Variability throughout Variant-rich Software Systems.- Security in UML Product Lines.- Security Compliance and Restructuring in Variant-rich Software Systems.- The GRaViTY Framework.- Case Studies.- Related Work.- Conclusion.
