Privilege and entitlement drift

Stop privilege and entitlement drift

Find and remove access beyond what was approved. Redblock’s AI agents work inside apps your IGA can’t reach, make approved changes, and verify the result.
The problem

Valid roles can hide 
excessive access.

Employees can stay in valid roles while their app access grows beyond what was approved. Group permissions change, admins add rights outside the IGA, and approved removals sometimes fail to take effect.

If your IGA cannot read the app, its record may miss those changes. Someone has to open the admin screens and compare permissions by hand.

Security incident

Guest permissions reached 
data they shouldn’t have.

CRM data extracted

Through guest permissions that exceeded their purpose

In March 2026, Salesforce reported a campaign exploiting “overly permissive Experience Cloud guest user configurations.” Attackers used excessive guest permissions to extract CRM data beyond what organizations intended to expose.

Salesforce traced the exposure to customer-configured access. The profile’s permissions had exceeded its intended purpose.

Source: Salesforce Security, March 7, 2026.

Where drift comes from

Your IGA sees the group, but the app holds the permissions.

Provisioning by role name often creates a group for each role, growing the catalog into thousands of entries. The IGA governs role and group assignments, while permissions are set inside the app.

Role mining cleans up the catalog once, then the app keeps changing.

Your AD says

  • View payments
  • View beneficiaries
  • View exceptions
  • View audit history

The app says

  • View payments
  • View beneficiaries
  • View exceptions
  • View audit history
  • View branch CRMNot in AD
  • Edit beneficiaryNot in AD
  • Approve paymentsNot in AD
Why Redblock

Redblock finds excess access 
and removes it in the app.

Redblock agents run as a service in your environment and use app admin screens to extend your IGA to legacy, internal, and vendor apps.

Find

Redblock agents read current roles, groups, and entitlements exposed by the app, comparing them with approved IGA records. Agents check again on a schedule and flag new changes.

Remove after approval

Redblock agents remove the permissions and memberships your team approves for removal, working through the app’s admin screens and checking the target before making changes.

Verify

Redblock agents read the updated permissions back from the app, record audit evidence, and log the outcome to your SIEM and IGA. If a change fails, your team gets an alert.

Illustrative example

A view-only group gained 
payment approval rights.

The IGA records five view permissions for this group. Redblock finds two additional rights inside the payments app, and your team approves their removal.

Access
Found by Redblock
Done and verified by Redblock
View payments, beneficiaries, payment batches, exceptions, and audit history
FoundMatches approved access
DoneView access retained
Edit beneficiary bank details
FoundNot approved
DonePermission removedVerified
Approve payments
FoundNot approved
DonePermission removedVerified
Redblock agent

Removes the extra rights after approval, verifies the remaining access in the app, and logs the result to the IGA and SIEM.

Find the access that has drifted.

See Redblock find excess access, remove it after approval, and verify the result inside your apps.

Book a Demo
Book a Demo