Triaging Posture Findings
Posture findings lists every open posture risk finding across discovered identities, grouped by severity: Critical, High, Medium, and Low. Each finding names the contributing factor, shows the evidence behind it and its history, and links straight to the identity it affects. You can filter findings by Identity, Class, Type, Severity, Risk Area, Owner, Detection type, Status, Finding status, or an Advanced filter set, or group them by identity. Click Export to download the findings.
Findings are grouped into four risk areas, shown in the finding's Risk Area field: Access (what the identity can reach or do), Credentials & Ownership (the health of its credentials and whether it has an accountable owner), Host (the health of the device or endpoint it runs on), and Activity (unusual or insufficient behavioral history). The following table lists a few examples of the findings.
| Finding | Risk Area | What It Means |
|---|---|---|
| Can gain more privilege | Access | This identity can take actions that may give it or another identity more access. |
| Publicly accessible | Access | The asset can be reached from outside your organization. |
| Credential has no expiration | Credentials & Ownership | This long-lived credential has no configured expiration date. |
| Owner is missing or no longer active | Credentials & Ownership | No accountable owner is assigned to the identity, or the assigned owner has left the organization. |
| Host does not meet security requirements | Host | The device or endpoint the identity runs on does not meet your security requirements. |
| Activity matches a threat alert | Activity | The identity's recent activity matches a threat alert from a connected source. |
The summary cards at the top of the page show the Open Queue (open findings and the assets they affect), Severity, 7-Day Movement (new findings compared with resolved), and Top Drivers. The page has two tabs, Findings and Finding types. The Finding types tab lists every finding Agent ID can raise, with its default severity, risk area, and detection type, and whether it is turned on. The findings table itself lists the following columns:
| Column | What It Shows |
|---|---|
| Identity | The agent, non-human identity, or resource the finding is open against. |
| Class | Whether the identity is an agent or a non-human identity (NHI). |
| Finding | The specific condition detected, such as Publicly accessible or Can gain more privilege. |
| Severity | The finding's severity: Critical, High, Medium, or Low. |
| Finding status | The finding's current lifecycle state: Open, Under review, Resolved, or Closed. |
| Risk Area | The risk area the finding rolls up to: Access, Credentials & Ownership, Host, or Activity |
| Detected | How long ago the finding was first detected by the connected source. |
Procedure
On the Posture findings page, click a finding to open its detail panel and review the What was found, Why it matters, Recommended action, Supporting evidence, and Evidence source shown for the finding, along with its Finding details, Blast radius, Finding history, and JSON tabs.
Review the Supporting evidence, which lists the facts that support the finding and, where relevant, the failed requirements, a before and after comparison, or a related security alert. Evidence source shows which connector supplied the facts, with the event time and the scan time. Open Source details (closed by default) to see raw identifiers and other connectors on the record, to search by key or value, or to click View raw evidence and open the JSON tab. A finding with an information icon (Insufficient evidence) is not confirmed because a required fact is missing.
- Click Actions and choose the required option.
Resolve
Mark for review
Reassign owner (or Assign owner)
Block identity (or Unblock identity)
Resolving a Posture Finding
Use this action to close a finding with a reason for the audit record. The fix itself happens at the source; this action only records that it is done or that the risk is accepted.
Procedure
On the finding's Actions menu, click Resolve.
Under Reason, select one option from the Fixed group (Gateway policy created, Disabled at source, Blocked elsewhere), the Risk accepted group (Accepted business risk, Compensating control in place, False positive, Dismissed — not relevant), or Other.
Enter Notes for the audit record; notes are required if you selected Other.
Click Resolve.
The finding's status changes to Resolved and it drops out of the open queue on future scans.
Marking a Posture Finding for Review
Use this action to flag a finding so any administrator can view and work on it before resolving it.
Procedure
On the finding's Actions menu, click Mark for review.
Optionally, enter a Comment giving other administrators context for the review.
Click Mark for review.
The finding's status changes to Under review, and you can add further comments from its detail panel while it stays in that state.
Reassigning or Assigning the Owner
Use this action to choose who is accountable for the affected identity.
Procedure
On the finding's Actions menu, click Reassign owner if an owner already exists, or Assign owner if it does not.
In the Search box, type at least three characters to search for a person; results show Name, Title, and Team.
Optionally enter a Reason for reassignment (or a Note when assigning an owner).
Click Reassign owner (or Assign owner).
Blocking or Unblocking the Affected Identity
Use this action to block the identity at every gateway. Blocking applies identity-wide and affects every finding open against that identity. It is available only for identities with Source: Agent ID Secure.
Procedure
On the finding's Actions menu, below the divider, click Block identity.
Enter a Reason for the block; it is recorded against the block entry.
Click Block agent. The block is raised immediately and appears in Blocked agents, but is not enforced until the gateway accepts the draft policy.
To reverse a block, open the finding and click Unblock identity from the Actions menu.
Related Articles
Agent ID Administration 1Number of Views RSA Agent ID Installation, Deployment, and Administration Guide 5Number of Views Triaging Shadow Assets 1Number of Views Agent ID Architecture 1Number of Views Agent ID Components 1Number of Views