Chief Information Officer

NCTC Speeches, Testimonies and Interviews

Chief Information Officer

IC Technical Specifications

Intelligence Discipline

Overview

This CVE Encoding Specification for Intelligence Discipline (INTDIS.CES) defines detailed implementation guidance for using Extensible Markup Language (XML) to encode Intelligence Discipline (INTDIS) controlled vocabulary. The INTDIS.XML vocabulary defines values that are valid intelligence discipline. The CVE Encoding Specification (CES) defines the XML elements and attributes, associated structures and relationships, mandatory and cardinality requirements, and permissible values for representing data concepts for using XML.

Compliance with this specification is measured against all aspects of the technical and documentary artifacts contained within the specification release package.

This specification is maintained by the IC Chief Information Officer via the Data Standards Coordination Activity (DSCA) and Entity Specification Tiger Team (ESTT).

 

Technical Specification Downloads

 

Latest Approved Public Release:

 

Mission Requirements

This specification is designed to fulfill a number of requirements in support of the transformational efforts of the Intelligence Community. Many of these requirements are articulated in IC Directives 203, 206, 208, 501, and 710, among others. This specification is designed to support the Intelligence Community Information Technology Enterprise (IC ITE) Increment 1 Implementation Plan.

This specification provides a common, consistent way to encode Intelligence Discipline controlled vocabulary.

 

Chief Information Officer

IC Technical Specifications

Web Security Standards Guidance: Token Services

 

Overview

The information guidance document for Web Security Standards Guidance for Token Services (WSS-TS) defines guidance on the use of token services. Token services represent a technical approach to implement secure messaging for credentials both within and across trust domains. This document outlines and describes a set of representative use cases.

 

This specification is maintained by the IC Chief Information Officer via the Data Standards Coordination Activity (DSCA) and Common Metadata Standards Tiger Team (CMSTT).

 

Technical Specification Downloads

 

Latest Approved Public Release:

 

Mission Requirements

 

The IC CIO funds and oversees a number of critical enabling projects, including the IC Information Technology Enterprise (IC ITE). The IC ITE makes extensive use of web services and distributed processing, yet each individual program providing services therein requires explicit guidance on building secure, interoperable web services.

 

This document provides general and prescriptive guidance for the development of secure and interoperable web services security solutions in support of the following Office of the Director of National Intelligence (ODNI) policies and implementation guidance.

 

Chief Information Officer

IC Technical Specifications

Source Citations

Overview

The XML Data Encoding Specification for Source Citations (SRC.XML) defines detailed implementation guidance for xml-encoding of source citations in analytic products. The purpose of sourcing information is to enhance the credibility and transparency of intelligence analysis, and to assist readers in making an informed assessment of the quality and the scope of sources underlying the analysis.

 

This specification is maintained by the IC Chief Information Officer via the Data Standards Coordination Activity (DSCA) and Common Metadata Standards Tiger Team (CMSTT).

 

Technical Specification Downloads

 

Latest Approved Public Release:

 

Mission Requirements

 

This specification is designed to fulfill a number of requirements in support of the transformational efforts of the Intelligence Community. Many of these requirements are articulated in IC Directives 203, 206, 208, 501, and 710, among others.

 

This specification is designed to fulfill a number of requirements in support of the transformational efforts of the IC. These requirements include:

  • Capturing source citations to provide intelligence collectors the ability to systematically analyze how and how often the data they gather or produce is being used in order to facilitate better management of collection and production resources.
  • Capturing source citations to enhance the analytic integrity of formally disseminated intelligence information and improving the traceability of collected information to analytic judgments and conclusions.

 

Chief Information Officer

IC Technical Specifications

Electronic Records Management

Overview

The Electronic Records Management specification defines detailed implementation guidance for using Extensible Markup Language (XML) to encode electronic records management data. It defines the XML elements and attributes, associated structures and relationships, mandatory and cardinality requirements, and permissible values for representing ERM data assertion concepts using XML within the use of a Trusted Data Format (TDF) Object (TDO) or TDF Collection (TDC).

 

Electronic Records Management (ERM) is required to control the creation, receipt, maintenance, use and disposition of records in accordance with legislation such as the Federal Records Act, 44 U.S.C 3101, the Freedom of Information Act (FOIA), 5 U.S.C. 552, the Privacy Act, 5 U.S.C. 552a, and Executive Branch direction. This applies to permanent and temporary records. IC ITE Service Providers shall provide the means to audit, track, and manage disposition information, using agreed upon metadata tags that can be adapted to changing missions and records management practices.

 

This specification is maintained by the IC Chief Information Officer via the Data Standards Coordination Activity (DSCA) and Common Metadata Standards Tiger Team (CMSTT).

 

Technical Specification Downloads

 

Latest Approved Public Release:

 

Mission Requirements

 

Information sharing within the national intelligence enterprise increasingly relies on information assurance metadata (including enterprise data headers) to allow interagency access control, automated exchanges, and appropriate protection of shared intelligence. An enormous amount of data are collected each year by the IC to fulfill missions in protecting the United States. Federal laws govern the way that Agencies must maintain and dispose of data (records) collected in the course of fulfilling Agency missions. Including metadata for ERM within IC data collected or generated by the Community allows for more thorough and timely management of these records.

 

ERM helps automate the sharing, processing, routing, discovery, and access control of information. ERM enables users to quickly discover information related to FOIA requests, Privacy Act cases and other specialized legal requests, identify documents for mandatory declassification, and respond to other open government initiatives.

 

Chief Information Officer

IC Technical Specifications

CVE Encoding Specification for Production Metrics

Overview

The CVE Encoding Specification for Production Metrics (PM.CES) defines detailed implementation guidance for using Extensible Markup Language (XML) to encode Production Metrics (PM) controlled vocabulary. This Controlled Vocabulary Enumeration (CVE) Encoding Specification (CES) defines the XML elements and attributes, associated structures and relationships, mandatory and cardinality requirements, and permissible values for representing data concepts using XML.

This specification is maintained by the IC Chief Information Officer via the Data Standards Coordination Activity (DSCA) and Common Metadata Standards Tiger Team (CMSTT).

Technical Specification Downloads

Latest Approved Public Release:

Mission Requirements

This specification is designed to fulfill a number of requirements in support of the transformational efforts of the Intelligence Community. Many of these requirements are articulated in IC Directives 203, 206, 208, 501, and 710, among others.

This CES defines the Production Metrics related CVEs including Subjects, Actors, and Locations. While PM values are not directly used for Access Control, the PM values are aggregated into the Mission Need (MN.CES) Issue CVE, and a mapping of PM values to MN.CES Issue values is provided in the Taxonomy Encoding Specification for Mission-Need Taxonomy (MNT.XML).  

Subcategories