IT OPS

Detect New Shadow-IT SaaS Apps from SSO Login Logs

Scans Snowflake-warehoused SSO authentication logs nightly for SaaS domains nobody has approved.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly schedule fires
  • ActionQuery SSO auth events from SnowflakeSnowflakeSnowflake
  • LogicDrop apps already on approved-vendor list
  • LogicAggregate unique users per new app
  • OutputPost new-app digest to IT review channelSlack

What it does

Every night this workflow reads your identity provider's authentication events out of Snowflake, isolates the destination SaaS applications employees logged into, and compares them against your approved-vendor list. Any application seen for the first time is flagged as potential shadow IT and reported to your IT team with usage context so they can decide whether to sanction, block, or ignore it.

When to use it

Run this when SSO covers most of your workforce but you have no automated way to spot the long tail of unsanctioned tools employees adopt on their own. It turns raw login telemetry into a short, actionable list of genuinely new apps instead of a noisy dump.

How it works

  1. 1A nightly schedule fires the run.
  2. 2Query Snowflake for the last 24 hours of SSO auth events, grouping by application and counting distinct users.
  3. 3Filter out any application already present in the approved-vendor reference table.
  4. 4For each remaining new app, enrich the row with first-seen timestamp and unique-user count.
  5. 5Post a single digest to the IT review Slack channel listing each new app, its user count, and a quick approve/block prompt.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SnowflakeWarehouses, queries, shares.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.