Configure Security Checkpoints for CAPA

Explanation

The purpose of security checkpoints is to provide extra security in a specific function, method or business flow. With an activated security checkpoint on a function the current user will have to re-authenticate in order to fulfill the function. Additionally, whenever a security checkpoint is successfully passed a security checkpoint log is written, creating an audit trail of what was done.

Security checkpoints can be configured for the following activities of the corrective and preventive action (CAPA) action line:

• Setting the status of the action line to Investigated - CAPA_INVESTIGATED security checkpoint.
• Setting the status of the action line to Action Completed - CAPA_COMPLETED security checkpoint.
• Setting the status of the action line to Verified - CAPA_VERIFIED security checkpoint.
• Setting the status of the action line to Effectiveness Determined - CAPA_EVALUATE_EFFECTIVENESS security checkpoint.

You can activate and deactivate security checkpoints individually, but security checkpoints can also be activated and deactivated on a system level. To activate/deactivate a security checkpoint individually click View Legacy Checkpoints, select the specific checkpoint and click Activate/Deactivate.

Prerequisites

Only a system administrator can access and configure the security checkpoints.

System Effects

• When the security checkpoint is active and turned on, the end user will be presented with an extra authentication dialog at the checkpoint.
• Successful security checkpoints are logged and can be viewed on the Security Checkpoint Logs page.

Pages

Security Checkpoints

Activity Diagrams

BDR for Corrective And Preventive Action (CAPA)