As SaaS purposes dominate the enterprise panorama, organizations want optimized community pace and sturdy security measures. Lots of them have been turning to SASE, a product class that gives cloud-based community safety whereas enhancing community infrastructure efficiency.
Nonetheless, a brand new report: “Higher Collectively: SASE and Enterprise Browser Extension for the SaaS-First Enterprise” (Obtain right here), challenges SASE’s capability to ship complete security in opposition to web-borne cyber threats by itself. From phishing assaults to malicious extensions and account takeovers, conventional community visitors evaluation and security falls brief. The report sheds gentle on these limitations and introduces the function of safe browser extensions as an integral part in a complete security technique.
SASE Benefits and Limitations
SASE takes on a twin function in addressing each infrastructure and security. Nonetheless, whereas SASE affords clear benefits in security, it could not fully cowl the expanse of the web-borne risk panorama. SWG, CASB, and NGFW usually are not a silver bullet to all of the security wants of the SaaS-first group, even when they’re packaged as SASE.
The trendy risk panorama is formed by the centrality of the browser as a important working area. These new threats leverage the browser as a bridge between the gadget and organizational assets and goal to realize malicious entry to the group by way of phishing, malicious extensions, and account takeover, to call a couple of. Whereas SASE is designed to guard the perimeter from threats that try to enter it, this new risk panorama depends on visitors from the browser to a SaaS app or web site, which SASE doesn’t fully cowl.
Bridging the Hole with Safe Browser Extensions
Safe browser extensions complement SASE’s community security measures. By means of deep session evaluation and proactive risk prevention, these extensions present granular visibility and real-time safety in opposition to refined web-borne threats, successfully addressing the gaps left by SASE.
SASE vs. Safe Browser Extensions: 3 Use Instances
How do the variations between SASE and safe browser extensions play out relating to precise threats? The report supplies three use circumstances.
1. Phishing
- SASE limitations: SASE’s NGFW or SWG lacks visibility into the precise session, leaving it to depend on identified malicious addresses or emulate the session in a digital surroundings. Because of this, SASE misses ~60% of malicious internet pages. It is also unable to detect pages that disable their phishing exercise when executed in a digital surroundings.
- The answer: A safe browser extension supplies granular visibility into the dwell session, enabling the monitoring of malicious parts within the phishing internet web page and disabling them in actual time.
2. Malicious Extensions
- SASE limitations: SASE’s NGFW or SWG lacks the power to detect and block outbound visitors generated by any malicious extensions.
- The answer: The safe browser extension supplies visibility into the browser and detects and disables all extensions that introduce an information exfiltration danger.
3. Account Takeover
- SASE limitations: SASE’s CASB lacks visibility into advanced, trendy internet apps and relies on the app’s API, limiting safety to sanctioned apps.
- The answer: The safe browser extension integrates with the organizational id supplier and acts as an extra authentication issue. Entry is feasible solely from a browser that has the extension.
With SaaS app utilization changing into dominant, the extra vital the function of the browser turns into – and the risk panorama it encounters will improve. Can organizations ignore the dangers that derive from the fashionable browser? In response to LayerX, community security is inadequate by itself, they usually name for complementary measures that may deal with SASE’s gaps.
To learn extra about how you can acquire real-time safety in opposition to this evolving danger with a safe browser extension, learn all the report.
