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.