{"id":162432,"date":"2022-06-01T06:00:02","date_gmt":"2022-06-01T13:00:02","guid":{"rendered":"https:\/\/www.paloaltonetworks.com\/blog\/?p=162432"},"modified":"2022-06-15T16:24:01","modified_gmt":"2022-06-15T23:24:01","slug":"security-inspection-problem","status":"publish","type":"post","link":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/2022\/06\/security-inspection-problem\/","title":{"rendered":"ZTNA 1.0\u2019s Security Inspection Problem"},"content":{"rendered":"

<\/a>ZTNA 2.0 Provides Deep and Ongoing Security Inspection<\/h1>\n

This is part 3 of \u201c<\/em>ZTNA Straight Talk,<\/em><\/a>\u201d a 5-part series where we take a closer look at the five tenets of ZTNA 2.0, the new standard for securing access.<\/em><\/p>\n

The rapid move to hybrid work, brought about by the pandemic, drove the adoption of ZTNA<\/a> as a new way to securely connect users with the applications that they need to get work done from anywhere. However, as I discussed previously<\/a>, initial implementations of ZTNA have been deeply flawed.<\/p>\n

In my previous post, I talked about how the ZTNA 1.0 concept of \u201callow and ignore<\/a>\u201d is a recipe for disaster. This concept maintains that once a connection is established, all user and device behavior for that session is trusted implicitly and goes unchecked. Unfortunately, there is another limitation with the \u201callow and ignore\u201d approach \u2013 it prohibits security inspection of the traffic.<\/p>\n

<\/a>ZTNA 1.0 Lacks Security Inspection<\/h2>\n

Because the \u201callow and ignore\u201d model lacks security inspection, there is no means for a ZTNA 1 .0 solution to detect any malicious or other compromised traffic and respond accordingly. This means there are no in-line controls to expose and inspect the traffic payload and determine if anything malicious or unknown is being introduced. Likewise, there is no mechanism to take action by blocking traffic, terminating the session, or reporting anything unusual, at the very least.<\/p>\n

This turns ZTNA 1.0 into a \u201csecurity-through-obscurity-only\u201d approach, which further puts organizations, their users, apps and data at risk of malware, compromised devices and malicious traffic.<\/p>\n

<\/a>ZTNA 2.0 Includes Continuous Security Inspection<\/h2>\n
\n