Data Security Option for Ponemah v5.3x

The Data Security Option (DSO) for the Ponemah v5.3x system allows the system to operate within FDA 21 CFR Part 11 regulations. DSO provides:

Secure Program Login

A System Administrator defines access levels unique to each Ponemah system. Each Ponemah User utilizes a combination of Windows credentials and a unique Ponemah password to gain controlled access to the system.

Electronic Signatures

Each acquisition automatically creates an encrypted Signature file used as a unique “finger print” for future verification of the files. Additional data from the user's account will support Electronic Signatures. A user may attach their electronic signature and any notes related to the signing.

Controlled User Privileges

Ten unique Access Levels can be defined on each Ponemah System. The Access Level determines the privileges granted to users of the application. Every available user function can be independently assigned or reserved. Constructing the Access Level structure is simplified by our logical setup dialog.

530 Access Level Setup

Multiple User Profiles

Each system user is assigned a specific Access Level. In the case of multiple systems at a facility, a user may have different privileges on individual Ponemah Systems. If a user is not assigned on a system, their username will not be accepted as a valid login. Hundreds of users can be assigned to each system.

530 User Setup 2

File Integrity Validation

The verify function allows saved data sets to be quickly checked for evidence of corruption of tampering. A green check mark identifies files that are intact and unchanged. A red X mark identifies altered files. A question Mark identifies a file that does not have an associated .SIG file.

530 Verify Files

Audit Trail

During operation the user can “lock” the program through a simple key stroke. Locking the system will not alter the current operational state of the system but will prevent unauthorized manipulation if the operator leaves the system unattended. Users can also set a pre-determined time after which the system will automatically lock if unattended.  Each login and system lock and all changes to operational settings will be recorded in a Log file. Log files provide an Audit Trail, documenting all system activity from application start to end.