Skip to content

refactoring of crypto SFRs to match crypto catalog #196

@jfisherbah

Description

@jfisherbah

As part of ensuring PPs are conformant to CNSA 2.0 and externally consistent with one another, it is recommended that the presentation and iteration naming of FCS_CKM.1 and FCS_COP.1 be updated to reflect what has been specified in the CCDB crypto catalog (https://commoncriteriaportal.org/files/ccfiles/CCDB-018-v1.0-2025-Jan-31-Final-Specification_of_Functional_Requirements_for_Cryptography.pdf).

Preliminary updates to the GPCP PP (https://commoncriteria.github.io/gpcp/master) have been made to reflect this catalog, so the XML is generally portable aside from the specific selections that we want to make available.

It is my understanding that EAs are in development but completion is a high priority, so these could be entered as placeholders for the time being.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions