- A
The application's role-to-permission mapping is based on group SID rather than group name.
Why wrong: While group SID vs. name could cause mapping errors, it would affect all users in that group, not specifically branch-level access. This is less likely than missing branch validation.
- B
The application does not perform proper session management.
Why wrong: Session management issues could allow session hijacking, but the audit found the Teller was using their own session; the problem is authorization, not session integrity.
- C
The application fails to validate the user's branch attribute after authentication.
The application likely uses the Teller role correctly but does not check the user's branch attribute to restrict access to only customers from the same branch, allowing cross-branch access.
- D
The application uses a horizontal privilege escalation vulnerability.
Why wrong: Horizontal privilege escalation would allow a Teller to access accounts of another Teller, but the issue is across branches, which may not be horizontal if the role is the same; still, the primary gap is branch-based restrictions.
Quick Answer
The answer is a failure to validate the user's branch attribute after authentication. This is the most likely root cause because the Teller’s AD group membership was verified correct, meaning the role-based access control (RBAC) mapping is functioning properly; however, the Teller could still access accounts outside their assigned branch, which points directly to a missing attribute validation within the authorization logic. On the Systems Security Certified Practitioner SSCP exam, this scenario tests your understanding of horizontal privilege escalation due to missing attribute validation, where an attacker or insider exploits the absence of a post-authentication check on a context-specific attribute like branch or department. A common trap is to assume the flaw lies in role mapping when the roles are correct, but the real vulnerability is the lack of attribute-based access control (ABAC) enforcement within the RBAC framework. Memory tip: think “roles get you in, attributes keep you in line”—always validate the user’s specific attributes after authentication to prevent horizontal escalation.
SSCP Access Controls Practice Question
This SSCP practice question tests your understanding of access controls. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A large financial institution has deployed a new web application for customer account management. The application uses role-based access control (RBAC) with roles such as Customer, Teller, Manager, and Admin. Recently, an audit revealed that a Teller was able to view and modify account details belonging to customers outside their assigned branch. The application authenticates users via the corporate Active Directory and uses AD groups for role mapping. The Teller's AD group membership was verified to be correct. The security team suspects a flaw in the authorization logic. Which of the following is the MOST likely root cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"most likely"Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
The application fails to validate the user's branch attribute after authentication.
The Teller's AD group membership was verified correct, so the role mapping (RBAC) is functioning. However, the Teller could access accounts outside their assigned branch, indicating the application lacks a post-authentication check of the user's branch attribute. This is a classic failure of attribute-based access control (ABAC) within an RBAC framework, where the application must validate the user's branch (e.g., from an AD attribute like 'physicalDeliveryOfficeName' or a custom attribute) against the account's branch before allowing read/write operations.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The application's role-to-permission mapping is based on group SID rather than group name.
Why it's wrong here
While group SID vs. name could cause mapping errors, it would affect all users in that group, not specifically branch-level access. This is less likely than missing branch validation.
- ✗
The application does not perform proper session management.
Why it's wrong here
Session management issues could allow session hijacking, but the audit found the Teller was using their own session; the problem is authorization, not session integrity.
- ✓
The application fails to validate the user's branch attribute after authentication.
Why this is correct
The application likely uses the Teller role correctly but does not check the user's branch attribute to restrict access to only customers from the same branch, allowing cross-branch access.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
The application uses a horizontal privilege escalation vulnerability.
Why it's wrong here
Horizontal privilege escalation would allow a Teller to access accounts of another Teller, but the issue is across branches, which may not be horizontal if the role is the same; still, the primary gap is branch-based restrictions.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse the symptom (horizontal privilege escalation) with the root cause (missing attribute validation), or they incorrectly assume that correct AD group membership guarantees proper authorization without considering contextual attributes like branch.
Detailed technical explanation
How to think about this question
In enterprise environments, RBAC often integrates with AD via LDAP, where the application retrieves the user's group memberships (e.g., 'CN=Teller,OU=Groups,DC=bank,DC=com') to assign roles. However, fine-grained authorization requires additional attributes, such as 'branchCode' stored in an AD extensionAttribute or a separate database field. The application must enforce a policy like 'if user.role == Teller AND user.branch == account.branch then allow', otherwise a Teller from Branch A can access Branch B's accounts. This is a common oversight when developers assume RBAC alone is sufficient for multi-tenant or multi-branch systems.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A security team runs a vulnerability scan on a web application and discovers an unpatched SQL injection flaw. The team prioritises remediation by CVSS score — critical flaws are patched within 24 hours, high within 7 days. Questions like this test whether you understand vulnerability management processes, scanning tools, and remediation prioritisation.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Access Controls — study guide chapter
Learn the concepts, then practise the questions
- →
Access Controls practice questions
Targeted practice on this topic area only
- →
All SSCP questions
504 questions across all exam domains
- →
Systems Security Certified Practitioner SSCP study guide
Full concept coverage aligned to exam objectives
- →
SSCP practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SSCP practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Risk Identification, Monitoring and Analysis practice questions
Practise SSCP questions linked to Risk Identification, Monitoring and Analysis.
Network and Communications Security practice questions
Practise SSCP questions linked to Network and Communications Security.
Systems and Application Security practice questions
Practise SSCP questions linked to Systems and Application Security.
Security Operations and Administration practice questions
Practise SSCP questions linked to Security Operations and Administration.
Incident Response and Recovery practice questions
Practise SSCP questions linked to Incident Response and Recovery.
Access Controls practice questions
Practise SSCP questions linked to Access Controls.
Cryptography practice questions
Practise SSCP questions linked to Cryptography.
SSCP fundamentals practice questions
Practise SSCP questions linked to SSCP fundamentals.
SSCP scenario practice questions
Practise SSCP questions linked to SSCP scenario.
SSCP troubleshooting practice questions
Practise SSCP questions linked to SSCP troubleshooting.
Practice this exam
Start a free SSCP practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SSCP question test?
Access Controls — This question tests Access Controls — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The application fails to validate the user's branch attribute after authentication. — The Teller's AD group membership was verified correct, so the role mapping (RBAC) is functioning. However, the Teller could access accounts outside their assigned branch, indicating the application lacks a post-authentication check of the user's branch attribute. This is a classic failure of attribute-based access control (ABAC) within an RBAC framework, where the application must validate the user's branch (e.g., from an AD attribute like 'physicalDeliveryOfficeName' or a custom attribute) against the account's branch before allowing read/write operations.
What should I do if I get this SSCP question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more ways this is tested on SSCP
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. You are a security analyst at a financial institution. The company uses a role-based access control (RBAC) system for its internal banking application. Recently, the compliance team discovered that a teller, who should only have access to customer account information for their branch, was able to view account details for customers in other branches. The RBAC system assigns roles based on job titles. You review the configuration and find that the 'Teller' role has a permission that allows viewing all customer accounts, regardless of branch. The company wants to enforce branch-level restrictions. Which of the following is the best approach to address this issue?
medium- ✓ A.Implement attribute-based access control (ABAC) to incorporate branch location as an attribute.
- B.Use mandatory access control (MAC) with labels for each customer account.
- C.Create separate roles for each branch, such as 'Teller_Branch1', 'Teller_Branch2', etc.
- D.Modify the 'Teller' role to remove the permission to view all accounts.
Why A: Adding an attribute for branch location and using ABAC in conjunction with RBAC allows fine-grained control. Option A is correct. B would create many roles, C is not granular, and D is not relevant.
Last reviewed: Jun 25, 2026
This SSCP practice question is part of Courseiva's free ISC2 certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SSCP exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.