Chief Information Officer
IC Technical Specifications
Unified Identity Attribute Set - Attribute Practice Compliance Statements
Overview
This Attribute Practice Compliance Statements for the Unified Identity Attribute Set (UIAS-APCS) provides concise direction to Intelligence Community (IC) elements required by Intelligence Community Standard (ICS) 500-30, Enterprise Authorization Attributes: Assignment, Authoritative Sources, and Use for Attribute-Based Access Control Of Resources, to produce an Attribute Practice Statement (APS) for each Attribute Service (AS) of an IC element.
Compliance with an Attribute Practice Compliance Statement (APCS) document ensures interoperability and consistently applied attributes in dynamic Information Technology (IT) environments including the Intelligence Community Information Technology Enterprise (IC ITE). An APCS alleviates the need for each IC element to produce an APS and ensure compliance with ICS 500-30, and IC Enterprise Attribute Exchange Between IC Attribute Services Unified Identity Attribute Set (UIAS.XML).
This UIAS-APCS has a dependency on UIAS.XML. Citations for the Controlled Vocabulary Enumeration (CVE)s are covered in the UIAS.XML technical specification and should be complied with in accordance with the needs and practices of the responding organization, and that such compliance should also designate the reasoning for compliance approach or its variations. The UIAS.XML MUST be consulted in conjunction with this document.
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:
- Attribute Practice Compliance Statements for the Unified Identity Attribute Set (V2021-NOV - Standalone Package)
- Attribute Practice Compliance Statements for the Unified Identity Attribute Set (V2021-NOV - Convenience Package)
- Attribute Practice Compliance Statements for the Unified Identity Attribute Set (V2021-NOV - Light Package)
Mission Requirements
As the IC environment evolves, the user base grows with more diverse membership with unique data sources per member entity. The IC's move to a simplified architecture for access control and authorization is predicated on ABAC and an IC Authorization service being trustworthy. This drives an increased need to better understand attribute provisioning and ensure that all IC elements provision and maintain access control and authorization related attributes consistently. This document specifies compliance statements to confirm that enterprise identity attributes are consistent with the attributes defined in the UIAS.XML technical specification and that IC elements maintain attributes consistent with Appendix C of ICS 500-30, Operation of ASs and AAS. Compliance with the ICS 500-30 will ensure that all IC elements provision and maintain attributes for availability, accuracy, consistency, privacy, confidentiality, and integrity across persona lifecycles.
Chief Information Officer
IC Technical Specifications
XML Data Encoding Specification for Intelligence Community Enterprise Data Header
Overview
This XML Data Encoding Specification for Enterprise Data Header (EDH.XML) defines detailed implementation guidance for using Extensible Markup Language (XML) to encode EDH 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 enterprise data header data concepts using XML.
This specification is applicable to the Intelligence Community (IC) and information produced by, stored, or shared within the IC. This DES may have relevance outside the scope of intelligence; however, prior to applying outside of this defined scope, the DES should be closely scrutinized and differences separately documented and assessed for applicability.
This specification applies to the IC, as defined by the National Security Act of 1947, as amended; 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 Standards Coordination Activity (DSCA) and Common Metadata Standards Tiger Team (CMSTT).
Technical Specification Downloads
Latest Approved Public Release:
- XML Data Encoding Specification for Intelligence Community Enterprise Data Header (V2019-MAR - Standalone Package)
- XML Data Encoding Specification for Intelligence Community Enterprise Data Header (V2019-MAR - Convenience Package)
- XML Data Encoding Specification for Intelligence Community Enterprise Data Header (V2019-MAR - Light Package)
Mission Requirements
Information sharing within the national intelligence enterprise will increasingly rely on information assurance metadata (including enterprise data headers) to allow interagency access control, automated exchanges, and appropriate protection of shared intelligence. A structured, verifiable representation of security 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.
The Intelligence Community (IC) has standardized the various classification and control markings established for information sharing within the Information Security Markings (ISM) specification. The IC Enterprise Data Header XML specification further expands on this body of work, adapting and extending it as necessary to meet mission-unique needs. By specifying a data object's header information required for exchange on the IC Enterprise, EDH ensures a secure method of information sharing and discovery, supporting use cases such as the IC Cloud.
Chief Information Officer
IC Technical Specifications
Web Service Security
Overview
The High Level Guidance for Web Service Security (WSS-HLG) provides guidance to solutions architects and developers on how to consistently approach circumstances for which security solutions are required. This document focuses on security fundamentals essential to designing and building secure solutions that involve web services focusing on approaches for access control, use of assertions, security markings, confidentiality, integrity, and non-repudiation. The WSS-HLG provides solution approaches at a high level, intended to provide an understanding of information security fundamentals essential to such solutions, for the purpose of building both secure and interoperable approaches that are consistent across the IC.
The High Level Guidance for Web Service Security (WSS-HLG) provides important guidance for building and integrating with web services solutions in an interoperable, secure, and consistent manner. As there is a great number of standards, technical mechanisms, and capabilities that can be used for building web services security solutions, it is important that solutions architects understand the tradeoffs, risks, and benefits of approaches. It is critical, from a security and interoperability perspective, that security mechanisms are applied in a consistent manner, and this document provides needed guidance in the areas of access control, assertion passing, security markings, confidentiality, integrity, and non-repudiation.
The intended audience of this information guidance document is project managers, software architects, network architects, and developers who develop and integrate with web services. This document provides guidance in areas that will be important in satisfying security requirements and information security goals in a secure and interoperable manner.
Technical Specification Downloads
Latest Approved Public Release:
Chief Information Officer
IC Technical Specifications
Intelligence Community Only Need-To-Know
Overview
This XML Data Encoding Specification for Intelligence Community Only Need-To-Know Profile (ICO-NTK.XML) provides detailed implementation guidance to limit dissemination of appropriately tagged information solely to members of the Intelligence Community (IC). Certain information is only permitted to be disseminated to and accessed by members of the IC. This profile defines a specification that uses NTK for conveying the requirement to limit dissemination.
This is the first release of the specification and therefore provides no backward capability.
Compliance with this specification is measured against all aspects of the technical and documentary artifacts contained within the specification release package.
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:
- Intelligence Community Only Need-To-Know Profile (V10 – Standalone Package (Release Date: 18 Oct 2013))
- Intelligence Community Only Need-To-Know Profile (V10 – Light Package (Release Date: 18 Oct 2013))
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:
- Defines the use of elements and attributes from NTK, associated structures, relationships, requirements, cardinality, and permissible values for representing ICO-NTK data concepts using XML.
- Defines how information is disseminated to and accessed by members of the IC.
- Discusses relationship between ICO-ACES and ADD re mapping