SECOPS

Daily Paste-Site Credential Sweep with Evidence-Backed Rotation Ticket

Each morning, sweeps Brave Search for your company domains appearing on paste sites and dump indexes, has an LLM confirm real exposed credentials.

CategorySecOps
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule fires the sweep
  • ActionQuery Brave Search across paste sites per domainBraveBrave Search
  • ActionOpenAI classifies each hit and extracts the leaked accountOpenAI
  • LogicDrop benign and low-confidence results
  • OutputOpen a Linear rotation ticket per confirmed leakLinearLinear

What it does

Runs a scheduled sweep across paste sites (Pastebin, Ghostbin, dpaste, paste.ee and similar) for your monitored domains, then turns only the genuine credential exposures into actionable rotation tickets. It filters out marketing hits, old job postings, and unrelated mentions so on-call isn't buried in noise.

When to use it

Use it as a standing daily control when you own a handful of domains and want early warning that employee or service credentials have been pasted publicly — before they get scraped into a credential-stuffing list.

How it works

  1. 1A daily schedule fires the sweep.
  2. 2Brave Search runs targeted queries (`site:pastebin.com "yourdomain.com"` and variants) for each monitored domain.
  3. 3An OpenAI step reads each result snippet and classifies it: real exposed credential, benign mention, or uncertain — extracting the affected account, leak URL, and a confidence score.
  4. 4A logic filter drops benign and low-confidence hits.
  5. 5For each confirmed leak, a Linear issue is created tagged `credential-exposure` with the source URL, matched account, and recommended rotation steps as evidence.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Brave SearchWeb, news, image, video search.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect LinearIssues, projects, cycles, triage.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.