Agent discovery is enabled per workspace. To turn it on, contact us at support@oleria.com.
Risk reasons at a glance
Oleria has 17 risk reasons. The table lists them most severe first, the order in which the Risk tooltip lists an agent’s reasons. Select a reason for what it means, why it matters, and everything to check.Risk levels
An agent’s risk level is the highest severity among its risk reasons.
Oleria evaluates an agent’s risk each time the agent’s own integration syncs, from what Oleria holds at that moment about every connected application. A change made in another connected application shows only after that application’s integration has synced and the agent’s integration has synced after it.
Where risk appears
How to read risk reasons
Some risk reasons combine two simpler ones. When a combined reason applies, Oleria lists it in place of the reasons it combines:
The Risk Finding filter matches the reasons an agent lists, so filtering on a simple reason doesn’t return an agent where a combined reason replaced it. To find every agent with a simple reason, select it together with every combined reason whose row names it. For Runs as an account with elevated privilege, that is four combined reasons. The first two combined reasons also apply to an agent that can act as others and has no elevated-privilege account, so the filter returns those agents too.
Each reason below shows its on-screen title and severity. The “Why it matters” and “What to check” notes are Oleria’s guidance, not text you see in the product.
Two terms recur in the reasons below:
- An elevated-privilege account is an account the agent runs as whose Privilege is Elevated on the Agent Identities tab.
- An agent can act as others when an account it runs as, or a group or role that account belongs to, can act as an account, group, or role other than the agent’s own accounts.
Who can use the agent
Anyone can use it without signing in
Severity: High The agent’s audience is Public, and a grant lets anyone use it without signing in. Why it matters: Anyone who can reach the agent can make it act, and there is no identity to attribute an interaction to, limit, or revoke. What to check: On the Who Can Use tab, find the principal that stands for anyone, such as an account whose Type is Anonymous user, and the entry point under Via. If the agent isn’t meant to be public, remove that grant in the source application.Set to allow anyone, but not reachable yet
Severity: Low The agent’s audience is Public, but no grant lets an anonymous caller use it. Why it matters: The agent is configured to be public. One grant to an anonymous principal opens it to anyone. What to check: Confirm that the Audience of Public is intended. If it isn’t, change the agent’s audience in the source application.Principals outside the organization can use it
Severity: Moderate Someone outside your organization can use the agent, and Anyone can use it without signing in doesn’t apply. This includes a grant to anyone on an agent whose audience isn’t Public. Why it matters: People you don’t manage can make the agent act with the access its accounts hold. What to check: On the Who Can Use tab, look for principals whose Type is External user, for groups and roles that reach beyond your organization, and for a principal that stands for anyone, such as a group named for anonymous or all users. On AWS, a resource policy that allows any principal shows this way. Confirm that each one is intended.Anyone can use it, and it runs as an account with elevated privilege or can act as others
Severity: Critical Anyone can use the agent without signing in, and the agent either runs as an elevated-privilege account or can act as others. Why it matters: An anonymous caller can steer an agent that holds elevated-privilege access or can borrow another identity’s access. What to check: Find the public grant on the Who Can Use tab. On the Agent Identities tab, look for an account whose Privilege is Elevated. When no account is Elevated, the reason comes from what the agent’s accounts can act as:- Select an account’s name on the Agent Identities tab to open the account’s own page. For a non-human identity (NHI), look on the Access tab there for access the account gets by acting as another account or a group. When it acts as another account, Impersonation names that account.
- On the Access Graph, with Access selected under Graph types, select the account. When its side panel has a Can impersonate list, look there for accounts it can act as directly.
- Neither place shows a right the account holds through a group or role it belongs to, or a right to act as a role. When neither place explains the reason, check in the source application which accounts, groups, and roles the account, and each group and role it belongs to, can impersonate or assume.

