Protect selected information with a recoverable key design
Powertech Encryption for IBM i is a data-protection enquiry that must begin with the information and application paths to be protected. Define where the selected configuration applies encryption and where authorised applications must still obtain readable data. Encryption is distinct from deciding who has permission to use information.
Map the files or fields, interfaces and workloads in scope with application owners. Confirm supported algorithms, integration methods and platform versions in current manufacturer documentation. Key generation, custody, backup and recovery deserve equal attention to the encryption operation itself.
Test reads, writes and recovery before rollout
Use approved non-production data to validate normal application reads and writes, scheduled processing and the response when key access is unavailable. Measure any relevant performance impact under documented conditions. A successful conversion test is insufficient if the backup or disaster-recovery process cannot restore usable data and its authorised key access.
Handover should preserve the encryption boundary, application dependencies, key responsibilities and change procedures without placing secret key material in ordinary project files. MMC can scope the selected deployment and testing; legal interpretation of data-protection obligations and application modifications should be separately allocated.
Evidence to request for this scope
- Confirm the exact data scope and supported application integration before selecting a licence.
- Demonstrate authorised read/write behaviour and a denied-access or unavailable-key scenario.
- Validate recovery of the protected information together with the approved key-recovery procedure.