NIAP: Archived U.S. Government Approved Protection Profile - Intrusion Detection System System Protection Profile, Version 1.6, dat...

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 - Intrusion Detection System System Protection Profile, Version 1.6, dated April 4, 2006

Short Name: pp_ids_sys_v1.6

Technology Type: Wireless Monitoring

CC Version: 2.x

Date: 2006.04.04

Preceded By: pp_ids_sys_v1.5

Succeeded By: pp_ids_sys_br_v1.7

Sunset Date: 2008.03.21 [Sunset Icon]

Conformance Claim: EAL2

Protection Profile [PDF]



Herewith a brief summary, sufficiently detailed to enable a potential user to determine whether the PP is of interest. This PP version contains the same information as version 1.4. However, an Errata sheet section has been added to clarify some of the security functional requirements that do not support the stated applicability.

The Common Criteria (CC) Intrusion Detection System (System) Protection Profile specifies a set of security functional and assurance requirements for Information Technology (IT) products. An Intrusion Detection System (IDS) monitors an IT System for activity that may inappropriately affect the IT System's assets. An IT System may range from a computer system to a computer network. An IDS System (System) consists of Sensors, Scanners and Analyzers (i.e., IDS components). Sensors and Scanners collect information regarding IT System activity and vulnerabilities, and they forward the collected information to Analyzers. Analyzers perform intrusion analysis and reporting of the collected information.

IDSSYPP_V1.6-conformant products support the ability that monitor (both real-time and statically) an IT System for activity that may inappropriately affect the IT System's assets and react appropriately. IDSSYPP_V1.6-conformant products also provide the ability to protect themselves and their associated data from unauthorized access or modification and ensure accountability for authorized actions.

The IDSSYPP_V1.6 provides for a level of protection which is appropriate for IT environments that require detection of malicious and inadvertent attempts to gain inappropriate access to IT resources, where the System can be appropriately protected from hostile attacks. Though products that are IDSSYPP_V1.6-conformant can be used to monitor and analyze a system or network in a hostile environment, they are not designed to resist direct, hostile attacks. The IDSSYPP_V1.6 does not fully address the threats posed by malicious administrative or system development personnel. This profile is also not intended to result in products that are foolproof and able to detect intrusion attempts by hostile and well-funded attackers. IDSSYPP_V1.6-conformant products are suitable for use in both commercial and government environments. The IDSSYPP_V1.6 was constructed to provide a target and metric for the development of systems. This PP identifies security functions and assurances that represent the lowest common set of requirements that should be addressed by a useful IDS System.


Because a PP is written to be implementation-independent, there may be some ambiguities that do not arise until a specific implementation is being evaluated against it. When this happens, a resolution is established through the Observation Decision (OD) process in the form of a Precedent Decision (PD), which is to be used consistently in subsequent evaluations involving the PP in question. The Precedent Decisions specifically associated with this PP are listed below:


This profile is intended to be generally applicable to products regardless of whether they are embedded, stand-alone, centralized, or distributed. However, based upon the results of numerous products trying to claim conformance to this PP, it was noted that several of the security functional requirements do not support the stated applicability. The Errata Section identifies the areas that have been identified as problematic for software vendors who are seeking conformance to this PP and clarifies the security function requirements in a manner that would allow a vendor to successfully achieve compliance. Software vendors who follow the guidance in this Errata Section will be able to successfully claim conformance to this PP, effective immediately.

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