PUBlished on
June 14, 2024
updated on
November 5, 2025

The Growing Importance of Securing Local Access in SaaS Applications

CHRIS FULLER

Introduction

Due to the growing importance of securing local access in SaaS applications, we recently posted a blog discussing the complexity of enforcing Single Sign-On (SSO) within Salesforce and the frequent misconfigurations we encounter at Obsidian Security. A striking statistic from our observations: 60% of Obsidian’s customers initially have local access without Multi-Factor Authentication (MFA) configured for Salesforce. This is a significant security gap that Obsidian works diligently with customers to secure.

The Hidden Vulnerability of Local Access

One of the interesting observations we make is that application owners who manage Salesforce daily are often unaware of this misconfiguration. Despite their deep knowledge of Salesforce management, local access without MFA remains an overlooked vulnerability. If this is true for Salesforce, it raises concerns about the state of other SaaS applications, especially those without developed expertise or knowledge.

Attacker Focus and Trends

Historically, attackers have concentrated on the Identity Provider (IdP) space, targeting providers like Okta, Microsoft Entra, and Ping. This focus is due to several reasons:

Over the past 12 months, nearly 100% of the breaches where companies sought our help through CrowdStrike or other incident response partners were IdP-focused. Notably, 70% of these breaches involved subverting MFA, often through methods like SIM swapping. In instances where local access bypass the IdP exists (aforementioned 60% of customers), we observe that 95% of the time it has no MFA.

However, with recent discussions around Snowflake, the topic of “shadow authentication” is gaining traction among attackers. We define shadow authentication as the existence and use of unsanctioned means to authenticate a user within an application, as in the case of local authentication described earlier. Obsidian Security has observed an increase in bruteforce attacks against SaaS applications via local access pathways over the last two weeks, indicating a growing awareness of this attack vector.

Future Expectations

Given that attackers are always looking for the easy and most efficient pathways, we anticipate that in the next 12 months, local access or shadow authentication will become a major attack path. As attackers shift their focus, organizations must be proactive in securing these pathways.

What You Can Do to Secure Local Access
How Obsidian Helps

Obsidian Security offers robust solutions to address these challenges:

Securing local access in SaaS applications is important. By leveraging Obsidian’s capabilities, organizations can enhance their security posture, protecting against the evolving threats targeting local access and shadow authentication.

For a more detailed analysis, read our original blog post here.

Frequently Asked Questions (FAQs)

What is local access in SaaS applications and why is it a security risk?

Local access in SaaS applications refers to users logging in directly via the application’s own login mechanism rather than through a centralized identity provider (IdP) like Okta or Microsoft Entra. This is a security risk because it often bypasses organizational controls such as Single Sign-On (SSO) and Multi-Factor Authentication (MFA), leaving a potential gap that attackers can exploit.

What is "shadow authentication" in the context of SaaS security?

Shadow authentication describes unsanctioned or undocumented ways users can authenticate to SaaS applications, often circumventing official identity and access management processes. This can include legacy local accounts or other hidden authentication paths that are not protected by standard security measures like MFA or SSO, increasing exposure to brute-force attacks and unauthorized access.

Why do attackers often target Identity Providers (IdPs) instead of individual SaaS applications?

Attackers focus on IdPs because compromising one can grant them access to multiple connected applications, maximizing impact and efficiency. However, with the rise of misconfigured local access points in SaaS apps, attackers are increasingly shifting their attention to these easier, less protected targets as well.

How can organizations discover and secure overlooked local access points in SaaS apps?

Organizations should establish a comprehensive SaaS discovery program to identify all applications in use, including those with local access. Once discovered, they should either integrate these apps with their IdP, enforce SSO and MFA, or apply rigorous monitoring and documentation for any exceptions, focusing security efforts on high-risk accounts.

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