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.

An incident right now?Do not wait. Every minute counts.

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
DetectContainEradicateRecoverLessons

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.

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:
PhishingStolen credentialsExposed remote accessUnpatched vulnerabilities
Read the full article ›

Malware

Malicious software inside the organization, often working quietly to steal data or credentials.

Usually caused by:
Malicious files and linksUnsafe downloadsOutdated systems
Read the full article ›

Account takeover

Unauthorized access to email, cloud or admin accounts.

Usually caused by:
Weak or reused passwordsLeaked passwordsNo two-factor authenticationPhishing
Read the full article ›

Phishing and social engineering

Deception that leads to exposed details or a harmful action.

Usually caused by:
Impersonating messagesLow awarenessWeak approval processes
Read the full article ›

Site and server breaches

Getting into a system through an existing vulnerability.

Usually caused by:
Outdated softwareMisconfigurationNeedlessly exposed services
Read the full article ›

Data leaks

Sensitive data exposed outside the organization.

Usually caused by:
Over-broad permissionsConfiguration mistakesAn insiderAn attack
Read the full article ›

Denial of service

Flooding a service with traffic until it stops working.

Usually caused by:
A targeted attackNo infrastructure protection
Read the full article ›

Physical events

Fire, flood or power loss that hits the availability of systems and data.

Usually caused by:
Everything in one placeBackup in the same placeNo alternative site
Read the full article ›

Human error

Deleting or changing data and settings, even by accident.

Usually caused by:
Broad permissionsMissing proceduresAn untested backup
Read the full article ›

A supplier incident

A failure or breach at a supplier that affects the organization.

Usually caused by:
Single-supplier dependenceUncontrolled supplier accessNo supplier review
Read the full article ›

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.

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.

IR team on the way
Chat on WhatsApp