IT & Security Operations
Investigate an alert, approve the response and keep the lesson
Shorten evidence gathering and incident handoffs, and turn each resolved incident into reusable operational knowledge.
Gather incident evidence faster, and turn each resolved incident into reusable knowledge.
One story, four steps
A privileged account signs in from an unfamiliar location shortly after an access change.
With KVARK AI Services
Step 1 of 4
Build the incident timeline
The analyst adds the SIEM alert to an incident workspace. An investigation skill retrieves sign-in logs, the account’s role and recent service-desk changes, and KVARK builds a timestamped timeline; the access-change entry opens its originating ticket.
An investigation skill turns the alert, sign-in logs and recent changes into one timestamped timeline.
Example · Incident timeline
Build a timeline for this alert from sign-ins, roles and recent changes.
Used 5 tools
adm.djovic is Dragan Jović’s database administrator account. It joined Prod DB Admins at 08:42 and signed in from Lisbon at 09:51.
Timeline, 10 November
- 08:42Access changeREQ-20417 adds adm.djovic to Prod DB AdminsService desk
- 09:05Sign-inBelgrade office, known laptopSign-in log
- 09:446 failed sign-insLisbon, new deviceSign-in log
- 09:51Sign-in succeededLisbon, MFA push approvedSign-in log
- 09:52Alert raisedSIEM alert 7731, unfamiliar locationSIEM
Type your message here...
Context board1 item
- SIEM alert 7731SIEM
HighUnfamiliar sign-in location, privileged account
- Account
- adm.djovic
- From
- Lisbon, new device
- Raised
- 09:52
REQ-20417Service desk
Add adm.djovic to Prod DB Admins
- Requester
- Dragan Jović
- Reason
- Database migration
- Closed
- 10 Nov, 08:42
Temporary access, to be removed on 13 November.
With KVARK AI Services
Step 2 of 4
Propose a targeted response
Search retrieves the approved account-compromise runbook and a similar resolved incident. The assistant proposes revoking active sessions and temporarily blocking the account, lists affected services and drafts a notification; the analyst revises the plan after the owner responds.
From the runbook and a similar incident, KVARK proposes revoking sessions and blocking the account.
Example · Response plan
Find our runbook and a similar resolved incident, then propose a response.
Used 3 tools
The approved account-compromise runbook 1 and INC-2026-0291 2, a resolved incident with the same pattern, point to two actions:
- 1Revoke all active sessions of adm.djovic and d.jovic 1
- 2Block both accounts until the password and MFA are reset 12
Affected services: Prod SQL cluster, backup console, email and VPN.
Notification sent to Dragan Jović
DJDragan Jović replied to the notification10:31
Not me. I’m in the Belgrade office, working on d.jovic.
Keep d.jovic active and limit the plan to adm.djovic.
Used 1 tool
Response plan, revised
- Scope
adm.djovic, d.jovicadm.djovic
- 1Revoke active sessions 1
- 2Block sign-in until reset 12
- Affected
- Prod SQL cluster, backup console
d.jovic stays active: all 14 of its sign-ins today came from the Belgrade office.
Sources used
- 1Account compromise runbook v3.2p.4
- 2INC-2026-0291 closure reportp.2
Type your message here...
Built with KVARK AI Development
Step 3 of 4
Execute the approved actions
An Incident Response screen shows the exact account, the proposed actions and the approval they need. Once the incident lead approves, the module calls the identity-management tools and shows each confirmed result, session revocation and account block, with timestamps.
The incident lead approves, and the identity tools confirm each action with its timestamp.
Example · Incident Response
Incident Response
INC-2026-0412 · Privileged sign-in from Lisbon
- Planned
- Approved
- Contained
Account
adm.djovicPrivileged
- Owner
- Dragan Jović, database administrator
- Access
- Prod DB Admins since 08:42
- Last sign-in
- Lisbon, 09:51
Linked accountd.jovic stays active
Proposed actionsPlan revised at 10:34
1Revoke active sessions3 sessions, including the Lisbon device
Sessions revokedIDP-58213
2Block sign-inUntil the password and MFA are reset
Account blockedDIR-58214
Approval
Required approval
Incident lead
Both actions run in the identity tools once approved.
JMJelena MarićApproved both actions at 10:40
Audit trail
- 10:34Plan revisedScope limited to adm.djovic
- 10:40ApprovedJelena Marić, incident lead
- 10:40:52Sessions revokedIDP-58213
- 10:40:58Account blockedDIR-58214
With KVARK AI Services
Step 4 of 4
Verify and capture the lesson
A scheduled follow-up job checks for further successful sign-ins and posts the result. The assistant drafts a closure report from the timeline and action records, with a proposed knowledge-base update the analyst reviews and saves.
A follow-up job confirms no further sign-ins, and the approved lesson is saved for future searches.
Example · Incident closure
Sign-in check, adm.djovic24 hourly runs, last 11 Nov 10:41Succeeded
No further successful sign-ins. The block holds.
Used 3 tools
Drafted from the timeline and the action records, for your review:
INC-2026-0412 Closure report.docxTimeline, IDP-58213 and DIR-58214, 24-hour check
Knowledge-base updateApproved
Privileged sign-in from a new location
- Check the owner’s other accounts before blocking them.
- Remove temporary access on the date its ticket gives.
Saved for incident searchKB-0217
Type your message here...
Start with one alert. Keep every lesson for the next.
Start with assistants, skills and context boards in KVARK AI Services, and build dedicated screens, business rules and approval flows with KVARK AI Development where the process needs them.
Start with AI Services, and add dedicated screens as the process needs them.