<?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>Rdp on Aperture Zone</title>
    <link>https://aperturezone.com/tags/rdp/</link>
    <description>Recent content in Rdp 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>Fri, 01 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aperturezone.com/tags/rdp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>GPO - RDP on custom port</title>
      <link>https://aperturezone.com/gpo/rdp-custom-port/</link>
      <pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/gpo/rdp-custom-port/</guid>
      <description>&lt;p&gt;Windows Remote Desktop listens on port 3389. As is well known, this is the first port that automated tools scan when looking for exposed access points. On an internal network isolated behind proper NAT, the risk is limited. But as soon as a machine is accessible from the outside—or simply if you want an extra layer of security with minimal effort—moving RDP to a non-standard port is a simple and effective measure.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
