EDR and endpoint and server protection

Antivirus looks for known files (signature-based), while EDR follows what happens on the device, stops a suspicious process and isolates the device from the network. We deploy and configure it, handle the alerts, and harden the workstations and servers so an attacker has much less to exploit (attack surface).

A padlock on a computer keyboard

An attack that stops
at the first device

EDR sees the chain of actions (process tree): which file the process started from, what it ran and where it tried to connect. When something deviates, the process is stopped, the device is isolated from the network and the incident goes to handling.

  • Detection based on the behavior of processes on the device (behavioral detection)
  • Device isolation and rollback of encrypted files
  • Hardening, LAPS and MFA around the EDR

Call +972-3-3801180

Who this is for

  • Businesses still on classic antivirus

    And want protection that detects an attack even when it has no known signature, for example new ransomware or misuse of built-in Windows tools (living off the land).

  • Organizations with servers and sensitive data

    Where one compromised workstation can lead to the file server, Active Directory and the backups (lateral movement).

  • Those who already have EDR and do not use it

    For example Microsoft Defender, included in some Microsoft 365 plans, installed with default settings while nobody looks at the alerts.

Sound familiar?

These are gaps that let a single attack move from one device to the whole network.

  • All employees log in with administrator rights on their computer (local admin)
  • The same local administrator password on every computer in the office
  • The antivirus raises alerts, and the alerts go to a mailbox nobody reads
  • It is not clear whether the servers are protected, or only the workstations
  • An employee opened an attachment and there is no way to know what it ran
  • MFA is set up for only some users, or only for email

What the endpoint and server protection service includes

We choose the platform according to the environment and existing licensing, and look after it over time.

  • Choosing a platform

    SentinelOne, Microsoft Defender for Endpoint or ESET, depending on the size of the environment, the operating systems and the licensing the organization already has.

  • Staged deployment

    Rollout to workstations and servers in stages, a monitoring period before blocking (audit mode), and defined exclusions so the business applications keep working.

  • 24/7 alert handling (MDR)

    Continuous tracking of alerts, investigation of every incident until it is closed and containment when needed.

  • Isolation and rollback

    Disconnecting an infected device from the network (network isolation) while keeping management access, and restoring encrypted files when the platform supports it.

  • Workstation and server hardening

    Attack surface reduction rules (ASR), blocking macros in files that came from the internet, disk encryption (BitLocker) and turning off old protocols.

  • Removing local admin rights

    Employees work with regular user rights (least privilege), and installations and admin actions go through an orderly process.

  • LAPS

    A unique local administrator password for each computer, rotated automatically and stored in Active Directory or Entra ID.

  • MFA

    Two-factor authentication for all users: email, VPN, remote access and admin accounts.

What we take care of, in detail

EDR / XDR

  • SentinelOne: deployment, policy, isolation and rollback
  • Microsoft Defender for Endpoint and Defender for Business, including integration with Intune and Entra ID
  • ESET PROTECT and ESET Inspect
  • XDR: correlation across endpoints, identities, email and cloud
  • Protection for Windows and Linux servers
  • Controlled exclusions for business applications
  • Migration from existing antivirus without leaving devices unprotected

Alert handling and response

  • 24/7 alert monitoring and automated containment (automated response) according to policy
  • Investigating every alert (triage): the process chain, source and scope
  • Isolating devices, stopping processes and removing malicious files (remediation)
  • Threat hunting based on indicators of compromise (IOCs)
  • An incident report and recommendations to prevent a recurrence
  • Integration with the SIEM and the organization’s incident response procedure

Hardening and identities

  • ASR (attack surface reduction) rules and blocking macros from the internet
  • Disk encryption (BitLocker) and recovery key management
  • Turning off legacy protocols: SMBv1, LLMNR, NTLMv1
  • Removing local admin rights and a controlled process for installations
  • Windows LAPS: a unique, rotating password for each computer
  • MFA for all users and admin accounts, including Cisco Duo
  • Separating admin accounts from everyday work accounts (admin tiering)

From the first conversation to an organized routine

  1. 1

    Mapping the devices (asset inventory)

    Which workstations and servers there are, what is installed on them today and what the existing licensing is.

  2. 2

    Selection and deployment

    Choosing the platform, a staged rollout and a monitoring period (audit mode) before full blocking is turned on.

  3. 3

    Hardening

    Removing admin rights, LAPS, MFA and hardening rules, coordinated with the needs of the work.

  4. 4

    Ongoing handling

    Tracking alerts, investigating incidents and a periodic report on the status of the devices.

What is the difference between antivirus and EDR

Both tools are installed on the device, and they answer different questions. Antivirus checks whether a file is known to be malicious, and EDR checks whether what is happening right now looks like an attack.

  1. Signatures versus behavior

    Classic antivirus compares files against a list of known malware. Attackers often use legitimate Windows tools (living off the land), such as PowerShell, or malware built specifically for the target, and then there is no signature to detect. EDR identifies the pattern (behavioral detection): a Word document that runs a script, connects to an external server and starts encrypting files.

  2. Isolation and rollback

    When an attack is detected, the device can be cut off from the network (network isolation) and left connected only to the management console, so it can be examined without the damage spreading. On some platforms, such as SentinelOne on Windows, encrypted files can also be returned to their previous state. This does not replace an offline (air-gapped) backup, but it saves quite a few full restores.

  3. What XDR adds

    XDR connects the data from the endpoints with data from email, identities and the cloud. That way you can see that the same user received a phishing email, signed in from another country (impossible travel) and right after that ran something suspicious on the computer, and handle it all as one incident.

  4. An alert nobody sees

    Some alerts require a person’s decision (triage): is this a legitimate business application or the start of an attack. If alerts are not reviewed continuously, including at night and on weekends, the tool documents the attack instead of stopping it. Ransomware attacks are often timed for exactly those hours.

  5. Admin rights and LAPS

    An employee logged in with admin rights lets malware install itself, turn off protections and collect passwords (credential dumping). The same local admin password on all computers lets an attacker move from device to device (lateral movement). Removing the rights and LAPS, which gives each computer a unique password that rotates, close both of these gaps.

Guide: Ransomware in a small business: what you can do today

Frequently asked questions

About EDR and endpoint and server protection.

Didn’t find an answer? +972-3-3801180

Antivirus mainly detects known malware. Many attacks use legitimate operating system tools (living off the land) or new malware, and these get through without an alert. EDR identifies the behavior, lets you isolate a device and keeps a record of what happened, so you can understand the scope of the incident.

There is no single answer. Microsoft Defender fits well in an environment that works with Microsoft 365 and Intune, and sometimes the licensing already exists. SentinelOne stands out in autonomous containment and rollback, and ESET is light on resources and convenient in small, mixed environments. The recommendation is given after mapping the environment and the licensing.

Current EDR agents are relatively light. Slowdowns are usually caused by two protection products on the same device or by scans that were not configured correctly. During deployment we remove the previous product in an orderly way and define exclusions for applications that require them.

The platform automatically contains what it identifies with certainty. Alerts that require judgment are reviewed continuously (MDR), outside working hours too, and handled according to a procedure: isolation, investigation, cleanup and an update to the contact person in the organization.

At first some of them will notice. So we prepare the applications they need in advance and set up a simple way to request an installation. Everyday work usually does not require admin rights (least privilege), and the protection you gain is worth the adjustment.

No. EDR reduces the chance that an attack succeeds and the extent of the damage, but no protection blocks everything. An immutable or offline (air-gapped) backup, tested by restoring it, is the last layer of protection when something gets through.

Want to know whether your workstations and servers are really protected?

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

Leave your details and we’ll get back to you

Your details are used only to get back to you. Privacy policy

Call +972-3-3801180Get in touch