0% found this document useful (0 votes)
21 views5 pages

What Are Practical Projects For Implementing Zero Trust

Uploaded by

Daniel L
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
21 views5 pages

What Are Practical Projects For Implementing Zero Trust

Uploaded by

Daniel L
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

22/07/2022, 17:40 Gartner Reprint

Licensed for Distribution

What Are Practical Projects for Implementing Zero


Trust?
FOUNDATIONAL Refreshed 17 February 2022, Published 17 March 2021 - ID G00744839 - 4 min read

By John Watts, Neil MacDonald

Vendor marketing abuses the overloaded term “zero trust” to imply improved security. Security
and risk management leaders must move beyond the hype and implement two key projects to
reduce risk with least privileged access and adaptive security.

Quick Answer
What are practical projects for implementing zero trust?

■ “Zero trust” is an overused, widely misunderstood term used by many organizations.

■ The majority of organizations interested in zero trust are in the planning or strategy phase.

■ Organizations looking to move to practical implementation should focus on two primary


projects: user-to-application segmentation (ZTNA) and workload-to-workload segmentation
(identity-based segmentation).

More Detail
Gartner observes, based on client inquiry, that most organizations are in the strategy phase for
zero trust. However, “zero trust” is an overloaded term used by vendor marketing as a shorthand
for “new and improved” security. Zero trust is seen by many security leaders as a silver bullet, but
it does not cover all aspects of threats and security, such as phishing and sensitive data
protection. A complete zero trust security posture may never be fully achieved, due to limitations
such as legacy applications, organizational resistance, complexity of managing granular security
controls and other factors.

However, the term “zero trust” has value as a shorthand way of describing a paradigm where
implicit trust is removed from all of our computing infrastructure. Implicit trust is replaced with
explicitly calculated, real-time adaptive trust levels for just in time, just enough access to
enterprise resources.

https://www.gartner.com/doc/reprints?id=1-273JRYQI&ct=210804&st=sb%E2%80%A9 1/5
22/07/2022, 17:40 Gartner Reprint

There are two primary projects that organizations should focus on when looking to implement
zero trust (see Figure 1).

Figure 1. What Are Practical Projects for Implementing Zero Trust?

Most zero trust strategies start with networking-related initiatives due to the excessive implicit
trust in traditional network security models. Zero trust networking initiatives break into two areas:

1. Front-end network access focused on user-to-application segmentation (ZTNA)

2. Back-end network access focused on workload-to-workload segmentation (identity-based


segmentation)

Before starting these projects, a solid identity foundation must be in place.

Federated Identity Systems


Zero trust requires a secure, common federated identity management system. For large
organizations, there is unlikely to be a single source of truth for user and machine identity. Security
and risk management leaders should:

■ Document the existing federation relationships.

■ Identify the source of truth for user identities, including the process for third-party identities.

■ Define polices where stronger authentication is required (MFA, CAC card, PIN, etc.).

■ Develop a standardized way to determine if a given device is managed or unmanaged (e.g.,


certificates).

■ For workloads, define how machine and application identities are established.

■ Architect for managing machine identities at scale for container and Kubernetes environments.

https://www.gartner.com/doc/reprints?id=1-273JRYQI&ct=210804&st=sb%E2%80%A9 2/5
22/07/2022, 17:40 Gartner Reprint

Adaptive Access Controls


Adaptive access applies context such as device security posture and location for more granular
resource access control. Security and risk management leaders should:

■ Require stronger authentication for all remote access and SaaS application access.

■ Make context-based access mandatory for all SaaS applications (e.g., cloud SSO or CASB).

■ Integrate device security posture assessment into access control decisions.

■ Integrate with the federated identity systems to control access on-premises and in the cloud.

After a solid foundation is in place, focus on these projects and critical questions:

User-to-Application Segmentation (ZTNA)


ZTNA reduces excessive implicit trust for access to resources, primarily from remote locations, by
employees, contractors and other third parties. Start with a pilot of a ZTNA product. Plan rollouts
to the organization by prioritizing contractor and third-party access. Then conduct a proof of
concept (POC) to test applications with the ZTNA product, and use observation mode to learn
patterns of access by user and role to build policies from there.

Security and risk management leaders should:

■ Inventory all instances of VPN that allow access to the network. Replace these over time.

■ Identify applications and servers in the DMZ with named sets of users. Replace these over time.

■ Make unmanaged device access a mandatory part of the ZTNA architecture.

■ Test ZTNA solutions for legacy application compatibility.

■ Define policies for combining user attributes and services to enforce who has access to what.

■ Determine if an on-premises policy management and policy controller is needed.

Workload-to-Workload Segmentation (Identity-Based Segmentation)


Identity-based segmentation reduces excessive implicit trust by allowing organizations to move
individual workloads to a default deny model for communication, rather than an implicit allow
model. Implement network segmentation to reduce excessive trust zones, starting with high level
segmentation of campus and server networks. Like ZTNA, observation mode will be necessary to
learn the patterns of communications by workloads and applications in order to build policies.
Then, evaluate machine identity management techniques such as SPIFFE, OpenID Connect and
SAML across workloads to support granular segmentation. When starting an identity-based
strategy, start with a small collection of critical assets to build initial implementations and expand
from there.

https://www.gartner.com/doc/reprints?id=1-273JRYQI&ct=210804&st=sb%E2%80%A9 3/5
22/07/2022, 17:40 Gartner Reprint

Security and risk management leaders should:

■ Develop a strategy to address heterogeneous workloads spanning on-premises, hybrid, virtual


and container environments.

■ Identify workloads that require segmentation using means other than agents, such as network-
based or API-based orchestration.

Recommended by the Authors


Market Guide for Zero Trust Network Access

Three Styles of Identity-Based Segmentation

Market Guide for Cloud Workload Protection Platforms

Market Guide for Network Access Control

IAM Leaders’ Guide to Access Management

Designing Security for Remote-Work-First Enterprises

Quick Answer: Cost Effectively Scaling Secure Access While Preparing for a Remote Workforce

© 2022 Gartner, Inc. and/or its affiliates. All rights reserved. Gartner is a registered trademark of Gartner, Inc.
and its affiliates. This publication may not be reproduced or distributed in any form without Gartner's prior
written permission. It consists of the opinions of Gartner's research organization, which should not be construed
as statements of fact. While the information contained in this publication has been obtained from sources
believed to be reliable, Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such
information. Although Gartner research may address legal and financial issues, Gartner does not provide legal or
investment advice and its research should not be construed or used as such. Your access and use of this
publication are governed by Gartner’s Usage Policy. Gartner prides itself on its reputation for independence and
objectivity. Its research is produced independently by its research organization without input or influence from
any third party. For further information, see "Guiding Principles on Independence and Objectivity."

https://www.gartner.com/doc/reprints?id=1-273JRYQI&ct=210804&st=sb%E2%80%A9 4/5
22/07/2022, 17:40 Gartner Reprint

About Careers Newsroom Policies Site Index IT Glossary Gartner Blog Network Contact Send
Feedback

© 2022 Gartner, Inc. and/or its Affiliates. All Rights Reserved.

https://www.gartner.com/doc/reprints?id=1-273JRYQI&ct=210804&st=sb%E2%80%A9 5/5

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy