PUBlished on
December 17, 2021
updated on
November 5, 2025

Extending Zero Trust to Your SaaS Applications

GLENN CHISHOLM

The zero trust odyssey

It’s been over a decade since former Forrester analyst John Kindervag helped popularize the term “zero trust,” and while the underlying principles aren’t new, the model of “never trust, always verify” has never been more relevant. In response to an increasingly mobile workforce and the widespread adoption of cloud services, zero trust has helped enterprise security evolve from a fortress mindset (perimeter security) to a more thoughtful identity-centric model. Just as the framework is able to evolve with changes in how companies connect, access, and use corporate IT, security teams recognize that the journey to “never trust, always verify” is continuous.

Bringing the principles of zero trust to SaaS

Zero trust brings substantial security advantages to an enterprise, as avoiding implicit trust minimizes the likelihood, impact, and time to detect a breach. Zero trust requires the implementation of three key tenets, as defined by National Institute of Standards and Technology (NIST 800-207):

While these principles can be applied to infrastructure in the data center or cloud with relative ease using well-established techniques, the tools and processes are not well known or repeatable for SaaS. As a practical stopgap, most companies rely on single sign-on (SSO) and multi-factor authentication (MFA) as their primary enforcement mechanism of their zero trust architecture for SaaS. This allows companies to provide some verification of access for users but fails to verify all elements in the SaaS environment. For those companies, zero trust stops at the identity provider and leaves SaaS applications out of scope. Security teams are unable to detect attackers that breach or bypass the identity provider and could otherwise go undetected, including cookie stealing, OAuth abuse of third-party apps, insider threats, and non-user accounts.

Zero trust for SaaS requires a deeper understanding of each application, not relying on the identity provider alone. As risk can come from the client connections, applications, and integrations of cloud-based services, your security team needs holistic coverage of these core SaaS components in order to extend the principles of zero trust.

The Obsidian approach to zero trust

Obsidian provides comprehensive security and compliance for SaaS built on a deep, consolidated understanding of your business-critical applications—making Obsidian the first truly zero trust solution for SaaS.

Our approach is built on a foundational knowledge graph populated by data on the users, configurations, privileges, and activities within and across your applications — including your identity provider. Obsidian’s threat mitigation and posture management solution extends the three tenets of the zero trust framework to the components within your SaaS environment:

These capabilities are essential to understanding enterprise risk and protecting your SaaS environment. Without them, your security team is effectively blind to threats and posture gaps within your core applications, leaving your zero trust architecture incomplete. To learn more about how Obsidian helps extend zero trust to SaaS, download our solution brief.

Frequently Asked Questions (FAQs)

What is zero trust and why is it important for SaaS applications?

Zero trust is a security framework centered on the principle of "never trust, always verify." It requires continuous verification of user and device access, minimizing implicit trust and reducing the risk of breaches. For SaaS applications, zero trust is crucial because traditional perimeter defenses are ineffective; threats can originate from compromised credentials, OAuth abuse, or insider actions within cloud services.

How do traditional security measures like SSO and MFA fall short in zero trust for SaaS?

While Single Sign-On (SSO) and Multi-Factor Authentication (MFA) help authenticate users, they primarily protect the identity layer and may leave SaaS applications vulnerable. Attackers who bypass or breach the identity provider—via cookie theft, abused OAuth integrations, or insider threats—can still access SaaS data and resources undetected. Zero trust for SaaS demands security controls that examine application-level activity and configurations, beyond what's covered by SSO and MFA.

What are the three core zero trust principles recommended by NIST for SaaS environments?

The National Institute of Standards and Technology (NIST) advocates for three key zero trust principles: continuous verification of all access attempts, limiting the potential impact of any breach, and collecting behavioral data for rapid incident response. Effective SaaS security solutions must implement these principles by monitoring users, apps, and connection behaviors, and by recommending best practices to mitigate risks.

How does Obsidian Security extend zero trust principles to SaaS applications?

Obsidian Security implements zero trust in SaaS by providing holistic coverage of users, configurations, privileges, and activity across critical applications. Its platform continuously monitors connections—including third-party OAuth apps—hardens configurations, right-sizes privileges to limit breach impact, and uses machine learning to detect threats. Obsidian’s behavioral analytics give deep, actionable insights for rapid response and ongoing compliance.

You May Also Like

Get Started

Start in minutes and secure your critical SaaS applications with continuous monitoring and data-driven insights.

get a demo