Create a module policy exception to change the lifecycle policy of a key at the
module level for an instance. The exception(s) applies only to that module and not to the
entire instance. For example, if the administrator configured symmetric keys to be limited
to one year at the instance level, an exception can be made at the module level to be two
years.
Before you begin
Role required: sn_kmf.cryptographic_manager and sn_kmf.admin
Procedure
-
Navigate to
.
-
Select the cryptographic module that will use the policy exceptions.
-
In the Cryptographic Module table, select the tab.
-
Click .
-
Complete the form.
Table 1. Module Policy Exceptions fields
| Field |
Description |
| Crypto Module |
Read only, name of the module selected. |
| Applies to |
The specified key is auto-populated. |
| Key Type |
Select the key type, as the exception policies are
related to a specific key. Multiple exception policies
can be created per crypto module. |
| Policy condition |
Choose the qualifying conditions from the drop-down
and complete the additional constraint criteria. |
| New criteria |
Select additional policy conditions, as
required. |
| Result |
Select to Reject to reject
usage of the key or Track to
allow usage of it when the criteria is met. |
-
Click to be returned to the Cryptographic Module table.