Cyber Incident Response Team (IR)
When an information security incident is suspected, we step in (incident response) at any hour, including nights and weekends: we contain the attack, preserve evidence for investigation (forensics), clean up and restore from a clean backup. When we also manage the business’s IT, we already know the network, the backups and the admin accounts, and the response starts without a getting-to-know-you phase.
An incident managed
from the first call
An incident brings a lot of pressure and little certain information. From the first call we keep an incident log: what was detected, what was isolated, which decisions were made and who approved them. The same documentation later serves management, the insurer and the report to the regulator.
- An initial triage call and containment
- Evidence preservation and investigation (forensics) before cleanup
- Restore from a clean backup and lessons learned
Interactive illustration
How a cyber incident is handled, step by step
Based on the NIST incident handling cycle (SP 800-61). Choose a stage to see what happens in it and what the team does.
What happens at this stage
Before anything happens: there is a response plan, a contact list, tested backups and documentation of the infrastructure. Most of the difference between a short incident and a long one is decided here.
What the team does
We write a response plan (IR plan) and ready-made scenarios (playbooks), run exercises with management (tabletop) and make sure there are logs, monitoring and an isolated backup.
Who it’s for
A business in the middle of an incident
Encrypted files, an email account sending messages nobody wrote, or an alert whose meaning isn’t clear. You call, and we start with containment and evidence preservation.
Organizations that hold personal data
Clinics, law and accounting firms, service companies and any business where an incident could require reporting to the Privacy Protection Authority and a difficult conversation with customers.
Anyone who wants to be prepared in advance
Businesses that want a written response plan (IR plan), a response agreement in place (IR retainer) and an exercise for management, sometimes because their cyber insurer or a large customer requires it.
Sound familiar?
These are the gaps that turn an incident that could have been contained early into a long and expensive one.
- It’s not clear who to call when a computer starts encrypting files in the middle of the night
- There’s no written response plan (IR plan), and every incident is handled by improvisation
- On the day of the incident, nobody knows where the backups are or who holds the admin passwords
- Whoever got to the problem first formatted the computer, and the evidence (forensics) disappeared with it
- It’s not clear whether the incident must be reported to the Privacy Protection Authority, or who decides that
- There’s a cyber insurance policy, and nobody has checked what it requires on the day of an incident
What incident handling includes
The work follows the standard incident response phases, and every significant decision is made in coordination with management.
24/7 incident availability
A contact line for security incidents, including nights and weekends. In the first call (triage) we work out what is happening, what is at risk, what to do right away and what not to touch.
Containment
Isolating workstations and servers, locking compromised accounts, cutting off remote access and blocking at the firewall, to stop the spread without destroying evidence.
Digital forensics
Preserving evidence from workstations, servers and logs, and building a timeline: how the attacker got in, how far they got and what they took out.
Cleanup and closing the breach (eradication)
Removing malware, backdoors and accounts the attacker created, changing passwords and keys, and closing the weakness they got in through.
Restoring from a clean backup (recovery)
Choosing a restore point from before the intrusion, checking that the backup wasn’t affected, and bringing systems back in order of business priority.
Communication and reporting
Supporting management, draft notices to employees and customers, and support with reporting to the Privacy Protection Authority and the Israel National Cyber Directorate when required, in coordination with the insurer.
Lessons learned
A summary report on what happened, what worked and what didn’t, and a hardening plan implemented in the infrastructure itself so that a similar incident doesn’t happen again.
Readiness before an incident
A response agreement in place (IR retainer), a written response plan (IR plan) with scenarios for each type of incident (playbooks), and a tabletop exercise for management.
Types of incidents we handle
An information security incident is any event that harms the confidentiality, integrity or availability of information, so a fire in the server room or an accidental deletion also counts as one.
Ransomware
Malware that encrypts files and servers and stops work. Attackers often copy data before encrypting it and threaten to publish it (double extortion).
Usually caused by:
- Remote access exposed to the internet
- Stolen or leaked passwords
- Security updates that weren’t installed
Malware
Malicious software that runs quietly on the computer, collects passwords and data (infostealer) or opens a way for the attacker to continue the attack.
Usually caused by:
- A malicious attachment
- A download from an unknown source
- A computer without EDR
Account takeover
An attacker who gets into an email, cloud or admin account and acts as a real user, for example to send customers fake payment requests (BEC).
Usually caused by:
- An account without MFA
- The same password on several services
- A fake login page
Phishing and social engineering
A message or call that impersonates someone familiar and gets an employee to hand over details, approve a payment or open a file.
Usually caused by:
- Impersonating a supplier or a manager
- Pressure to act urgently
- No double approval for payments
Website or server breach
Exploiting a weakness in a website, a plugin or an internet-facing service to take over the server, change content or spread malware to visitors.
Usually caused by:
- An outdated plugin or system
- An admin interface open to everyone
- Default settings
Data leak
Personal or business information that reached someone who shouldn’t see it, as a result of an attack, a mistake or an insider. When personal data is involved, a reporting obligation may apply.
Usually caused by:
- A sharing link that’s too open
- Broader permissions than needed
- Unprotected cloud storage
Denial of service (DDoS)
Flooding a website, server or internet line with traffic from many sources until customers and employees can’t connect.
Usually caused by:
- No protection at the internet provider
- A single service with no alternative
- High public exposure
Physical incident: fire, flood, power
Damage to the server room or the office that takes systems down and can wipe data, with no attacker involved. This too harms the availability of information.
Usually caused by:
- Servers and backup in the same room
- No alternate site (DR)
- A UPS that hasn’t been tested
Human error
An accidental deletion, a configuration change that took down a service, an email with sensitive data sent to the wrong recipient, or an AI agent with broad permissions that ran a destructive action.
Usually caused by:
- Admin permissions for everyone
- Changes without control (change management)
- A backup never tested with a restore
Supplier incident (supply chain)
A breach or failure at a software, cloud or service supplier that reaches the organization through the access and connections the supplier has.
Usually caused by:
- Unrestricted supplier access
- No alternative to a critical supplier
- A compromised software update
What we take care of, in detail
Response during an incident
- A 24/7 security incident line and an initial triage call
- Assessing scope and severity: which systems, accounts and data were affected
- Containment: isolating workstations and servers, locking accounts, revoking active sessions and blocking at the firewall
- Working with EDR, Active Directory, Microsoft 365, Google Workspace, the firewall and the VPN without losing logs
- Eradication: removing malware, persistence mechanisms, and accounts and scheduled tasks the attacker added
- Changing passwords, keys and access tokens, including service accounts and admin accounts
- Recovery from a clean, tested backup, in the order of priority set by the business impact analysis (BIA) and the RTO/RPO targets
- Heightened monitoring after returning to normal operation, to detect any attempt by the attacker to return
- Cloud and website incidents: a compromised Microsoft 365 account, mail forwarding rules set by the attacker, cleaning up a hacked website (malware cleanup)
Investigation, evidence and reporting
- Evidence preservation and chain of custody
- Disk and memory imaging and log collection from critical systems
- An incident timeline: the point of entry, lateral movement, access to data and its removal (exfiltration)
- Indicators of compromise (IOC) and feeding them into the security tools, the firewall and email filtering
- Checking the reporting obligation under the Privacy Protection Law and the Data Security Regulations, and preparing the report to the Privacy Protection Authority
- Reporting and information sharing with the Israel National Cyber Directorate
- Coordination with the cyber insurer, the legal counsel and whoever manages communication with customers
- Draft notices to employees, customers and suppliers
- A technical report and an executive summary with hardening recommendations
Readiness before an incident
- A response agreement arranged in advance (IR retainer): contact channels, access and permissions set up ahead of time
- An incident response plan (IR plan): roles, decision authority, contact details and escalation thresholds
- Response scenarios (playbooks): ransomware, account takeover, email payment fraud (BEC), data leak, physical incident, supplier incident
- A tabletop exercise for management and the IT team
- Log readiness check: what is kept, for how long and where
- Restore testing and backup that can’t be changed or deleted (immutable backup)
- A contact list for incident time: management, suppliers, insurer, legal counsel
- Alignment with NIST SP 800-61, NIST CSF, ISO 27001 and the Israel National Cyber Directorate guidelines
From the first conversation to an organized routine
- 1
First conversation
In an incident, call right away. Without an incident, we start with an introductory conversation about the infrastructure, the data the business holds and the requirements of customers, a regulator or an insurer.
- 2
Readiness check
We check the backups, the logs, the admin accounts and the access, so that on the day of an incident there is something to work with.
- 3
IR plan and playbooks
We write the response plan, the roles and the contact channels, and a scenario for each type of incident relevant to the business.
- 4
Tabletop exercise and IR retainer
We run an exercise for management and the team, fix the gaps it reveals and sign a response agreement that is ready for incident time.
What determines how long an incident lasts and how much damage it does
The outcome of an incident is decided mainly by the preparation done beforehand and by the decisions made in the first hours. These are the points where the difference shows.
An IT provider that knows the infrastructure contains faster
In the first hours you need to know where every server is, which accounts are admin accounts, how the network is divided into zones (segmentation, VLAN) and where the backup is. An outside team that arrives without that knowledge spends this time on mapping, and meanwhile the attacker keeps moving through the network (lateral movement). When the people who manage the infrastructure are also the ones responding, the access, the documentation and the network map are already in their hands.
Why you don’t format right away
The natural urge is to wipe, reinstall and get back to work. That destroys the evidence that shows how the attacker got in, and without it there is no way to know whether the breach was closed or whether data left the organization (exfiltration). Preserving evidence (forensics) already at the containment stage makes it possible to answer these questions, including before a regulator, an insurer or a court.
The question is which backup you restore from
In ransomware attacks the attackers also try to reach the backups, and sometimes they are in the network for a while before the encryption. So you choose a restore point from before the intrusion and check that it is clean before bringing it back onto the network. A backup that can’t be changed or deleted (immutable backup) and an off-site copy determine whether there is anything to restore from.
Reporting to the regulator and the insurer
A severe security incident in a personal database may require reporting to the Privacy Protection Authority under the Data Security Regulations, and Amendment 13 expanded the Authority’s supervision and enforcement powers. Cyber insurance policies often include conditions about early notice to the insurer and about who handles the incident. These decisions belong to management, and to make them it needs a factual, documented picture as early as possible.
Preparation does most of the work
An organization with a response plan (IR plan) and written scenarios (playbooks) knows who decides, who talks to customers and who calls the insurer, and doesn’t find out in the middle of the night. A tabletop exercise exposes gaps such as a backup nobody knows how to restore or a supplier with no contact details. A response agreement in place (IR retainer) saves inquiries on the day there is no time for them.
Guide: Account takeover: when someone else signs in as your employee
Call right away, and don’t turn off computers, delete files or contact the attacker. Disconnect a computer that looks infected from the network, both the cable and the Wi-Fi, and leave it on to preserve what is in memory. If the mailbox may have been compromised, don’t use it to report the incident. In the first call you get instructions based on what is actually happening.
Cyber insurance policies often include a duty to notify the insurer early, and sometimes also conditions about who handles the incident and which expenses are covered. So the policy is checked within the first hours and every action is documented. When its requirements are written into the response plan (IR plan) in advance, there are no surprises.
That’s a management decision, and it’s better not made under the pressure of the first hours. Paying doesn’t guarantee a decryption key that works, and it doesn’t change the fact that the data has already been copied. Before any decision, check whether you can restore from a clean backup, what the insurance policy says and what the legal counsel advises.
The Privacy Protection Regulations (Data Security) require reporting a severe security incident in a personal database to the Authority, and what counts as severe depends on the database’s security level and on what was affected. The obligation falls on the database owner. We provide the technical picture, help prepare the report and work alongside the organization’s legal counsel. At the same time, you can report to the Israel National Cyber Directorate and get assistance from it.
An agreement signed before anything happens: how to reach us, what access is already in place, the scope of work and who in the organization is authorized to approve actions. On the day of an incident it saves inquiries and negotiation, and the work starts with containment. Cyber insurers and large customers sometimes ask about it in security questionnaires.
Management and the IT team go through a scenario together, for example ransomware discovered on a Thursday evening, and decide at each stage what to do. No systems are touched. The exercise shows where the plan falls short: who is authorized to decide, who gets notified, and whether anyone actually knows how to restore the backup.
More you can centralize with us
CISO as a service
An outsourced CISO: risk assessment and risk management, policies and procedures, compliance with Amendment 13 and ISO 27001, management reporting and an annual work plan.
EDR and endpoint and server protection
Advanced protection for workstations and servers with SentinelOne, Microsoft Defender or ESET: behavioral detection, isolation, rollback and 24/7 alert handling.
DRP and business continuity
A recovery plan built from a BIA: RTO and RPO targets, a DR site, immutable and air-gapped backup, ransomware recovery and exercises that check everything works.
Suspect an incident, or want to prepare before one happens?
Tell us briefly about your business and what concerns you about your IT. We’ll get back to you to understand what you need and suggest a way of working that fits.
Business hours: Sunday to Thursday, 08:00 to 17:00
Existing client? Open a support ticket