A phishing email got through, an account logs in from where it should not, a file server shows a ransom note. Incidents takes your team from that first alert to the closing report: every indicator checked against what mlab knows, a timeline kept for you, and the notification deadlines that apply to you, before they pass.
Built for teams of one to five people who handle security next to everything else. No process to configure, no playbook to write first.
Paste what you found. mlab tells you what it knows about each one.
Domains, IPs, URLs, emails, hashes, phone numbers, wallets, CVEs: paste them however they came, they are typed and checked against mlab's lookups as they are added. The worst verdict rises to the top of the incident, and the same indicator showing up in two incidents is one click away.
Every change of phase, severity or owner, every indicator added, every note and every notice sent is written down with who did it and when. Add what happened outside mlab in a line ("isolated the laptop at 14:10"). Entries are added, never edited: it is the record your insurer or an authority will ask for.
The deadlines that apply to you, counted from the right moment.
Say whether personal data is involved, whether you fall under NIS2 or DORA, and Incidents counts every notice you owe, shows what each one must contain and reminds you before it is due, by email, Slack, Teams, Discord or webhook. You name the authority of your own country once, in the settings.
A personal data breach: 72 hours from the moment you became aware of it.
A significant incident: early warning within 24 hours, notification within 72, final report a month later.
A major ICT incident: initial notice 4 hours after classifying it, and no later than 24 hours after detection.
mlab computes and reminds; it never files a notice for you, and deciding whether an incident is significant or major stays yours. This is help, not legal advice.
One PDF with what happened, the notices sent and their references, the post-mortem (root cause, impact, follow-up actions), the timeline and every indicator with its verdict. Download it, or share it with a read-only link.
Every feature on every plan. What changes is how many incidents can be open at the same time; closed ones do not count and stay in your history.
Team and Enterprise add cases, to investigate before anything is declared an incident. Compare all plans.
No. Incidents is made for the IT person, the small team or the managed service provider who handles security among other things. The phases and fields are fixed on purpose, so there is nothing to design before the first incident.
No. mlab tells you which notices apply, by when and what they must contain, and reminds you. Sending them, and deciding whether an incident is significant or major, stays with you.
No. Indicators are checked against what mlab already holds. One that mlab has never seen is marked "not looked up", with a link to run the lookup if you want it.
That is ir.mlab.sh, our self-hosted incident response platform, with chain of custody and multi-team workflows. Talk to us.
Yes, through the mlab MCP server: open an incident, file indicators, update it and write in its timeline, within the permissions you give the agent.