Anomaly Detection
Safeguard against potential risky access to your tools
Last updated
Safeguard against potential risky access to your tools
Last updated
Anomalies identify and alert users to unusual or unexpected activities within a system.
This helps to safeguard against potential risks and ensure that tool access remains controlled:
Detects high-risk access requests, approvals of previously rejected requests, and sudden requests from inactive users
Flags repetitive or suspicious automated actions, ensuring that automation doesn't become a security vulnerability
Provides detailed information on each detected anomaly
Anomalies are sorted by the detection date.
You can also create a webhook to send Anomalies notifications to an internal system.
Item | Description |
---|---|
Apono Premium | Apono plan providing the most features and dedicated account support |
Access Flow | Minimum of one configured self serve access flow |
Follow these steps to investigate an anomaly:
Review the alert.
If the alert is a valid concern, revoke the request and update the access flow.
On the Alert Details panel, under Alert Details, click the Request ID link. The Access request details panel appears.
If the request Status is Active, click the Timeline tab to view the history details of the request.
On the Resources tab, click Revoke Access to revoke the request and the associated access. The request Status will change to Revoked.
On the Alert Details panel, under Alert Details, click the Access Flow link. The Edit Access Flow page appears.
Edit the access flow (steps 3-5).
Anomalies can be filtered by one or multiple filters. Follow the steps in the table below to apply each filter.
Filter | Description |
---|---|
All time | Filters by relative or absolute time filter Relative Follow these steps to set the relative time filter:
Absolute Follow these steps to set the absolute time filter:
|
Type | Filters by type of anomaly Follow these steps to filter by anomaly:
|
Severity | Filters by level of concern for the anomaly defined by Apono Follow these steps to filter by anomaly:
|
Resource Type | Filters by type of resource Follow these steps to filter by resource type:
|
User | Filters by user Follow these steps to filter by user:
|
Integrations | Filters by integration Follow these steps to filter by user:
|
The following table explains each anomaly type.
Anomaly Type | Description |
---|---|
Request high risk access | Triggered when elevated access is requested to a sensitive resource and may pose risks to the organization Sensitive Resource Resource name or tag contains one of the following:
Elevated Access Permission name contains one of the following:
Recommended Actions:
|
Approved after being rejected in the past | Triggered when a request of similar scope was manually rejected and subsequently approved within the last 90 days This may indicate one or both of the following circumstances:
Recommended Actions:
|
Inactive user detected | Triggered when a user makes a request for the first time in 90 days This may indicate one of the following:
Recommended Action:
|
Access automation detected | Code has made repeated requests with similar This may indicate that someone is using CLI commands or other cloud automations to bypass the just-in-time mechanism. Recommended Action:
|
On the Anomalies page, under the RECOMMENDATION column, click the icon (). The Alert Details panel opens.