Loading...

Security in the age of the
porous perimeter

A zero trust cybersecurity posture provides the opportunity to create a more robust and resilient security, simplify security management, improve end-user experience, and enable modern IT practices.

Conventional castle-and-moat cybersecurity models, which rely on secure network perimeters and virtual private network-based employee and third-party remote access, are proving to be no match for evolving cyberthreats, particularly as business models and workforce dynamics evolve. For instance, the move to cloud and hybrid IT environments—along with increasing numbers of cloud-based systems, remote workers, and connected devices—are constantly expanding and dissolving the network perimeter. The anticipated growth of smart devices, 5G, edge computing, and artificial intelligence promises to create even more data, connected nodes, and expanded attack surfaces.
With cloud now mainstream, businesses managing services across multiple cloud providers are responsible for securing these technologies. As an enterprise more frequently relies on third-party vendors to host and manage data, infrastructure, and other services, the attack surface expands. In one study, 59% of companies surveyed had experienced a data breach due to a vendor or other third party;1 another study concluded that multiparty security incidents result in 13 times the financial losses of single-party events.2
In fact, while perimeter-based security assumes the trustworthiness of users and devices connected to the organization’s network, stolen credentials cause more than a quarter of security breaches.3
Consider the case of an employee who logs in regularly on weekdays from her home and occasionally on weekends from a coffee shop. When her username and password are used on a Saturday night from somewhere in Eastern Europe, traditional approaches might allow the connection. But because a zero trust architecture is more risk-driven and context-aware, it recognizes the inconsistency, automatically denies the access request, and raises an alert. Automated response capabilities could be triggered to temporarily disable the user’s account, given the likelihood that its credentials have been compromised.
Proper design and engineering of zero trust architectures can result in simple, modular environments and straightforward user access control and management. Streamlining the security stack can eliminate considerable management headaches, significantly reduce operational overhead, and help scale to tens of thousands of users. Similarly, onboarding employees, contractors, cloud service providers, and other vendors can become more efficient, flexible, responsive, and secure.
Carefully designed zero trust architectures that embed automation and orchestration capabilities can amplify and work in concert with other automated IT practices such as DevSecOps and NoOps. The use of APIs across the technology ecosystem can facilitate system management in a zero trust manner by providing a consistent control layer. And cloud-based services enable organizations to leverage the substantial ongoing security investments of cloud vendors.
A final key element of the zero trust approach is microsegmenting networks, data, applications, workloads, and other resources into individual, manageable units to contain breaches and wrap security controls at the lowest level possible. By limiting access based on the principle of least privilege, a minimum set of users, applications, and devices has access to data and applications.
By removing the assumption of trust from the security architecture and authenticating every action, user, and device, zero trust helps enable a more robust and resilient security posture. The organizational benefits are complemented by a considerable end-user perk: seamless access to the tools and data needed to work efficiently.
As the benefits of zero trust continue to pile up, enterprises are catching on. The global zero trust market is expected to grow to US$38.6 billion by 2024, a 20% increase from 2019.4
Beefing up basic cyber hygiene
The zero trust mindset shift brings with it a set of design principles that guide security architecture development and build on existing security investments and processes. To enforce access control, companies must have situational awareness of their data and assets; companies that lag on basic cyber hygiene principles and practices may be challenged to realize the full benefits of zero trust. Fundamentals include:
  • Data discovery and classification. Data governance, inventory, classification, and tagging are critical. To create the appropriate trust zones and access controls, organizations need to understand their data, the criticality of that data, where it resides, how it is classified and tagged, and the people and applications that should have access to it.
  • Asset discovery and attack-surface management. Many organizations lack a real-time, updated inventory of all IT resources—including cloud resources, IP addresses, subdomains, application mapping, code repositories, social media accounts, and other external or internet-facing assets—and therefore can’t identify security issues across the complete attack surface. To facilitate risk-based policy decisions surrounding their assets, it’s critical for organizations to understand the enterprise IT environment.
  • Configuration and patch management. Without the ability to efficiently manage and document baseline configurations of key technology systems, deploy appropriate patches, test patched systems, and document new configurations, companies cannot easily identify changes and control risks to these systems. Malicious actors can exploit any vulnerabilities to gain a foothold within an organization.
  • Identity and access management. To ensure that access to technology resources is granted to the proper people, devices, and other assets, enterprises need to standardize and automate their identity life cycle management processes. They can extend their operations beyond traditional boundaries while protecting critical resources and maintaining an efficient user experience by moving the identity stack to the cloud, consuming identity-as-a-service, or implementing such advanced authentication methods as physical biometrics, behavioral monitoring, and conditional access.
  • Third-party risk management. To fully understand their entire risk surface, organizations need greater visibility into cyber risks related to their supply chains and ecosystem partners, including suppliers to third-party vendors.
  • Logging and monitoring. To identify potentially malicious incidents and issues, security teams need automated logging and monitoring systems with advanced AI and machine learning capabilities to help simplify the process of tracking, analyzing, and correlating data from volumes of detailed logs as well as alerts generated by internal and external systems, security controls, networks, and processes.
Engineered security automation and orchestration
Many security operations center (SOC) teams are challenged to keep pace with the volume of information generated by their technology and security controls. They must monitor, manage, and act upon continuous alerts and streams of data generated by fragmented security architectures and disparate, disconnected tools.
The number and nature of risk factors interrogated to support zero trust authentication and authorization—users, devices, or credentials and contextual data points such as location, privileges, application requirements, and behaviors—warrants a more automated approach to monitoring, decision-making, enforcement, and auditing.
Many existing security technologies can be leveraged to build out zero trust architectures. To ensure more efficient automation and orchestration, zero trust adopters should rationalize the security stack and eliminate unnecessary and duplicative technologies or those that contribute to data overload, delay detection and response, and complicate system maintenance and management.
With a simplified security stack, existing systems and tools can be integrated via API connections to a security orchestration, automation, and response (SOAR) platform that can automate workflows and repetitive and manual tasks, and coordinate the flow of data and alerts to the SOC. SOAR platforms help add context to triggered events and can auto-remediate identified and known vulnerabilities, enabling staff to keep pace with incoming alerts and notifications, improving operational efficiency and accuracy, and decreasing response time.
“Migrating to zero trust architectures can seem like a heavy lift, especially in large enterprises saddled with legacy technologies and a lot of technical debt,” says a senior technology leader at a large financial institution. “You have to break it into manageable chunks where you can identify a discrete win, such as deploying pervasive endpoint segmentation, and understand that win as part of your larger story of operationalizing zero trust.”
Rethinking the role of the cyber organization
Zero trust represents a philosophical shift in how security is managed and likely requires cultural change across the enterprise. Creating a culture in which all key stakeholders understand their vested interest in securing the enterprise can help build confidence in zero trust.
For example, zero trust could significantly change the day-to-day activities of the cyber workforce. To design and continually refine and evolve the zero trust architecture, enterprises likely will need more cyber engineering skills. And the role of the SOC will likely evolve as the security architecture takes command of manual, day-to-day tasks and processes, replacing them with more accurate machine-driven decision-making and faster response time and freeing SOC staff to focus on critical security issues and higher-risk incidents that require human analysis. Organizational structures will likely need to be reconfigured to account for new automated workflows, and it will be important to retrain security analysts to focus on strategic activities instead of tedious daily tasks.
In addition, to embed zero trust principles into every business initiative from inception, organizations will likely need more collaboration and integration between security teams and the lines of businesses they support. Business-function system owners likely will need to become more engaged in security planning. For example, to provide the security team with a better and deeper understanding of appropriate system behavior and access requirements, business partners can help identify who accesses and uses applications—and how. Business areas may need to become more intentional about system access, including limiting access privileges and making them more granular.
The way forward
The zero trust approach is not a product, solution, or platform—it’s a philosophical shift in the way enterprises think about security. The process of migrating to an effective zero trust security architecture tends to be a marathon rather than a sprint, with organizations not only tackling foundational cybersecurity issues and embracing security automation and orchestration but preparing for the organizational and cultural changes that accompany such mindset shifts. To build confidence in zero trust, organizations will need to engage stakeholders ranging from cyber and IT to business area system owners and application end users. An iterative and incremental approach aligned to business objectives can help demonstrate the value of zero trust and enhance stakeholder confidence and acceptance.
The anticipated growth of smart devices, 5G, edge computing, and artificial intelligence promises to create even more data, connected nodes, and expanded attack surfaces.
“The anticipated growth of smart devices, 5G, edge computing, and artificial intelligence promises to create even more data, connected nodes, and expanded attack surfaces.”

Lessons from the front lines

Read insights from thought leaders and success stories from leading organizations.

Zero trust mindset enables digital growth

Takeda

Zero trust mindset enables digital growth

Like many global pharmaceutical companies, Takeda Pharmaceuticals supports better patient outcomes by innovating and collaborating across a diverse group of internal and external stakeholders—including, in its case, more than 52,000 employees and thousands of research partners, logistics partners, and other third-party service providers as well as patients, physicians, and other health care providers.

Takeda

Zero trust mindset enables digital growth

Like many global pharmaceutical companies, Takeda Pharmaceuticals supports better patient outcomes by innovating and collaborating across a diverse group of internal and external stakeholders—including, in its case, more than 52,000 employees and thousands of research partners, logistics partners, and other third-party service providers as well as patients, physicians, and other health care providers. The ongoing need to extend access to applications and systems to its broad external ecosystem spurred the Tokyo-based pharmaceutical giant to begin a journey toward a zero trust-based security architecture.

“We realized that the demarcation between internal and external was no longer relevant or scalable,” says chief information security officer (CISO) Mike Towers. “The zero trust mindset—assuming that every request to connect is coming from an unknown access device on the internet that can’t be predicted or controlled—is a much better way to move forward.”5

Previously, access to an internal application would require granting access to the Takeda network, which inherently enabled access to a number of additional, unrelated services. “We could have tried to manually manage and restrict this additional system access, but, invariably, things will be missed over time,” says Scott Sheahen, global head of information risk management. “With the zero trust approach, we eliminate superfluous system access and thereby reduce the avenues that could be exploited in a future cyberattack. Now we have granular, policy-based controls so that people have access only to needed resources.”

This approach provides users with a more efficient way of navigating Takeda’s complex technology environment—a mix of cloud-based applications and services and legacy systems residing on internal servers and in data centers—and eliminates the difficulty of accessing systems via multiple firewalls and VPNs. The transition to zero trust, well underway before COVID-19 struck, helped the company securely manage the sudden shift of its global workforce to a work-from-home model. “Our China workforce, the first affected by the pandemic, had less experience and comfort with work-from-home, so it was really important for us to get it right,” Towers says. “By having shifted to zero trust-based access, we were able to aggressively and quickly move China to the work-from-home model.”

Setting clear expectations with business partners is critical during the transition, says Thomas Likas, global head of security architecture and engineering. He recommends that security and IT organizations planning a zero trust migration engage with business partners from the beginning of the journey. “The business—not IT—has the best understanding of how people access and use their applications,” he says. “In the zero trust world, the business will need to determine who should have access to their systems and data.”

Indeed, Likas continues, “this knowledge needs to be baked into the access model from the very beginning. To business partners, this might seem like a lot of work, but as a bonus, the organization gets a solid understanding of their application landscape.”

Towers believes that once leaders understand the numerous benefits, most companies will inevitably adopt the zero trust mindset. “Frankly,” he says, “I don't think that businesses can digitally or technologically scale in any other way.”

Zero trust secures the “new perimeter”

Halliburton

Zero trust secures the “new perimeter”

A zero trust approach is helping Halliburton, a global provider of products and services to the energy industry, meet its strategic business goals and objectives.

Halliburton

Zero trust secures the “new perimeter”

A zero trust approach is helping Halliburton, a global provider of products and services to the energy industry, meet its strategic business goals and objectives. Several years ago, as part of a drive to be more operationally efficient, the company began adopting cloud, mobile, and Industrial Internet of Things platforms to reduce costs and improve productivity. At the same time, Halliburton’s vendors and suppliers began pushing their products and services to the cloud. “With the dispersion of our computing resources from the data center to the internet, we realized that our traditional network perimeters were dissolving,” says Mary Rose Martinez, CISO and senior director for IT architecture.6 “This impelled us to develop a zero trust strategy.”

Halliburton’s zero trust approach revolves around securing people, network connections, and data. “We are moving toward a reality where it doesn’t really matter if employees are on the network or not,” Martinez says. “The new perimeter is identity, whether user identity, endpoint device identity, or service identity.”

When Halliburton began its zero trust journey about two years ago, it focused first on securing mobile devices through multifactor authentication—using identity credentials, an authenticator, and registered devices. Soon after, the company migrated to cloud-based identity providers to further secure its people. Over time, the number of applications accessible without using a VPN continues to grow. A longtime adopter of the principle of least privilege, data encryption, and other data controls, the company is also working to enhance the classification and protection of unstructured data.

The more granular security controls that are part of Halliburton’s zero trust approach have created a more disciplined security posture. Because it controls user devices and endpoints, the company can push policies to any device via the internet. And because VPN access isn’t required for the zero trust-enabled applications, employees have a considerably improved user experience.

Martinez is quick to emphasize that zero trust is not only a technology initiative—it is also a people initiative. For example, whether Halliburton employees are on the company network or the internet, in the office or at home, they receive a verification prompt before accessing applications protected by multifactor authentication. This workflow change required education and awareness. And it is incumbent on users to guard their credentials and devices. “Raising security awareness has to be part and parcel of the zero trust approach,” Martinez says. “An ongoing education program that includes increasingly sophisticated phishing simulations can help people become more aware.”

Halliburton’s adoption of zero trust is an ongoing journey, with many components that are constantly moving and changing shape. “Because of the fluid nature of technological advancements, the end state will probably always be a moving target,” Martinez says. “But we’ve laid a foundation that’s both solid and adaptable, and upon which we can continue to build over time.”

Lessons from the front lines

Read insights from thought leaders and success stories from leading organizations.

My take
John Kindervag, field CTO, Palo Alto Networks
John Kindervag, field CTO, Palo Alto Networks
“The hallmark of zero trust is simplicity.”
When I worked as a security analyst, I became fascinated by how people and businesses anthropomorphized their digital environments by applying the concept of trust to computing—that somehow a device could be trusted and that it cared that it was trusted. Back then, many CISOs and CIOs adhered to the idea—and many still do—that what’s inside the corporate firewall can be trusted. This idea of inside versus outside became a variable that was used to determine security policy, with many organizations operating under the adage “trust, but verify.” In the trust-but-verify model, trust is the default. When identity is verified, trust is assumed and access is granted.
But trust applies only to people—not digital environments. Identity credentials can be stolen, networks can be hacked, and insiders with bad intent are often in positions of trust. This means it’s impossible to know with certainty that the originator of network traffic can truly be trusted: An asserted identity is only an assertion, not an actual person.
In response to what CISOs and CIOs told me about their cybersecurity strategies, I created the concept of zero trust, which is framed around the principle that no network user, packet, interface, or device—whether internal or external to the network—should be trusted. Some people mistakenly think zero trust is about making a system trusted, but it really involves eliminating the concept of trust from cybersecurity strategy. By doing this, every user, packet, network interface, and device is granted the same default trust level: zero.
Zero trust should be thought of as a strategy or framework. It requires companies to rethink their philosophy and approach to trusted network users and devices. Zero trust is not a product, although zero trust-based security infrastructures can be implemented by using many different products. Nor does zero trust require organizations to rip and replace existing security infrastructure—rather, it leverages existing technology to support the zero trust mindset, with new tools added as needed.
The hallmark of zero trust is simplicity. When every user, packet, network interface, and device is untrusted, protecting assets becomes simple. To reduce the complexity of cybersecurity environments, organizations can prioritize security technologies and tools that support simplicity by automating repetitive and manual tasks, integrating and managing multiple security tools and systems, and autoremediating known vulnerabilities.
Zero trust is a journey best taken one step at a time. I recommend that organizations begin by prioritizing the smallest possible protect surfaces—a single data set, asset, application, or service—depending on the level of sensitivity or business criticality. Then, they can create a microperimeter around each protect surface and granularly control the traffic allowed into the perimeter.
I encourage security teams to learn and practice on less sensitive protect surfaces, moving to protect increasingly more sensitive or valuable protect surfaces as they fine-tune their approaches and their confidence increases. Over time and with lots of practice, they’ll be ready to migrate their most critical assets to the zero trust environment. Finally, when high-value assets are protected, teams can focus on less important assets. And by continuing to maintain a zero trust mindset, organizations can protect themselves even as security technologies and tools evolve.

Learn more

Download the trend to explore more insights, including the “Executive perspectives” where we illuminate the strategy, finance, and risk implications of each trend, and find thought-provoking “Are you ready?” questions to navigate the future boldly. And check out these links for related content on this trend:

Next Trend:

Authors

Key contact

Our insights can help you take advantage of emerging trends. If you’re looking for fresh ideas to address your challenges, let’s talk.

Endnotes

Endnotes

5.
  
Mike Towers (CISO, Takeda), Scott Sheahen (global head of information risk management, Takeda), and Thomas Likas (global head of security architecture and engineering, Takeda), phone interview with the authors, September 22, 2020.
6.  
Mary Rose Martinez (CISO and senior director for IT architecture, Halliburton), phone interview with the authors, October 2, 2020.