Windows Symlink [new]

From a security perspective, symlinks can be dangerous. An attacker with write access to a directory could replace a trusted file with a symlink pointing to a sensitive system file (e.g., replacing a log file with a symlink to C:\Windows\System32\config\SAM ). When a privileged process writes to the log, it might inadvertently corrupt the SAM file. Windows mitigates this through administrator-only creation by default, and through auditing. However, administrators must be cautious when granting symlink creation rights or when using tools that follow symlinks in security-sensitive contexts. The fsutil behavior set SymlinkEvaluation command allows fine-grained control over whether local or remote symlinks are followed, a critical setting on file servers.

Symlinks only work on NTFS or ReFS formatted drives. They are not supported on older FAT32 or exFAT file systems. windows symlink