This report details the configuration review and modifications applied via the . The objective was to harden system security, enforce user environment standardization, and restrict unauthorized system changes. All changes were implemented under the scope of Local Computer Policy due to the absence of an Active Directory domain environment.
To access the Local Policy Group Editor, follow these steps:
| Policy Path | Setting | New State | Justification | | :--- | :--- | :--- | :--- | | System\Removable Storage Access\All Removable Storage classes: Deny all access | | Enabled | Prevent data exfiltration via USB drives. | | System\Ctrl+Alt+Del Options\Remove Lock Computer | Not Configured ➜ Disabled | Disabled | Ensure "Lock" button remains visible (reversed previous disable). | | Windows Components\Windows Update\Configure Automatic Updates | Enabled | Enabled (Auto download & notify for install) | Maintain patch compliance. |
The Local Group Policy Editor is much safer than the . In the Registry, one wrong character can crash your system. In the Group Policy Editor, settings are presented in plain English with clear descriptions. However, you should still exercise caution:
These settings are specific to the user currently logged in. They govern things like the desktop wallpaper, taskbar behavior, and access to specific folders or apps. Common Use Cases: Why Use GPedit?
The sheer number of settings can be overwhelming, but here are some of the most practical ways the Local Group Policy Editor is used: