Organization

NCTC Newsroom

Chief Information Officer

IC Technical Specifications

DigitalHazMat Assertion

Overview

This XML Data Encoding Specification for DigitalHazMat Assertion (DHZM.XML) defines detailed implementation guidance for using XML to encode DHZM data. This specification defines the XML elements and attributes, associated structures and relationships, mandatory and cardinality requirements, and permissible values for representing DHZM data assertion concepts using XML within the use of a Trusted Data Format (TDF) Object.

 

The IC Chief Information Officer maintains this specification 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 (IC). These requirements include:

  • The need for a shared common technique to securely encapsulate, obfuscate and transport potentially malicious artifacts from one network to another.
  • The need to normalize metadata to facilitate communication between groups (e.g., government, commercial industry) with regards to digital hazmat provenance and analysis (e.g., isolated environments for triage, classified environments for deep analysis, multiple assertions for group analysis).

Chief Information Officer

IC Technical Specifications

DigitalHazMat Commercial TDF

Overview

This XML Data Encoding Specification for DigitalHazMat Commercial TDF (DHZMC-TDF.XML) defines detailed implementation guidance for using XML to encode DHZMC-TDF data. This specification defines the XML elements and attributes, associated structures and relationships, mandatory and cardinality requirements, and permissible values for representing trusted data format data concepts using XML within the use of a Trusted Data Format (TDF) Object. It is a profile of XML Data Encoding Specification for Trusted Data Format (IC-TDF.XML) that is suitable for use by commercial entities in an unclassified uncaveated environment while maintaining the ability to become a full IC-TDF.XML TDF on networks that require it.

 

The IC Chief Information Officer maintains this specification 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 (IC). These requirements include:

  • The need for a minimized profile of TDF for commercial entity use in unclassified uncaveated environments.
  • The need to provide non-repudiation, obfuscation, and secure cross domain transfer of digital hazmat across the various domains in the enterprise for provenance and analysis.

Chief Information Officer

IC Technical Specifications

Fine Access Control

Overview

Any IT system performing entity authentication may use this specification to determine if a given entity should be granted access to a specific piece of data.

 

This specification applies to the IC, as defined by the National Security Act of 1947, as amended, and ICS 500-27, Collection and Sharing of Audit Data,  and such other elements of any other department or agency as may be designated by the President, or designated jointly by the Director of National Intelligence (DNI) and  the head of the department or agency concerned, as an element of the IC.  Joint and Coalition forces may use this specification but it is not required.

 

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 Services 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 relies on the ability to discover and access intelligence content from any location, at any time, with as few restrictions as possible.  ICD 501 empowers analysts, operators, and collectors with a wide range of capabilities for discovering, using, and sharing content within the IC and with partners.  This authority comes with great responsibility, a responsibility that must be tracked, analyzed, and reported on.

The auditing of person and non-person entities within the IC protects the nation from abuse, voluntary or involuntary disclosure, as well as insider and outside threats.  The audit specification is derived from the fundamental mission requirement to track and audit the discovery and access of intelligence content and information resources within the IC enterprise.

Chief Information Officer

IC Technical Specifications

Intelligence Community Specification Framework

Overview

The Intelligence Community Specification Framework (IC-SF.XML) defines the basic conceptual structure and outlines the core philosophy of Intelligence Community (IC) technical specifications. This framework is applicable to the IC and information produced by, stored, or shared within the IC. This framework may have relevance outside the scope of intelligence; however, prior to applying outside of this defined scope, the framework should be closely scrutinized and differences separately documented and assessed for applicability.

 

The IC Chief Information Officer maintains this specification via the Data Standards Coordination Activity (DSCA) and Common Metadata Standards Tiger Team (CMSTT).

 

Technical Specification Downloads

 

Latest Approved Public Release:

 

Mission Requirements

 

Over the years, the number of IC technical specifications has grown substantially for various reasons, from addressing new enterprise needs to isolating independent concepts into separate specifications. Within these specifications, there are many aspects that are universal to all the IC specifications, or at least applicable to a particular family or format of specification. In a desire to simplify the specifications and make them easier to understand by those who are engineering and implementing enterprise exchange systems, this framework was born.

Chief Information Officer

IC Technical Specifications

Community Shared Resources

Overview

This IC enterprise data encoding specification defines detailed implementation guidance for Community Shared Resources (CSR) to sub-set the large possible combinations of specification versions.  CSRs are systems or services that live on the enterprise and are made available for use by the community.  This specification defines the minimum relationship sets of specifications mandatory for consuming systems (CSRs that receive data), and the allowed relationship sets for production systems (CSRs that transmit data).

This standard supports Executive Order (EO) 13526, Classified National Security Information which "prescribes a uniform system for classifying, safeguarding, and declassifying national security information," across national security disciplines, networks, services, and data.

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 Services Coordination Activity (DSCA) and Common Metadata Standards Tiger Team (CMSTT).

Technical Specification Downloads


Latest Approved Public Release:


Mission Requirements

All systems at the enterprise level need to be able to send and receive with a common vocabulary to permit understanding.  Since the decoupling of the IC Technical Specifications from one another, permitting them to revision independently, the potential combinations of versions of the specifications that can be mixed and matched together have grown exponentially.  This puts a large burden on data producers and consumers on the enterprise to be able to produce and/or interpret all possible combinations. The ever-growing number of combinations leads to a need to have a minimal number of sets of combinations that CSRs must be able to produce/consume to relieve them of the infeasible burden of being able to produce/consume all possible combinations.

National Counterterrorism Center