Research Topics
Research Topic Compliance
Key issues:- Standards
- Laws
- Pattern
- Privacy
| Year | Title | Author | Journal/Proceedings | Publisher | |
|---|---|---|---|---|---|
| 2017 | A structured and systematic model-based development method for automotive systems, considering the OEM/supplier interface | Beckers, K., Côté, I., Frese, T., Hatebur, D. & Heisel, M. | Reliability Engineering & System Safety | ||
| Abstract: Abstract The released ISO 26262 standard for automotive systems requires to create a hazard analysis and risk assessment and to create safety goals, to break down these safety goals into functional safety requirements in the functional safety concept, to specify technical safety requirements in the safety requirements specification, and to perform several validation and verification activities. Experience shows that the definition of technical safety requirements and the planning and execution of validation and verification activities has to be done jointly by OEMs and suppliers. In this paper, we present a structured and model-based safety development approach for automotive systems. The different steps are based on Jackson's requirement engineering. The elements are represented by UML notation extended with stereotypes. The UML model enables a rigorous validation of several constraints. We make use of the results of previously published work to be able to focus on the OEM/supplier interface. We illustrate our method using a three-wheeled-tilting control system (3WTC) as running example and case study. | |||||
BibTeX:
@article{Beckers2016-4,
year = {2017},
title = {A structured and systematic model-based development method for automotive systems, considering the OEM/supplier interface},
author = {Beckers, Kristian and C{\^{o}}t{\'{e}}, Isabelle and Frese, Thomas and Hatebur, Denis and Heisel, Maritta},
journal = {Reliability Engineering \& System Safety},
volume = {158},
pages = {172 - 184},
note = {Special Sections : Reliability and Safety Certification of Software-Intensive Systems},
url = {http://www.sciencedirect.com/science/article/pii/S0951832016304057},
doi = {10.1016/j.ress.2016.08.018}
}
|
|||||
| 2017 | A structured hazard analysis and risk assessment method for automotive systems—A descriptive study | Beckers, K., Holling, D., Côté, I. & Hatebur, D. | Reliability Engineering & System Safety | ||
| Abstract: Abstract The 2011 release of the first version of the ISO 26262 standard for automotive systems demand the elicitation of safety goals following a rigorous method for hazard and risk analysis. Companies are struggling with the adoption of the standard due to ambiguities, documentation demands and the alignment of the standards demands to existing processes. We previously proposed a structured engineering method to deal with these problems developed in applying action research together with an OEM. In this work, we evaluate how applicable the method is for junior automotive software engineers by a descriptive study. We provided the method to 8 members of the master course Automotive Software Engineering (ASE) at the Technical University Munich. The participants have each been working in the automotive industry for 1–4 years in parallel to their studies. We investigated their application of our method to an electronic steering column lock system. The participants applied our method in a first round alone and afterwards discussed their results in groups. Our data analysis revealed that the participants could apply the method successfully and the hazard analysis and risk assessment achieved a high precision and productivity. Moreover, the precision could be improved significantly during group discussions. | |||||
BibTeX:
@article{Beckers2016-5,
year = {2017},
title = {A structured hazard analysis and risk assessment method for automotive systems—A descriptive study},
author = {Beckers, Kristian and Holling, Dominik and C{\^{o}}t{\'{e}}, Isabelle and Hatebur, Denis},
journal = {Reliability Engineering & System Safety},
volume = {158},
pages = {185 - 195},
note = {Special Sections : Reliability and Safety Certification of Software-Intensive Systems},
url = {http://www.sciencedirect.com/science/article/pii/S0951832016305002},
doi = {10.1016/j.ress.2016.09.004}
}
|
|||||
| 2017 | Deriving Safety Requirements according to ISO 26262 for complex systems: A method applied in the automotive industrie | Frese, T., Heisel, M., Hatebur, D. & Côté, I. | Innovative Produkte und Dienstleisungen in der Mobilität | ||
BibTeX:
@article{mobi2017,
year = {2017},
title = {Deriving Safety Requirements according to ISO 26262 for complex systems: A method applied in the automotive industrie},
author = {Frese, Thomas and Heisel, Maritta and Hatebur, Denis and C{\^{o}}t{\'{e}}, Isabelle},
journal = {Innovative Produkte und Dienstleisungen in der Mobilit{\"{a}}t},
volume = {Wissenschaftsforum Mobilit{\"{a}}t 8},
pages = {211-222}
}
|
|||||
| 2015 | A Structured Validation and Verification Method for Automotive Systems considering the OEM/Supplier Interface | Beckers, K., Côté, I., Frese, T., Hatebur, D. & Heisel, M. | Proceedings of the International Conference on Computer Safety, Reliability and Security (SAFECOMP) | Springer | |
| Abstract: The released ISO 26262 standard for automotive systems requires several validation and verification activities. These validation and verification activities have to be planned and performed jointly by the OEMs and the suppliers. In this paper, we present a systematic, structured and model-based method to plan the required validation and verification activities and collect the results. Planning and the documentation of performed activities are represented by a UML notation extended with stereotypes. The UML model supports the creation of the artifacts required by ISO 26262, enables document generation and a rigorous check of several constraints expressed in OCL. We illustrate our method using the example of an electronic steering column lock system. | |||||
BibTeX:
@inproceedings{fs2015,
year = {2015},
title = {A Structured Validation and Verification Method for Automotive Systems considering the OEM/Supplier Interface},
booktitle = {Proceedings of the International Conference on Computer Safety, Reliability and Security (SAFECOMP)},
author = {Beckers, Kristian and C{\^{o}}t{\'{e}}, Isabelle and Frese, Thomas and Hatebur, Denis and Heisel, Maritta},
publisher = {Springer},
volume = {9337},
pages = {90 - 107},
url = {www.springer.com}
}
|
|||||
| 2015 | A Pattern-Based and Tool-Supported Risk Analysis Method Compliant to ISO 27001 for Cloud Systems | Alebrahim, A., Faßbender, S., Hatebur, D., Goeke, L. & Côté, I. | International Journal of Secure Software Engineering (IJSSE) | ||
| Abstract: Security plays a major role when companies decide whether to move to the cloud and use cloud services. One way to obtain the confidence of the customers is to establish security mechanisms when using clouds. The ISO 27001 standard provides general concepts for establishing information security in an organization. Risk analysis is an essential part in the ISO 27001 standard for achieving information security. This standard, however, contains ambiguous descriptions. In addition, it does not stipulate any method to identify assets, threats, and vulnerabilities. In this paper, we present a structured and pattern based method to conduct risk analysis for cloud computing systems. It is tailored to SMEs. Our method addresses the requirements of the ISO 27001. We make use of the cloud system analysis pattern, security requirement patterns, threat patterns, and control patterns for conducting the risk analysis. The method is illustrated by a cloud logistics application example. | |||||
BibTeX:
@article{IJSSE2015,
year = {2015},
title = {A Pattern-Based and Tool-Supported Risk Analysis Method Compliant to ISO 27001 for Cloud Systems},
author = {Alebrahim, Azadeh and Fa{\ss}bender, Stephan and Hatebur, Denis and Goeke, Ludger and C{\^{o}}t{\'{e}}, Isabelle},
journal = {International Journal of Secure Software Engineering (IJSSE)},
volume = {6},
number = {1},
pages = {24-46},
url = {http://www.igi-global.com/chapter/a-pattern-based-and-tool-supported-risk-analysis-method-compliant-to-iso-27001-for-cloud-systems/128695}
}
|
|||||
| 2014 | Supporting Common Criteria Security Analysis with Problem Frames | Beckers, K., Hatebur, D. & Heisel, M. | Journal of Wireless Mobile Networks, Ubiquitous Computing, and Dependable Applications (JoWUA) | Innovative Information Science & Technology Research Group (ISYOU) | |
| Abstract: Security standards, e.g., the Common Criteria (ISO 15408), are applied by software vendors to establish a level of confidence that the security functionality of their products and their applied assurance measures are sufficient. To get a Common Criteria certification, a comprehensible set of documents is necessary, including a detailed threat analysis and security objective elicitation. We focus on improving the Common Criteria threat analysis and the derivation of security objectives in our work. Our method is based upon an attacker model, which considers different attacker types, e.g., software attackers, that threaten only specific parts of a system. We provide tool support for checking the consistency and the completeness of the specified software systems using OCL expressions. For example, we check if all types of attackers have been considered for a specific domain, we check for all software domains that either a software attacker is considered or an assumption is documented that excludes software attackers, and we check if all threats are addressed by security objectives. Moreover, we can generate tables and texts from our UML models to satisfy the Common Criteria documentation demands. For instance, we can generate Common Criteria specific cross-table, which maps every security objective and assumption to a specific threat. The consistency checks are integrated in our structured method for threat analysis that considers the Common Criteria’s (CC) demands for documentation of the system in its environment and the reasoning that all threats are discovered and addressed. With our support tool UML4PF (that extends a UML tool and contains e.g., a UML profile and an OCL validator), we support security reasoning, validation of models, and we are able to generate Common Criteria-compliant documentation using model-to-text transformations. Our threat analysis method can also be used for threat analysis without the common criteria, because it uses a specific part of the UML profile that can be adapted to other demands with little effort. For example, it could be adapted for other security standards like ISO 27001.We illustrate our approach with the development of a smart metering gateway system. |
|||||
BibTeX:
@article{Beckers2014-Jowua,
year = {2014},
title = {Supporting Common Criteria Security Analysis with Problem Frames},
author = {Beckers, Kristian and Hatebur, Denis and Heisel, Maritta},
journal = {Journal of Wireless Mobile Networks, Ubiquitous Computing, and Dependable Applications (JoWUA)},
publisher = {Innovative Information Science \& Technology Research Group (ISYOU)},
volume = {5},
number = {1},
pages = {37-63},
url = {http://isyou.info/}
}
|
|||||
| 2014 | Goal-based Establishment of an Information Security Management System compliant to ISO 27001 [BibTeX] |
Beckers, K. | SOFSEM 2014: Theory and Practice of Computer Science | Springer Berlin Heidelberg | |
BibTeX:
@incollection{Beckers2014-sofsem,
year = {2014},
title = {Goal-based Establishment of an Information Security Management System compliant to ISO 27001},
booktitle = {SOFSEM 2014: Theory and Practice of Computer Science},
author = {Beckers, Kristian},
publisher = {Springer Berlin Heidelberg},
series = {LNCS 8327},
note = {accepted for publication},
url = {http://www.springerlink.com/}
}
|
|||||
| 2014 | A Meta-Pattern and Pattern Form For Context-Patterns | Beckers, K., Faßbender, S. & Heisel, M. | Proceedings of the 19th European Conference on Pattern Languages of Programs (Europlop) | ACM | |
| Abstract: In a previous EuroPlop publication we introduced a catalog of context-patterns.We described common structures and stakeholders for several different domains in our context-patterns. The common elements of the context were obtained from observations about the domain in terms of standards, domain specific-publications, and implementations. Whenever a system-to-be is already described by a context-pattern, one can use this context-pattern to elicit domain knowledge via instantiation of the context-pattern. Moreover, we analyzed the common concepts in our context-patterns and created a meta-model to describe the relations between these concepts. This meta-model was the initial step towards a pattern language for context-patterns. In this work, we show the consequent next step for the definition of a pattern language for context-patterns. |
|||||
BibTeX:
@inproceedings{BeckersFassbender2014-europlop-A,
year = {2014},
title = {A Meta-Pattern and Pattern Form For Context-Patterns},
booktitle = {Proceedings of the 19th European Conference on Pattern Languages of Programs (Europlop)},
author = {Beckers, Kristian and Fa{\ss}bender, Stephan and Heisel, Maritta},
publisher = {ACM},
series = {EuroPloP'14},
pages = {5:1--5:23},
url = {http://doi.acm.org/10.1145/2721956.2721979},
doi = {10.1145/2721956.2721979}
}
|
|||||
| 2014 | A Threat Analysis Methodology for Smart Home Scenarios | Beckers, K., Faßbender, S., Heisel, M. & Suppan, S. | Smart Grid Security, Proceddings of the Second International Workshop (SmartGridSec) | Springer | |
| Abstract: A smart grid is envisioned to enable a more economic, environmen- tal friendly, sustainable and reliable supply of energy. But significant security concerns have to be addressed for the smart grid, dangers range from threatened availability of energy, to threats of customer privacy. This paper presents a struc- tured method for identifying security threats in the smart home scenario and in particular for analyzing their severity and relevance. The method is able to unveil also new threats, not discussed in the literature before. The smart home scenario is represented by a context-pattern, which is a specific kind of pattern for the elic- itation of domain knowledge [5]. Hence, by exchanging the smart home pattern by a context-pattern for another domain, e.g., clouds, our method can be used for these other domains, as well. The proposal is based on Microsoft’s Security Development Lifecycle (SDL) [4], which uses Data Flow diagrams, but proposes new alternatives for scenario definition and asset identification based on context- patterns. These alleviate the lack of scalability of the SDL. In addition, we present Attack Path DFDs, that show how an attacker can compromise the system. |
|||||
BibTeX:
@inproceedings{BFassbenderHS2014,
year = {2014},
title = {A Threat Analysis Methodology for Smart Home Scenarios},
booktitle = {Smart Grid Security, Proceddings of the Second International Workshop (SmartGridSec)},
author = {Beckers, Kristian and Fa{\ss}bender, Stephan and Heisel, Maritta and Suppan, Santiago},
publisher = {Springer},
volume = {8448},
series = {Lecture Notes in Computer Science},
pages = {94-124},
url = {http://link.springer.com/chapter/10.1007/978-3-319-10329-7_7},
doi = {10.1007/978-3-319-10329-7_7}
}
|
|||||
| 2014 | ISMS-CORAS: A Structured Method for Establishing an ISO 27001 Compliant Information Security Management System [BibTeX] |
Beckers, K., Heisel, M., Solhaug, B. & Stølen, K. | Advances in Engineering Secure Future Internet Services and Systems | Springer | |
BibTeX:
@inproceedings{BHSS2014,
year = {2014},
title = {ISMS-CORAS: A Structured Method for Establishing an ISO 27001 Compliant Information Security Management System},
booktitle = {Advances in Engineering Secure Future Internet Services and Systems},
author = {Beckers, Kristian and Heisel, Maritta and Solhaug, Bj{\o}rnar and St{\o}len, Ketil},
publisher = {Springer},
number = {8431},
series = {LNCS State-of-the-Art Surveys},
pages = {315-344},
url = {https://link.springer.com/}
}
|
|||||
| 2014 | Pattern-Based and ISO 27001 Compliant Risk Analysis for Cloud Systems | Alebrahim, A., Hatebur, D. & Goeke, L. | Proceedings of the 1st International Workshop on Evolving Security and Privacy Requirements Engineering (ESPRE) | IEEE | |
| Abstract: For accepting clouds and using cloud services by companies, security plays a decisive role. For cloud providers, one way to obtain customers’ confidence is to establish security mechanisms when using clouds. The ISO 27001 standard provides general concepts for establishing information security in an organization. Risk analysis is an essential part in the ISO 27001 standard for achieving information security. This standard, however, contains ambiguous descriptions. In addition, it does not stipulate any method to identify assets, threats, and vulnerabilities. In this paper, we present a structured and patternbased method to conduct risk analysis for cloud computing systems. It is tailored to SMEs. Our method addresses the requirements of the ISO 27001. We make use of the cloud system analysis pattern, security requirement patterns, threat patterns, and control patterns for conducting the risk analysis. The method is illustrated by a cloud logistics application example. | |||||
BibTeX:
@inproceedings{ESPRE2014,
year = {2014},
title = {Pattern-Based and ISO 27001 Compliant Risk Analysis for Cloud Systems},
booktitle = {Proceedings of the 1st International Workshop on Evolving Security and Privacy Requirements Engineering (ESPRE)},
author = {Alebrahim, Azadeh and Hatebur, Denis and Goeke, Ludger},
publisher = {IEEE},
pages = {42-47},
url = {https://www.ieee.org}
}
|
|||||
| 2014 | A Computer Aided Process From Problems to Laws in Requirements Engineering | Faßbender, S. & Heisel, M. | Software Technologies | Springer | |
| Abstract: In today’s world many products and services are highly dependent on software and information systems. With the growing importance of IT systems, legislators worldwide decided to regulate and enforce laws for IT systems. With respect to this situation, the impact of compliance on the development of IT sys- tems becomes more and more severe. Hence, software engineers have a need for techniques to deal with compliance. But identifying relevant compliance regu- lations for IT systems is a challenging task. We proposed patterns and a struc- tured method to tackle these problems [1]. A crucial step is the transformation of requirements into a structure, which allows for the identification of laws. The transformation step was described in general in [2]. This work describes a method to structure the requirements, elicit the needed domain knowledge and transform requirements into law identification pattern instances. The manual execution of this method was reported by us to be time consuming and tedious. Hence, in this work we identify the points for (semi-)automation, and we outline a first imple- mentation for the automation. We present our results using a voting system as an example, which was obtained from the ModIWa DFG1 project and the common criteria profile for voting systems. |
|||||
BibTeX:
@inproceedings{FassbenderH13_SDT,
year = {2014},
title = {A Computer Aided Process From Problems to Laws in Requirements Engineering},
booktitle = {Software Technologies},
author = {Fa{\ss}bender, Stephan and Heisel, Maritta},
publisher = {Springer},
volume = {457},
series = {Communications in Computer and Information Science},
pages = {215-234},
url = {http://link.springer.com/chapter/10.1007%2F978-3-662-44920-2_14},
doi = {10.1007/978-3-662-44920-2_14}
}
|
|||||
| 2014 | A Structured Comparison of Security Standards | Beckers, K., Côté, I., Fenz, S., Hatebur, D. & Heisel, M. | Advances in Engineering Secure Future Internet Services and Systems | Springer | |
| Abstract: A number of di erent security standards exist and it is dif- cult to choose the right one for a particular project or to evaluate if the right standard was chosen for a certi cation. These standards are often long and complex texts, whose reading and understanding takes up a lot of time. We provide a conceptual model for security standards that relies upon existing research and contains concepts and phases of security standards. In addition, we developed a template based upon this model, which can be instantiated for given security standard. These instantiated templates can be compared and help software and security engineers to understand the di erences of security standards. In particular, the instantiated templates explain which information and what level of detail a system document according to a certain security standard contains. We applied our method to the well known international security standards ISO 27001 and Common Criteria, and the German IT-Grundschutz standards, as well. |
|||||
BibTeX:
@inproceedings{Lopez2014,
year = {2014},
title = {A Structured Comparison of Security Standards},
booktitle = {Advances in Engineering Secure Future Internet Services and Systems},
author = {Beckers, Kristian and C{\^{o}}t{\'{e}}, Isabelle and Fenz, Stefan and Hatebur, Denis and Heisel, Maritta},
publisher = {Springer},
number = {8431},
series = {LNCS State-of-the-Art Surveys},
pages = {1-34},
url = {http://www.springerlink.com/}
}
|
|||||
| 2014 | Enhancing Problem Frames with Trust and Reputation for Analyzing Smart Grid Security Requirements [BibTeX] |
Moyano, F., Fernandez-Gago, C., Beckers, K. & Heisel, M. | Proceedings of the Second Open EIT ICT Labs Workshop on Smart Grid Security (SmartGridSec14) | Springer | |
BibTeX:
@inproceedings{MGBH2014,
year = {2014},
title = {Enhancing Problem Frames with Trust and Reputation for Analyzing Smart Grid Security Requirements},
booktitle = {Proceedings of the Second Open EIT ICT Labs Workshop on Smart Grid Security (SmartGridSec14)},
author = {Moyano, Francisco and Fernandez-Gago, Carmen and Beckers, Kristian and Heisel, Maritta},
publisher = {Springer},
series = {LNCS 8448},
pages = {166 -- 180},
url = {http://www.springerlink.com/}
}
|
|||||
| 2014 | A Catalog of Security Requirements Patterns for the Domain of Cloud Computing Systems | Beckers, K., Côté, I. & Goeke, L. | ACM | ||
| Abstract: Security and privacy concerns are essential in cloud computing scenarios, because cloud customers and end customers have to trust the cloud provider with their critical business data and even their IT infrastructure. In projects these are often addressed late in the software development life-cycle, because these are difficult to elicit in cloud scenarios, due to the large amount of stakeholders and technologies involved. We contribute a catalog of security and privacy requirement patterns that support software engineers in eliciting these requirements. As requirements patterns provide artifacts for re-using requirements. This paper shows how these requirements can be classified according to cloud security and privacy goals. Furthermore, we provide a structured method on how to elicit the right requirements for a given scenario. We mined these requirements patterns from existing security analysis of public organizations such as ENISA and the Cloud Security Alliance, from our practical experience in the cloud domain, and from our previous research in cloud security. We validate our requirements patterns in co-operation with industrial partners of the ClouDAT project. |
|||||
BibTeX:
@inproceedings{SAC2014,
year = {2014},
title = {{A Catalog of Security Requirements Patterns for the Domain of Cloud Computing Systems}},
author = {Beckers, Kristian and C{\^{o}}t{\'{e}}, Isabelle and Goeke, Ludger},
publisher = {ACM},
url = {http://dl.acm.org/}
}
|
|||||
| 2014 | Systematic Derivation of Functional Safety Requirements for Automotive Systems | Beckers, K., Côté, I., Frese, T., Hatebur, D. & Heisel, M. | Proceedings of the International Conference on Computer Safety, Reliability and Security (SAFECOMP) | Springer | |
| Abstract: The released ISO 26262 standard for automotive systems requires breaking down safety goals from the hazard analysis and risk assessment into functional safety requirements in the functional safety concept. It has to be justi ed that the de ned functional safety requirements are suitable to achieve the stated safety goals. In this paper, we present a systematic, structured and model-based method to de ne functional safety requirements using a given set of safety goals. The rationale for safety goal achievement, the relevant attributes of the functional safety requirements, and their relationships are represented by a UML notation extended with stereotypes. The UML model enables a rigorous validation of several constraints expressed in OCL. We illustrate our method using an example electronic steering column lock system. |
|||||
BibTeX:
@inproceedings{safecomp2014,
year = {2014},
title = {{Systematic Derivation of Functional Safety Requirements for Automotive Systems}},
booktitle = {Proceedings of the International Conference on Computer Safety, Reliability and Security (SAFECOMP)},
author = {Beckers, Kristian and C{\^{o}}t{\'{e}}, Isabelle and Frese, Thomas and Hatebur, Denis and Heisel, Maritta},
publisher = {Springer},
series = {LNCS 8666},
pages = {65--80},
url = {https://link.springer.com/}
}
|
|||||
| 2013 | A Problem-based Threat Analysis in compliance with Common Criteria | Beckers, K., Hatebur, D. & Heisel, M. | Proceedings of the International Conference on Availability, Reliability and Security (ARES) | IEEE Computer Society | |
| Abstract: In order to gain their customers’ trust, software vendors can certify their products according to security standards, e.g., the Common Criteria (ISO 15408). A Common Criteria certification requires a comprehensible documentation of the software product, including a detailed threat analysis. In our work, we focus on improving that threat analysis. Our method is based upon an attacker model, which considers attacker types like software attacker that threaten only specific parts of a system. We use OCL expressions to check if all attackers for a specific domain have been considered. For example, we propose a computer-aided method that checks if all software systems have either considered a software attacker or documented an assumption that excludes software attackers. Hence, we propose a structured method for threat analysis that considers the Common Criteria’s (CC) demands for documentation of the system in its environment and the reasoning that all threats are discovered. We use UML4PF, a UML profile and support tool for Jackson’s problem frame method and OCL for supporting security reasoning, validation of models, and also to generate Common Criteria-compliant documentation. Our threat analysis method can also be used for threat analysis without the common criteria, because it uses a specific part of the UML profile that can be adapted to other demands with little effort. We illustrate our approach with the development of a smart metering gateway system. |
|||||
BibTeX:
@inproceedings{Beckers2013-ares1,
year = {2013},
title = {A Problem-based Threat Analysis in compliance with Common Criteria},
booktitle = {Proceedings of the International Conference on Availability, Reliability and Security ({ARES})},
author = {Beckers, Kristian and Hatebur, Denis and Heisel, Maritta},
publisher = {IEEE Computer Society},
pages = {111-120},
url = {http://www.ieee.org/}
}
|
|||||
| 2013 | A mapping between ITIL and ISO 27001 processes for use by a high availability video conference service provider [BibTeX] |
Beckers, K., Hofbauer, S., Quirchmayr, G. & Wills, C. C. | Proceedings of the International Cross Domain Conference and Workshop (CD-ARES 2013) | Springer | |
BibTeX:
@inproceedings{Beckers2013-cdares1,
year = {2013},
title = {A mapping between ITIL and ISO 27001 processes for use by a high availability video conference service provider},
booktitle = {Proceedings of the International Cross Domain Conference and Workshop (CD-ARES 2013)},
author = {Beckers, Kristian and Hofbauer, Stefan and Quirchmayr, Gerald and Wills, Christopher C.},
publisher = {Springer},
series = {LNCS 8127},
pages = {224-239},
url = {http://www.springerlink.com/}
}
|
|||||
| 2013 | A Structured and Model-Based Hazard Analysis and Risk Assessment Method for Automotive Systems | Beckers, K., Frese, T., Hatebur, D. & Heisel, M. | Proceedings of the 24th IEEE International Symposium on Software Reliability Engineering | IEEE Computer Society | |
| Abstract: The released ISO 26262 standard requires a hazard analysis and risk assessment for automotive systems to determine the necessary safety measures to be implemented for a certain feature. In this paper, we present a structured and model-based hazard analysis and risk assessment method for automotive systems. The hazard analysis and risk assessment are based on a requirements engineering process using problem frames. Their elements are represented by a UML notation extended with stereotypes. The UML model enables a rigorous validation of several constraints expressed in OCL. We illustrate our method using an electronic steering column lock system. |
|||||
BibTeX:
@inproceedings{Beckers2013-issre,
year = {2013},
title = {A Structured and Model-Based Hazard Analysis and Risk Assessment Method for Automotive Systems},
booktitle = {Proceedings of the 24th IEEE International Symposium on Software Reliability Engineering},
author = {Beckers, Kristian and Frese, Thomas and Hatebur, Denis and Heisel, Maritta},
publisher = {IEEE Computer Society},
pages = {238-247},
url = {http://www.ieee.org/}
}
|
|||||
| 2013 | Common Criteria CompliAnt Software Development (CC-CASD) | Beckers, K., Faßbender, S., Hatebur, D., Heisel, M. & Côté, I. | Proceedings of the 28th Annual ACM Symposium on Applied Computing (SAC) | ACM | |
| Abstract: In order to gain their customers’ trust, software vendors can certify their products according to security standards, e.g., the Common Criteria (ISO 15408). However, a Common Criteria certification requires a comprehensible documentation of the software product. The creation of this documentation results in high costs in terms of time and money. We propose a software development process that supports the creation of the required documentation for a Common Criteria certification. Hence, we do not need to create the documentation after the software is built. Furthermore, we propose to use an enhanced version of the requirements-driven software engineering process called ADIT to discover possible problems with the establishment of Common Criteria documents. We aim to detect these issues before the certification process. Thus, we avoid expensive delays of the certification effort. ADIT provides a seamless development approach that allows consistency checks between different kinds of UML models. ADIT also supports traceability from security requirements to design documents. We illustrate our approach with the development of a smart metering gateway system. |
|||||
BibTeX:
@inproceedings{SAC2013,
year = {2013},
title = {{Common Criteria CompliAnt Software Development (CC-CASD)}},
booktitle = {Proceedings of the 28th Annual ACM Symposium on Applied Computing (SAC)},
author = {Beckers, Kristian and Fa{\ss}bender, Stephan and Hatebur, Denis and Heisel, Maritta and C{\^{o}}t{\'{e}}, Isabelle},
publisher = {ACM},
pages = {1298--1304},
url = {https://dl.acm.org/citation.cfm?id=2480604}
}
|
|||||
| 2012 | Using Security Requirements Engineering Approaches to Support ISO 27001 Information Security Management Systems Development and Documentation | Beckers, K., Heisel, M., Faßbender, S. & Schmidt, H. | Proceedings of the International Conference on Availability, Reliability and Security (ARES) | IEEE Computer Society | |
| Abstract: An ISO 27001 compliant information security management system is difficult to create, due to the the limited support for system development and documentation provided in the standard. We present a structured analysis of the documentation and development requirements in the ISO 27001 standard. Moreover, we investigate to what extent existing security requirements engineering approaches fulfill these requirements. We developed relations between these approaches and the ISO 27001 standard using a conceptual framework originally developed for comparing security requirements engineering methods. The relations include comparisons of important terms, techniques, and documentation artifacts. In addition, we show practical applications of our results. |
|||||
BibTeX:
@inproceedings{Beckers2012-ares4,
year = {2012},
title = {Using Security Requirements Engineering Approaches to Support ISO 27001 Information Security Management Systems Development and Documentation},
booktitle = {Proceedings of the International Conference on Availability, Reliability and Security ({ARES})},
author = {Beckers, Kristian and Heisel, Maritta and Fa{\ss}bender, Stephan and Schmidt, Holger},
publisher = {IEEE Computer Society},
pages = {243-248},
url = {http://www.ieee.org/}
}
|
|||||
| 2012 | Supporting the Context Establishment according to ISO 27005 using Patterns | Beckers, K. & Faßbender, S. | Software Engineering 2012 - Workshopband | GI | |
| Abstract: The documentation of an information and communication system according to the requirements of the ISO 27005 standard is difficult, because the standard only provides sparse descriptions. We propose the use of specific patterns for the ISO 27005 standard, which can be instantiated for any given information and communication system. Each of our pattern will cover a section of the standard. In this paper we present one pattern for Section 7 of the standard, the context establishment. This is one of the initial steps of the standards and it is the input for following steps, e.g., the asset identification. |
|||||
BibTeX:
@inproceedings{beckersF12zemoss,
year = {2012},
title = {Supporting the Context Establishment according to ISO 27005 using Patterns},
booktitle = {Software Engineering 2012 - Workshopband},
author = {Beckers, Kristian and Fa{\ss}bender, Stephan},
publisher = {GI},
pages = {141-146},
note = {Workshop Zertifizierung und modellgetriebene Entwicklung sicherer Software, Software Engineering 2012 (ZeMoSS'12)},
url = {https://gi.de/}
}
|
|||||
| 2012 | A Pattern-Based Method for Identifying and Analyzing Laws | Beckers, K., Faßbender, S., Küster, J.-C. & Schmidt, H. | Proceedings of the International Working Conference onRequirements Engineering: Foundation for Software Quality (REFSQ) | Springer | |
| Abstract: This paper presents a novel method for identifying and analyzing laws. The method makes use of different kinds of law analysis patterns that allow legal experts and software and system developers to understand and elicit relevant laws for the given development problem. Our approach also helps to detect dependent laws. We illustrate our method using an online-banking cloud scenario. |
|||||
BibTeX:
@inproceedings{BeckersFKS12,
year = {2012},
title = {A Pattern-Based Method for Identifying and Analyzing Laws},
booktitle = {Proceedings of the International Working Conference onRequirements Engineering: Foundation for Software Quality ({REFSQ})},
author = {Beckers, Kristian and Fa{\ss}bender, Stephan and K{\"{u}}ster, Jan-Christoph and Schmidt, Holger},
publisher = {Springer},
series = {LNCS 7195},
pages = {256-262},
url = {https://link.springer.com/chapter/10.1007%2F978-3-642-28714-5_23},
doi = {10.1007/978-3-642-28714-5_23}
}
|
|||||
| 2012 | Patterns- and Security-Requirements-Engineering-based Support for Development and Documentation of Security Standard Compliant ICT Systems [BibTeX] |
Beckers, K. | DOKTORANDENSYMPOSIUM DER SOFTWARE ENGINEERING 2012 PROCEEDINGS | Brandenburg University of Technology | |
BibTeX:
@other{BeckersSE2012,
year = {2012},
title = {{P}atterns- and {S}ecurity-{R}equirements-{E}ngineering-based {S}upport for {D}evelopment and {D}ocumentation of {S}ecurity {S}tandard {C}ompliant {ICT} {S}ystems},
booktitle = {DOKTORANDENSYMPOSIUM DER SOFTWARE ENGINEERING 2012 PROCEEDINGS},
author = {Beckers, Kristian},
publisher = {Brandenburg University of Technology},
volume = {01/12},
pages = {25-30},
url = {http://www-docs.tu-cottbus.de/programmiersprachen-compilerbau/public/publikationen/2012/DS-SE-2012.pdf}
}
|
|||||
| 2012 | Supporting the Development and Documentation of ISO 27001 Information Security Management Systems Through Security Requirements Engineering Approaches | Beckers, K., Faßbender, S., Heisel, M., Küster, J.-C. & Schmidt, H. | Proceedings of the International Symposium on Engineering Secure Software and Systems (ESSoS) | Springer | |
| Abstract: Assembling an information security management system according to the ISO 27001 standard is difficult, because the standard provides only sparse support for system development and documentation. We analyse the ISO 27001 standard to determine what techniques and documentation are necessary and instrumental to develop and document systems according to this standard. Based on these insights, we inspect a number of current security requirements engineering approaches to evaluate whether and to what extent these approaches support ISO 27001 system development and documentation. We re-use a conceptual framework originally developed for comparing security requirements engineering methods to relate important terms, techniques, and documentation artifacts of the security requirements engineering methods to the ISO 27001. |
|||||
BibTeX:
@inproceedings{essos2012,
year = {2012},
title = {Supporting the Development and Documentation of {ISO} 27001 Information Security Management Systems Through Security Requirements Engineering Approaches},
booktitle = {Proceedings of the International Symposium on Engineering Secure Software and Systems ({ESSoS})},
author = {Beckers, Kristian and Fa{\ss}bender, Stephan and Heisel, Maritta and K{\"{u}}ster, Jan-Christoph and Schmidt, Holger},
publisher = {Springer},
series = {LNCS 7159},
url = {https://link.springer.com/}
}
|
|||||
| 2012 | Pattern- and Component-based Development of Dependable Systems | Hatebur, D. | School: University of Duisburg-Essen | Deutscher Wissenschafts-Verlag (DWV) Baden-Baden | |
BibTeX:
@phdthesis{Hatebur2012,
year = {2012},
title = {Pattern- and Component-based Development of Dependable Systems},
author = {Hatebur, Denis},
publisher = {Deutscher Wissenschafts-Verlag (DWV) Baden-Baden},
school = {University of Duisburg-Essen},
url = {http://www.dwverlag.de/index.php?art=Pattern-+and+Component-based+Development+of+Dependable+Systems&mod=Onlineshop&view=Artikel&abid=166}
}
|
|||||
| 2012 | Pattern-based Context Establishment for Service-Oriented Architectures | Beckers, K., Faßbender, S., Heisel, M. & Meis, R. | Software Service and Application Engineering | Springer | |
| Abstract: A context description of a software system and its environment is essential for any given software engineering process. Requirements define statements about the environment (according to Jackson's terminology). The context description of a Service-Oriented Architecture is difficult to provide, because of the variety of technical systems and stakeholders involved. We present two patterns for SOA systems and support their instantiation with a structured method. In addition, we show how the pattern can be used in a secure service development life-cycle. |
|||||
BibTeX:
@inproceedings{sdps2012,
year = {2012},
title = {Pattern-based Context Establishment for Service-Oriented Architectures},
booktitle = {Software Service and Application Engineering},
author = {Beckers, Kristian and Fa{\ss}bender, Stephan and Heisel, Maritta and Meis, Rene},
publisher = {Springer},
series = {LNCS 7365},
pages = {81-101},
url = {http://dx.doi.org/10.1007/978-3-642-30835-2_7},
doi = {10.1007/978-3-642-30835-2_7}
}
|
|||||
| 2011 | Pattern-Based Support for Context Establishment and Asset Identification of the ISO 27000 in the Field of Cloud Computing | Beckers, K., Küster, J.-C., Faßbender, S. & Schmidt, H. | Proceedings of the International Conference on Availability, Reliability and Security (ARES) | IEEE | |
| Abstract: The ISO 27000 is a well-established series of information security standards. The scope for applying these standards can be an organisation as a whole, single business processes or even an IT application or IT infrastructure. The context establishment and the asset identification are among the first steps to be performed. The quality of the results produced when performing these steps has a crucial influence on the subsequent steps such as identifying loss, vulnerabilities, possible attacks and defining countermeasures. Thus, a context analysis to gather all necessary information in the initial steps is important, but is not offered in the standard. In this paper, we focus on the scope of cloud computing systems and present a way to support the context establishment and the asset identification described in ISO 27005. A cloud system analysis pattern and different kinds of stakeholder templates serve to understand and describe a given cloud development problem, i.e. the envisaged IT systems and the relevant parts of the operational environment. We illustrate our support using an online banking cloud scenario. |
|||||
BibTeX:
@inproceedings{ares2011,
year = {2011},
title = {Pattern-Based Support for Context Establishment and Asset Identification of the {ISO} 27000 in the Field of Cloud Computing},
booktitle = {Proceedings of the International Conference on Availability, Reliability and Security ({ARES})},
author = {Beckers, Kristian and K{\"{u}}ster, Jan-Christoph and Fa{\ss}bender, Stephan and Schmidt, Holger},
publisher = {IEEE},
pages = {327--333},
url = {https://www.ieee.org}
}
|
|||||
| 2011 | A Pattern-Based Method for Identifying and Analyzing Laws in the Field of Cloud Computing Compliance | Beckers, K., Faßbender, S., Küster, J.-C. & Schmidt, H. | |||
| Abstract: Cloud computing o ers highly exible and scalable usage of IT resources, from which companies can bene t. Clouds are sociotechnical systems with a high number of di erent kinds of stakeholders. Moreover, they are often geographically distributed, process critical data, and support sensitive IT processes. Therefore, aligning clouds to meet compliance regulations is a challenging task. Presently, this unsolved problem prevents companies from using clouds for critical tasks. This paper presents a novel method for identifying and analyzing laws for clouds. The method makes use of di erent kinds of patterns, which help to systematically elicit relevant laws. We present law analysis patterns that allow legal experts and software and system developers to understand and elicit relevant laws for the given development problem. Our approach also helps to detect dependent laws. Our law analysis patterns make use of results generated by the application of a cloud system analysis pattern and di erent kinds of stakeholder templates that serve to understand and describe a given cloud development problem. We illustrate our method using an online banking cloud scenario. |
|||||
BibTeX:
@techreport{,
year = {2011},
title = {A Pattern-Based Method for Identifying and Analyzing Laws in the Field of Cloud Computing Compliance},
author = {Beckers, Kristian and Fa{\ss}bender, Stephan and K{\"{u}}ster, Jan-Christoph and Schmidt, Holger}
}
|
|||||
| 2002 | A Problem-Oriented Approach to Common Criteria Certification | Rottke, T., Hatebur, D., Heisel, M. & Heiner, M. | Proceedings of the 21st International Conference on Computer Safety, Reliability and Security (SAFECOMP) | Springer | |
| Abstract: There is an increasing demand to certify the security of systems according to the Common Criteria (CC). The CC distinguish several evaluation assurance levels (EALs), level EAL7 being the highest and requiring the application of formal techniques. We present a method for requirements engineering and (semi-formal and formal) modeling of systems to be certified according to the higher evaluation assurance levels of the CC. The method is problem oriented, i.e. it is driven by the environment in which the system will operate and by a mission statement. We illustrate our approach by an industrial case study, namely an electronic purse card (EPC) to be implemented on a Java Smart Card. As a novelty, we treat the mutual asymmetric authentication of the card and the terminal into which the card is inserted. | |||||
BibTeX:
@inproceedings{RHH+2002,
year = {2002},
title = {A Problem-Oriented Approach to Common Criteria Certification},
booktitle = {Proceedings of the 21st International Conference on Computer Safety, Reliability and Security (SAFECOMP)},
author = {Rottke, Thomas and Hatebur, Denis and Heisel, Maritta and Heiner, Monika},
publisher = {Springer},
series = {LNCS 2434},
pages = {334--346},
url = {https://link.springer.com/}
}
|
|||||
Created by JabRef on 13/03/2018.