Subscribe to ODNI news via emailSubscribe via RSSListen to ODNI PodcastsLike ODNI on FacebookFollow ODNI on TwitterView ODNI photos on FlickrVisit ODNI’s YouTube Channel

Organization

IdAM: Authorization Attribute Set

Friday, August 17, 2012

Chief Information Officer

IC CIO Enterprise Integration & Architecture

IdAM: Authorization Attribute Set

Overview

The IC Enterprise Authorization Attribute Exchange between IC Attribute Services, Authorization Attribute Set v1.0 codifies the minimum set of enterprise-level authorization attributes that IC elements are expected to provide if they participate in the Intelligence Community Unified Authorization and Attribute Service (UAAS) architecture. It provides a common, consistent way to identify IC enterprise authorization attributes of IC persons produced by, stored within, or shared throughout the IC’s TS/SCI information domain.

The name, definition, cardinality, and controlled vocabulary for each attribute are defined in order to promote interoperability between UAAS-compliant attribute services established by participating IC Agencies. The set of authorization attributes described in the specification is designed for implementation within products and servers that are capable of supporting the Encrypted Mode option of the OASIS SAML V2.0 Attribute Sharing Profile for X.509 Authentication-Based Systems, Committee Specification 01.

Value Proposition

IC Enterprise Authorization Attribute Exchange between IC Attribute Services, Authorization Attribute Set v1.0 establishes detailed requirements for enterprise-level authorization attributes that IC elements are expected to provide if they participate in the Intelligence Community Unified Authorization and Attribute Service federation. Its function is to facilitate the availability, accuracy, and standardization of these attributes across the IC TS/SCI enterprise, building a consistent basis for the exchange of this information between IC Elements.


Defining the mandatory minimum set of IC enterprise authorization attributes and values for sharing through the IC UAAS federation supports consistent and assured information sharing across the enterprise. The IC UAAS supports Attribute-Based Access Control (ABAC) to promote on-demand access to information and other resources by IC users and services, and reduces authorization vulnerabilities by strengthening the access control decision process.


The primary audience for this document is the implementer and/or administrator who must configure an Attribute Service to meet the requirements for participation in the IC UAAS federation. The audience for this document also includes those responsible for implementing and managing the capabilities that create, provide, modify, store, exchange, search, display, or further process IC enterprise authorization attributes.


Latest Approved Version

Previous Version

CDR: Specification Framework

Friday, August 17, 2012

Chief Information Officer

IC CIO Enterprise Integration & Architecture

CDR: Specification Framework

Overview

This Content, Discovery and Retrieval (CDR) Specification Framework document provides guidance for ensuring consistency and interoperability in the development of CDR Service Specifications. Generally, it describes the structure and content for CDR Service Specifications including the description of their key characteristics and a decomposition of key behaviors in the context of various environmental and technical considerations.

This CDR Specification Framework document is intended to provide both CDR Service Specification developers/authors and CDR service developers/implementers guidance for developing and implementing CDR Service Specifications. Specifically, this Specification Framework describes the Interface models and related behavior for each Service Specification and how they should be codified. For CDR Service Specification developers/authors, the framework provides the structure and content guidance for how CDR Service Specifications should be documented. For CDR service developers/implementers, the framework provides the common implementation and behavior guidance that, coupled with a specific CDR Service Specification, enables the realization of a CDR service.

This specification supports Intelligence Community Directive 501(ICD 501), Discovery, Dissemination or Retrieval of Information within the Intelligence Community, which establishes policies for (1) discovery, and (2) dissemination or retrieval of intelligence and intelligence-related information collected, or analysis produced by the Intelligence Community.

This specification framework is maintained by the IC Chief Information Officer via the Services Coordination Activity (SCA) and Content Discovery and Retrieval Integrated Product Team (CDR IPT).


Value Proposition

This CDR Specification Framework describes in greater detail the CDR Components and capabilities presented in the CDR Reference Architecture. It is meant to provide guidance in enough detail to enable interoperability among independent implementations without otherwise constraining the implementation itself. In this vein, this document describes inputs and outputs to each component in the context of the expected behavior that clarifies what is needed as inputs, outputs, and other effects that are expected to be produced. It does not, however, specify the details of the internal implementation processing.


Latest Approved Version

CDR: Reference Architecture

Friday, August 17, 2012

Chief Information Officer

IC CIO Enterprise Integration & Architecture

CDR: Reference Architecture

Overview

This IC/DoD enterprise Content Discovery and Retrieval Reference Architecture (CDR RA) provide conceptual and contextual guidance to architects, engineers, and developers tasked to implement CDR specifications. The CDR Reference Architecture (RA) is the keystone artifact for the overall set of guidance artifacts. The primary content of the CDR RA is the definition of an extensible set of capabilities and components that are realized via service specifications. It also describes various architecture interaction patterns and the specific technical framework to enable robust, scalable, and repeatable implementations across varying business and mission boundaries.

The CDR RA defines two primary capabilities - content discovery and content retrieval and is comprised of six core CDR components: Search, Brokered Search, Retrieve, Describe, Deliver, and Query Management that provide these capabilities. The CDR RA describes an architecturally driven approach for guiding the IC/DoD Enterprise towards enabling content discovery and retrieval.

This specification supports Intelligence Community Directive 501(ICD 501), Discovery, Dissemination or Retrieval of Information within the Intelligence Community, which establishes policies for (1) discovery, and (2) dissemination or retrieval of intelligence and intelligence-related information collected, or analysis produced by the Intelligence Community.

This reference architecture is maintained by the IC Chief Information Officer via the Services Coordination Activity (SCA) and Content Discovery and Retrieval Integrated Product Team (CDR IPT).


Value Proposition

This CDR reference architecture defines two distinct, but inter-related capabilities: Content Discovery, and Retrieval.
  • Content Discovery provides consumers with the ability to discover the existence of potentially relevant content resources and content collections from across the IC/DoD Enterprise. Content Discovery also enables consumers to discover valuable metadata about content resources to support making them visible, accessible, understandable, and trusted.
  • Retrieval provides consumers the ability to retrieve and route specific content resources. To do so, content providers are to ensure their content is accessible to the Enterprise.



Latest Approved Version

 

Previous Version

 

CDR: Search

Friday, August 17, 2012

Chief Information Officer

IC CIO Enterprise Integration & Architecture

CDR: Search

Overview

This IC/DoD enterprise encoding specification defines requirements and provides guidelines for the realization of the Content Discovery and Retrieval (CDR) Search component as both a RESTful, OpenSearch [OS] web service and using the SOAP binding, hereafter termed a Search Service. This component provides a common interface and behavioral model for IC and DoD content collections, enabling content consumers to discover relevant content resources from disparate collections across the IC/DoD Enterprise. The content of this specification describes the Search Service’s behavior, interface and other aspects in detail, providing enough information for Search Service providers and consumers to create and use CDR-conformant Search services.

The Search service exposes a single Search operation that is responsible for three activities that underpin Content Discovery capabilities: search, result presentation, and results paging. A Search service’s results are resource metadata rather than actual content resources. In the context of Search, resource metadata generally refers to a subset of a resource’s available metadata, not the entire underlying record. Results normally contain information needed for a consumer to retrieve or otherwise use the referenced resource.


Value Proposition

This specification supports Intelligence Community Directive 501(ICD 501), Discovery, Dissemination or Retrieval of Information within the Intelligence Community, which establishes policies for (1) discovery, and (2) dissemination or retrieval of intelligence and intelligence-related information collected, or analysis produced by the Intelligence Community.

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 Services Coordination Activity (SCA) and Content Discovery and Retrieval Integrated Product Team (CDR IPT).

This specification is designed to fulfill a number of requirements in support of the transformational efforts of the Intelligence Community and Department of Defense Enterprise(IC/DoD). Features of this specification are to:
  • Searching through content and metadata in multiple formats as specified by the consumer, such as image files and textual documents.
  • Searching through information content that is static, dynamic, structured and unstructured.
  • Enable searching through and appropriately processing of information content and metadata at different classification levels, and with different handling caveats; information which could be located on different security domains.
  • Searching through natural language content (probably in many different languages) or highly formatted content such as geospatial or temporal content. (Data sources can be active [current, dynamically changing] or historic [static], each containing different data types).



Latest Approved Versions



Previous Versions

CDR: Query Management

Friday, August 17, 2012

Chief Information Officer

IC CIO Enterprise Integration & Architecture

CDR: Query Management

Overview

This IC/DoD enterprise encoding specification defines requirements and provides guidelines for the realization of the Content Discovery and Retrieval (CDR) Query Management component as a web service using both a RESTful, OpenSearch [OS] and SOAP style binding, hereafter termed the Query Management (QM) Service, as a web service using the SOAP style binding. The Query Management (QM) Component, as defined by the “IC/DoD Content Discovery and Retrieval (CDR) Specification Framework” , is a CDR Component that manages Saved Searches and may initiate search requests based on Saved Searches. It describes the external service interfaces and the internal activities that provide service behaviors so that service providers and consumers can create and use CDR-compliant Query Management Services.

This specification supports Intelligence Community Directive 501(ICD 501), Discovery, Dissemination or Retrieval of Information within the Intelligence Community, which establishes policies for (1) discovery, and (2) dissemination or retrieval of intelligence and intelligence-related information collected, or analysis produced by the Intelligence Community.

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 Services Coordination Activity (SCA) and Content Discovery and Retrieval Integrated Product Team (CDR IPT).


Value Proposition

This specification is designed to fulfill a number of requirements in support of the transformational efforts of the Intelligence Community and Department of Defense Enterprise(IC/DoD). ). The six functions listed below provide QM service consumers with a coordinated set of capabilities that support managing and using both searches and search related information. This specification mandates the generic interfaces that a QM consumer would utilize to manage and use a Saved Search:
  • Create –The Create function is used to insert a new Saved Search into the QM Collection.
  • Read – The Read function is used to retrieve a Saved Search from the QM Collection.
  • Update – The Update function is used to change a Saved Search in the QM Collection.
  • Delete – The Delete function is used to logically remove a Saved Search from the QM Collection.
  • Execute – The Execute function enables a QM consumer to execute (run) a Saved Search at the location specified by the Target Search Capability. To process an execute request, the Query Management Service retrieves the Target Search Capability (the location of the Search Service) and the Search Request from the Saved Search. This information is then used to initiate the Search. This capability SHOULD leverage the CDR Search approach to effect the execution of a Saved Search.
  • Search – The Search function enables a prospective consumer to interrogate the QM Collection on the basis of anything to be found in the Saved Search Bundle or the Saved Search Description to determine if a suitable search has already been created. Generic search terms can be used to provide functionality that provides a ‘list’ of the contents of the QM Collection. This capability SHOULD leverage the CDR Search discovery approach.

Latest Approved Versions

You are leaving DNI.gov

You have selected to open
http://www.anotherwebsite.com

If you would like to not see this alert again, please click the
"Do not show me this again" check box below