Breached? An IR team is on its way
When there is a security incident, we put an incident response (IR) team on it: we contain, investigate, clean up and get you back to work, and stay with you until the final report.
Every incident is different. The process is consistent.
No two incidents are alike, so no checklist fits everyone. What is constant is the process: an orderly assessment, evidence-based decisions and a response plan built around the organization, its systems and its risk.
- Calling early shortens the incident and limits the damage
- The initial assessment shapes the response plan
- Evidence is preserved throughout
- Decisions in full coordination with management
- Full documentation, from the first minute to the final report
The incident lifecycle
- Detect: understanding the incident, its scope and impact.
- Contain: stopping the spread and limiting the damage.
- Eradicate: removing the threat and closing what allowed it.
- Recover: a controlled return to operation, by business priority.
- Lessons: a final report, recommendations and a stronger security posture.
The phases in depth
Pick a phase to see its goal and what you get at its end.
Understanding what happened, what was affected and how severe it is, as the basis for every decision that follows.
At the end of the phase: A situation picture and a response plan.
Limiting spread and damage, while preserving evidence and keeping the business running as far as possible.
At the end of the phase: A bounded, controlled incident.
Collecting and analyzing evidence to understand the source, scope and timeline of the incident.
At the end of the phase: Documented findings, also for legal or regulatory needs.
Removing the threat and bringing systems back in a controlled, safe way, by business priority.
At the end of the phase: Systems back up and clean.
Supporting management, and helping prepare reports to authorities and deal with regulators and external parties.
At the end of the phase: Orderly, timely reports.
Analyzing what made the incident possible, and recommendations to strengthen, so it does not recur.
At the end of the phase: A final report and a hardening plan.
What the team brings
Containment
Limiting the incident and the damage.
Forensics
Evidence collection, advanced log analysis and evidentiary documentation for legal or regulatory needs.
Attack analysis
The source, scope and timeline of the incident.
Safe recovery
A controlled return to operation, by priority.
Reporting to authorities
Support preparing reports to the Privacy Protection Authority and dealing with a regulator.
Hardening after the incident
Recommendations and work to strengthen your security posture.
Kinds of incidents
Ransomware
One of the hardest and most common attacks. It encrypts data and systems, and sometimes threatens to publish the data.
Usually caused by:Malware
Malicious software inside the organization, often working quietly to steal data or credentials.
Usually caused by:Account takeover
Unauthorized access to email, cloud or admin accounts.
Usually caused by:Phishing and social engineering
Deception that leads to exposed details or a harmful action.
Usually caused by:Site and server breaches
Getting into a system through an existing vulnerability.
Usually caused by:Data leaks
Sensitive data exposed outside the organization.
Usually caused by:Denial of service
Flooding a service with traffic until it stops working.
Usually caused by:Physical events
Fire, flood or power loss that hits the availability of systems and data.
Usually caused by:Human error
Deleting or changing data and settings, even by accident.
Usually caused by:A supplier incident
A failure or breach at a supplier that affects the organization.
Usually caused by:A security incident is anything that harms the confidentiality, integrity or availability of information. Every incident gets a response plan of its own.
Reporting duties
A security incident in a personal database may require a report to the Privacy Protection Authority. The duty is on the database owner, and we help prepare it and deal with the regulator.
The Israel National Cyber Directorate can be reached at 119.
After the incident
Management & security
The layers of protection and ongoing management.
Learn more ›CISO as a Service
A security chief, without hiring one.
Learn more ›DRP & continuity
The business keeps running, even when something fails.
Learn more ›Supplier risk
Your suppliers, and what happens when they go down.
Learn more ›Frequently asked questions
Are you available at night?
There is a night on-call for urgent issues. In an incident, call right away.
How is it priced?
By the working hours of the IR team, in a separate engagement.
Every incident is different. Where do you start?
With an assessment. It sets the response plan, the order of actions and who needs to be involved.
An incident? Call now
Calling early shortens the incident and limits the damage.