ISC · Security and Confidentiality and Privacy · 6 practice questions
Vendor Privileged Access: Standing Rights vs. Time-Bound Access
Named accounts and MFA do not remove the exposure from continuously enabled administrator rights. Below: compare standing privileges with time-bound elevation while keeping identity, authentication, access scope, and session recording unchanged.
Try one first
Hint
Which choice most directly prevents reuse of stolen vendor credentials and gives the company user-level accountability and company-controlled session visibility, rather than only improving recovery, auditing, or insurance?
Answer D. Option D addresses the root causes: shared credentials, lack of MFA, and absence of brokered sessions and company-accessible logs. Unique per-user accounts plus MFA prevent reuse of compromised credentials and provide individual accountability; a bastion with session recording and centralized logging gives the company visibility and faster response. The other options emphasize recovery, risk transfer, or detection without removing the underlying access and accountability weaknesses.
Why not A: Tempting because improved detection, segmentation, and audits can shorten dwell time and surface incidents sooner. It fails because detection and audits do not prevent unauthorized logins using compromised shared credentials or provide per-user accountability or company-controlled session logs; the root access vulnerability remains.
Why not B: Tempting because system restoration and credential rotation are immediate, familiar remedial steps and an incident plan appears proactive. It fails because rotating a single shared credential and keeping non-brokered shared-account access leaves the same authentication and accountability weaknesses; attackers could still obtain or reuse the shared credential.
Why not C: Tempting because insurance and forensic investigation reduce financial impact and provide formal remediation documentation. It fails because insurance and attestations transfer or record risk rather than eliminating the technical authentication and session-control weaknesses that allowed the breach, so they do not materially reduce the chance of repeat compromise.
Side by side
| Harbor: standing privileges | Harbor: time-bound elevation | |
|---|---|---|
| Vendor identity | Named account for each technician. | Same named accounts. |
| Authentication | MFA required for privileged access. | Same MFA requirement. |
| Permitted tasks | Role-based least privilege. | Same role-based task limits. |
| Session evidence | Individual session recording and centralized logging. | Same recording and logging. |
| When privileges are active | Continuously, including between support tasks. | Only during an authorized support window. |
| When the authorized window ends | Administrator rights remain enabled. | Elevation expires; the named account remains. |
| After-hours support | Available using standing administrator rights. | Available through a configured elevation workflow. |
| Deciding fact | Privilege exposure continues between support tasks. | Privilege exposure is limited to authorized windows. |
Key points
- Remember: knowing who signed in does not justify leaving that person's administrator rights continuously enabled.
- Just-in-time elevation grants privileges when needed; time-bound access makes those privileges expire.
- The comparison changes privilege duration, not identity, authentication, permitted tasks, or session evidence.
How the exam traps you
- Choose named accounts and MFA but retain permanent administrator rights. Those controls address identity and authentication, not the duration of privileged access.
- Keep standing privileges because after-hours support must remain available. Use an elevation workflow that preserves support while limiting how long privileges remain active.
- Treat session recording as a substitute for privilege expiration. Recording provides evidence; expiration removes privileges when the authorized period ends.
Question 2
Hint
Focus on which response directly reduces the likelihood or impact of the identified security risk, rather than shifting, avoiding, or merely acknowledging it.
Answer D. Risk mitigation reduces either the likelihood or impact of a risk through controls or process changes. Replacing shared admin accounts with unique IDs and requiring multi-factor authentication lowers the chance of unauthorized access and improves accountability. That makes this a classic mitigation response rather than a transfer, avoidance, or acceptance.
Why not A: This is tempting because insurance helps cover financial consequences after an incident, but it does not reduce the likelihood of unauthorized access. It primarily transfers financial risk rather than mitigating the technical control weakness.
Why not B: Formal documentation of inaction does not reduce likelihood or impact. This reflects risk acceptance, where management chooses to live with the risk rather than implement controls to mitigate it.
Why not C: Eliminating the activity removes the exposure, which is risk avoidance, not mitigation. Mitigation involves reducing the risk while continuing the activity or process.
Question 3
Hint
Which option most directly removes standing, shared privileges and adds per‑user accountability while allowing fast emergency access?
Answer A. The key residual risk is the continuously enabled shared privileged account, which prevents per‑user attribution and leaves standing privileges that can be misused. Replacing it with individually assigned accounts managed by a PAM solution provides just‑in‑time elevation, enforces MFA and least privilege, and records sessions and logs, directly reducing confidentiality and integrity risk while preserving rapid emergency access.
Why not B: This is tempting because stronger authentication, credential hygiene, and function restrictions appear to reduce risk without changing operations. It fails because the account remains shared and continuously enabled, so individual accountability and true attribution are still absent; administrative mitigations cannot substitute for per‑user access and session-level forensics.
Why not C: This distractor tempts by focusing on vendor assurance and readiness, which can be useful background information. It fails because third‑party attestations do not change Harbor's internal access model, the continuously enabled shared account still permits anonymous actions in the ERP and preserves the core confidentiality/integrity risk.
Why not D: Network isolation and a monitored jump server are tempting fixes because they centralize connectivity and monitoring. They fail to address the primary problem: keeping a shared, always‑enabled privileged account preserves standing privileges and lack of per‑person attribution, so confidentiality and integrity risks remain.
Question 4
Hint
Focus on which option best mitigates the specific residual risks revealed by the facts: credential misuse, lack of user-level accountability, and excessive standing privilege.
Answer C. Option C most directly mitigates the residual risks identified in the stem: replacing the shared account with named IDs restores individual accountability, MFA reduces the chance that valid credentials will be used maliciously, and just-in-time privileged elevation removes excessive always-on admin rights by limiting access duration. Because encryption at rest and segmentation are already effective, the primary Year 1 defenses should focus on controlling and authenticating privileged access.
Why not A: IP restrictions and log reviews are useful controls but preserving a shared admin account prevents reliable attribution and does not stop misuse of valid credentials. Detective controls and network filters do not substitute for removing unnecessary standing privileged access.
Why not B: This option improves accountability and authentication but leaves standing administrative rights intact; a compromised vendor account would still have continuous broad access to PII, so the excessive always-on privilege remains an unresolved residual risk.
Why not D: Encryption and tokenization protect data at rest, but the stem already states encryption at rest is effective. The residual threat arises from authenticated privileged sessions (valid credentials and standing admin rights), which data-at-rest controls do not prevent.
Question 5
Hint
Which interim control most directly restores per-person authentication and auditable session attribution for privileged console activity when the application itself cannot be changed yet?
Answer C. When the application cannot provide native MFA or per-user admin accounts, the most effective interim mitigation is a compensating control that enforces individual authentication and supports attribution. A managed gateway or bastion can require per-user MFA, manage controlled checkout or just-in-time use of shared credentials, and centrally record sessions for auditable attribution and monitoring. Other measures (password tightening, encryption-at-rest, or IP restrictions) reduce certain risks but do not as directly restore individual authentication and reliable accountability for privileged console actions.
Why not A: This is tempting because it strengthens preventive and detective controls, but it retains a single shared credential and therefore does not provide consistent per-user authentication or reliable attribution for administrative actions.
Why not B: Data-centric controls protect stored data, and better key management helps, but they do not prevent an authenticated administrator from viewing or exporting decrypted data via the admin console unless key use is tightly coupled to per-user session controls; they therefore do not by themselves address the immediate authentication and accountability gap.
Why not D: IP allowlisting and VPNs reduce the attack surface, but they do not establish per-user authentication; misuse of a shared credential from an allowed endpoint still prevents reliable attribution of administrator actions.
Question 6
Hint
Focus on controls that change how administrative credentials are issued and used (authentication and privileged access), not just controls that detect or protect stored data.
Answer A. The primary vulnerability is shared administrative credentials and lack of MFA. A PAM deployment that issues unique, time-limited admin credentials, enforces RBAC and MFA, and provides centralized session recording and alerting both reduces the chance that stolen or overused credentials grant unauthorized access and limits the scope and detectability of any misuse. The other options are useful layered controls but do not as directly or immediately address the root cause.
Why not B: Encryption and TLS protect data confidentiality if storage or transport is compromised, and key rotation improves long-term security, but they do not stop a valid administrative user or an attacker who authenticates with admin credentials from accessing data through the application. Encryption reduces impact in some breach scenarios but does not meaningfully reduce the likelihood of unauthorized access via shared credentials.
Why not C: Network segmentation limits exposure and lateral movement from other systems, which is valuable, but it does not fix shared admin accounts or missing MFA. If an attacker can authenticate using the shared administrative credentials, segmentation alone will not prevent access to the database.
Why not D: Vendor oversight, SOC reports, and penetration tests increase accountability and help detect weaknesses over time, but they are largely detective/compliance controls that do not immediately prevent misuse of shared credentials or reduce the near-term likelihood and impact of an administrative compromise.
Common questions
Are named accounts and MFA enough for vendor administrator access?
They establish individual identity and strengthen authentication. In this comparison, continuously enabled administrator rights remain an exposure that time-bound elevation addresses.
What is the difference between standing privileges and just-in-time access?
Standing privileges remain enabled between support tasks. Just-in-time access grants elevation when needed, and a time limit ends that elevation.
Can time-bound privileged access preserve after-hours vendor support?
Yes. Harbor's configured elevation workflow keeps after-hours support available without leaving administrator rights continuously enabled.
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
- Least Privilege and Masking for PII: CPA ISC
- 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.