Clipboard convenience moves data onto a sharing surface outside the application. A public identifier and a secret that controls an account should not have identical copy behavior.
Evaluation approach
Review copyable fields and platform features for marking sensitive content. Consider user needs alongside data classification.
Application example
A one-time code, account number and private key should not share one copying policy.
Limits and considerations
RASP cannot automatically undo every disclosure the application permits.
Convenience and data propagation
Copying can help users while moving sensitive data beyond the application. Establish where it is necessary, and test clipboard behavior for the platform version under actual usage conditions.
One-time codes, account details and secret keys have different risk levels. Removing an unnecessary copy option can be an appropriately narrow control. A RASP event does not establish that shared copies were automatically cleared.
Checks and decisions
- Identify copyable fields
- Mark sensitive content
- Remove unnecessary sharing
Limit circulation of high-risk data without disabling usability altogether.
Sources
The primary references above provide the technical basis. Example workflows and evaluation suggestions are this publication’s explanations, not independent test results for a particular product.