Definition
The email removal technique deletes email files from system storage.
How it works
Email removal is a technique that can be used to prevent a user from executing malware or responding to phishing attempts. Security software or users themselves may detect malicious or suspicious email in a local or remote mail folder email and then employ this technique.
Considerations
For email that needs to be removed, an infosec organization may choose to take additional follow-up actions (such as blocking the sources or notifying providers), rather than only relying on email deletion.
For the case where users detect likely suspicious email files, the organization should consider implementing a means for reporting these emails to their infosec organization.
Email files may propagate through many storage systems across an organization's systems over time, so early detection and blocking helps avoid residual, latent stores of malicious email content in the enterprise.
Implementation perspective
Email Removal should be treated as a technical defensive capability rather than a product checkbox. In practice, teams should define the protected scope, the conditions under which the technique acts, and the observable evidence that demonstrates the intended behavior. For this technique, likely engineering context includes Email, Mail Server.
Use the technique to remove adversary access, malicious objects, processes, credentials, or persistence from the defended environment.
Questions to ask
- What evidence or decision threshold authorizes eviction?
- Which sessions, credentials, processes, objects, or dependencies must be removed together?
- How is business impact controlled while preventing the adversary from retaining access?
- What validation confirms that persistence and alternate access paths no longer remain?
Evidence and validation
- Approved containment and eviction procedures
- Case records showing the trigger, authorization, and actions taken
- Credential, session, object, or process invalidation records
- Post-action scans and monitoring showing that access did not recur
Common failure patterns
- Visible symptoms are removed while credentials, persistence, or alternate paths remain.
- Eviction begins before the scope is understood and causes the adversary to change behavior prematurely.
- Recovery and business restoration occur without post-eviction validation.
This implementation perspective is original Bare Metal Cyber educational content. It does not replace the official D3FEND definition or establish that a specific product implements the technique.
Technique hierarchy
Top-level family
Parent techniques
Direct child techniques
None listed at this level.
Artifacts and ontology entities
These relationships describe how D3FEND connects a defensive technique to artifacts or other ontology entities. They describe graph semantics, not a product certification.
Explicit technique relationships
Show inferred artifact relationship paths (2)
Offensive-technique relationships
These relationships are generated from D3FEND graph paths and are explicitly experimental. They should be treated as hypotheses for defensive analysis—not as proof that the technique prevents, detects, or removes an offensive behavior.
ATT&CK Enterprise (6)
ATT&CK for ICS (1)
Authoritative sources
- Open this technique on the official D3FEND website ↗
- Open the official ontology resources ↗
- System and method for scanning remote services to locate stored objects with malware ↗Mandiant Inc, FireEye Security Holdings US LLC · Sai Vashisht · PatentReference
Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by The MITRE Corporation. MITRE D3FEND™ and the D3FEND logo are trademarks of The MITRE Corporation. MITRE ATT&CK® and ATT&CK® are registered trademarks of The MITRE Corporation. Use of D3FEND source material is subject to the official Terms of Use.