Cybersecurity Fundamentals
RecruitScenario sim

Identity and Access Management

Manage identities, authentication and permissions across the full access lifecycle.

100 min 500 XPSkills: Authentication, Federation, Access models, Access lifecycle

What you'll be able to do

  • ›Distinguish identities, accounts and access activities
  • ›Compare authentication factors, passwords and passkeys
  • ›Explain federation and common access models
  • ›Apply least privilege, lifecycle controls and access reviews
  • ›Trace access removal across accounts, sessions and application permissions

Loading the lessons...

Labs

160 bonus XP

Hands-on work. You edit the artefact, the server runs the checks: the expectations and the reference solution never reach your browser.

Lab 1 · YAML lab

Record a mover access decision

Briefing 40 XP

Translate an approved transfer into an access record. Keep the old clinical grant separate from the new training role.

Approved transfer request

Identity: Asha Patel. Account: apatel. Asha moves from nursing to training on 2027-04-12. Approved role: trainer. Clinical editing must be removed. Administrator access is not approved. The training manager owns the review, due 2027-05-12. Existing sessions must be revoked.

Checks

  • Distinguish identity and account
  • Apply the transfer
  • Handle existing sessions
  • Assign follow-up
Lab 2 · Review lab

Review access design claims

Briefing 40 XP

Check the proposed clinic guidance for misleading access claims.

Verdicts are accept or reject. Every rejection needs one reason code from: attribution-weakened | same-factor | permission-confused.

Draft guidance

I-1 | Shared administrator accounts make individual attribution easier.
I-2 | A password and secret answer are different authentication factors.
I-3 | Federation lets an application trust an external identity provider.
I-4 | A mover review should remove obsolete permissions.
I-5 | Signing in successfully grants permission to every record.
I-6 | Time-limited elevation reduces standing privileged access.

Checks

  • Every line in the fixture carries a verdict
  • Accept and reject land on the right lines
  • Each rejection cites a valid reason code
Lab 3 · YAML lab

Record a controlled role overlap

Briefing 40 XP

Write the decision record in YAML, a simple text format for structured data.

Use the fixture rather than inventing missing evidence.

Decision evidence

Cedar Clinic records a temporary role overlap for account jreed. Stage is mover. Approver is ward manager. Clinical access expires on 2027-09-03. The scheduling session must be revoked, so revoke is true. The training manager verifies removal on 2027-09-04.

Checks

  • Complete identity
  • Complete overlap
  • Complete session
  • Complete review
Lab 4 · Review lab

Review lifecycle and federation claims

Briefing 40 XP

Review each claim against the deeper lesson. Accept accurate claims and reject misleading ones.

Verdicts are accept or reject. Every rejection needs one reason code from: audience-ignored | session-assumption | removal-unverified.

Review notes

D-1 | A trusted signature allows scheduling to ignore a response intended only for payroll.
D-2 | A temporary role overlap needs an approver and expiry.
D-3 | Disabling central sign-in always terminates every existing application session immediately.
D-4 | A service provider applies application permissions after validating identity evidence.
D-5 | A closed removal ticket proves the permission has disappeared from the application.
D-6 | Emergency access use should be recorded and reviewed.

Checks

  • Every line in the fixture carries a verdict
  • Accept and reject land on the right lines
  • Each rejection cites a valid reason code

Next on your path · Cybersecurity Fundamentals

Cryptography Part 1: Foundations

Choose cryptographic tools for secrecy, trustworthy messages and password storage, while recognising dangerous key and randomness mistakes.

Analyst 200 min 800 XP
Start next room

Community

Discussion & writeups

Sign in to post

Share how you approached the room or ask where you got stuck. Never paste task answers or full lab solutions: write the reasoning, not the key.

Loading discussion…