3: Sensitive Data Retention
Control objective 3.5
Transient sensitive data is securely deleted from temporary storage facilities automatically by the software once the purpose for which it is retained is satisfied.
To meet the requirement, attributes can be encrypted in memory. For attributes that are encrypted in memory, clear-text values that are temporarily held in memory are cleansed after use. For more information, see Enabling data encryption in memory.
Control objective 3.6
The software does not disclose sensitive data through unintended channels.
| Possible side-channel attacks | Notes |
|---|---|
| Error messages | IBM® Safer Payments does not show sensitive data in error messages. |
| Logs | IBM Safer Payments does not show sensitive data in error logs. |
| Memory dumps | Memory dumps might contain sensitive data. |
| Observable timing discrepancy | IBM Safer Payments hides the time it takes to log in by ensuring that login always takes 200ms. |
| Keyboard spelling and auto-correct features | IBM Safer Payments sets auto-complete to off. However, your organization must disable keyboard spelling and auto-correct features at the browser-level. |
| Cache timing or branch prediction within the platform processor | Outside of IBM Safer Payments control. |