As SaaS functions dominate the enterprise panorama, organizations want optimized community pace and sturdy safety measures. Lots of them have been turning to SASE, a product class that provides 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 safety towards web-borne cyber threats by itself. From phishing assaults to malicious extensions and account takeovers, conventional community site visitors evaluation and safety falls quick. The report sheds mild on these limitations and introduces the function of safe browser extensions as an integral part in a complete safety technique.
SASE Benefits and Limitations
SASE takes on a twin function in addressing each infrastructure and safety. Nonetheless, whereas SASE gives clear benefits in safety, it might not fully cowl the expanse of the web-borne menace panorama. SWG, CASB, and NGFW are usually not a silver bullet to all the safety wants of the SaaS-first group, even when they’re packaged as SASE.
The trendy menace panorama is formed by the centrality of the browser as a principal working area. These new threats leverage the browser as a bridge between the system and organizational sources and intention to achieve malicious entry to the group by phishing, malicious extensions, and account takeover, to call a number of. Whereas SASE is designed to guard the perimeter from threats that try to enter it, this new menace panorama depends on site 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 safety measures. By means of deep session evaluation and proactive menace prevention, these extensions present granular visibility and real-time safety towards 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 in the case of precise threats? The report offers three use circumstances.
1. Phishing
- SASE limitations: SASE’s NGFW or SWG lacks visibility into the precise session, leaving it to depend on recognized malicious addresses or emulate the session in a digital atmosphere. Consequently, SASE misses ~60% of malicious net pages. It is also unable to detect pages that disable their phishing exercise when executed in a digital atmosphere.
- The answer: A safe browser extension offers granular visibility into the stay session, enabling the monitoring of malicious elements within the phishing net web page and disabling them in actual time.
2. Malicious Extensions
- SASE limitations: SASE’s NGFW or SWG lacks the flexibility to detect and block outbound site visitors generated by any malicious extensions.
- The answer: The safe browser extension offers visibility into the browser and detects and disables all extensions that introduce an information exfiltration threat.
3. Account Takeover
- SASE limitations: SASE’s CASB lacks visibility into complicated, trendy net apps and relies on the app’s API, limiting safety to sanctioned apps.
- The answer: The safe browser extension integrates with the organizational identification supplier and acts as a further authentication issue. Entry is feasible solely from a browser that has the extension.
With SaaS app utilization turning into dominant, the extra essential the function of the browser turns into – and the menace panorama it encounters will enhance. Can organizations ignore the dangers that derive from the fashionable browser? In accordance with LayerX, community safety is inadequate by itself, they usually name for complementary measures that may handle SASE’s gaps.
To learn extra about the best way to acquire real-time safety towards this evolving threat with a safe browser extension, learn all the report.
