Definition
File eviction techniques delete files from system storage.
How it works
Adversaries may place files or programs into a computer's file system to perform malicious actions. As part of the eviction process, these files and programs should be removed to prevent further compromise or reinfection. Examples of malicious types of files are malware which is directly harmful and content files with the intent to deceive users (e.g., phishing.)
On Windows systems, antivirus (AV) software should be used to safely and permanently remove malicious files. AV software may first quarantine a suspected malicious file, which is the process of moving a file from its original location to a new location and makes changes so that it cannot be executed. Users can then verify that the file is not benign and then permanently delete it.
Considerations
When it is determined that a file should be removed for security purposes, the organization--or systems implementing an organization's policies--may determine that the file should not simply be deleted from the enterprise's mission systems, but be quarantined to a secure system by an approved mechanism, so as to allow follow-up investigation by security staff.
On Windows systems, deleting a file in File Explorer does not permanently delete a file - it sends it to the Recycle Bin instead. The Recycle Bin must be emptied, or alternative steps must be performed to remove files completely. Even then, in some cases the data may persist in disk, so data shredder tools may be needed to completely wipe a file. Thus, AV tools are recommended.
Implementation perspective
File Eviction 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 File, 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
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 (101)
Showing the first 60 of 101 source-derived relationships. Open the official D3FEND technique for the current graph view.
ATT&CK for ICS (8)
Authoritative sources
- Open this technique on the official D3FEND website ↗
- Open the official ontology resources ↗
- How Does Antivirus Quarantine Work? ↗Katarina Glamoslija · InternetArticleReference
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.