WGU C845 VUN1Task1 ,2&3 | Passed on
68 68 68 68 68 68 68 68 68
68 First Attempt |Latest Update with
68 68 68 68
68 Complete Solution. 68
THISEXAM CONTAINS:
68 68
➢ WGU C845 VUN1 Task 1 ,2& 3
68 68 68 68 68 68
➢ Latest Update with Complete Solution
68 68 68 68
➢ WGU C845 VUN1 68 68
➢ Guaranteed Pass 68
, WGU C845 VUN1 Task 1 | Passed on FirstAttempt 68 68 68 68 68 68 68 68 68
|Latest Update with Complete Solution
68 68 68 68 68
VUN1 — VUN1 Task 1: Managing Security Operations and Access Controls
68 68 68 68 68 68 68 68 68 68
Information Systems Security - C845
68 68 68 68 68
A. ApplyanAccess Control Model 68 6
8 68 68
A.1. Chosen Access Control Model 68 68 68
I have chosen the Role-Based Access Control (RBAC) model. The principles of RBAC are:
68 68 68 68 68 68 68 68 68 68 68 68 68
• Role Assignment: A user is assigned to a role based on their job function (e.g., "Finance
68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
Analyst").
68
• Permission Assignment: Permissions to perform operations on systems are assigned to roles,
68 68 68 68 68 68 68 68 68 68 68
not to individual users.
68 68 68 68
• Session Management: A user activates a role to gain the associated permissions for a session.
68 68 68 68 68 68 68 68 68 68 68 68 68 68
• Least Privilege: Users should only have the minimum level of access necessary to perform their
68 68 68 68 68 68 68 68 68 68 68 68 68 68
job duties.
68 68
The organization's access control structure, as seen in the user matrix, is implicitly role-based (e.g.,
68 68 68 68 68 68 68 68 68 68 68 68 68 68
"Finance manager," "HR coordinator"). Applying a formal RBAC model would streamline this by ensuring
68 68 68 68 68 68 68 68 68 68 68 68 68 68
permissions are strictly tied to business functions, reducing complexity and the potential for user error
68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
when assigning permissions.
68 68 68
A.2. Four Misalignments with RBAC Principles 6 8 6 8 6 8 6 8
1. Misalignment 1: Privilege Escalation Beyond Role Scope 68 68 68 68 68 68
• Description: The "Junior system admin" (J. Lopez) has "Domain admin" privileges. A 68 68 68 68 68 68 68 68 68 68 68
junior role should not have the highest level of access in a Windows environment.
68 68 68 68 68 68 68 68 68 68 68 68 68 68
• Conflict with RBAC: This violates the principle of least privilege. The role "Junior system
68 68 68 68 68 68 68 68 68 68 68 68 68
admin" implies a subset of administrative duties, not unrestricted domain-wide control.
68 68 68 68 68 68 68 68 68 68 68
2. Misalignment 2: Unnecessary Access Across Departments 68 68 68 68 68
• Description: The "Finance analyst" (L. Cheng) has "Full access" to the CRM, a system 68 68 68 68 68 68 68 68 68 68 68 68 68
, primarily for Sales and Support. A finance role typically does not require full modification
68 68 68 68 68 68 68 68 68 68 68 68 68
rights in a customer relationship system.
68 68 68 68 68 68
• Conflict with RBAC: This violates least privilege and separation of duties. It allows for
68 68 68 68 68 68 68 68 68 68 68 68 68
potential data manipulation outside the user's core business function.
68 68 68 68 68 68 68 68 68
3. Misalignment 3: Violation of User-Role Assignment Post-Termination
68 68 68 68 68 68
• Description: The "HR assistant" (P. Ellis), who was terminated on 2025-05-20, has an
68 68 68 68 68 68 68 68 68 68 68 68
"Active" account status and successfully logged in on 2025-06-29.
68 68 68 68 68 68 68 68 68
• Conflict with RBAC: RBAC requires timely revocation of role assignments upon a change in
68 68 68 68 68 68 68 68 68 68 68 68 68
employment status. An active session for a terminated user completely bypasses the
68 68 68 68 68 68 68 68 68 68 68 68
security provided by the role structure.
68 68 68 68 68 68
4. Misalignment 4: Overly Broad Privileged Access
68 68 68 68 68
• Description: The "IT administrator" (T. Miller) has "Full admin" access to "All internal
68 68 68 68 68 68 68 68 68 68 68 68
systems," and the log shows they made a firewall rule change without a ticket_id.
68 68 68 68 68 68 68 68 68 68 68 68 68 68
• Conflict with RBAC: While some access is necessary, blanket "Full admin" access
68 68 68 68 68 68 68 68 68 68 68
violates least privilege and impedes accountability. It does not segment duties within the IT
68 68 68 68 68 68 68 68 68 68 68 68 68
department itself.
68 68
68 68 68 68 68 68 68 68 68
68 First Attempt |Latest Update with
68 68 68 68
68 Complete Solution. 68
THISEXAM CONTAINS:
68 68
➢ WGU C845 VUN1 Task 1 ,2& 3
68 68 68 68 68 68
➢ Latest Update with Complete Solution
68 68 68 68
➢ WGU C845 VUN1 68 68
➢ Guaranteed Pass 68
, WGU C845 VUN1 Task 1 | Passed on FirstAttempt 68 68 68 68 68 68 68 68 68
|Latest Update with Complete Solution
68 68 68 68 68
VUN1 — VUN1 Task 1: Managing Security Operations and Access Controls
68 68 68 68 68 68 68 68 68 68
Information Systems Security - C845
68 68 68 68 68
A. ApplyanAccess Control Model 68 6
8 68 68
A.1. Chosen Access Control Model 68 68 68
I have chosen the Role-Based Access Control (RBAC) model. The principles of RBAC are:
68 68 68 68 68 68 68 68 68 68 68 68 68
• Role Assignment: A user is assigned to a role based on their job function (e.g., "Finance
68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
Analyst").
68
• Permission Assignment: Permissions to perform operations on systems are assigned to roles,
68 68 68 68 68 68 68 68 68 68 68
not to individual users.
68 68 68 68
• Session Management: A user activates a role to gain the associated permissions for a session.
68 68 68 68 68 68 68 68 68 68 68 68 68 68
• Least Privilege: Users should only have the minimum level of access necessary to perform their
68 68 68 68 68 68 68 68 68 68 68 68 68 68
job duties.
68 68
The organization's access control structure, as seen in the user matrix, is implicitly role-based (e.g.,
68 68 68 68 68 68 68 68 68 68 68 68 68 68
"Finance manager," "HR coordinator"). Applying a formal RBAC model would streamline this by ensuring
68 68 68 68 68 68 68 68 68 68 68 68 68 68
permissions are strictly tied to business functions, reducing complexity and the potential for user error
68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
when assigning permissions.
68 68 68
A.2. Four Misalignments with RBAC Principles 6 8 6 8 6 8 6 8
1. Misalignment 1: Privilege Escalation Beyond Role Scope 68 68 68 68 68 68
• Description: The "Junior system admin" (J. Lopez) has "Domain admin" privileges. A 68 68 68 68 68 68 68 68 68 68 68
junior role should not have the highest level of access in a Windows environment.
68 68 68 68 68 68 68 68 68 68 68 68 68 68
• Conflict with RBAC: This violates the principle of least privilege. The role "Junior system
68 68 68 68 68 68 68 68 68 68 68 68 68
admin" implies a subset of administrative duties, not unrestricted domain-wide control.
68 68 68 68 68 68 68 68 68 68 68
2. Misalignment 2: Unnecessary Access Across Departments 68 68 68 68 68
• Description: The "Finance analyst" (L. Cheng) has "Full access" to the CRM, a system 68 68 68 68 68 68 68 68 68 68 68 68 68
, primarily for Sales and Support. A finance role typically does not require full modification
68 68 68 68 68 68 68 68 68 68 68 68 68
rights in a customer relationship system.
68 68 68 68 68 68
• Conflict with RBAC: This violates least privilege and separation of duties. It allows for
68 68 68 68 68 68 68 68 68 68 68 68 68
potential data manipulation outside the user's core business function.
68 68 68 68 68 68 68 68 68
3. Misalignment 3: Violation of User-Role Assignment Post-Termination
68 68 68 68 68 68
• Description: The "HR assistant" (P. Ellis), who was terminated on 2025-05-20, has an
68 68 68 68 68 68 68 68 68 68 68 68
"Active" account status and successfully logged in on 2025-06-29.
68 68 68 68 68 68 68 68 68
• Conflict with RBAC: RBAC requires timely revocation of role assignments upon a change in
68 68 68 68 68 68 68 68 68 68 68 68 68
employment status. An active session for a terminated user completely bypasses the
68 68 68 68 68 68 68 68 68 68 68 68
security provided by the role structure.
68 68 68 68 68 68
4. Misalignment 4: Overly Broad Privileged Access
68 68 68 68 68
• Description: The "IT administrator" (T. Miller) has "Full admin" access to "All internal
68 68 68 68 68 68 68 68 68 68 68 68
systems," and the log shows they made a firewall rule change without a ticket_id.
68 68 68 68 68 68 68 68 68 68 68 68 68 68
• Conflict with RBAC: While some access is necessary, blanket "Full admin" access
68 68 68 68 68 68 68 68 68 68 68
violates least privilege and impedes accountability. It does not segment duties within the IT
68 68 68 68 68 68 68 68 68 68 68 68 68
department itself.
68 68
