incident response
You need incident response, not another unread report.
We fix it within 24 hours.
Something has already happened, or you are no longer sure it has not.
Recognize your situation?
- You cannot say whether the attacker is still inside
- The first hour was improvised
- Logs you would need are already short or missing
One free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool.
The problem
What incident response looks like, how you can tell, and what is at stake if it stays.
Signs you need incident response, not only a reboot
These are concrete signals that the event is not over, or that you cannot yet say whether it is.
You cannot say whether the attacker is still inside
A symptom stopped, a password was changed, or a host was reimaged, and there is no picture of persistence, stolen credentials, or mailbox rules.
The first hour was improvised
People pulled cables, wiped disks, or posted in a large chat group. Evidence and timing were not preserved, and nobody led.
Logs you would need are already short or missing
Audit retention was too brief, a critical source was never on, or someone recycled a host that held the only local trail.
Different teams have different stories
IT, a vendor, and a manager each have a fragment. There is no single, human-checked narrative of what is known and what is not.
What incident response looks like
What a messy incident looks like, how it feels when you need certainty you do not have, and why the event is not over when the symptom stops.
You need containment, a clear picture, and a recovery you can stand behind.
Incident response is analysis, containment and clean-up after an attack, with forensics and evidence preservation — not a rush to wipe machines and hope the story holds.
Logs are incomplete, the first changes were made in a panic, and nobody owns forensics. A service may look 'up' again while a back door, a stolen mailbox, or a seeded account is still in the estate.
The attacker may still have a path back in
Logs are incomplete, the first changes were made in a panic, and nobody owns forensics or evidence preservation. The attacker may still have a path back in.
You are being asked for certainty too soon
You are tired, you are being asked for certainty you do not have, and you are afraid of destroying the only evidence you will get.
An incident ends when a human can explain it
An incident is not over when the obvious symptom stops. It is over when a human can explain what happened, what was contained, and what remains.
If you leave it, and if we close the urgent gaps
If you leave it
If you clean up blindly, you can wipe the trail, miss a back door, and tell the board a story that will not survive the next week.
If we close it
You get a human-checked picture of what was found, what was contained, and what still has to be done — in language you can use inside the company.
Recognize your situation?Message us, we will sort it out.
Why it happens
Where this usually comes from, why it shows up in fast or AI-assisted work, and how to check it yourself.
Why incidents become messier than the first symptom
The cause is often the absence of a lead and a pre-agreed order, not a lack of tools on the shelf.
- 01
There was no first-response path
The first hours were invented under pressure, so evidence and containment competed with each other.
- 02
Tools were present and nobody was authorised to contain
An EDR isolate action, a mailbox freeze, or a network block existed, and no one was sure they were allowed to use them.
- 03
Logging was designed for troubleshooting, not for an investigation
The sources, clocks, and retention that forensics needs were never specified.
- 04
Vendors were called in a random order
Each arrives with a partial view and a different idea of 'cleaned.' Without a lead, the pictures do not add up.
Why incident response is being asked of lean teams more often now
Estates are more connected, and a single stolen identity can travel further than it used to. Assistants can summarise logs and still miss persistence if no human leads the order of work.
How to steady an incident yourself before a specialist arrives
These steps do not replace incident response. They stop the situation getting worse.
Stop wholesale wiping unless a specialist has agreed it
Reimaging can be necessary later. Doing it first can erase the only trail.
Write a timeline of what you already did
Times, people, systems, and changes. Imperfect notes are better than a reconstructed memory tomorrow.
Preserve what you still have
Logs, disk images if you know how, mailbox exports, and admin audit. Do not tidy the evidence.
Limit who is in the live discussion
A large group chat spreads rumour and, sometimes, the attacker-visible panic.
0/ 4
Recognize your situation?Message us, we will sort it out.
How Contentum fixes it
A senior specialist leads. AI is a tool. A human checks the result.
This is a hard moment, and rushing without a lead usually makes it worse. You are not expected to be a forensics team on a weekday afternoon.
Contentum is Human First. A specialist leads incident-response and forensics work. AI may help us search logs faster. A human checks containment and the write-up. If you are under an active attack, write to us now and say so in the first message. Keep your own incident plan running in parallel. We take emergency work; we do not promise to stop every attack in a day.
You need someone who can preserve what must be preserved, contain what is still open, and write what happened in language you can use inside the company. AI may help us search logs. A human checks the result.
How a typical weekday case moves
- 01Message received
- 02Specialist named
- 03Diagnosis
- 04Fix
- 05Human check
- 06Handover
How to get a human onto incident response and forensics
No web form, no web chat. If you are under an active attack, write to us now. We take emergency work. We do not promise to stop any attack in a day.
Write what you know, and what you already changed
Write on WhatsApp or Telegram. Say whether you think the event is still active, which systems are involved, and what has already been wiped or isolated.
You get a specialist's name
Within a minute you should see the name of the person who will lead. That specialist is alerted, and can be called if they do not respond.
A weekday case in scope is the 24-hour aim
A first containment picture, preservation, and a human-checked note is the aim on a typical weekday. A long forensic engagement on a large estate is a complex project, and we will say so.
How a Contentum specialist runs incident response
We start from the live system and the evidence you still have, then contain, preserve, and clean up in that order.
We start from the live system and the evidence you still have, then contain, preserve, and clean up in that order. A long forensic engagement on a large estate is a complex project; a typical weekday case in scope is the 24-hour aim. We do not promise to stop any attack in a day.
- 01
Establish what is known and what is still live
A short, honest picture first: systems, identities, and whether containment is even possible in the current state.
- 02
Preserve evidence while containing what is open
These are not opposites when a specialist leads. The order is the point.
- 03
Hunt for persistence, not only the first symptom
Mailbox rules, new accounts, tokens, scheduled tasks, and other paths back in.
- 04
Clean up with a human-checked result
Restore or rebuild only when the path is understood well enough to explain.
- 05
Hand over a written account and the leftover work
What happened, what was contained, and what remains a longer investigation or a hardening project.
What to send so the first session is sharp
If the event may still be active, write to us now and say so, and send what you can. Keep your own incident plan running in parallel.
Whether you believe the attack is still active
Say this first. It changes the order of work.
Systems and identities already involved
Mail, a server, a cloud tenant, a plant network — even a short list helps.
What has already been changed
Password resets, wipes, isolations, power-offs, and vendor calls.
Which logs you still have
Names and roughly how far back they go.
Who must be informed, and any legal hold
We will not invent a public statement for you.
Quick and urgent fixes
First 4 hours with a specialist + unlimited AI: free, once per client. Further work is paid, on request. A human leads and checks the result.
Free (first session)
Complex projects
Larger work uses a different rate, on request. We say so before we continue.
On request
Weekdays, then weekends
The base plan is weekdays only. Weekend work is a separate product. Any surcharge is stated up front, before any call, and depends on complexity. Amount: on request.
On request
The first session is free: the first 4 hours with a specialist, plus unlimited AI, once per client. Work beyond that, the complex-project rate, and the weekend rate are paid, on request.
One free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool.
Stay fixed
What not to do next, the stacks we see in this kind of work, and how to keep the fix in place.
Mistakes that make an incident harder to close
These are common under pressure, and they are why a lead matters.
Wiping first and investigating later
You may destroy the only evidence of how they will come back.
Reusing the same chat for rumour and action
Keep a small, factual channel. A large group becomes a second incident.
Letting every vendor 'clean something'
Uncoordinated changes hide persistence and destroy timelines.
Declaring the incident over because the site is up
Availability is not the same as containment.
How to be less exposed the next time
The session can close an incident in scope. Staying ready is a function you keep.
Write a first-response path while it is still calm
Who is called, what is preserved, what is contained.
Keep logs long enough and in a place an attacker cannot quietly wipe
Forensics starts before the event, or it starts too late.
Decide who is allowed to isolate a host or a mailbox
Authorisation should not be invented at 02:00.
Exercise the path
A short rehearsal is cheaper than the first real event.
Where incident response usually has to look
We work with the estate you have. These are common places, not a complete map of every intrusion.
Identity and email
Entra ID, Active Directory, mailbox rules, forwarding, and stolen tokens.
Endpoints and servers
EDR trails, persistence, and hosts that were already reimaged.
Cloud control planes
Azure, AWS and similar audit trails, access keys, and new resources you did not create.
Network paths
Where the traffic went, including segments with no agent.
Recognize your situation?Message us, we will sort it out.
Questions about incident response
Straight answers about this problem, the session, and what happens next.
Do you take emergency work during an active attack?
Yes. If you are under an active attack, write now on WhatsApp or Telegram and say so in the first message. A specialist is alerted, and can be called. Keep your own incident plan running in parallel — two paths are safer than waiting. We start as soon as we can on a typical weekday case in scope. We do not promise to stop every attack in a day, but we do take this work.
Will you guarantee you can evict any attacker in 24 hours?
No. We will tell you what we can contain, what we know, and what remains. We do not invent certainty.
Do you preserve evidence for a legal case?
We work carefully and we will tell you what we can preserve. If you need a formal forensic expert witness, we will say whether that is in scope or a separate engagement.
Should I tell customers now?
We will not invent a public statement. We will help you see what is actually known so you can decide with your own counsel.
Can this be closed within 24 hours?
For a typical weekday case in agreed scope — diagnosis, the urgent fix, and a human-checked note — that is the aim.
Do I fill in a form?
No. There is no web form and no web chat. Write on WhatsApp or Telegram. Within a minute you should see the specialist's name.
Will you publish findings?
No. This is a private service conversation, not a public write-up.
What is free?
You get one free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool. Further work is paid, on request.
What is free, and what does “within 24 hours” mean?
You get one free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool. On a typical weekday, for a case in agreed scope, we aim to give you a first result within 24 hours: a gap assessment and a plan. On urgent, in-scope fixes we often close the job itself in that window. That 24-hour line is a speed aim, not 24 hours of unpaid work, and not a promise to finish a large programme in a day.
Related security problems we also take on.
See all 20 problems. Each page is written for one pain, not as a copy of this one.
Need urgent help, fast?
If you have a deadline or an incident in motion, these Help Hub topics are a closer match.
You need incident response, not another unread report. We fix it within 24 hours.
Write on WhatsApp or Telegram.
One free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool.