How to use Incidents

Finds and handles security incidents by severity, state, type, owner, tenant and request ID.

What this section is for

Finds and handles security incidents by severity, state, type, owner, tenant and request ID.

Before you start

You need access to IAM.Secure, the correct tenant/workspace and permission to read this data. Prepare a non-sensitive example value such as req_demo_20260806.

Buttons and forms

ControlWhat it does
SearchNarrows the visible list without changing server-side objects.
FiltersNarrows the visible list without changing server-side objects.
Refresh incidentsReloads data from the server and keeps the current page context.
Export CSVDownloads the current result set; active filters normally affect the export.
View detailsOpens the selected record and its available evidence or configuration.

Primary path in the interface

  1. Open the application link above and sign in with the least-privileged role required for this section.
  2. Select the intended tenant or workspace. Do not continue while the header shows a different tenant.
  3. In the navigation, click Incidents. The expected address is https://app.iamsecure.ru/incidents.
  4. Click Search. Enter the documented safe values: req_demo_20260806. Do not paste a production secret into a free-text field.
  5. Review every field before the final Save, Run, Publish or Confirm action. If a preview or validation control exists, run it first.
  6. Review the validation message or changed row. The result must match this purpose: Finds and handles security incidents by severity, state, type, owner, tenant and request ID.
  7. Only then continue to the next dependent section. Copy the request/correlation ID when the interface shows one.
  1. Open the deep link https://app.iamsecure.ru/incidents instead of navigating through the sidebar.
  2. Confirm the tenant/workspace after the page loads; a deep link must not silently switch scope.
  3. Before automating the API path, run this product-specific read-only or validation command. It proves reachability but does not bypass application permissions:
export IAM_SECURE_URL=https://api.iamsecure.ru
curl --fail --silent --show-error "$IAM_SECURE_URL/healthz"

How to verify the result

The selected incident has an owner, disposition and linked audit records.

If it did not work

SymptomWhat to do
401 / sign-in screenSign in again, then return to this page. Do not put a session token in a URL.
403Check the selected tenant and request the documented role; retrying with the same role will not help.
404Verify the exact path and whether the feature is enabled in this environment.
409Search for an object named req_demo_20260806; continue with it or choose a unique name.
422 / validation errorCorrect only the highlighted fields. Keep identifiers lowercase unless the form explicitly allows otherwise.
429Wait for the displayed retry interval or reduce the request scope; do not start parallel retries.
5xx / timeoutRefresh once after the server has recovered; do not repeat a destructive action while its result is unknown. Save the correlation ID and timestamp for support.