Study guide

7.1 Configuring and Leveraging Policies

SailPoint Certified IdentityIQ Engineer Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: The IdentityIQ Engineer Exam

1.1 Exam Format, Official Blueprint, and Study Strategy

2 Chapter 2: Infrastructure, Installation, and Extended Attributes

2.1 IdentityIQ Infrastructure Components 2.2 Installation Steps and Procedures 2.3 Creating Extended Attributes and the Objects That Support Them

3 Chapter 3: Build, Deployment, Patching, Access, and Email

3.1 Ongoing Build and Deployment 3.2 Installing Patches and Performing Upgrades 3.3 Configuring End-User Access 3.4 Email Server Settings and Email Redirection

4 Chapter 4: Lifecycle Manager Configuration, Provisioning Policies, and Workflows

4.1 Configuring Lifecycle Manager 4.2 Identity Provisioning Policies 4.3 Configuring LCM Workflows

5 Chapter 5: Lifecycle Events, QuickLinks, Batch Requests, and Rapid Setup

5.1 Lifecycle Events and Their Workflows 5.2 QuickLinks and QuickLink Populations 5.3 Configuring and Using Batch Requests 5.4 Rapid Setup in Lifecycle Events and Identity Operations

6 Chapter 6: Certification Campaigns and Certification Rules

6.1 Configuring and Scheduling Certification Campaigns 6.2 The Purpose of Common Certification Rules

7 Chapter 7: Policies and Policy Violations

7.1 Configuring and Leveraging Policies 7.2 Responding to Policy Violations

8 Chapter 8: Reporting, Advanced Analytics, and Auditing

8.1 Executing and Leveraging Reports 8.2 Leveraging Advanced Analytics 8.3 Configuring and Using Auditing

9 Chapter 9: Rules, Rule Libraries, and the SailPoint API

9.1 The Purpose and Use of Rule Libraries 9.2 Rule Input and Output Arguments 9.3 Common SailPoint API Objects and Methods

10 Chapter 10: Workflow Development

10.1 Workflow Variables, Transitions, and Step Conditions 10.2 Workflow Steps That Generate Work Items 10.3 The Different Workflow Step Usages 10.4 Leveraging Sub-Workflows

11 Chapter 11: Email Templates, Branding, and Localization

11.1 Customizing and Using Email Templates 11.2 Branding the SailPoint User Interface 11.3 Localizing the SailPoint UI

12 Chapter 12: Application Definitions, Connector Settings, and Rapid Setup Aggregation

12.1 Configuring Application Definitions 12.2 Configuring Common Connector Settings 12.3 Configuring Rapid Setup Aggregation Settings

13 Chapter 13: Data-Loading Tasks and Application and Connector Rules

13.1 Scheduling Tasks for Data Loading and Processing 13.2 Common Application Rule Types 13.3 Common Connector Rule Types

14 Chapter 14: Debugging with log4j, Syslog, and the IdentityIQ Console

14.1 Configuring and Leveraging log4j 14.2 Configuring and Leveraging Syslog 14.3 Leveraging the IdentityIQ Console for Debugging

15 Chapter 15: Debug Pages and the Administrator Console

15.1 Leveraging the Debug Pages for Debugging 15.2 Leveraging the Administrator Console for Debugging

16 Chapter 16: Role Model and Identity Attribute Mappings

16.1 Default Role Models and Role Types 16.2 Configuring Roles and Role Options 16.3 Configuring Identity Attribute Mappings

17 Chapter 17: Data Objects, Relationships, and Group Types

17.1 Common IdentityIQ Data Objects 17.2 Relationships Between Common Data Object Models 17.3 The Difference Between Group Types

7.1 Configuring and Leveraging Policies

Key Takeaways Explain This Topic AI

The policy types are Role SOD, Entitlement SOD, Effective Entitlement SOD, Activity, Account, Risk, and Advanced.

A Role SOD rule is violated when an identity holds any role from the left list and any role from the right list.

Detective evaluation runs during aggregation or identity refresh when Check active policies is selected; preventive evaluation runs in LCM request workflows.

A rule-level violation owner overrides the policy-level owner, and the policy owner is the fallback when no violation owner is set.

Running a policy simulation makes the policy inactive (or disables the single rule tested), so reactivate it afterwards.

Last updated: September 2026

Configuring and Leveraging Policies

Objective 3.3 is configure and leverage policies . A policy describes a condition an identity should never have, such as the same person both creating and approving payments. When an active policy finds that condition, IdentityIQ creates a policy violation for someone to act on (section 7.2). Policies are defined on Setup > Policies . That page is usually limited to System Administrators and Policy Administrators.

The Seven Policy Types

Type Detects How it is defined

Role SOD Conflicting roles of any role type Two lists. Any role on the left plus any role on the right is a violation.

Entitlement SOD Conflicting entitlements within or across applications Two entitlement sets that can use nested AND/OR expressions

Effective Entitlement SOD Conflicts in effective (indirect) access, such as nested groups, unstructured targets, or access through roles Like Entitlement SOD, plus target permissions

Activity Undesirable activity such as logins or account creation, when activity data sources are enabled Identity filters plus activity filters (time frames, source and target applications)

  • Account An identity with multiple accounts on an application A single built-in rule; no separate rule page
  • Risk A composite risk score at or above a threshold A single built-in rule; no separate rule page
  • Advanced Anything else Match lists, filters, scripts, BeanShell rules, or populations

A policy can contain many rules . For example, one Finance Role Conflicts policy might hold a dozen SOD rules. SailPoint's best practice is to group related rules under one well-named policy and give every rule a name that says what it checks.

Policy-Level Settings

Owner – maintains the policy and is the fallback violation owner. If alerts are enabled, the owner is emailed about each violation by default.

Policy Violation Owner – who acts on violations: a specific identity or workgroup, the manager of the violating identity, or someone chosen by a rule . A violation owner set on a rule overrides the policy-level one.

Scope – limits who can see the policy on the Policies page. It does not change how violations are shown or monitored.

Description – can be entered in several languages. Rule descriptions cannot be localized.

Violation formatting rule – adds detail to the violation, such as the applications involved, which is especially useful for Advanced policies.

Violation business process – a workflow that assigns or handles violations. A business process set on a rule overrides the policy's.

State – Active policies are evaluated. Inactive policies are not.

Send Alerts – initial notification template, an Open Work Item option, and an escalation style: None, Send Reminders, Reminders then Escalation, or Escalation Only. You also set reminder frequency, reminders before escalation, an Escalation Owner Rule , and Observers . Observers get emails only, and only the owner gets a work item.

Rule-Level Settings

Each rule has a summary, description, violation owner, formatting rule, business process, and Disabled flag. It also has two informational text fields:

Compensating Control – documents exceptions, such as executives being exempt. It is documentation only and does not change risk scoring or reporting.

Correction Advice – shown to a certifier or violation owner who is deciding which access to revoke.

Detective vs. Preventive Evaluation

Policies are evaluated per identity .

Detective: finds violations that already exist . Select Check active policies in an Account Aggregation or Identity Refresh task. Refresh adds Keep previous violations (retain history of resolved violations) and a comma-separated list of policy names to check only those active policies. Inactive policies are never evaluated, even if listed.

Preventive: catches violations at request time . The LCM Provisioning and LCM Create and Update business processes have policy-checking settings: Disable Policy Checking , Continue on Policy Violations (approvers see them), Present Failures to Requester (requester can remove items), or Fail Workflow . They also let you check All or Selected policies. Preventive checking is optional because you may not want to reveal which combinations enable fraud.

Testing Safely with Simulation

Run Simulation checks a policy, or a single rule, against every identity . It reports only a count of violators. It does not create violations, work items, or a list of names. It can be slow on large systems.

Side effects to remember:

Simulating the whole policy saves it and sets it to Inactive . Set the state back to Active and save when done.

Simulating one rule disables only that rule . The policy state does not change.

Make sure rule names are unique within the policy before simulating.

Loading diagram... Detective and preventive policy checks

Worked Example: A Payment SOD Policy

Create a Role SOD policy named Finance Payment Controls . The owner is the Compliance workgroup, and the violation owner is the manager of the violating identity.

Add a rule, Payment Prep vs Payment Approval . Put Payment Preparation on the left and Payment Approval on the right, and add correction advice ("revoke the role not tied to the person's job code").

Run Simulation to see how many identities already violate it. Review the count, then set the policy back to Active .

Enable Check active policies on the nightly refresh (detective), and set LCM Provisioning to Present Failures to Requester (preventive).