Free lesson 1 · SailPoint Identity Security Cloud · Architect
Requirements and architecture boundaries
Practice at Pogo Bank, a fictional workplace.
Learn the basics
How the cloud works. A cloud service reads accounts from connected systems and helps you decide who should have access.
A design starts with the problem, affected people, the owner of each decision, and what success looks like. Identity governance connects records, permissions, approvals, and review evidence. Authentication proves who is signing in. The access decision still depends on permissions and policies.
Use a data-flow diagram to show which system sends which record. Mark a trust boundary wherever responsibility or access changes, such as between the bank network and the hosted service. Separate requirements from assumptions and give each assumption an owner and a check.
SailPoint source configuration
Lab · Map the first release
Pogo Bank has 250 workers, one HR system, an internal directory, and a loan app. It wants approved employees to gain loan access and leavers to lose it. Draw the three systems and SailPoint ISC. Label the direction of identity records, account inventory, and permission changes. Identify one item outside the first release and one condition that stops the rollout.
Compare your design
HR owns employment data. The directory and loan app report account and entitlement state. ISC evaluates configured governance and sends supported changes or routes manual work. The target owner verifies access. Keep contractor automation outside the first release if contractor authority is unresolved. Stop rollout if the test leaver retains sensitive access.
Check your understanding
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