ISC · Security and Confidentiality and Privacy · 7 practice questions
Least Privilege and Masking for PII: CPA ISC
Valid login credentials do not justify access to full sensitive records or unrestricted exports. Follow NorthCo’s SSN data through role design, default masking, controlled full-value access, and export permissions.
Try one first
Hint
Which option most directly eliminates developers' broad, shared access to live production data rather than only shifting financial risk or focusing on stored bytes?
Answer D. This choice addresses the root causes: excessive and shared access to live production data and lack of environment separation. Enforcing RBAC and least-privilege removes unnecessary access, masked or synthetic development data prevents exposure of real PII during debugging, and comprehensive logging/alerting improves detection. Together these measures reduce the likelihood of unauthorized internal access while allowing development to continue.
Why not A: Encryption is tempting because it protects data at rest and in transit, a standard security control. However, encryption does not stop users who connect with valid credentials from viewing decrypted PII (the DB or application typically performs decryption), and full encryption/key-management changes can be complex and slow to deploy. It therefore fails to remove the immediate risk created by shared credentials and lack of least-privilege.
Why not B: Suspending access is tempting because it immediately reduces exposure. But a blanket suspension is highly disruptive and unsustainable for development and operations. A targeted, sustainable approach, implementing least-privilege, providing masked test data, and improving logging, reduces risk while allowing development to continue; temporary suspension might be used selectively, not as a long-term substitute.
Why not C: Insurance and HR measures are tempting because they address consequences and behavior, but they do not change technical access rights. Insurance shifts financial risk after a breach and policies/training are deterrents, yet none of these actions prevent developers with broad or shared credentials from accessing live PII.
Step by step
- Identify the actual business need
NorthCo’s application displays full SSNs to representatives despite database encryption and MFA. Most representatives need only the last four digits; a few documented exception cases require full values.
- Limit roles and mask by default
Remove unnecessary full-SSN viewing rights from routine roles and show only the last four digits by default. Design permissions around the work each role must perform.
- Control full-value exceptions
For documented exception cases, require just-in-time approval before revealing the full SSN. Limit access to the approved period and log the reveal.
- Authorize exports separately
Do not let routine lookup access or an approved full-SSN reveal automatically grant bulk export rights. Restrict full-data exports to approved roles with a documented business need and require separate export approval.
Key points
- Remember: Permission to log in is not permission to view full SSNs or export them.
- Encryption at rest does not hide full SSNs that the application displays to authorized users.
- Logs support accountability, but they do not replace limits on viewing and export permissions.
How the exam traps you
- Choose stronger database encryption while leaving full SSNs visible to the same users. Change application permissions and default displays to limit what those users can see.
- Assume a business need to view one full SSN also justifies bulk export. Evaluate export permissions separately and restrict them to approved roles with documented needs.
Question 2
Hint
Focus on the specific risk scenario that was identified, not on the platform’s average risk profile or the appearance of stronger general controls.
Answer A. Mitigation sufficiency should be governed by whether the chosen response addresses the actual risk scenario and reduces residual risk to an acceptable level. Here, the key exposure is excessive logical access and export of highly sensitive personal data, not loss of encrypted media or general control-environment appearance. Privacy obligations and the sensitivity of the affected data must be considered in determining whether the remaining risk is acceptable.
Why not B: This distractor is tempting because candidates often equate a stronger general control environment with adequate mitigation. It is wrong because an audit-friendly or generally satisfactory environment does not by itself resolve the specific high-risk path identified: authorized bulk export of restricted personal data.
Why not C: This option appeals because mitigation often targets reduced likelihood of incidents. It is incorrect here because management should judge sufficiency against the specific scenario; lowering overall breach probability does not make the residual risk from the unaddressed export path acceptable.
Why not D: A candidate might average risk across records and deprioritize the small set of sensitive documents. That is wrong: mitigation must be adequate for the highest-risk affected data and scenario, particularly for restricted personal data subject to privacy obligations.
Question 3
Hint
Choose the control that directly stops an accidental sharing action as it happens, not one that mainly detects issues later or generally hardens accounts.
Answer A. This is a preventive, point‑of‑disclosure control that directly stops accidental external sharing. Blocking external sharing by default removes the opportunity for an inadvertent public link, and DLP inspects content and enforces approval or blocks when sensitive data is present. Training and log review are administrative or detective measures and do not stop the act at the moment of sharing.
Why not B: Training is tempting because it reduces careless behavior over time, but it is an administrative control that relies on human behavior and memory. It does not technically prevent a user from creating a public link at the moment of sharing, so it is weaker than a direct technical preventive control here.
Why not C: MFA and RBAC are tempting because they strengthen account security and can limit who has sharing privileges. However, these measures do not by themselves stop an authorized user from accidentally creating a public link; they address unauthorized access rather than preventing inadvertent disclosure at the point of sharing.
Why not D: Log reviews are tempting because they help detect and investigate incidents, but they are detective and after‑the‑fact. Quarterly review is relatively slow, so this approach would likely identify exposures only after sensitive data has already been disclosed.
Question 4
Hint
Which control removes active access at the moment of termination rather than merely making access harder or relying on periodic/manual checks?
Answer A. Automated deprovisioning tied to HR termination events directly removes active accounts when employees leave, addressing the root cause. It minimizes the window during which former employees can use valid credentials; other measures may reduce risk but do not ensure prompt account removal.
Why not B: Stronger passwords reduce the risk of credential compromise, which makes this a tempting control, but they do not stop a former employee from authenticating if their account remains active. This option fails to eliminate the primary risk, active accounts after termination.
Why not C: MFA reduces the chance that stolen passwords alone will allow access and is a valuable improvement, so it is an attractive fix. However, MFA does not guarantee that a departed employee cannot access resources if they retain their second factor or if enrollment persists; it does not remove access on termination.
Why not D: A manual HR-to-IT process addresses notifications and can work in practice, which makes it plausible. But manual steps are slower and more error-prone than automation, notifications can be delayed or missed, so this approach still leaves a significant exposure window.
Question 5
Hint
Identify where in the workflow full sensitive data becomes visible to more people than necessary, then choose the control that narrows that exposure without stopping the business process.
Answer C. The primary residual risk is unnecessary internal exposure of full sensitive data after legitimate download. Applying least privilege and data minimization by providing redacted working files for routine staff directly reduces that exposure. A time-limited, logged checkout preserves the occasional business need while narrowing the window and providing an audit trail.
Why not A: Blocking outbound emailing addresses one exfiltration path and is a legitimate control, but it does not reduce the routine internal visibility of full files in the shared folder. Because the main overexposure occurs from broad authorized access, DLP alone fails to mitigate the core confidentiality/privacy risk.
Why not B: Stronger encryption and credential hygiene protect against unauthorized external access but do not limit which authorized users can open full files. Since files are already encrypted in transit and at rest and the problem is excessive authorized access, this control does not implement least privilege or data minimization.
Why not D: Enhancing portal monitoring helps detect external compromise or credential abuse, but the scenario's principal risk happens after successful, legitimate downloads when files are stored broadly. Additional portal alerts do not materially reduce unnecessary internal exposure of full account data.
Question 6
Hint
Focus on what the attacker actually obtained and how tokenization changes the sensitivity of that data.
Answer B. Tokenization reduces exposure of sensitive data by replacing card numbers with surrogate tokens. If an attacker only obtains the tokenized database and not the separate vault that maps tokens to actual card numbers, the attacker is less likely to obtain usable PANs; confidentiality risk is reduced but not eliminated.
Why not A: This overgeneralizes: tokenization reduces the usefulness of stolen records but does not make them harmless in all circumstances, tokens may still have value or be exploitable when combined with other data or processes.
Why not C: Tokenization is a data-protection mitigation, but it does not replace the need for logical access controls, monitoring, and other security measures around the database.
Why not D: This confuses security objectives: tokenization primarily reduces confidentiality risk (exposure of card data), not availability or recovery after outages.
Question 7
Hint
Ask what encryption protects against and what it does not control once an authorized user can already view the data.
Answer C. Encryption at rest and in transit protects against unauthorized viewing of stored data and intercepted traffic. Those controls do not, by themselves, prevent misuse by someone who already has legitimate access to the decrypted data. Insider misuse (an authorized user exporting and sharing records) is the clearest limitation of encryption as a confidentiality/privacy mitigation.
Why not A: Packet capture is a common threat, but TLS is intended to protect the confidentiality of data in transit; properly implemented TLS should prevent an interceptor from reading the customer data.
Why not B: Physical theft sounds serious, but encryption at rest is specifically designed to mitigate the confidentiality risk from stolen media when keys are properly managed, so a stolen encrypted drive is less likely to expose readable data.
Why not D: Losing a backup is a typical incident, but encryption at rest generally mitigates the confidentiality risk of a lost encrypted backup, provided the encryption remains intact and keys are not compromised.
Common questions
Why isn't encryption enough to protect PII from authorized users?
NorthCo’s application decrypts SSNs for display. Encryption at rest does not prevent a logged-in representative from viewing full values that the application permits.
How should full SSN access work when exceptions are necessary?
Mask SSNs by default. For NorthCo’s documented exception cases, require just-in-time approval to reveal full values and log that access.
Should users who can view SSNs also have export access?
Not automatically. NorthCo should grant export permissions separately, based on a documented business need, rather than attach them to routine lookup access.
Watch it solved
A full CPA ISC task-based simulation on Mitigation, worked step by step.
IT Risk-to-Control Mapping | CPA ISC Simulation (TBS) on YouTube
Practice ISC like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Mitigation
- Stolen Credentials: When MFA Is the Best Mitigation
- Full-Disk Encryption on Laptops: Protection and Limits
- Suspected Data Exfiltration: Contain and Preserve Evidence
- Compensating Controls for Unpatched Vulnerabilities
- Vendor Privileged Access: Standing Rights vs. Time-Bound Access
- Risk Responses: Mitigation, Transfer, Acceptance, Avoidance
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.