Incident response support
Attackers can delete logs and switch off security tools. They can't stop communicating. We put a passive sensor on your network, show your responders every connection the attacker makes, and verify after the clean-up that nothing is still calling home.
Active incident
Email us with “URGENT: incident” in the subject, or use the contact form. We call back within two business hours, in Australian and Swiss business hours.
Have this ready
Three moments
Before you know, while it happens, and after the clean-up. Each has its own question, and its own service.
Have we been hit?
A critical vulnerability in your web server or firewall, a breached supplier, or something that feels off. We watch your traffic, typically for a week, and tell you what we see: no signs of compromise, machines to investigate, or an active compromise. With the evidence.
Fixed scope, fixed price.
We're under attack
We work alongside your responders from the first day: every outside system the attacker talks to, which of your machines are involved, how the attacker moves between them, and whether data is leaving. Hourly / daily findings, ready for your firewall, endpoint tools and SIEM.
For as long as the incident runs.
Are they really gone?
After containment and rebuild, we monitor for 14 to 30 days against everything learned in the incident. You get a dated report for your board, insurer and regulator: what was watched, for how long, and what was found.
Fixed scope, fixed price.
Be ready next time: Incident Readiness Retainer. A sensor in place and a record of normal traffic before anything happens, agreed response times, and a Compromise Check every year.
Talk to us →After a critical vulnerability
New vulnerabilities are published every day, and the ones in web servers, firewalls and remote-access gateways are often exploited before the patch goes in. A patch closes the door. It does not remove an attacker who already came through it. Whatever they left behind still has to call home, and that traffic is what we look for.
Request a Compromise Check →What we look for
Machines calling home on a regular timer
Data hidden inside DNS lookups
Contact with known attacker infrastructure and anonymising networks
Signs that an exploit worked, such as a server calling back after an attack attempt
Attackers moving between internal systems, including files written to admin shares
Remote-access tools that bypass the firewall
Unusual amounts of data leaving the network
Passwords travelling in clear text, so you know what could have been taken
An analyst reviews every finding before it reaches you. Where the network can't show something, such as a device's patch level, we say so.
How it works
01
You call
We call back within two business hours and agree the scope with you and your responders.
02
Sensor in place
A passive sensor connects to a mirror port or tap, on site or installed remotely with your IT team. It only listens.
03
Hourly / Daily findings
First findings within hours, then regular briefings for your incident lead: attacker addresses and domains, affected machines, what changed.
04
Written evidence
A report your board, insurer and regulator can rely on, with the evidence behind every finding.
05
All-clear
After recovery, we verify that nothing is still calling home.
Works with your responders
We don't replace your incident response firm, your endpoint tools or your insurer's panel. We give them the network evidence they're missing: attacker addresses and domains ready for your firewall and endpoint tools, as CSV or sent to Splunk or ServiceNow.
Your data stays with you
The sensor runs on your site and works fully offline. Traffic, findings and reports stay under your control, which matters when lawyers and insurers are involved. Built on Cy-Mind IP and, for sites where a radio link could be the way out, Cy-Mind RF.
A scenario we’re built to catch
A company rebuilt its servers after a ransomware attack and declared the incident closed. During All-Clear monitoring, one machine that had been cleaned but never rebuilt kept looking up the same unusual domain name every few minutes, day and night. The attacker’s way back in was still open.
Questions
Look at what your network is doing, not only at what your security tools report. An attacker who stays has to communicate: machines calling out on a regular timer, lookups of odd domain names, connections to known attacker infrastructure, new remote-access tools. Our All-Clear Verification watches for exactly these after an incident and documents what it finds.
Preserve evidence: isolate affected systems from the network rather than wiping them, and write down what you noticed and when. Call your incident response provider or insurer, and check your reporting deadlines. Then get visibility of the network, so you can see what the attacker is still doing. That is the step we help with from the first day.
No. We work alongside them. They handle containment, endpoint forensics and recovery. We provide independent network evidence during the incident and, at the end, verify that the attacker is gone.
No. The sensor runs on your premises and can work fully offline. Traffic, findings and reports stay under your control.
We call back within two business hours, in Australian and Swiss business hours. A sensor can usually start listening as soon as your team can give it a mirror (SPAN) port or a network tap.
It states what we watched, for how long, what we checked and what we found, with the evidence. It says whether any indicators of compromise were observed in that period. It does not promise that a network will stay clean, and no honest report can.
Not necessarily. A patch stops new attacks through that flaw, but it does not remove an attacker who got in before you patched. A Compromise Check looks for the traffic such an intruder makes.
Start with a Compromise Check. Fixed scope, low effort on your side, and a clear answer with the evidence behind it.