Threat & Vulnerability · Integration
Lookout
Add Lookout to your product for your customers, and give your AI agents governed access to it.
Embed a Lookout integration so mobile device and threat state appears alongside the assets your product already tracks, without you building a security integration per customer. Each customer connects their own Lookout tenant, so detections and device records are read under their credentials and scoped to them. Detections arrive through event triggers rather than polling and are deduplicated per condition, which matters because a device that keeps reconnecting should not fill your users' queues with identical records. fastn owns the auth, token refresh, rate limits and API upkeep, and the same governed connection gives your AI agents scoped, audited access.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Lookout tenant so device and threat state appears next to the assets your product already tracks.
React to a Lookout detection with an event trigger so your product opens a record or holds a workflow immediately.
Read device state per tenant so your product can gate a sensitive action on whether the device is healthy.
Support each customer's own policies and device fleet as configuration rather than a branch in your code.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent investigates a detection by reading the device and threat detail behind it, within scoped permissions.
An agent reports which devices in one customer's tenant are unprotected or out of date, with each read audited.
An agent triages overnight detections for a tenant and explains which ones need a human.
Example prompt
Which devices in this tenant have open Lookout detections, and what triggered them?
Set up Lookout in 4 steps
- 01Enable the Lookout connector in your fastn dashboard.
- 02Have each customer authorise their own Lookout tenant so calls run under their credentials.
- 03Map the device and detection fields your product uses, then enable the triggers you need.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Lookout integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Lookout integration without building it. Your customers connect their own Lookout account inside your product and work their findings, detections and assets there, with no per-customer code on your side.
- Handle the part that actually costs time: a rescan re-reports everything, so the same finding arriving twice must not read as two problems. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Lookout update is not your on-call problem.
- One integration serves your product and your agents. The same governed Lookout connection powers in-product features and gives AI agents scoped, audited access, so you get security findings in front of the people and systems that act on them without wiring it twice.
Used by these teams
Compare with
CrowdStrike FalconWorks well with
JamfOften used alongside
Tools the same teams tend to run next to Lookout, across other categories.
ServiceNow
Okta
Datadog
Microsoft Entra IDLookout integration FAQ
How do I add a Lookout integration to my product?
Enable the Lookout connector in your fastn dashboard, then let each customer authenticate their own Lookout account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Lookout client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Lookout account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Lookout account and only ever sees their own findings, detections and assets. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Lookout integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent investigates a detection by reading the device and threat detail behind it, within scoped permissions.
Who maintains the Lookout integration?
fastn does. When Lookout changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
How does a new Lookout finding reach my product?
Through event triggers rather than polling, delivered per tenant, so your product reacts when a finding is raised or its severity changes rather than on a schedule that is always slightly out of date.
How is Lookout finding noise kept manageable?
Findings are deduplicated per asset so a rescan does not re-raise what you already have, and you can filter by severity and status before anything reaches your product. That matters more here than in most integrations, because the volume is what stops teams acting on any of it.
What can I build with the Lookout integration?
A common starting point: connect their own Lookout tenant so device and threat state appears next to the assets your product already tracks. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Lookout integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Lookout does not change your per-connector cost. You can start free with 3 connected accounts.
Add Lookout to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.