<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>zero-trust on Digital Archive Systems Tech Blog</title><link>https://tech.ldas.jp/en/tags/zero-trust/</link><description>Recent content in zero-trust on Digital Archive Systems Tech Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 07 Apr 2026 11:00:00 +0900</lastBuildDate><atom:link href="https://tech.ldas.jp/en/tags/zero-trust/index.xml" rel="self" type="application/rss+xml"/><item><title>Securing SSH with Cloudflare Zero Trust</title><link>https://tech.ldas.jp/en/posts/cloudflare-zero-trust-ssh/</link><pubDate>Tue, 07 Apr 2026 11:00:00 +0900</pubDate><guid>https://tech.ldas.jp/en/posts/cloudflare-zero-trust-ssh/</guid><description>&lt;h1 id="securing-ssh-with-cloudflare-zero-trust">Securing SSH with Cloudflare Zero Trust&lt;/h1>
&lt;h2 id="background">Background&lt;/h2>
&lt;p>To access a server via SSH, you typically need to expose port 22 to the internet. However, an open SSH port is a constant target for attacks.&lt;/p>
&lt;p>With Cloudflare Zero Trust, you can build an environment where only authenticated users can connect via SSH, &lt;strong>while keeping the SSH port completely closed&lt;/strong>.&lt;/p>
&lt;h2 id="what-is-zero-trust">What Is Zero Trust?&lt;/h2>
&lt;p>Traditional security models relied on the assumption that &amp;ldquo;anything inside the corporate network is trusted.&amp;rdquo; Zero Trust discards this assumption and instead &lt;strong>verifies every access request&lt;/strong>.&lt;/p></description></item></channel></rss>