<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Applocker on Aperture Zone</title>
    <link>https://aperturezone.com/tags/applocker/</link>
    <description>Recent content in Applocker on Aperture Zone</description>
    <image>
      <url>https://aperturezone.com/logo.webp</url>
      <link>https://aperturezone.com/logo.webp</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>fr-fr</language>
    <lastBuildDate>Thu, 18 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aperturezone.com/tags/applocker/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>GPO — Block PowerShell and CMD for non-admins</title>
      <link>https://aperturezone.com/gpo/block-console/</link>
      <pubDate>Thu, 18 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/gpo/block-console/</guid>
      <description>&lt;h2 id=&#34;the-problem&#34;&gt;The Problem&lt;/h2&gt;
&lt;p&gt;A standard user has no legitimate reason to open a PowerShell console or a command prompt. Allowing them access is like leaving a door open: an attacker who gains a user session can use PowerShell as a tool for reconnaissance, lateral movement, or execution. Closing this backdoor reduces the attack surface.&lt;/p&gt;
&lt;p&gt;Let’s be clear about the scope: &lt;strong&gt;this GPO does not protect against ransomware&lt;/strong&gt;. A modern crypto-locker includes its own execution engine and does not rely on &lt;code&gt;powershell.exe&lt;/code&gt; or &lt;code&gt;cmd.exe&lt;/code&gt; present on the machine. Blocking the console is a hardening measure (reducing the attack surface, defense-in-depth), not a bulwark against malware. True ransomware protection involves removing local admin rights, comprehensive application whitelisting, and offline backups.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
