Skip to content
nulltapE-reader edition

← All e-reader articles

3 min read

CrowdStrike Adds Browser Controls for Unmanaged Devices on Falcon

Falcon Seraphic brings browser-session, data-movement and extension controls to existing browsers, including contractor devices. Check where policies apply and test a safe blocked action.

Read on the standard site

Illustration of a browser-shaped glass pane holding a document behind a metal access bar.

A contractor can open a company app in a browser on a device the company does not manage. On November 4, CrowdStrike announced that Falcon Seraphic Enterprise Browser is now native to its Falcon platform, with session controls intended for that kind of access as well as managed devices. CrowdStrike says it works in browsers employees already use, without routing traffic through a new path or requiring a dedicated enterprise browser.

That places the control where credentials, active sessions and sensitive files move through web apps. The announcement describes CrowdStrike’s own product capabilities, including protection on BYOD and contractor devices “without mobile device management (MDM) enrollment.” For a team considering this rollout, the first question is which actual browser sessions receive policy, particularly on devices outside endpoint management.

Browser actions carry the risk

A stolen session token can give an attacker a route into an application after the user has authenticated. A user can also move company data into an unsanctioned web app through the browser’s ordinary upload or paste controls. CrowdStrike names phishing, ClickFix, malicious scripts and adversary-in-the-middle activity among the threats its runtime browser inspection aims to disrupt. CrowdStrike presents these as product capabilities; plan the rollout around your own access routes.

CrowdStrike says Falcon Seraphic can apply policy to copy, paste, upload and download actions inside supported browsers. It also describes session-token and session-hijack protection, browser-extension inventory and allow/block policy, and policy-controlled access to private applications. For supported workflows, CrowdStrike positions that access as an alternative to traditional VPN or VDI, including for contractors on unmanaged devices.

These controls act at different moments. Extension policy deals with what code a browser is allowed to run. Action policy governs what a user can move during a session. Private-app access policy governs which internal resource the user can reach. Browser deployment and policy assignment determine whether those decisions apply on a contractor’s own device.

Falcon receives browser activity

CrowdStrike says browser telemetry is available in Falcon Next-Gen SIEM, where analysts can correlate it with endpoint, identity and third-party data. In a session-theft investigation, that gives responders another place to look for unusual browser activity alongside sign-in and endpoint records. Identify the browser event fields and retention in your own tenant before writing a detection around them.

For a managed workstation and an approved unmanaged test device, map the browser actually used, the private apps reached and the data-handling policy assigned. Inspect the Falcon policy state for upload, download, copy and paste, then compare the browser-extension allow/block list with the extensions visible in the browser. Include alternate browsers and sessions outside the configured path in your inventory.

Test the policy at work

Choose an approved test account and a non-sensitive sample document. In a browser that the deployment is meant to protect, attempt an upload to a destination your policy blocks; confirm that the browser action is stopped and that the expected browser event reaches Falcon Next-Gen SIEM if you have enabled that telemetry path. Run the same check on the authorized unmanaged-device path. This local check ties enforcement to the event an analyst will investigate.

If the action succeeds, correct the browser deployment, policy scope or access route before relying on that control for contractor traffic. Check private-app access separately using an account without permission for the test resource; the expected result is a denied access attempt under your configured policy. Keep existing identity and application logs in the investigation: browser controls give you another enforcement point, while sessions and data can also move through paths your pilot has yet to cover.

The useful result is a policy decision made in the browser your people actually use, on the device they actually bring. Match that decision to the event your analysts will see, and extend the rollout only after both sides line up.

Primary sources