Chief Information Officer
Chief Information Officer
IC Technical Specifications
The successes of our intelligence, defense, homeland security, and law enforcement missions are critically dependent on information producers and consumers being able to share, manage, discover, retrieve, and access information across national and international boundaries.
To automate the enterprise, data, service, network, and information assurance architecture and engineering efforts must come together in response to defined mission and business requirements. The enterprise data specifications below are the result of IC collaboration and coordination in response to public law, executive orders, DNI policy and guidance, and change requests submitted by IC elements.
Data Encoding Specifications
The following data encoding specifications define agreed upon digital encodings or formats for information being shared or exchanged within the enterprise. These specifications are optimized for consistent and efficient processing within software, systems, or service applications.
These specifications should be viewed as component modules. Many of the specifications are tightly integrated and dependent on each other. They can be integrated into other data encoding specifications or profiled (i.e., configured or constrained) to achieve a particular mission or business objective. They may also serve in a standalone role as an encodings for exchange payloads within a web services environment.
Each version of an IC enterprise data encoding specification is individually registered in the IC Enterprise Standards Baseline (implemented via the IC Standards Registry (ICSR)). The registry citations address the prescriptive status and validity period for each new version. Data Encoding Specifications exist for the following types of data:
- Abstract Data Definition
- Abstract Data Definition for Electronic Records Management
- Access Rights and Handling
- Analysis Assertion
- Body Of Evidence
- Authority Category
- Community Shared Resources
- Contextual Entity Markup
- Cross Domain System Manifest Assertion
- Cross Domain System Manifest TDF
- Data Element Definition
- DigitalHazMat Assertion
- DigitalHazMat TDF
- DigitalHazMat Commercial TDF
- Document and Media Exploitation
- DoD Discovery Metadata
- Electronic Records Management
- Enterprise Audit
- Fine Access Control
- Geopolitical Entities, Names, and Codes
- Information Resource Metadata
- Information Security Marking Access
- Information Security Marking Country
- Information Security Marking Metadata
- Information Transport Service Messaging Service
- Information Transport Service - Organizational Messaging
- Intelligence Community Docbook
- Intelligence Community Access Control
- Intelligence Community Enterprise Data Header
- Intelligence Community Identifier
- Intelligence Community Only Need to Know
- Intelligence Community Specification Framework
- Intelligence Discipline
- Intelligence Publications
- License
- Media Type Controlled Vocabulary
- Mission Need
- Mission Need Taxonomy
- Multi Audience Collections
- Multi Audience Tearline
- Need-To-Know Metadata
- Need-To-Know Access Control Encoding Specification
- ORCON Need-To-Know Access
- Production Metrics
- Production Metrics Assertion
- Revision Recall
- Role
- Rollup Guidance for ISM
- Source Citations
- Trusted Data Format
- Trusted Data Format - Base
- US Agency Acronym
- US Government Agency
- Unified Identity Attribute Set
- Unified Identity Attribute Set - Attribute Practice Compliance Statements
- Virtual Coverage
- Whitelist Guidance for ISM
Service Specifications
- CDR: Atom Results Set
- CDR: Brokered Search
- CDR: Deliver
- CDR: Manage Component
- CDR: Query Management
- CDR: Retrieve
- CDR: Search
- CDR: Reference Architecture
- CDR: Specification Framework
- CDR: Keyword Query Language
- IdAM: Full Service Directory
- RR: End-to-End Identity Propagation
- RR: Security Markings
- WSS High Level Guidance
- WSS XML Signature and XML Encryption
- WSS Guidance: Token Services
We are very interested in hearing your views on issues of importance to you. We encourage you to contact us with any questions, comments, and concerns of interest to the Intelligence Community Data Coordination Activity (Data Activity). Someone from the Data Activity staff will respond to your email.
As always, we thank you for your time and continued collaboration through the Data Activity.
Mission: To enable enhanced mission success by leading IT transformation and protection of the Intelligence Community's Information Environment.
Vision: The IC executes its mission with increasing effectiveness, integration, and agility to stay ahead of threats.
In 2012, the IC CIO embarked on the largest IT transformation in the history of the Intelligence Community. This transformation, guided by the IC Information Technology Enterprise (IC ITE) Strategy, is focused on enabling greater integration, information sharing, and information safeguarding through a common IC IT approach that substantially reduces costs. The IC ITE “officially opened for business” in August 2013.
The Office of the IC CIO provides strategic direction and oversight for the planning, assessing, implementing, and monitoring of IC ITE activities in support of the IC ITE vision of an “Integrated Intelligence Enterprise.”
The IC ITE Strategy 2016-2020 is focused on the three primary goals of IC ITE:
Goal 1: Enhance Intelligence Integration
Promote the Intelligence Community’s ability to integrate and unify intelligence activities by fully leveraging IC ITE.
Goal 2: Optimize Information Assurance to Secure and Safeguard the IC Enterprise
Enhance IC mission success through a trusted collaborative environment while protecting national intelligence information, sources, and methods, as well as privacy and civil liberties.
Goal 3: Operate as an Efficient, Effective IC Enterprise
Achieve an IC ITE operating model that employs common business practices and Community teams to deliver, adopt, and sustain shared enterprise services and capabilities across the IC.
The IC ITE represents a strategic shift from agency-centric information technology (IT) to a common enterprise platform where the IC can easily and securely share technology, information, and capabilities across the Community. To enable this change, the Director of National Intelligence (DNI), in consultation with the applicable IC element head, has designated IC elements as service providers, who assume the responsibility for developing and maintaining IC ITE services of common concern. IC ITE Services are the capabilities and shared solutions that are being delivered across the IC to help complete the vision of IC ITE. These services currently include: a common desktop environment; a joint cloud environment; an applications mail; an enterprise management capability; identification, authentication, and authorization capabilities; network requirements and engineering services; and a security coordination service.
Working with the IC under the IC ITE Strategy, the IC CIO facilitates the development, implementation, and adoption of seamless and secure enterprise solutions that promote trusted collaboration – connecting people to people, people to data, and data to data. The strategy enhances the IC’s ability to securely discover, access, and share information across agencies and ultimately enables greater mission success.
IC ITE Implementation is an evolving process of consolidating and adopting Community capabilities. With the adoption of IC ITE Services, users will have broader and faster access to data and an increased ability to collaborate on common systems across the IC in ways that enhance mission integration and optimize mission success.
Congress passed the Intelligence Reform and Terrorism Prevention Act Dec. 17, 2004, establishing the position of the Director of National Intelligence and the supporting Office of the DNI. Six days later, Congress established the Intelligence Community Chief Information Officer through the Intelligence Authorization Act of 2005, empowering the position with Community-wide authority over enterprise architecture. The act established four areas of IC CIO responsibility above and beyond those accorded to other federal-level CIOs through legislation.
- Manage activities relating to IC Information Technology infrastructure and Enterprise Architecture requirements.
- Exercise procurement approval authority over all IT items related to IC EA components.
- Direct/manage IC IT-related procurement.
- Ensure all expenditures for IT research and development are consistent with the IC EA and the DNI’s strategy for such architecture.
The Office of the IC CIO is organized to respond to the mission, business, and technology needs of the Intelligence Community, ensuring IC collectors and analysts have the secure services and capabilities they need to effectively do their jobs. The Office of the IC CIO has four divisions: Strategic Programs, Mission Engagement, Information Assurance, and Information Management.
Douglas Cossa is the Chief Information Officer (CIO) of the Intelligence Community (IC)
Updated Content
Vision for the IC Information Environment - An Information Technology Roadmap