of TSF Data Protection Application Note 30 states: Clarify Application Note language 1 Added additional Profile to better align it with SFR. If explanatory paragraph to distributed TOEs all TOE components “For v1.0.3, mandatory component testing is Application Note 30 have to perform self-tests.” Section intended new requirement, consider which provides additional This language (“have to”) mandates 6.7.3 changing SFR wording to make clarity over the performing of self-tests for TOE “all this clearer. requirement. components”. This is does not align with actual SFR wording or how it is applied to TSF non-distributed TOEs. testing Protection Application Note 38 states: Revise application note to clarify 2 Application note 38 Profile that automatic synchronization reworded to clarify the distributed TOEs it is expected that the “For v1.0.3, between components is necessary. requirement. administrator ensures synchronization Section between the time settings of different TOE 6.7.5, components.” This application note would likely be Time misinterpreted to argue that MANUAL time Stamps settings is acceptable. Protection Authentication Failure Management is I believe IP blocking must be 1 No change. The addition Profile much needed addition to NDcPP. allowed in addition to account of IP blocking with v1.0.3, Unfortunately, FIA_AFL.1.2 as written will blocking or end-users will simply FIA_AFL requires further lead to usability issues. turn off such feature to prevent discussion by the wider Section frequent administrative lockouts. iTC and the commenter is 6.5.1 Administrative Usernames are not presently advised to raise this for FIA_AFL treated as sensitive and often follow discussion as part of a organization-mandated conventions (e.g. future version. FirstLastname). Consequently, for many
of TSF Data Protection Profile v1.0.3, Section 6.7.3 TSF testing Application Note 30 states: “For distributed TOEs all TOE components have to perform self-tests.” This language (“have to”) mandates performing of self-tests for “all TOE components”. This is does not align with actual SFR wording or how it is applied to non-distributed TOEs. Clarify Application Note language to better align it with SFR. If mandatory component testing is intended new requirement, consider changing SFR wording to make this clearer. 1 Added additional explanatory paragraph to Application Note 30 which provides additional clarity over the requirement. Protection Profile v1.0.3, Section 6.7.5, Time Stamps Application Note 38 states: “For distributed TOEs it is expected that the administrator ensures synchronization between the time settings of different TOE components.” This application note would likely be misinterpreted to argue that MANUAL time settings is acceptable. Revise application note to clarify that automatic synchronization between components is necessary. 2 Application note 38 reworded to clarify the requirement. Protection Profile v1.0.3, Section 6.5.1 Authentication Failure Management is much needed addition to NDcPP. Unfortunately, FIA_AFL.1.2 as written will lead to usability issues. Administrative Usernames are not presently treated as sensitive and often follow organization-mandated conventions (e.g. FirstLastname). Consequently, for many FIA_AFL I believe IP blocking must be allowed in addition to account blocking or end-users will simply turn off such feature to prevent frequent administrative lockouts. 1 No change. The addition of IP blocking with FIA_AFL requires further discussion by the wider iTC and the commenter is advised to raise this for discussion as part of a future version.
ConsolidatediTCcomments-NDcPPv2-20160721_v2.9.docx