PogoIAM

Free lesson 1 · SailPoint Identity Security Cloud · Administrator

Cloud, IAM and IGA basics

Practice at Pogo Bank, a fictional workplace.

Learn the basics

How the cloud works

Cloud software runs on systems the provider operates. You use it in a browser. SailPoint connects to selected systems so it can read identity and access information and, where configured, request changes. At Pogo Bank, HR tells us who works there. An application decides what someone can do when they sign in.

Why it matters. A worker can sign in and still have the wrong access. Identity governance helps the bank keep track of who should have access, who approved it, and when it should change.

SailPoint access overview

Try the lab

A teller can sign in but cannot open Branch tools. PB-001 · Active · Branch Operations · Teller. The identity provider reports a successful sign-in.

What would you check first?

Check your understanding

A teller uses a security key to prove who they are. Is that authentication?
A teller signs in successfully. Does that alone give them permission to approve a payment?
Should you match two records using only a first name if several employees share it?
Can one worker identity be linked to both an email account and a banking-app account?
Can the bank keep its employee records in HR while a cloud service uses those records to guide access decisions?
If a system is connected, can you assume the cloud service can change any account in it?
Does changing a password settle whether a worker should keep access after transferring?
A bank asks managers to confirm who still needs access. Is that an example of identity governance?
Should a teller keep all their old access automatically after moving to Loans?
Could the bank use a teller role to provide the same routine access to new tellers?
Should a worker get only the access they need for their job?
Should the bank grant administrator access just because it saves time during onboarding?
Is a transfer between bank departments a mover event?
If someone leaves the bank, is checking one application enough to confirm all their access is gone?
Does approval by itself prove that the target application actually granted access?
Can an approval record help explain who decided to grant access and when?
Can the bank lower payment risk by giving payment creation and payment approval to different people?
Should a payment creator get approval rights merely because they already have one payment permission?
If an access review finds an old role, should you ignore it because the worker’s account is active?
If a worker can sign in but cannot open a required screen, should you check their permissions?

Continue learning

The first lesson is free. The remaining lessons, final assessment and completion certificate are part of the full course.

See planned course access