agentleFS
kaandgnshkaandgnsh/Claude-Blue/skills/asset-attack-surface/shadow-it-discovery/SKILL.md

shadow-it-discovery

Skill0 starsChanged 12 days agoMITView on GitHub

Discover unsanctioned SaaS, cloud accounts, AI tools and infrastructure — via proxy/DNS/CASB logs, SSO and OAuth grant data, expense and procurement records, cloud org enrollment, email sign-up notifications and external attack surface data — and bring them under governance without just blocking. Use when assessing unmanaged technology risk, preparing SaaS governance, or after finding unknown assets.

The file

Files
SKILL.md

Shadow IT Discovery

Sources

SourceFinds
Proxy / SWG / DNS logsSaaS domains used, volume of uploads, users
CASB (Defender for Cloud Apps, Netskope, Zscaler)App catalog with risk scores, discovered apps
OAuth consent / token dataApps users connected to corporate identities (oauth-app-review)
EmailSign-up/verification emails from SaaS vendors to corporate addresses (search mail logs for "verify your email", "welcome to")
FinanceExpense reports and card transactions for software/cloud vendors
Cloud providersAccounts/subscriptions/projects using corporate emails outside the organization (AWS Organizations, Azure tenant discovery, GCP org)
External ASMHosts under corporate domains not in inventory (external-attack-surface-review)
Browser extensionsExtension inventory via EDR/MDM

DNS example (Zeek): zeek-cut query < dns.log | awk -F. '{print $(NF-1)"."$NF}' | sort | uniq -c | sort -rn | head -100 → compare with sanctioned app list.

Triage

For each discovered app/account: users and departments, data types uploaded, authentication (SSO? local passwords?), vendor security posture (vendor-security-assessment), business need.

Decide: sanction (onboard to SSO/SCIM, contract, DPA), tolerate with controls (no sensitive data, monitored), replace with an approved alternative, or block (with communication). Generative AI tools deserve explicit policy and an approved option (llm-gateway-controls).

Output

App/asset | Category | Users | Data | Auth | Risk | Decision | Owner

Related skills

asset-inventory-reconciliation, oauth-app-review, vendor-security-assessment, llm-gateway-controls

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.