Welcome to the InfoSci Platform
Reference Hub5
Goal Modelling for Security Problem Matching and Pattern Enforcement

Goal Modelling for Security Problem Matching and Pattern Enforcement

Yijun Yu, Haruhiko Kaiya, Nobukazu Yoshioka, Zhenjiang Hu, Hironori Washizaki, Yingfei Xiong, Amin Hosseinian-Far
Copyright: © 2017 |Volume: 8 |Issue: 3 |Pages: 16
ISSN: 1947-3036|EISSN: 1947-3044|EISBN13: 9781522513872|DOI: 10.4018/IJSSE.2017070103
Cite Article Cite Article

MLA

Yu, Yijun, et al. "Goal Modelling for Security Problem Matching and Pattern Enforcement." IJSSE vol.8, no.3 2017: pp.42-57. http://doi.org/10.4018/IJSSE.2017070103

APA

Yu, Y., Kaiya, H., Yoshioka, N., Hu, Z., Washizaki, H., Xiong, Y., & Hosseinian-Far, A. (2017). Goal Modelling for Security Problem Matching and Pattern Enforcement. International Journal of Secure Software Engineering (IJSSE), 8(3), 42-57. http://doi.org/10.4018/IJSSE.2017070103

Chicago

Yu, Yijun, et al. "Goal Modelling for Security Problem Matching and Pattern Enforcement," International Journal of Secure Software Engineering (IJSSE) 8, no.3: 42-57. http://doi.org/10.4018/IJSSE.2017070103

Export Reference

Mendeley
Favorite Full-Issue Download

Abstract

This article describes how earlier detection of security problems and the implementation of solutions would be a cost-effective approach for developing secure software systems. Developing, gathering and sharing similar repeatable programming knowledge and solutions has led to the introduction of Patterns in the 90's. The same concept has been adopted to realise reoccurring security knowledge and hence security patterns. Detecting a security problem using the patterns in requirements models may lead to its early prevention. In this article, the authors have provided an overview of security patterns in the past two decades, followed by a summary of i*/Tropos goal modelling framework. Section 2 outlines model-driven development, meta-models and model transformation, within the context of requirements engineering. They have summarised security access control types, and formally described role-based access control (RBAC) in particular as a pattern that may occur in the stakeholder requirements models. Then the authors used the i* modelling language and some elements from its constructs - model-driven queries and transformations - to describe the pattern enforcement. This is applied to a number of requirements models within the literature, and the pattern-based transformation tool they designed has automated the detection and resolution of this security pattern in several goal-oriented stakeholder requirements. Finally, the article also reflects on a variety of existing applications and future work.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.