Skip to main content

Findings

A KRI tells you how many accounts, systems, entitlements or services breach it. Findings turn each of those into something you can work: one finding per KRI and affected item, with an owner, a severity, a due date, a status and an age.

Navigate to Key Risk Indicators > Findings.

Edition

Findings is available in Pro and Enterprise. Accepting a finding's risk needs an approver and creates a KRI exception, so it needs Enterprise. See Licensing.

What creates a finding​

Findings come from the KRIs that flag individual items. When such a KRI flags an account (or system, entitlement or service), OrbisID creates a finding for it. When the same KRI flags the same item again, the existing finding is updated; you never get a second finding for the same KRI and item.

These KRIs create findings by default:

KRIAffected itemDefault severity
High-Risk Unmanaged Privileged AccountsAccountCritical
Inactive Identity with Privileged AccountAccountCritical
Privileged Without OwnerAccountHigh
Not in PAM ToolAccountHigh
Dormant Privileged AccountsAccountHigh
Expired Credentials Still ActiveAccountHigh
Credential Policy BreachesAccountMedium
Orphaned Non-Human AccountsAccountHigh
Systems with Overdue Attestation RequestsSystemHigh
Shared/Non-Human Privileged AccountsAccountMedium
Stale Passwords on Privileged AccountsAccountMedium
Systems Never ScannedSystemMedium
Systems with Stale ScansSystemMedium
Privileged Services with Non-Privileged AccountServiceMedium
Privileged Services Without AccountServiceMedium
Privileged Account ConcentrationSystemMedium
Systems Overdue for Scheduled AttestationSystemMedium
Disabled Accounts in PAMAccountLow
Systems Without CredentialsSystemLow

Four KRIs that flag individual items do not create findings by default, because on most estates they flag a large share of everything: Standing Privileges (every privileged account), Unlinked Accounts, Unclassified Entitlements and Account-Identity Type Mismatch. You can switch them on.

KRIs that measure a rate or a total (for example Scan Failure Rate, PAM Coverage Ratio, and the Threat Detection KRIs) have no individual item to attach a finding to, so they never create findings. Threat detections are worked on the Threat Detections page.

Choosing which KRIs create findings​

An administrator can change this per KRI: on the Key Risk Indicators page, click the configure icon on a KRI and use Create findings and Finding severity. Disabling a KRI also stops it creating findings.

When findings are refreshed​

Findings are refreshed:

  • after every scan that completes or partially completes, whether it was started by a scan policy or from the Systems page,
  • every night at 03:45 (server time), so time-based KRIs such as stale passwords and dormant accounts move between scans,
  • when a manager or administrator clicks Refresh findings on the Findings page.

Each refresh also closes and reopens findings:

  • A fixed problem closes its finding. When a KRI no longer flags an item, its Open, In Progress or Accepted Risk finding becomes Resolved. The finding records when it was resolved and what confirmed it: the scan whose results showed the fix, or a nightly or manual refresh. Fixes made in OrbisID itself count too, such as linking an identity to an account, or a PAM vault scan that links the account to a vault entry.
  • A problem that comes back reopens its finding. When a KRI flags an item whose finding is Resolved, the same finding goes back to Open (or Accepted Risk, if a KRI exception covers it). This includes findings someone marked resolved by hand: if the next refresh still finds the problem, the finding reopens.
  • A deleted item closes its finding. If the account, system, entitlement or service no longer exists, the KRI no longer flags it, so its finding is resolved.

If a KRI cannot be calculated during a refresh, its findings are left exactly as they were: nothing is resolved because of a failed calculation.

Findings of a KRI that is disabled, or that no longer creates findings, are not refreshed, so they keep their current status.

Severity and due dates​

Each finding takes its KRI's finding severity. For a finding on an account, entitlement or system, the severity is raised to that item's own risk level when that is higher, so a stale password on a Critical-risk account is a Critical finding.

The due date is the start of the finding's current open period (when it was first detected, or when it last reopened) plus the days allowed for its severity:

SeverityDays to remediate (default)
Critical7
High30
Medium90
Low180

An administrator can change these in Administration > Settings > Findings & Risk > Findings SLA. Changes apply to existing unresolved findings the next time findings are refreshed.

A finding is overdue when it is past its due date and still Open or In Progress. Resolved findings and findings with accepted risk are never overdue.

Owners​

A finding's owner is the owner of the affected system (for a finding on a system, the system itself). If the system's owner changes, findings that follow the system owner move to the new owner. A manager or administrator can assign a different identity instead; an assigned owner is kept until someone changes it or clicks Use system owner.

A finding on a system with no owner shows No owner. Setting owners on your systems (Systems) gives every finding on them an owner.

Working a finding​

Click a finding to open it. The detail shows what is affected, when it was first and last detected, the due date, the owner, and the full history of changes.

StatusMeaning
OpenDetected and not yet being worked on
In ProgressSomeone is working on it
ResolvedFixed: the KRI no longer flags it, or someone marked it resolved
Accepted RiskCovered by an approved KRI exception

Managers and administrators can Start work, Mark resolved and Reopen, with an optional comment that is kept in the history.

The Last detected date shows when a refresh last found the item still breaching the KRI.

You don't need to mark a finding resolved once it's fixed: the next refresh after the fix resolves it. You can still mark it resolved by hand; if the next refresh finds the problem is still there, the finding reopens with a note in its history. A reopened finding shows how many times it has reopened, and its due date and age count from the latest reopening, while First detected keeps the original date. Reopening a finding by hand does the same.

Accepting risk​

When a finding is a deliberate, approved exception (for example a break-glass account that must stay outside the PAM tool), click Request risk acceptance. You give:

  • a justification,
  • an optional reference, such as a change or risk-register ID,
  • an expiry date, and
  • an approver: any other IAM Governance Manager or Administrator. An Administrator may choose themselves, after confirming with a tick box that they are approving their own request; the finding then becomes Accepted Risk at once and the audit log records a self-approval.

The finding stays as it is, and the approver is emailed. While the request is waiting, the finding shows who it is waiting on, and the approver sees Approve and Reject buttons on it. Rejecting needs a reason.

When the approver approves, the finding becomes Accepted Risk straight away, and the item is left out of the KRI's adjusted value. If the approver rejects, the finding stays open, and the rejection and its reason appear in the history; you can then request again.

This creates a KRI exception for that KRI and item. When the exception expires, or an administrator deletes it, the next refresh puts the finding back to Open, so an accepted risk never lasts past its expiry date. An exception requested on the KRI Exceptions page works the same way for the matching finding.

Tickets​

Requires Pro or Enterprise edition and a ServiceNow or Jira system.

OrbisID can raise a ServiceNow ticket or a Jira issue for each finding and keep it up to date, so remediation is tracked where your teams already work. Set it up on the ServiceNow, Jira Cloud or Jira Data Center system.

  • A ticket is raised for each Open or In Progress finding of the severities you choose. It is assigned to the finding's owner (the system owner unless you set one by hand) and to the assignment group for its severity.
  • The ticket number (or Jira issue key) appears on the finding, with its state and assignee, and links to the ticket. Raising a ticket and each state change appear in the finding's history.
  • When someone starts work on the ticket (or moves the Jira issue out of To Do), an Open finding becomes In Progress.
  • When a scan confirms the fix, the finding resolves and OrbisID adds a note and resolves the ticket (or moves the Jira issue to Done). If the risk is accepted instead, the ticket is resolved with a note saying so.
  • Closing the ticket or issue in the tool does not resolve the finding: it stays open until a scan shows the problem has gone. No second ticket is raised while it remains in the same open period; if it is resolved and later detected again, a new ticket is raised and the old one stays in the history.

Tickets are raised and synced every few minutes, and on demand with Sync now in the ticketing settings.

Filtering​

The list shows Open and In Progress findings first, earliest due date first. Filter by status, severity, KRI, or overdue only, or search by item or system name. The cards at the top show how many findings are open, overdue, critical or high, and accepted. Click the open, overdue or accepted card to filter the list to those findings.

Remediation dashboard​

Dashboard > Remediation shows how remediation is going, for all findings or narrowed to one system, KRI or owner. Choose how far back the trends look: 4, 8, 12, 26 or 52 weeks, with weeks starting on Monday (UTC).

  • Open backlog. Findings that are Open or In Progress now, by severity (split into within SLA and overdue), by owner, by KRI, and by how long they have been waiting (up to a week, up to a month, up to three months, longer). Findings with accepted risk are counted separately and are not part of the backlog.
  • Average time to resolve. For every finding resolved in the period, the time from when it was detected, or last reopened, to when it was resolved, averaged overall, by severity and by week resolved. A finding that is resolved, reopened and resolved again counts each time, from its own start. Severity is the finding's current severity.
  • SLA. How many findings are past their due date now, which are furthest past it, and what share of the findings resolved in the period were resolved on or before their due date. A finding that has since been reopened is not part of that share, because its due date now belongs to the new period.
  • Detected and resolved per week. How many findings were detected or reopened, and how many were resolved, in each week.

Click an owner or KRI in the backlog tables to see those findings in the Findings list.

Export CSV (Pro and Enterprise) downloads one row per finding in the same scope as the page: KRI, item, system, severity, status, owner, opened, due, overdue, days overdue, resolved, days to resolve and times reopened.

Emailing owners​

Owners can be sent a link to their own findings. Email owners on the Findings page (Manager and above) sends every owner with open findings a short summary: how many open findings they have, how many are overdue and how many of each severity, with a link to their findings and a link to the remediation dashboard narrowed to them. When the Findings list is already narrowed to one owner, the button reads Email this owner and sends only to them.

The links need a sign-in. An owner is emailed only if they have an active OrbisID user with the same email address and a role that can view findings. After sending, OrbisID tells you how many were emailed and how many were skipped because they had no email address or no OrbisID account.

To send these automatically, turn on Email owners a weekly summary under Settings > Findings SLA. It sends every Monday morning and is off by default. The wording of the email can be edited under Email Templates (Findings - Owner Summary).

Who can do what​

ActionRole
View findings and the remediation dashboardIAM Governance Analyst and above
Change status, assign owners, refresh findings, email ownersIAM Governance Manager and above
Request risk acceptanceIAM Governance Manager and above (Enterprise)
Turn on ticketing, sync tickets nowAdministrator
Approve or reject a requestThe approver chosen for it: an IAM Governance Manager or Administrator other than the requester (Enterprise)
Choose which KRIs create findings, set SLA days, turn on the weekly owner emailAdministrator

Every status change, owner assignment, risk acceptance request and decision, and manual refresh is recorded in the audit log.