Collaborative Protection Profiles (cPP) and Supporting Documents (SD)


 
The lists below contain collaborative Protection Profiles and related Supporting Documents developed openly by international Technical Communities (iTC) consisting of vendors, test laboratories, CCRA nations, and academia.
 

   

 

cPPs with SDs that have completed review by the CCDB for compliance with the CC and CEM

The cPPs below include SDs that have completed CCDB review for compliance with the CC and CEM and are therefore available for use under the terms of the Common Criteria Recognition Arrangement (CCRA). Evaluations conducted against cPPs on this list are mutually recognized according to the terms of the CCRA.

<This list currently has no items.>

cPPs with SDs that are currently being reviewed by the CCDB for compliance with the CC and CEM

The following list contains collaborative Protection Profiles (cPPs) available for use. However, each Supporting Document (SD) listed below is currently being reviewed by the CCDB for compliance with the CC and the CEM. These documents are made available here in order to assist the iTC and to enable evaluations to take place as quickly as possible while the (necessarily thorough) CCDB review and voting process takes place. Not all schemes need to use these documents (although national endorsement statements may of course mandate their use). Those that do are encouraged to share experiences/recommendations with the iTC.

Products evaluated and certified using these documents are mutually recognized under the CCRA since the scheme performing the evaluation will ensure consistency with the CC and the CEM. Should the wider CCDB review find that an SD is not fully compliant; the iTC will be given notice of the necessary changes and a reasonable time to incorporate these before resubmitting to the CCDB review process. If an SD requires multiple CCDB reviews prior to approval, until the SDs are approved, the non-compliant parts of the SDs will be replaced by CEM activities. Once the documents have been approved by the CCDB they will be moved to the upper section and become mandatory.

 

expand/collapse all categories

Boundary Protection Devices and Systems – 1 Protection Profile
Protection Profile Version Assurance Level Issued Certified

collaborative Protection Profile for Stateful Traffic Filter Firewalls v1.0

  • Protection Profile
  • Supporting Document
  • Endorsement Statement
  • 1.0 None 2015-02-27 No *
    Data Protection – 4 Protection Profiles
    Protection Profile Version Assurance Level Issued Certified

    collaborative Protection Profile for Full Drive Encryption - Encryption Engine v2.0

  • Protection Profile
  • Supporting Document
  • Endorsement Statement
  • 2.0 None 2016-09-09 No *

    collaborative Protection Profile for Full Drive Encryption – Authorization Acquisition v2.0

  • Protection Profile
  • Supporting Document
  • Endorsement Statement
  • 2.0 None 2016-09-09 No *

    collaborative Protection Profile for Full Drive Encryption - Encryption Engine v1.0

  • Protection Profile
  • Supporting Document
  • Endorsement Statement
  • 1.0 None 2015-02-27 No *

    collaborative Protection Profile for Full Drive Encryption – Authorization Acquisition v1.0

  • Protection Profile
  • Supporting Document
  • Endorsement Statement
  • 1.0 None 2015-02-27 No *
    Network and Network-Related Devices and Systems – 1 Protection Profile
    Protection Profile Version Assurance Level Issued Certified

    collaborative Protection Profile for Network Devices v1.0

  • Protection Profile
  • Supporting Document
  • Endorsement Statement
  • 1.0 None 2015-02-27 Certification Report

    * A cPP without a Certification Report indicates that no determination of compliance to the CC/CEM (APE class) has yet been made. Consequently, the cPP is outside CCRA mutual recognition. Some schemes may certify a cPP upon first use in combination with an IT product evaluation. In that case, an evaluation of an IT product where the Security Target claims compliance to these collaborative Protection Profiles must include the relevant work units related to the ASE class.