NTFS - Revision history

Tom: /* Integrity */

2023-03-15T00:39:43Z

‎Integrity

Tom: /* Streams */

2023-03-15T00:38:25Z

‎Streams

Tom: /* Integrity */

2023-03-15T00:35:57Z

‎Integrity

Tom: /* Security */

2023-03-15T00:33:40Z

‎Security

Tom: /* PowerShell */

2023-03-14T22:04:15Z

‎PowerShell

Tom: /* PowerShell */

2023-03-14T22:00:03Z

‎PowerShell

Tom: /* PowerShell */

2023-03-14T21:58:30Z

‎PowerShell

Tom: /* PowerShell */

2023-03-14T21:30:22Z

‎PowerShell

Tom: /* Streams */

2023-03-14T20:23:16Z

‎Streams

Tom: /* Streams */

2023-03-14T20:22:19Z

‎Streams

@@ Line 15: / Line 15: @@
 ===Integrity===
-The NTFS file system objects and registry keys are not automatically labeled when they are created. These objects do not have mandatory labels after upgrade from a previous version of Windows to Windows Vista. Files on non-NTFS file systems (CDFS or FAT32) that do not have security descriptors are not securable objects and do not have an integrity level. Every security descriptor must have an implicit mandatory label. Processes with a subject integrity level at or above medium create files and registry keys without an explicit label. As a consequence, the file system and registry objects that are created by a high or system integrity level process have an implicit medium label.<ref>Windows Integrity Mechanism Design (2007-07-05) Out of data, but still the best explanation https://learn.microsoft.com/en-us/previous-versions/dotnet/articles/bb625963(v=msdn.10)</ref>
+The NTFS file system objects and registry keys are not automatically labeled when they are created. These objects do not have mandatory labels after upgrade from a previous version of Windows to Windows Vista. Files on non-NTFS file systems (CDFS or FAT32) that do not have security descriptors are not securable objects and do not have an integrity level. Every security descriptor must have an implicit mandatory label. Processes with a subject integrity level at or above medium create files and registry keys without an explicit label. As a consequence, the file system and registry objects that are created by a high or system integrity level process have an implicit medium label.<ref>Windows Integrity Mechanism Design (2007-07-05) Out of date, but still the best explanation https://learn.microsoft.com/en-us/previous-versions/dotnet/articles/bb625963(v=msdn.10)</ref>
 ===PowerShell===

@@ Line 6: / Line 6: @@
 ==Streams==
-NTFS has enabled multiple streams from an early release, but the Windows File Explorer has never managed any stream but the default stream called ":$DATA".  All of the others are consider to be "Alternate Data Streams".
+NTFS has enabled multiple streams from an early release, but the Windows File Explorer has never managed any stream but the default stream called ":$DATA".  All of the others are considered to be "Alternate Data Streams".
 * [https://blog.ironmansoftware.com/daily-powershell/powershell-alternate-data-streams/ Read Alternate Data Streams on Windows with PowerShell]

@@ Line 15: / Line 15: @@
 ===Integrity===
-The NTFS file system objects and registry keys are not automatically labeled when they are created. These objects do not have mandatory labels after upgrade from a previous version of Windows to Windows Vista. Files on non-NTFS file systems (CDFS or FAT32) that do not have security descriptors are not securable objects and do not have an integrity level. Every security descriptor must have an implicit mandatory label. Processes with a subject integrity level at or above medium create files and registry keys without an explicit label. As a consequence, the file system and registry objects that are created by a high or system integrity level process have an implicit medium label.
+The NTFS file system objects and registry keys are not automatically labeled when they are created. These objects do not have mandatory labels after upgrade from a previous version of Windows to Windows Vista. Files on non-NTFS file systems (CDFS or FAT32) that do not have security descriptors are not securable objects and do not have an integrity level. Every security descriptor must have an implicit mandatory label. Processes with a subject integrity level at or above medium create files and registry keys without an explicit label. As a consequence, the file system and registry objects that are created by a high or system integrity level process have an implicit medium label.<ref>Windows Integrity Mechanism Design (2007-07-05) Out of data, but still the best explanation https://learn.microsoft.com/en-us/previous-versions/dotnet/articles/bb625963(v=msdn.10)</ref>
 ===PowerShell===

@@ Line 12: / Line 12: @@
 ==Security==
 [https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/icacls icacls] Displays or modifies discretionary access control lists (DACLs) on specified files, and applies stored DACLs to files in specified directories.
 ===PowerShell===

@@ Line 19: / Line 19: @@
 * [https://woshub.com/manage-ntfs-permissions-powershell/ How to Manage NTFS Permissions with PowerShell?]
 * [https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/unblock-file?view=powershell-7.3 Unblock-File with PowerShell] Internally, the Unblock-File cmdlet removes the Zone.Identifier alternate data stream, which has a ZoneId=3 to indicate that it was downloaded from the internet.
 ==References==

← Older revision		Revision as of 21:30, 14 March 2023
Line 18:		Line 18:

	* [https://woshub.com/manage-ntfs-permissions-powershell/ How to Manage NTFS Permissions with PowerShell?]		* [https://woshub.com/manage-ntfs-permissions-powershell/ How to Manage NTFS Permissions with PowerShell?]
		+	* [https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/unblock-file?view=powershell-7.3 Unblock-File with PowerShell]

	==References==		==References==