Appendix C. Statements of Compliance
110
1006232_RevD
Requirement: § 11.200 (a)(2) Electronic signatures that are not based upon biometrics shall be used only
by their genuine owners.
Progeny 1064: Organizations must implement policies and procedures to ensure that electronic
signatures are used only by assigned users.
Requirement: § 11.200 (a)(3) Electronic signatures that are not based upon biometrics shall be
administered and executed to ensure that attempted use of an individual’s electronic signature by
anyone other than it’s genuine owner requires collaboration of two or more individuals.
Progeny 1064: The instrument creates electronic signatures only for the user name and password
combinations of users with the Administrator permission level. For other users, access to features that
require electronic signatures is restricted. If users forget their passwords, the primary system
administrator can re-set user passwords.
Requirement: § 11.200 (b) Electronic signatures based on biometrics shall be designed to ensure that
they cannot be used by anyone other than their genuine owners.
Progeny 1064: The instrument uses combinations of user names and passwords to create electronic
signatures. No biometrics option is available.
Requirement: § 11.300 Persons who use electronic signatures based upon the use of identification codes
in combination with passwords shall employ controls to ensure their security and integrity. Such controls
shall include: a) Maintaining the uniqueness of each combined identification code and password, such
that no two individuals have the same combination of identification code and password. b) Ensuring that
identification and password issuances are periodically checked, recalled, or revised. c) Following loss
management procedures to electronically deauthorize lost, stolen, missing, or otherwise potentially
compromised tokens, cards, and other devices that bear or generate identification code or password
information, and to issue temporary or permanent replacements using suitable, rigorous controls. d) Use
of transaction safeguards to prevent unauthorized use of passwords and/or identification codes and to
detect and report in an immediate and urgent manner any attempts at their unauthorized use to the
system security unit, and as appropriate, to organizational management. e) Initial and periodic testing of
devices, such as tokens or cards, that bear or generate identification code or password information to
ensure that they function properly and have not been altered in an unauthorized manner.
Progeny 1064: The instrument addresses each clause of this article as follows:
a) The instrument does not allow duplicate user names for different user accounts.
b), d) & e) The instrument allows for passwords to be periodically recalled or revised through a
password aging feature that is configured by the primary system administrator while setting up
the instrument.
c) When necessary, the primary system administrator can deactivate user accounts.
d) The instrument records failed login attempts in audit logs. If the number of failed login
attempts for a particular user account is greater than the number set by the primary system
administrator, that user account gets locked. Only another user with the Administrator
permission level may reset the password and release the user account.
e) The instrument does not user tokens or cards.
Содержание Progeny
Страница 1: ...1006232_RevD 3 Progeny and Progeny LT Analyzer User Manual Rev D...
Страница 74: ...Advanced Options 67 1006232_RevD Figure 40 Sample Application...
Страница 106: ...Export and Import Settings 99 1006232_RevD Figure 70 Progeny Settings Screen...
Страница 111: ...Appendix B Nose Cone Positions 104 1006232_RevD Appendix B Nose Cone Positions...
