The documents provided on this site are detailed instructions of how to create a blueprint of a given enterprise/Information/Weapons system. There are no specifics on any Department of Defense or Ministry of Defense systems given here Architecture views are based on the de facto Zackman Framework *

This post series is here to help System/System Security Engineers put together documents such as SSAA’s, DIACAP, and Information Support Plans (ISP) formerly known as Command, Control, Communications, Computers, and Intelligence Support Plan (C4ISP). Complex, critical enterprise, information and Weapon systems are documents that require Architecture Frameworks which are based on the Zachman Framework standard. Many of these documents are guided by policies that are in steady flux.

 Coming Soon:  OV-1, OV-2, OV-3, OV-4, SV-1, SV-2, SV-4, TV-1

Resources:

Documenst such as CJCSI 3170, CJCSM 3170 and CJCSI 6212 Can be found here:Resources and here Archives

Great links:

MODAF

Defense Link

Wiki Enterprise Architecture Framework

Architecture Framework Forum

 

The Security, Interoperability, Supportability, Sustainability and Usability (SISSU) is considered a part of the USAF IT LEAN process.  SISSU is a comprehensive database of security controls (IA Controls) addressed in DoDI 8500.02 needed to complete the DIACAP process. 

 

The SISSU questions includes everything from documentation of the system to physical security, to network security.  To access the SISSU process in the EITDR one need an account and “stakeholders list” approval via AFCA/EV.

Security, Interoperability, Supportability, Sustainability and Usability are each considered disciplines.  Each discipline is assigned a set of roles: producer, reviewer, validator, and approver.  Once all of these roles have done their part on each of their applicable questions in a given discipline they can move on to the next phase.  The phases are Define Need, Design, Build & Test, and Release.