How does Corix protect and unmask sensitive personal information?
Learn how Corix masks sensitive data such as SSNs and dates of birth, what unmasking means, and how unmasking is logged.
Overview
Corix helps protect sensitive personal information by masking certain data fields, such as Social Security Numbers (SSNs) and dates of birth (DOBs), by default.
Access to sensitive information should be limited to authorized personnel and only when required for operational, compliance, or support purposes.
What does "unmasking" mean?
Unmasking is the process of temporarily revealing sensitive information that is normally hidden within the platform. Examples may include:
- Social Security Numbers (SSNs)
- Dates of Birth (DOBs)
- Other sensitive personal information
How is unmasking logged?
When sensitive information is unmasked, Corix records the action in the audit log. This provides visibility into when sensitive information was viewed and supports compliance and security requirements.
Administrators can use audit records to review access to protected information when needed.
Best practices
When accessing sensitive information:
- Only unmask information when there is a legitimate business need.
- Follow your firm's privacy and compliance policies.
- Avoid sharing sensitive information outside approved channels.
- Review audit logs as part of periodic compliance reviews.
Frequently asked questions
Why is sensitive information masked?
Masking helps protect customer information and reduces unnecessary exposure of personal data.
Who can view unmasked information?
Access depends on the permissions assigned to your role.
Is unmasking tracked?
Yes. Unmasking activity is recorded for audit and compliance purposes.
Can users see when their information has been viewed?
Visibility into audit records depends on your firm's configuration and access controls.