Consistency Management for Security Annotations for Continuous Verification

Analyses on the architecture of systems can yield valuable insights into a system even before it is built. The applicability of the results of these design time analyses to the system requires the system to be built according to its specification, i.e., to not violate constraints defined on the architecture. The conformance of the results of static code analyses and design time analyses ensures the system is built according to its specification. The first step for conforming results of these analyses is to ensure that the system and its specification is represented consistently in the input of the design time analysis and static code analysis, i.e., they comprise corresponding system elements and specifications for them. To achieve conforming inputs, we used consistency specifications between architecture and code models and implemented them between annotation models that enrich the architecture description with security annotations on the architecture level, as well as security annotations on the code level. This allows the continuous conformance checking during implementation and later during evolution of the system. We implemented the consistency specifications in the Vitruvius framework for an ADL and Java and tested it on case studies.

Authors

Institutions

Publication Details

Published
2024-09-22
DOI
https://doi.org/10.1145/3652620.3687821
Citations
2
Primary Topic
Security and Verification in Computing
Type
article
Field-Weighted Citation Impact
0.69
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
article

Consistency Management for Security Annotations for Continuous Verification

Frederik Reiche, Sam L. Becker, Erik Bürger, Robert Heinrich et al.
2 citations
Security and Verification in Computing
0.69
article

Consistency Management for Security Annotations for Continuous Verification

Frederik Reiche, Sam L. Becker, Erik Bürger, Robert Heinrich, Thomas Weber, Sebastian Weber
article en
2 citations

Abstract

Analyses on the architecture of systems can yield valuable insights into a system even before it is built. The applicability of the results of these design time analyses to the system requires the system to be built according to its specification, i.e., to not violate constraints defined on the architecture. The conformance of the results of static code analyses and design time analyses ensures the system is built according to its specification. The first step for conforming results of these analyses is to ensure that the system and its specification is represented consistently in the input of the design time analysis and static code analysis, i.e., they comprise corresponding system elements and specifications for them. To achieve conforming inputs, we used consistency specifications between architecture and code models and implemented them between annotation models that enrich the architecture description with security annotations on the architecture level, as well as security annotations on the code level. This allows the continuous conformance checking during implementation and later during evolution of the system. We implemented the consistency specifications in the Vitruvius framework for an ADL and Java and tested it on case studies.

Karlsruhe Institute of Technology (DE), FZI Research Center for Information Technology (DE), Software (Germany) (DE)
Openalex Percentile: Top 23%
Security and Verification in Computing
0.69
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.