Welcome to the InfoSci Platform
Reference Hub3
Integrating Access Control into UML for Secure Software Modeling and Analysis

Integrating Access Control into UML for Secure Software Modeling and Analysis

Thuong Doan, Steven Demurjian, Laurent Michel, Solomon Berhe
Copyright: © 2010 |Volume: 1 |Issue: 1 |Pages: 19
ISSN: 1947-3036|EISSN: 1947-3044|ISSN: 1947-3036|EISBN13: 9781609600044|EISSN: 1947-3044|DOI: 10.4018/jsse.2010102001
Cite Article Cite Article

MLA

Doan, Thuong, et al. "Integrating Access Control into UML for Secure Software Modeling and Analysis." IJSSE vol.1, no.1 2010: pp.1-19. http://doi.org/10.4018/jsse.2010102001

APA

Doan, T., Demurjian, S., Michel, L., & Berhe, S. (2010). Integrating Access Control into UML for Secure Software Modeling and Analysis. International Journal of Secure Software Engineering (IJSSE), 1(1), 1-19. http://doi.org/10.4018/jsse.2010102001

Chicago

Doan, Thuong, et al. "Integrating Access Control into UML for Secure Software Modeling and Analysis," International Journal of Secure Software Engineering (IJSSE) 1, no.1: 1-19. http://doi.org/10.4018/jsse.2010102001

Export Reference

Mendeley
Favorite Full-Issue Download

Abstract

Access control models are often an orthogonal activity when designing, implementing, and deploying software applications. Role-based access control (RBAC) which targets privileges based on responsibilities within an application and mandatory access control (MAC) that emphasizes the protection of information via security tags are two dominant approaches in this regard. The integration of access control into software modeling and analysis is often loose and significantly lacking, particularly when security is such a high-priority concern in applications. This article presents an approach to integrate RBAC and MAC into use-case, class, and sequence diagrams of the unified modeling language (UML), providing a cohesive approach to secure software modeling that elevates security to a first-class citizen in the process. To insure that a UML design with security does not violate RBAC or MAC requirements, design-time analysis checks security constraints whenever a new UML element is added or an existing UML element is modified, while post-design analysis checks security constraints across the entire design for conflicts and inconsistencies. These access control extensions and security analyses have been prototyped within a UML tool.

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.