How should TELUS structure data access control for CX data?

• A. Role-based access control.
• B. Data masking alone.
• C. Audited access with no restrictions.
• D. Role-based access control, least privilege, and audited access with data masking where needed.

Answer: (D)

Access control for CX data should be layered: grant access by role, enforce the least privilege principle, keep thorough audit trails, and mask sensitive fields when full visibility isn’t needed. This combination is effective because each element addresses a different risk layer.

Role-based access control organizes permissions around specific roles, such as frontline CX agents, team leads, data analysts, and compliance auditors. It provides a scalable, manageable way to assign what each group can access rather than assigning permissions ad hoc to individuals. But on its own, RBAC can still expose too much data if roles aren’t finely defined or if people need more access than strictly necessary for their tasks.

Least privilege tightens that by ensuring every user receives only the minimum data and rights required to perform their job. This reduces the blast radius if a credential is compromised and limits exposure during normal operations, even within an authorized role.

Audited access adds visibility and accountability. By recording who accessed which data and when, you gain traceability for security reviews, regulatory compliance, and anomaly detection, which is essential in a CX environment with sensitive customer information.

Data masking where needed complements these controls by protecting sensitive fields. When a role or task doesn’t require seeing full PII or payment details, masking ensures the data shown is de-identified or partially obfuscated, allowing analysts to derive insights without exposing sensitive information.

In a TELUS CX context, customer data includes personal information, interaction history, and possibly payment details. Frontline agents can access necessary contact and history data, while payments and highly sensitive fields are masked or restricted. Analysts work with de-identified data, and auditors have access to complete logs to verify proper use. By combining RBAC, least privilege, auditability, and selective data masking, you achieve secure, compliant, and usable access control that supports both protection and operational needs.