Specifications

83
P.ACCOUNTABILITY
O.AUDIT_GENERATION addresses this policy by providing the administrator
with the capability of configuring the audit mechanism to record the actions of a
specific user, or review the audit trail based on the identity of the user.
Additionally, the administrator’s ID is recorded when any security relevant
change is made to the TOE (e.g., access rule modification, start/stop of the audit
mechanism, establishment of a trusted channel, etc.).
OE.AUDIT_PROTECTION provides protected storage of TOE and operational
environment audit data in the environment.
OE.AUDIT_REVIEW - Further supports accountability by providing
mechanisms for viewing and sorting the audit logs
O.MANAGE ensures that access to administrative functions and management of
TSF data is restricted to the administrator.
OE.MANAGE ensures that the administrator can manage audit functionality in
the TOE operational environment.
O.TIME_STAMPS plays a role in supporting this policy by requiring the TOE
to provide a reliable time stamp (via an external NTP server). The audit
mechanism is required to include the current date and time in each audit record.
All audit records that include the user ID, will also include the date and time that
the event occurred.
OE.TIME_STAMPS ensures that the TOE operational environment provides
time services.
O.TOE_ACCESS and OE.TOE_ACCESS support this policy by controlling
logical access to the TOE and its resources. This objective ensures that users are
identified and authenticated so that their actions may be tracked by the
administrator.
P.CRYPTOGRAPHY
O.CRYPTOGRAPHY satisfies this policy by requiring the TOE to implement
NIST FIPS validated cryptographic services. These services will provide
confidentiality and integrity protection of user data while in transit to remote
parts of the TOE.
O.RESIDUAL_INFORMATION satisfies this policy by ensuring that
cryptographic data is cleared according to FIPS 140-2.
P.CRYPTOGRAPHY_
VALIDATED
O.CRYPTOGRAPHY satisfies this policy by requiring the TOE to implement
NIST FIPS validated cryptographic services. These services will provide
confidentiality and integrity protection of user data while in transit to remote
parts of the TOE.
O.CRYPTOGRAPHY_VALIDATED satisfies this policy by requiring that all
cryptomodules for cryptographic services be NIST 140-2 validated. This will
provide assurance that the NIST-approved security functions and random
number generation will be in accordance with NIST and validated according the
FIPS 140-2.