-
The iTC received a request from NIAP to address ambiguity found in FTP_ITC.1.2 and FTP_ITC.1.3.
In FTP_ITC.1.2, there is no requirement on which party (the TSF or the authorized IT entity) shal…
-
As part of NIAP’s review process of the HCD cPP, we performed an evaluation of the APE work units and identified several needing correction. Please see the following comments:
APE_REQ.2-7, The eval…
-
**What is the change request for the cPP? Please describe.**
Selections for which only one selection is valid should use the "selection, choose one of:" construct. This is an actual CC thing. This wo…
-
As part of NIAP’s review process of the HCD cPP, we performed an evaluation of the APE work units and identified several needing correction. Please see the following comments:
APE_REQ.2-8, The eval…
-
As part of NIAP’s review process of the HCD cPP, we performed an evaluation of the APE work units and identified several needing correction. Please see the following comments:
APE_REQ.2-5, The eval…
-
As part of NIAP’s review process of the HCD cPP, we performed an evaluation of the APE work units and identified several needing correction. Please see the following comments:
APE_ECD.1-5, The eval…
-
What exactly is meant by "compliant cryptography" in the app note? Since HTTPS would seem to be a requirement from a different location (i.e. TLS package or Base-PP or something else), is there a spec…
-
Placeholder for updating TLS FP 1.1 to 2.0
We need to make sure this is consistent with existing SFRs, specifically new audit requirements.
-
**Provide the location of the issue**
cPP FCS_CKM.1 and FCS_COP.1/SigGen
**What is the enhancement request for the cPP? Please describe.**
Ed25519 was added as per #127 but Ed448 was not. Ed448 …
-
The updated CC:2022 version of the email client module will eventually reference the CC:2022 App PP which NIAP will be labeling as v2.0. To make the build work properly, a placeholder citation to the …