Configure Security Checkpoints for Control Plan
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 control plans and analyses:
- A control plan template is activated - QUAMAN_CTRL_PLAN_TMPL_ACTIVATE
security checkpoint.
- Approving a control plan checklist item - QUAMAN_CHECKLIST_ITEM_APPROVAL
security checkpoint.
- Activating a control plan - QUAMAN_CONTROL_PLAN_APPROVAL security
checkpoint.
- Approving a shop order control plan after
modifications - QUAMAN_SO_CTRL_PLAN_APPROVAL security checkpoint.
- Cancelling an analysis - QUAMAN_CANCEL_ANALYSIS security
checkpoint.
- Cancelling a data point in an analysis - QUAMAN_CANCEL_DATA_POINT
security checkpoint.
- Completing a data point in an analysis -
QUAMAN_COMPLETE_DATA_POINT security checkpoint.
- Confirming an analysis - QUAMAN_CONFIRM_ANALYSIS 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
Checkpoints Log page.