<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Policy Validation on Ivan Versluis — Networknet</title><link>https://networknet.nl/tags/policy-validation/</link><description>Recent content in Policy Validation on Ivan Versluis — Networknet</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 04 Nov 2026 16:22:49 +0100</lastBuildDate><atom:link href="https://networknet.nl/tags/policy-validation/index.xml" rel="self" type="application/rss+xml"/><item><title>Listen on TCP/443 with netcat</title><link>https://networknet.nl/snippets/nc-listener-ztna/</link><pubDate>Wed, 04 Nov 2026 13:00:00 +0100</pubDate><guid>https://networknet.nl/snippets/nc-listener-ztna/</guid><description>&lt;p>During ZTNA testing, I used a temporary &lt;strong>netcat&lt;/strong> listener on a Linux test host to check whether a remote connection could reach TCP/443.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" class="chroma">&lt;code class="language-sh" data-lang="sh">&lt;span class="line">&lt;span class="cl">nc -lvnp &lt;span class="m">443&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>When the connection appeared in the listener, I knew the TCP session had reached the test port. I then checked the ZTNA policy logs to confirm which access rule matched. Netcat alone cannot identify the policy that allowed the traffic.&lt;/p>
&lt;p>This was a TCP connectivity check, &lt;strong>not an HTTPS/TLS test&lt;/strong>. Binding to port 443 may require elevated permissions on Linux, and netcat syntax can vary by implementation.&lt;/p></description></item></channel></rss>