/FCS_COP.1 jikl Or as follows: FCS_COP.1/abcde FCS_COP.1/efgh FCS_COP.1/ijkl NDcPP, Application Note 5 reads as: Recommend the application note be 3 Suggested change not Page 53, changed to read as: implemented since the an auditable event is instigated Section intention of the original by another component, the Where an auditable event is 6.3.1.2 language was not to imply component that records the event triggered by another that the user identity must associate the event with the component, the component associated with a given identity of the instigator (applies to that records the event must event should be captured, distributed TOEs only). associate the event with the rather it was that the identity of the user that initiating component caused the event (applies to Not sure and are ‘instigated’ ‘instigator’ identity should be distributed TOEs only). the correct term to use. captured. Language updated to reflect and clarify the original intention. Fix the spacing in the application note 6, To: 3 Spacing fixed. Page 54, from (FTP_ITC.1) or “….external Section or intercomponent (FPT_ITT.1 or “….external(FTP_ITC.1) 6.3.2.1, intercomponent(FPT_ITT.1)….” FTP_ITC.1)….” case the transmission would not be done “In NDcPP, Change possible” to 3 Application note 6 and “the “that in real-time the TSS has to provide details possibility” 101 updated with new AppNote language to clarify intent 6
/FCS_COP.1 jikl Or as follows: FCS_COP.1/abcde FCS_COP.1/efgh FCS_COP.1/ijkl NDcPP, Page 53, Section 6.3.1.2 Application Note 5 reads as: an auditable event is instigated by another component, the component that records the event must associate the event with the identity of the instigator (applies to distributed TOEs only). Not sure ‘instigated’ and ‘instigator’ are the correct term to use. Recommend the application note be changed to read as: Where an auditable event is triggered by another component, the component that records the event must associate the event with the identity of the user that caused the event (applies to distributed TOEs only). 3 Suggested change not implemented since the intention of the original language was not to imply that the user identity associated with a given event should be captured, rather it was that the initiating component identity should be captured. Language updated to reflect and clarify the original intention. Page 54, Section 6.3.2.1, Fix the spacing in the application note 6, from “….external(FTP_ITC.1) or intercomponent(FPT_ITT.1)….” To: “….external (FTP_ITC.1) or intercomponent (FPT_ITT.1 or FTP_ITC.1)….” 3 Spacing fixed. NDcPP, AppNote 6 “In case the transmission would not be done in real-time the TSS has to provide details Change “the possible” to “that possibility” 3 Application note 6 and 101 updated with new language to clarify intent
ConsolidatediTCcomments-NDcPPv2-20160721_v2.9.docx