Study guide
7.2 Responding to Policy Violations
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.2 Responding to Policy Violations
Key Takeaways Explain This Topic AI
The main decisions are Allow (mitigate for a set period), Revoke, Delegate, and Certify, with comments where required.
Only SOD and entitlement-based violations can be revoked; Account, Activity, Risk, and Advanced violations offer Allow and Certify.
To clear an SOD violation by revocation, at least one complete side of the conflicting set must be revoked, and bulk revocation is not allowed.
An allowed violation reappears on the Policy Violations page and in certifications when its allowed period ends.
Users cannot act on their own violations, and certifications show violations only when Include Policy Violations is selected.
Last updated: September 2026
Responding to Policy Violations
Objective 3.4 asks you to understand different responses to policy violations . A policy violation is created when an active policy finds a condition on an identity. The policy violation owner must decide what to do: a specific identity or workgroup, the identity's manager, or an identity chosen by a rule, falling back to the policy owner. You cannot take action on your own violations.
Where Violations Show Up
The Policy Violations page (My Work > Policy Violations, or the QuickLink). The Open tab lists active violations you or your workgroups own. The Complete tab lets you view or edit past decisions. System and Policy Administrators see every violation from My Work, but only their own from the QuickLink.
Violation work items , if the policy's Send Alerts and Open Work Item options are set, or if a violation business process, rule, or alert creates them. Work items created by a business process can include decision buttons (Allow, Revoke, Certify) directly in the work item.
Certifications , if Include Policy Violations is selected. You can build a certification of only violations by including violations and clearing roles, additional entitlements, target permissions, and accounts without entitlements.
Preventively in access requests , through the LCM policy settings (section 7.1).
The Decisions
Decision What it does
Allow (mitigate) Lets the identity keep working in violation until an end date , without affecting compliance or risk. You add a comment and a date, and whether you can edit the date depends on Compliance Manager settings. When the date passes, the violation reappears in the list and in certifications.
Revoke Opens the detail view so you can choose which access to remove. You must revoke one complete set of the offending items, or the violation remains. Removal happens automatically through a connector, through a help desk ticket, or manually through a work request. Bulk revocation of violations is not allowed.
Delegate Sends the violation to someone else as a work item for corrective action. Available only when Enable Line Item Delegation is on in Compliance Manager.
Certify (Bulk Decisions menu) Opens Schedule Certification to launch a full certification for the selected identities
- Bulk Decisions Applies Allow or Certify to many violations at once
- Details Shows rule, description, compensating control , and correction advice
- Which Decisions Each Policy Type Supports
- Policy type Options
- SOD (role) Allow, Certify, Revoke
- Entitlement Allow, Certify, Revoke
- Advanced Entitlement Allow, Certify, Revoke
- Account Allow, Certify
- Activity Allow, Certify
- Risk Allow, Certify
- Advanced Allow, Certify
Revocation needs specific offending items. That is why only SOD and entitlement-type violations can be corrected by revoking. A risk-score or multiple-account violation has no single item to remove.
Violations Inside Certifications
In an access review, a violation appears as its own line item. The certifier can allow it with an exception period, or revoke one of the conflicting items. The rule's correction advice appears when the violation is selected for revocation. Revocations from certifications are processed with other certification remediations by the Perform Maintenance task, or immediately with Process Revokes Immediately. Remediations taken on the Policy Violations page are not part of that maintenance processing.
Keeping Violations Current
Allowed violations expire. When the allowed period ends, the violation comes back for a new decision. The Mitigation Expiration Scanner is one of IdentityIQ's system maintenance tasks.
Violations resolve themselves when later refreshes with Check active policies find the condition gone. Use Keep previous violations to retain their history.
Escalations transfer ownership. With Reminders then Escalation or Escalation Only , an Escalation Owner Rule moves an ignored violation, for example to the owner's manager.
Risk scores include open violations. The work item shows each violation's score weight , which feeds identity risk scoring configured in the Identity Risk Model.
Automating Responses with a Violation Business Process
Instead of waiting for someone to open the Policy Violations page, a policy or policy rule can name a violation business process . When a violation is detected, that workflow can create a customized work item with Allow , Revoke , and Certify decisions built in. It can route the item by department, open a ticket in an external system, or notify security for high-risk rules. A business process set on a rule overrides one set on the policy. Combine it with Send Alerts escalation settings so that ignored violations are transferred to someone else instead of aging silently.
Scenario Walk-Through
A nightly refresh finds that a buyer also holds the Vendor Master Update entitlement, which breaks an Entitlement SOD rule. The violation owner (the buyer's manager) receives a work item. The options:
Revoke Vendor Master Update . One complete side of the conflict is removed, a provisioning request goes to the ERP connector, and the next refresh clears the violation.
Or Allow it for 30 days, citing a documented compensating control such as dual approval on vendor changes. The violation returns after 30 days.
Or Delegate it to the ERP application owner, who knows which entitlement is legitimate.
What the manager cannot do: select this and 40 other SOD violations and bulk-revoke them. Bulk revocation of violations is not supported.