New NIAP CCEVS Strategy for FY10
-
March 16, 2009 -
Based on the results of evaluations against the Basic and Medium Robustness Protection Profiles and comments from vendors and
our customers, NIAP has determined that the current U.S. Protection Profile Robustness model needs to be revised. The model
assumed that the same assurance levels could be achieved for every technology. Also, the implementation did not create the
necessary test plans and documentation needed to achieve consistent results across different products evaluated in different
labs.
-
The security requirements for many technologies are the same for many sectors of Government and industry. For each technology,
NSA is creating a Standard Protection Profile, which will replace any corresponding U.S. Government Protection Profile. We
will work with industry, our customers, and the Common Criteria community to create these Protection Profiles. The first
generation of these Protection Profiles will take into account the current assurance that is achievable for a technology and
the Evaluated Assurance Level (EAL) will be set based on the availability of the documentation, test plans, and tools needed to
obtain consistent and comparable results.
-
Future increases in the Evaluated Assurance Level (EAL) of each Protection Profile will require more refinement of the
assurance criteria, more detailed test plans, and greater disclosure of evaluator evidence, testing performed, and
vulnerabilities found. NIAP will work with the Common Criteria community to ensure that Common Criteria 4.0 supports these
requirements.
-
All evaluated products will maintain their certification and remain on the NIAP CCEVS Validated Products List (VPL). All
on-going evaluations will continue to completion and receive their certification and VPL listing based on their original entry
criteria. Over the next few months, the existing U.S. Government Basic Robustness Protection Profiles will be updated to
reflect more current functional requirements. Beginning 1 October 2009, NIAP will only accept products into evaluation that
comply with either the updated U.S. Government Basic Robustness Protection Profile or with the corresponding new Standard
Protection Profile. As each new Standard Protection Profile is published, the old corresponding U.S. Government Protection
Profile will be given a 1-year expiration date.
-
When no validated U.S. Government Protection Profile exists and FIPS validation is not appropriate, NSTISSP #11 currently
requires that COTS IA and IA enabled IT products be Common Criteria evaluated. Consequently, many products are evaluated
against a vendor provided Security Target without any reference to government needs in a validated Protection Profile. NSA and
NIAP will pursue revisions to existing U.S. Government policies to only require a Common Criteria evaluated product if a
validated U.S. Government Protection Profile exists for that technology.
-
CCEVS will continue to provide updates on the status of the program via the NIAP CCEVS website. Please direct questions to us at
scheme-comments@niap-ccevs.org
or (410) 854-4458.
FY09 Acceptance Policy
-
October 1, 2008 -
For FY09, the NIAP CCEVS office will maintain the existing FY08 policy to continue accepting US
Government PP or EAL 4 compliant products into evaluation.
Mutual Recognition Statement
Since the Common Criteria Portal is successfully up and running and in order to harmonize with other CC Schemes, the NIAP Staff is no longer posting
certified products by other certificate-producing nations. The U.S. recognizes products that have been evaluated under the sponsorship of other
signatories and in accordance with the International Common Criteria for Information Technology Security Evaluation Recognition Arrangement (CCRA) for
EALs 1-4 only.
For a complete listing of products which have received Common Criteria certifications outside the U.S. please visit the
Common Criteria Portal.
Common Criteria Version 3.1 Update
The below information does not supersede the new FY08 evaluation acceptance constraints.
The Common Criteria Version 3.1 Revision 2 was published on September 2007. The criteria and methodology, is available on
the Common Criteria Portal
and the NIAP web site.
All Common Criteria Mutual Recognition Arrangement Schemes agreed to mutually recognize the use of Version 3.1. All CC
Schemes are now using CC Version 3.1. No further interpretations against CC Version 2 will be performed.
For the U.S. Common Criteria Evaluation and Validation Scheme (CCEVS) the following schedule shall be used for CC Version 3.1 evaluations:
For TOE/ST Evaluations with no PP Compliance Claims:
- All new TOE/ST evaluations shall use Version 3.1
For CC Evaluations with PP Compliance Claims:
-
A TOE/ST must claim compliance to a Version 3.1 PP, if no version 3.1 PP exists, a TOE/ST may only claim
compliance to a Version 2.x PP with the approval of the NIAP/CCEVS Director.
For PP Developments and Evaluations:
- All new PP evaluations shall use CC Version 3.1 as the evaluation standard.
For Assurance Maintenance:
Assurance Maintenance of Evaluations with NO PP Compliance Claims:
-
Assurance maintenance activities against Version 2.x evaluations may continue until 30 September 2009, after which a new
evaluation using Version 3.1 must be performed
Assurance Maintenance of Evaluations with PP Compliance Claims:
-
Assurance maintenance activities against an evaluation claiming conformance to a Version 2.x PP may continue until 30
September 2009.
|