<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reverse Proxy on Mexicali IT</title><link>https://mxlit.com/technologies/reverse-proxy/</link><description>Recent content in Reverse Proxy on Mexicali IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 03 Aug 2026 22:30:00 -0700</lastBuildDate><atom:link href="https://mxlit.com/technologies/reverse-proxy/index.xml" rel="self" type="application/rss+xml"/><item><title>ADSelf Service: Configuring a Reverse Proxy with AD360</title><link>https://mxlit.com/kb-00098/</link><pubDate>Mon, 03 Aug 2026 22:30:00 -0700</pubDate><guid>https://mxlit.com/kb-00098/</guid><description>&lt;p&gt;When deploying critical tools like ManageEngine&amp;rsquo;s ADSelfService Plus, infrastructure security must be the top priority. Exposing the ADSelfService server directly to the internet is generally poor practice, as it significantly increases the attack surface of your internal network.&lt;/p&gt;&#10;&lt;p&gt;The best way to secure it is by placing a Reverse Proxy inside a Demilitarized Zone (DMZ). This way, internet traffic hits the isolated proxy first, and your firewall only allows this proxy to communicate specifically with the internal ADSelfService server on the required port, creating an essential protective barrier.&lt;/p&gt;</description></item></channel></rss>