Ise enterprise architecture and common standards program
ISE Enterprise Architecture and Common Standards Program
IRTPA Section 1016: Creating the ISE 01/10/11 UNCLASSIFIED President George W. Bush on signing the Intelligence Reform and Terrorist Prevention Act 17 December 2004 Section 1016, as amended*: “ The President shall – create an information sharing environment for the sharing of terrorism information in a manner consistent with national security and with applicable legal standards relating to privacy and civil liberties; designate the organizational and management structures that will be used to operate and manage the ISE; and determine and enforce the policies , directives, and rules that will govern the content and usage of the ISE . ” * The Implementing Recommendations of the 9/11 Commission Act of 2007, enacted in August of this year, included amendments to section 1016 . The new law expands the scope of the ISE to explicitly include homeland security and terrorism-related weapons of mass destruction information.
National Strategy for Information Sharing 01/10/11 UNCLASSIFIED National Strategy for Information Sharing: Success and Challenges in Improving Terrorism-Related Information Sharing issued on October 31, 2007 by President Bush Prioritizes and unifies the Nation’s efforts to advance the sharing of terrorism-related information
Elements of National Strategy for Information Sharing 01/10/11 UNCLASSIFIED Providing a framework for enhanced information sharing among Federal, State, local, and tribal officials, the private sector, and foreign partners Describing the Federal Government's approach to support State and major urban area fusion centers Protecting the legal rights of Americans especially in the area of privacy and civil liberties The Strategy will help ensure those responsible for combating terrorism and protecting our local communities have access to the timely and accurate information they need by:
ISE Implementation Plan Responds to 11 specific IRTPA requirements DNI sent to Congress - Nov06 Described the vision and strategic goals for the future ISE Laid out two-phase implementation approach Phase 1: Nov 2006 – June 2007 Phase 2: July 2007 – June 2009 Incorporated responses to Presidential Information Sharing Guidelines Defines ISE Enterprise Architecture Framework and common standards (chapter 6) www.ise.gov
Who is the ISE? Multiple Communities of Interest Multiple User Types Multiple Governmental and Non-governmental Entities 01/10/11 UNCLASSIFIED Intel Law Enforcement Foreign Affairs Homeland Security Defense Operators Command & Control Analysts Investigators Collectors Responders Federal State, Local, Tribal Foreign Partners Private Sector Terrorism Info (Terrorism, Homeland Security, and WMD and Law Enforcement as it relates to Terrorism)
Why ISE Architecture and Common Standards Program? The Problem Need to weave together cross-agency, cross domain, national security and civil processes and systems to support the requirements of the ISE Factors in responding to the problem National security and homeland security processes and resources Controlled Unclassified Information (CUI) Privacy and civil liberties protections Domestic intelligence - foreign intelligence Seamless Federal, state, local, and tribal integration Investment Strategies (consistent with governmental guidelines) Acknowledgment this is a new, undefined area for government Federal law and Presidential direction IRTPA (December 2004) Presidential Guidelines (December 16, 2005 Presidential Memo) National Strategy for Information Sharing (October 2007) 01/10/11 UNCLASSIFIED
ISE Enterprise Architecture Framework, Version 1.0 Purpose Provide a terrorism information sharing dimension across civil and national security enterprise architectures Meet IRTPA direction to “plan for” the ISE using technology Aid ISE participants with integration and connection guidance to the ISE 01/10/11 UNCLASSIFIED
ISE EAF – Architect’s & Implementer’s Views
Impact of an EAF for the ISE Impacts across three disciplines: Business Processes Policy Technology ISE EAF will enable the ISE by: Translating ISE business process needs into a cohesive and aligned investment strategy Identifying policy areas Provide a program management tool for building the ISE (oversee implementation of ISE) ISE EAF Aligned with the FEA Priorities aligned with strategic plans and executive level direction. Proactive and collaborative across the Federal government Architecture development is an integral part of the capital investment process. No investment should be made without a business-driven architecture. Users Users Applications Applications Databases Databases Information Sharing Environment ISE Space ISE Space Core Services Discovery IA Security Mediation Messaging Enterprise Management Collaboration User Assistance Storage Application ISE Portal Service Registration ISE Documentation ISE Status Service Discovery User Assistance Search Tools Portal Hosting Admin Alerts
ISE EAF: Application and Services 01/10/11 UNCLASSIFIED 01/10/11 UNCLASSIFIED ISE Shared Space: Common Terrorism Information Sharing Standards. Common IA model.
FEA-ISE Profile, Version 1.0 Purpose A companion document to the ISE EAF, Version 1.0 (released 30 Aug ‘07) Describes how agencies use existing resources, standards, best practices and use cases to implement ISE attributes and connect to the ISE Communicated compliance through OMB’s Federal Transition Framework Catalog Current OMB Profiles Security and Privacy Geospatial Records Management 01/10/11 UNCLASSIFIED
Using the ISE EAF and FEA-ISE Profile 01/10/11 UNCLASSIFIED FEA-ISE Profile ISE Core Component Specs Department/Agency X System X System I ISE Core Dept/ Agency X EA System X Architecture ISE Enterprise Architecture Framework System I Architecture FTF Catalog ISE Business Processes ISE Performance Metrics EAF: Enterprise Architecture Framework FEA: Federal Enterprise Architecture FTF: Federal Transition Framework Agency Capital Planning & Investment Control (CPIC) Process >> Exhibits 53 & 300 Version 1.0 (December 2006)
ISE Standards Objective “ The ISE must, to the extent possible, be supported by common standards that maximize the acquisition, access, retention, production, use, management, and sharing of terrorism information within the ISE consistent with the protection of intelligence, law enforcement, protective, and military sources, methods, and activities.” President’s Memorandum for the Heads of Executive Departments and Agencies December 16, 2005 01/10/11 UNCLASSIFIED
Taxonomy of the CTISS 01/10/11 UNCLASSIFIED Functional standards: Rules, conditions, guidelines, and characteristics of data, mission products, and detailed operational activity supporting ISE business process areas. Technical standards: Specific technical methodologies and practices to design and implement information sharing capability into ISE systems. CTISS Program Issuance
Common Terrorism Information Sharing Standards 01/10/11 UNCLASSIFIED Better terrorism-related information sharing through standard formats, rules and conditions Relationships established with the National Information Exchange Model and DOD/IC U-Core to assist in developing and harmonizing standards across the ISE
QUESTIONS? Ken Clark Office of the PM-ISE 202-331-4071 [email_address]
A particular slide catching your eye?
Clipping is a handy way to collect important slides you want to go back to later.