PogoIAM

Free lesson 1 · SailPoint Identity Security Cloud · Engineer

Cloud architecture and platform 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.

Cloud refresher. SailPoint hosts the application. A tenant is your organization’s own environment. Your team still owns decisions about data, access, and source connections. Use a dedicated test environment for changes that could affect people or systems.

A source is ISC’s connection to another system. An authoritative source supplies identity data. A connector determines which operations that connection supports. A virtual appliance can reach private systems when the connector requires one. Some sources use a cloud connection. A flat-file import can supply data while changes to the target need a manual task.

SailPoint sources · Virtual appliances

Exam review · Tenant and connection design

In transit means data traveling between systems. At rest means data stored on disk or in a database. For a new source, list which fields can leave the private network and which systems store them. Check encryption and approved endpoints in each environment. A cluster can reduce dependence on one VA. Separately identify remaining dependencies such as the network and the target directory.

Lab · Draw the bank’s data flow

Pogo Bank uses hosted HR for workers, an internal directory for accounts, and a payroll file for visibility. Draw an arrow into ISC for each import. Add separate arrows for directory changes and for a payroll owner’s manual task. Mark which links need private-network access and name a person or team to call when each fails.

Compare your design

In this scenario, the directory connection uses a VA. HR provides identity data and the payroll file provides account data. A payroll owner handles changes in the target. Check import and change paths separately and assign each path an owner.

Check your understanding

Does a cloud tenant isolate an organization’s configuration?
Should an engineer use a separate environment for an untested access change?
Does every connected source have to be authoritative?
Can HR be authoritative for a start date?
Should you check supported actions before promising automated removal?
Does one working import prove the connector can disable accounts?
Must every SaaS source use the same VA?
Can a VA provide connectivity for an internal directory?
Can a flat file contain account records?
Does uploading an updated file alter the target application by itself?
Can an engineer assume sandbox and production use the same identifiers?
Should a production design identify each source owner?
Is aggregation a read into SailPoint?
Is propagation toward the target also aggregation?
Should a learner paste employer credentials into a training workspace?
Should a lab use fictional identities?
Can an application owner confirm access observed in the application?
Can an architecture diagram replace a connection test?
Does a healthy cloud interface prove every connector is healthy?
Would two failed targets sharing a VA make the VA worth checking?

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