SP '97 Proceedings of the 1997 IEEE Symposium on Security and Privacy
WORDS '05 Proceedings of the 10th IEEE International Workshop on Object-Oriented Real-Time Dependable Systems
Service-Oriented System Engineering: A New Paradigm
SOSE '05 Proceedings of the IEEE International Workshop
Tomorrow's Needs — Yesterday's Technology: DOD's Architectural Dilemma and Plan for Resolution
HASE '05 Proceedings of the Ninth IEEE International Symposium on High-Assurance Systems Engineering
RBAC Standard Rationale: Comments on "A Critique of the ANSI Standard on Role-Based Access Control"
IEEE Security and Privacy
Supporting a service-oriented architecture
Proceedings of the 2008 Spring simulation multiconference
Understanding security architecture
Proceedings of the 2008 Spring simulation multiconference
Information assurance modeling using the Department of Defense architecture framework
SpringSim '10 Proceedings of the 2010 Spring Simulation Multiconference
| Hi-index | 0.00 |
Currently the DoDAF v1.5 states that security measures are "[...] being scoped for subsequent DoDAF versions [...]". [4] With little else said in the documentation it is difficult to tell what the Department of Defense deems important to the security of their system architecture. Proper software architecture should not only produce extensible, scalable, reusable code, it should inject security into the very core of the system. If DoDAF architectures are to be used on enterprise-wide net-centric applications, security cannot be an afterthought. This paper uses some existing modifications that have been suggested as separate additions, provides a way to integrate them into the DoDAF and suggests templates for new views as well as modifications to any existing templates.