File and Directory Permissions Modification
- ID
- T1222
- Tactics
- TA0112 Defense Impairment
- Platforms
- ESXi, Linux, macOS, Windows
- Data sources
- Process Creation, File Metadata, Active Directory Object Modification, File Creation, Command Execution
- Source
- attack.mitre.org
- MITRE last modified
- 12 May 2026
Adversaries may modify file or directory permissions/attributes to evade access control lists (ACLs) and access protected files.[2][3] File and directory permissions are commonly managed by ACLs configured by the file or directory owner, or users with the appropriate permissions. File and directory ACL implementations vary by platform, but generally explicitly designate which users or groups can perform which actions (read, write, execute, etc.).
Modifications may include changing specific access rights, which may require taking ownership of a file or directory and/or elevated permissions depending on the file or directory’s existing permissions. This may enable malicious activity such as modifying, replacing, or deleting specific files or directories. Specific file and directory modifications may be a required step for many techniques, such as establishing Persistence via Accessibility Features, Boot or Logon Initialization Scripts, Unix Shell Configuration Modification, or tainting/hijacking other instrumental binary/configuration files via Hijack Execution Flow.
Adversaries may also change permissions of symbolic links. For example, malware (particularly ransomware) may modify symbolic links and associated settings to enable access to files from local shortcuts with remote paths.[4][5][6][7][8]
Sub-techniques (2)
Detection
- DET0299 Multi-Platform File and Directory Permissions Modification Detection Strategy
Data components: Process Creation, File Metadata, Active Directory Object Modification, File Creation, Command Execution
Mitigations (2)
- M1022 Restrict File and Directory Permissions
Applying more restrictive permissions to files and directories could prevent adversaries from modifying their access control lists. Additionally, ensure that user settings regarding local and remote symbolic links are properly set or disabled where unneeded.[1]
- M1026 Privileged Account Management
Ensure critical system files as well as those known to be abused by adversaries have restrictive permissions and are owned by an appropriately privileged account, especially if access is not required by users nor will inhibit system functionality.
