Identity Governance and Administration Foundations
Key Takeaways
Identity governance and administration connects why access is allowed to the identity, account, and assignment records that show who holds it.
Identity and access management covers a broader set of activities, including sign-in and runtime access enforcement.
Least privilege limits access to the permissions needed. Separation of duties limits combinations that concentrate conflicting powers.
Confirm the target effect of a governance decision independently of the assignment or approval record.
Follow an identity from data to effective access
Identity and access management (IAM) covers the management of digital identities and access, including signing in, managing credentials, and enforcing access decisions. Identity governance and administration (IGA) focuses on lifecycle administration, access policy, review, and evidence. In a deployment, these activities intersect. A sign-in service establishes a session for the employee. The governance system helps determine why that employee should hold a permission, applies the access change through a supported process, and supplies access and review evidence.
Start with a trusted record for the person. In Identity Security Cloud, an identity profile maps data from its authoritative source and represents the population it governs. A person’s identity can be associated with multiple accounts, each on a source. An account can hold specific entitlements such as group memberships. An access profile bundles entitlements from a single source. A role can group access across sources. Use stable identifiers to connect these records before making decisions about access. An employee name by itself is seldom sufficient evidence that a particular target account belongs to them.
| Question | Governance step | Evidence to inspect |
|---|---|---|
| Which person does the account belong to? | Correlate source account to identity | Source account identifier and associated identity |
| What access should a new worker receive? | Evaluate lifecycle state and applicable role criteria | Mapped values, assignment origin and target scope |
| Who approved an exception? | Route and evaluate the configured request review | Request, reviewer, decision and conditions |
| What access actually changed? | Reconcile provisioning or manual fulfillment | Operation result and native account membership |
| Does the worker still need it? | Review actual access and its source of assignment | Campaign scope, reviewer decision, sign-off and any resulting remediation |
Work an employee transfer
Suppose a worker moves from receiving goods to editing vendor records. Confirm the authoritative department change and whether the role criteria use that attribute. The person remains in the same employment lifecycle state. A new role should reflect the job change without accidentally repeating joiner or leaver actions that apply at other stages. Confirm employee and contractor rules apply to the intended populations separately, using the mapped worker data. Processing can recalculate role membership from the new department and lead to provisioning changes. Check whether an old permission is exclusive to the removed assignment or still supported by another role. Verify that the correct native accounts gained the new access and lost the obsolete access. A sign-in test alone answers whether the user can authenticate. It leaves the entitlement and access-model tests open.
Apply least privilege to the end state. If the new job requires editing a limited vendor field, give only the permission and scope needed for that task. Apply separation of duties independently. If editing vendor banking details and releasing payments are conflicting responsibilities, assess whether the identity holds both capabilities across its actual accounts and roles. Each permission might be justified for an approved role, while the combination violates the organization’s chosen conflict policy. A program can use preventive and detective controls to enforce or review that combination.
Choose the right evidence when something fails
If the worker cannot enter the sign-in page, inspect their credential or federation path. If the worker signs in but lacks the expected target privilege, inspect the assigned access, provisioning result and native policy. If the target permission is correct but nobody can explain its approval or continued business need, governance evidence is missing. Inspect the granting assignment and request or campaign records. Source aggregation gives visibility into current data. Provisioning sends or routes a change. Certification evaluates continued access and can lead to remediation once signed off. Each step has its own record and time.
NIST’s Cybersecurity Framework 2.0 includes access policies, enforcement, review, least privilege and separation of duties as a cybersecurity outcome. The organization implements those outcomes using its own configured operations and scope. In the worked case, record the access the role should grant, the prohibited combination and the actual after-state before closing the transfer. That gives an operator an outcome they can verify from the identity and account records.
See SailPoint’s IGA definition, identity profiles, access model, and NIST’s Cybersecurity Framework 2.0.
A user signs in successfully, but the team needs to know who authorized their temporary target entitlement and whether it was actually granted. Which evidence should the team use?
Only the user’s successful sign-in record
The access request decision and the fulfillment evidence for the specific native account
Only the tenant’s password policy
The display names of all connected sources
A worker can edit vendor bank details and release payments. Each grant came from a different role. Which control directly evaluates that combined access risk?
A password reset policy for both source accounts
A second copy of the user’s identity profile
A separation-of-duties rule that models both conflicting access paths
Additional permission to read unrelated supplier fields
Sections you finish are checked off in the contents.