PD-0052: Can There Be A Single Blanket Description Of Error Messages in an FSP?

This decision represents a long-term technical decision based on an OD, and may not be the same as the final results of the source OD. With respect to published criteria documentation and scheme documents, it provides suggested guidance on evaluation direction, but is not authoritative. Authoritative decisions are provided through the published criteria documents and published scheme and international interpretations thereof. With respect to published PPs, PDs are authoritative corrections to the PP, based on input from the PP author (if available), that are in force until the publication of the next revision of that PP.

Issue

If man pages are cited as evidence of the effects, exceptions, and errors, as required by the ADV_FSP.1 component, is it acceptable for the introduction section to contain a blanket coverage statement?

Resolution

Error codes must be associated with the interfaces that cause them to occur. Neither the format or presentation style is mandated. However, it must be possible for the evaluator to ascertain which error codes are caused by each interface.

Support

The CCEVS Scheme Publication #3, Version 1.0, February 2002, Section C.3.1 provides the following guidance relative to ADV_FSP work units:

"For instance, it is common in some documentation to simply group all possible error messages in one chapter, and not tie these error messages to a single interface. This does not meet the requirement; error messages need to be associated with each interface."

As an added point, it would not be possible to fully judge the developer's test coverage or to devise additional evaluator testing without knowing the expected results of providing various stimuli to the interfaces.

Modification History:

2004-08-12

Updated effective date to reflect the date the PD was issued. (August 2004 NIB 6.c.xiv)

References:

• CC v2.1

Related NIs:

• None

Related CCIMB-INTERPs:

• None

Source OD: 0087