Chief Information Officer
IC Technical Specifications
Document and Media Exploitation
Overview
This XML Data Encoding Specification for Intelligence Document and Media Exploitation (DOMEX.XML) defines detailed implementation guidance for using Extensible Markup Language (XML) to encode DOMEX data. This Data Encoding Specification (DES) defines the syntax, protocol and conventions for representing DOMEX data assertion and concepts using XML within the use of a Trusted Data Format (TDF) Object or Collection. This specification applies to the DOMEX Community, which is comprised of Intelligence Community (IC), Department of Defense (DoD), Department of Homeland Security (DHS), and Department of Justice (DoJ) components conducting or providing support to the conduct of DOMEX operations, activities, and functions. This specification defines the metadata standards for the uniform exchange of DOMEX.
Technical Specification Downloads
Latest Approved Public Release:
- XML Data Encoding Specification for Document and Media Exploitation (V2021-NOV - Standalone Package)
- XML Data Encoding Specification for Document and Media Exploitation (V2021-NOV - Convenience Package)
- XML Data Encoding Specification for Document and Media Exploitation (V2021-NOV - Light Package)
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.
This specification includes design features that address:
- Detailed implementation guidance on using XML to encode DOMEX data.
- Relationship between IC, NMEC
- Relationship between XML Data Encoding Specification for TDF and DOMEX
- Normative vs Informative Conformance issues
- Version Policies
- XML Namespace Policy
- Version Numbering
- Defines relationship between XML structures to abstract terms defined in the ADD
- Additional guidance for encoding data in specific situations
- Addresses relationship between TDO (payload and assertions), TDC, TDF and DOMEX
- TDO Format Overview: relationship between TDF and Metadata Assertions
- TDC Format Overview: relationship between DTC and TDO
- DOMEX schema namespace and respective elements
- Various Date specifications: entryDate; dateAccessed....lastModifiedDate, etc.
- Specification of Locations/Coordinates
Chief Information Officer
IC Technical Specifications
Abstract Data Definition
Intelligence Community Abstract Data Definition
Overview
The Intelligence Community Abstract Data Definition (IC.ADD) defines the high-level types of data and metadata that are important to the IC.
The selected or developed physical Data Encoding Specifications established by the IC map to the IC.ADD's abstract data elements providing a means to relate or translate different physical data encodings. The abstract data elements defined in the IC.ADD are not meant to be implementable within enterprise systems. IC elements should implement the physical Data Encoding Specifications that implement these abstract data elements.
This specification is maintained by the IC Chief Information Officer via the Data Coordination Activity (DCA) and Common Metadata Standards Tiger Team (CMSTT).
Latest Approved Public Release:
Chief Information Officer
IC Technical Specifications
Multi Audience Tearline
Overview
This Data Encoding Specification (DES) defines the XML elements and attributes; associated structures and relationships; mandatory and cardinality requirements; and permissible values for representing Multi Audience Tearlines... metadata associated with an information resource or part of an information resource using XML. MAT.XML can be incorporated into other Data Encoding Specifications.
These metadata are used to represent the system-specific properties assigned to an information resource that will be used, in conjunction with information about the user, and possibly other information, to determine the user’s access to the data. A single information resource may include multiple occurrences of these metadata in order to specify MAT information according to multiple, different access systems.
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 Coordination Activity (DCA) and Common Metadata Standards Tiger Team (CMSTT).
Technical Specification Downloads
Latest Approved Public Release:
- Multi Audience Tearlines have now been replaced by Multi Audience Collection.
Mission Requirements
Information sharing within the national intelligence enterprise frequently relies on being able to determine an individual’s MAT as one component in determining whether to allow access to data. The enterprise will increasingly rely on MAT metadata to allow users and systems to find and access a wide-range of data throughout the enterprise. A successful information sharing enterprise depends on the ability of data creators and or providers to specify means by which MAT can be established in a manner to facilitate discovery and access via automated means.
This DES provides a common specification for the means by which a data producer can encode, in their data, the information that an access system needs in order to determine how to grant access. This DES enables a comprehensive capability to appropriately protect data across the enterprise while also allowing access by individuals having appropriate MAT. The nature of the information to be encoded will vary system by system and could include lists of individuals or groups permitted access, descriptions of subject matter in terms defined by the access system, or other traits to be used in evaluating the access an individual has to the data.
This DES provides that common specification. Currently the particulars of any access system’s data needs are not defined. Details for specifying access information and documenting access parameters for particular access systems are to be added in the near future. The systems for which access information will be recorded and constrained will be expanded as their applicability’s are identified to the enterprise.
Chief Information Officer
IC Technical Specifications
Need-To-Know Metadata
Overview
This Data Encoding Specification (DES) defines the XML elements and attributes; associated structures and relationships; mandatory and cardinality requirements; and permissible values for representing NTK metadata associated with an information resource or part of an information resource using XML. NTK.XML can be incorporated into other Data Encoding Specifications.
NTK metadata facilitates automated systems making a “need-to-know” (NTK) access determination about an information resource. These metadata are used to represent the system-specific properties assigned to an information resource that will be used, in conjunction with information about the user, and possibly other information, to determine the user’s access to the data. A single information resource may include multiple occurrences of these metadata in order to specify NTK information according to multiple, different access systems.
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 Coordination Activity (DCA) and Common Metadata Standards Tiger Team (CMSTT).
Technical Specification Downloads
Latest Approved Public Release:
- Need To Know Metadata (V2015-AUG - Standalone Package)
- Need To Know Metadata (V2015-AUG - Convenience Package)
- Need To Know Metadata (V2015-AUG - Light Package)
Mission Requirements
Information sharing within the national intelligence enterprise frequently relies on being able to determine an individual’s NTK as one component in determining whether to allow access to data. The enterprise will increasingly rely on NTK metadata to allow users and systems to find and access a wide-range of data throughout the enterprise. A successful information sharing enterprise depends on the ability of data creators and or providers to specify means by which NTK can be established in a manner to facilitate discovery and access via automated means.
This DES provides a common specification for the means by which a data producer can encode, in their data, the information that an access system needs in order to determine how to grant access. This DES enables a comprehensive capability to appropriately protect data across the enterprise while also allowing access by individuals having appropriate NTK. The nature of the information to be encoded will vary system by system and could include lists of individuals or groups permitted access, descriptions of subject matter in terms defined by the access system, or other traits to be used in evaluating the access an individual has to the data.
This DES provides that common specification. Currently the particulars of any access system’s data needs are not defined. Details for specifying access information and documenting access parameters for particular access systems are to be added in the near future. The systems for which access information will be recorded and constrained will be expanded as their applicability’s are identified to the enterprise.
Chief Information Officer
IC Technical Specifications
Information Security Marking Metadata
Overview
This XML Data Encoding Specification for Information Security Markings (ISM.XML) defines detailed implementation guidance for using XML to encode Information Security Markings (ISM.XML) data. This Data Encoding Specification (DES) defines the XML elements and attributes, associated structures and relationships, mandatory and cardinality requirements, and permissible values for representing security markings and Need-to-Know (NTK) data concepts using XML, and for wrapping security markings and NTK attributes together in an Access Rights and Handling (ARH) XML container.
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.
This standard is a critical technical bridge between:
- Security marking requirements defined by the National Archives and Records Administration (NARA)/Information Security Oversight Office (ISOO),
- IC security markings register maintained by the Office of the Director of National Intelligence (ODNI)/Controlled Access Program Coordination Office (CAPCO), and
- Information technology solutions that implement structured security marking metadata.
Compliance with this specification is measured against all aspects of the technical and documentary artifacts contained within the specification release package.
This specification changed names and numeric designators multiple times since its inception in the late 1990's.
The IC Chief Information Officer maintains this specification via the Data Coordination Activity (DCA) and Common Metadata Standards Tiger Team (CMSTT).
Technical Specification Downloads
Latest Approved Public Release:
- XML Data Encoding Specification for Information Security Markings (V2021-NOVr2022-NOV -Standalone Package)
- XML Data Encoding Specification for Information Security Markings (V2021-NOVr2022-NOV -Convenience Package)
- XML Data Encoding Specification for Information Security Markings (V2021-NOVr2022-NOV -Light Package)
Mission Requirements
Information sharing within the national intelligence enterprise will increasingly rely on information assurance metadata (including information security markings) to allow interagency access control, automated exchanges, and appropriate protection of shared intelligence when necessary.
A structured, verifiable representation of security marking metadata bound to the intelligence data is required in order for the enterprise to become inherently “smarter” about the information flowing in and around it. Such a representation, when implemented with other data formats, improved user interfaces, and data processing utilities, can provide part of a larger, robust information assurance infrastructure capable of automating some of the management and exchange decisions today being performed by human beings.
Throughout the intelligence life cycle, the enterprise needs:
- User interfaces and processing logic that helps users and services to reliably assign and manipulate information security markings at the portion and document level.
- Automated rendering of electronic portion markings, security banners, classification authority blocks, and other security control markings in accordance with the IC's classification and control marking system and associated executive orders, statutes, and DNI policies.
- Marking validation to ensure controlled values and business rules are followed.
- Cross-domain discovery, access, and dissemination capabilities based on access policy logic that leverages electronic security markings along with other key metadata about users, services, clearances, and access environments.