As SaaS purposes 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 gives cloud-based community safety whereas enhancing community infrastructure efficiency.
Nevertheless, a brand new report: “Higher Collectively: SASE and Enterprise Browser Extension for the SaaS-First Enterprise” (Obtain right here), challenges SASE’s skill to ship complete safety towards web-borne cyber threats by itself. From phishing assaults to malicious extensions and account takeovers, conventional community visitors evaluation and safety falls brief. The report sheds gentle 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. Nevertheless, whereas SASE provides clear benefits in safety, it might not totally cowl the expanse of the web-borne menace panorama. SWG, CASB, and NGFW aren’t 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 house. These new threats leverage the browser as a bridge between the gadget and organizational assets and purpose to realize malicious entry to the group by 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 menace panorama depends on visitors from the browser to a SaaS app or web site, which SASE doesn’t totally cowl.
Bridging the Hole with Safe Browser Extensions
Safe browser extensions complement SASE’s community safety measures. Via deep session evaluation and proactive menace prevention, these extensions present granular visibility and real-time safety towards subtle 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 on the subject of precise threats? The report gives 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. In consequence, 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 gives granular visibility into the dwell session, enabling the monitoring of malicious elements 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 gives 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 advanced, trendy internet apps and depends upon 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 turning into dominant, the extra necessary the function of the browser turns into – and the menace panorama it encounters will improve. Can organizations ignore the dangers that derive from the fashionable browser? Based on LayerX, community safety is inadequate by itself, they usually name for complementary measures that may handle SASE’s gaps.
To learn extra about tips on how to achieve real-time safety towards this evolving threat with a safe browser extension, learn the whole report.