NIAP: Archived U.S. Government Approved Protection Profile - Protection Profile for Enterprise Security Management - Identity and C...
NIAP/CCEVS

NIAP Oversees Evaluations of Commercial IT Products for Use in National Security Systems
Questions?  We're here to help
  NIAP  »»  Protection Profiles  »»  Archived PPs  »»  Details  
Archived U.S. Government Approved Protection Profile - Protection Profile for Enterprise Security Management - Identity and Credential Management Version 1.4

Short Name: pp_esm_icm_v1.4

Technology Type: Enterprise Security Management

CC Version: 3.1

Date: 06 September 2012

Succeeded By: pp_esm_icm_v2.1

Sunset Date: 21 November 2013 [Sunset Icon]

Conformance Claim: None

 

PP OVERVIEW

This protection profile focuses on the aspect of ESM that is responsible for enforcing identity and credential management. Identity and Credential Management products will generate and issue credentials for subjects that reside within the enterprise. They will also maintain the organizational attributes that are associated with these subjects. By providing a means for subjects to validate their identities and determining the relationship these subjects have to the enterprise, an Identity and Credential Management product is able to support enterprise accountability and access control.

 

The establishment of unique, unambiguous identities is an important foundational capability that enables issuance and management of credentials and authorization attributes. The notion of identity refers to that unique identifier assigned to an individual against which credential and attribute data can be associated.

 

In order for an individual to be identified as a user within the ESM system, they must be enrolled. Enrollment refers to the act of assigning a unique identifier to a subject, generating and issuing credentials, defining attributes for a user, and propagating that data to any repositories that utilize it. It is necessary for the TSF to be able to securely transmit this data to those components.

The TOE is expected to exhibit the following behavior:

- Provisioning of subjects (enroll new subjects to an organizational repository, associate and disassociate subjects with organizationally-defined attributes)

- Issue and maintain credentials associated with user identities

- Publish and change credential status (such as active, suspended, or terminated)

- Establish appropriate trusted channels between itself and compatible Policy Management and Authentication Server ESM products

- Generate an audit trail of configuration changes and subject identification and authentication activities

- Write audit trail data to a trusted source

- Securely transmit identity and credential attribute data via a trusted channel

 

While this PP defines the capabilities of the TOE as if they belong to a standalone product, some or all of these capabilities may belong to an ESM Policy Management (PM) product as well. If an ST is written that claims conformance to this PP, the distribution of these capabilities must be clearly delineated.

 

Note that this is one of many Protection Profiles in the ESM PP family. This PP is meant to be used for one component in an ESM system and not to work in isolation. At minimum, at least one compatible Authentication Server product must be identified. Compatibility is defined by the ability of that product to authenticate identities and credentials that are defined by the TOE. Depending on how access control is implemented in the organization, ESM PP solutions for policy management, access control, and auditing may need to be implemented as well. If any of these components are expected to be deployed against an organizational baseline, a secure configuration management solution may also need to be deployed. A customer could seriously compromise the overall security of the enterprise architecture if they are to deploy a solution without using all applicable ESM PP evaluated products.

This U.S. Government Approved Protection Profile is not assigned to any Validated Products

This U.S. Government Approved Protection Profile does not have any related Technical Decisions

Please forward any Protection Profile specific comments to the applicable Technical Rapid Response Team (TRRT).

Please forward any general questions to our Q&A tool.

Site Map              Contact Us              Home