SectionEndpoint Security
Technology category
EDR
EDR belongs to the Endpoint Security area. EDR monitors endpoint activity and supports investigation, isolation, and response to suspicious behavior. It works with endpoint telemetry, processes, files, network connections, and the incident timeline.
Acronym Glossary
This glossary explains acronyms used in this part so the intended security function is clear.
- EDR
- Endpoint Detection and ResponseDetection, investigation, and response for suspicious behavior on endpoints and servers.
What This Technology Covers
EDR monitors endpoint activity and supports investigation, isolation, and response to suspicious behavior. It works with endpoint telemetry, processes, files, network connections, and the incident timeline.
Why It Matters
It follows EPP in environments where the organization needs to understand what happened on the device, respond quickly, and provide useful context for security operations.
In practice, this is not only a technical function. It is a way to place the solution into a broader security architecture. Many organizations operate dozens of consoles and tools, so the challenge is also to understand which technology solves which type of risk.
This category helps name the problem precisely, narrow the list of relevant solutions, and distinguish technologies that may look similar at first glance. That is useful for partners and customers who already understand cybersecurity but need a clear map of the market and available portfolio.
Typical Use Cases
EDR is usually considered when an organization needs tighter control over a specific security layer within Endpoint Security. It can complement an existing architecture, replace an outdated tool, improve visibility, or consolidate functions currently split across multiple products.
Place In The Architecture
Within the broader Endpoint Security architecture, EDR should be assessed by how it connects to existing security and operational processes. Its practical value appears when the solution provides usable data, clear policies, understandable reporting, and integrations with existing tools.
When mapping this technology to SecTec portfolio vendors, it is important to consider not only the feature itself, but also deployment model, licensing, management level, supported platforms, and integration with adjacent areas. In a specific architecture, EDR may be a standalone platform, a capability, or part of a broader solution.
How To Assess The Technology
When selecting a solution, the most important assessment points are:
- which problem the solution covers and where its boundaries are
- whether it supports the organization's existing environment
- how it integrates with SIEM, SOAR, XDR, IAM, cloud, or ticketing
- what level of automation, reporting, and auditability it provides
- whether it reduces operational complexity or only adds another isolated console
Related Areas
Vendors From The SecTec Portfolio
Attack coverage and defensive context
MITRE ATT&CK® Enterprise version 19.1 is used as a reference model. The mapping is a SecTec expert interpretation and does not imply endorsement by MITRE.
Practical attack scenarios
- Credential theftAn adversary obtains passwords, tokens, sessions, or other authentication material and uses it to expand access.
- Public application or API abuseAn adversary exploits a vulnerable web application, API, client-side code, or software component for initial access and execution.
- Malware and Command and ControlMalicious code executes, maintains access, and communicates with adversary infrastructure through common or covert channels.
- Ransomware and availability impactAn adversary encrypts or manipulates data, stops services, inhibits recovery, and creates operational impact.
- Privilege escalation and persistenceAn adversary expands privileges, creates or modifies accounts and policies, and establishes repeatable access to systems, identities, or cloud environments.
- Defense evasion and control impairmentAn adversary hides activity, removes evidence, disguises code, or weakens security tools, encryption, firewalls, and recovery mechanisms.
- Insider threat and authorized access abuseAn insider or an adversary with a valid account abuses legitimate permissions to discover, copy, manipulate, or transfer sensitive data.
- Injection and command executionUntrusted input changes the meaning of a command, query, or template and enables data access, logic bypass, or code execution.
- Malicious file upload and unsafe deserializationAn application accepts or processes a malicious file or serialized object and enables code execution, control bypass, or compromise of other users.
Relevant ATT&CK techniques
- T1003 · OS Credential DumpingDetect, Respond, Validate
- T1027 · Obfuscated Files or InformationDetect, Respond, Validate
- T1053 · Scheduled Task/JobDetect, Respond, Validate
- T1055 · Process InjectionDetect, Respond, Validate
- T1059 · Command and Scripting InterpreterDetect, Respond, Validate
- T1070 · Indicator RemovalDetect, Respond, Validate
- T1105 · Ingress Tool TransferDetect, Respond, Validate
- T1486 · Data Encrypted for ImpactDetect, Respond, Validate
- T1543 · Create or Modify System ProcessDetect, Respond, Validate
- T1547 · Boot or Logon Autostart ExecutionDetect, Respond, Validate
- T1685 · Disable or Modify ToolsDetect, Respond, Validate