log-watch
Log Watch — Scheduled Agent Log Review and Paging for Teams Without a SIEM
Most small SaaS teams already have the logs that would show an attack: Vercel or Heroku request logs, Sentry errors, a Postgres auth table, Stripe events, CloudTrail. Nobody reads them until after the incident. This skill wires a scheduled agent over those sources: cheap deterministic filters and a small model cut the volume, a stronger model looks only at what got flagged (with the previous run's state), and a human gets paged with a "why this fired" summary and raw event links.
Detection only. The watcher reads logs and sends messages. It never blocks an IP, disables a user, rotates a key, or changes config. Response is a human decision, made in incident-triage.
Write is pre-approved because the main output is a file: the log-watch.md plan, plus an optional scaffolded job. Don't write anywhere else without asking.
Cross-references: siem-detection for when the team outgrows this and adopts a real SIEM (the detections here port to Sigma); incident-triage for what happens after a page is real; soc-operations for regulated environments that need a SIEM/MDR and staffed triage instead of this; prompt-injection because the watcher is an LLM reading attacker-controlled text; secrets-audit for the API-key events this detects and for storing the watcher's own credentials; cloud-audit and iam-audit for the CloudTrail/IAM side; threat-hunting for one-off hunts that later graduate into a detection here.
When this fits, when it doesn't
Fits: 1–30 engineers, PaaS-hosted (Vercel, Heroku, Render, Fly, Supabase, Neon), no SIEM, no on-call security person, some logs already retained somewhere.
Doesn't fit, say so and point elsewhere:
- Regulated environments (HIPAA, PCI DSS, SOC 2 with a monitoring control, FedRAMP) that need retained, tamper-evident logs and documented triage. A cron job doesn't satisfy that; use
soc-operationsand a SIEM or MDR. Log-watch can still run as an extra layer. - Already have a SIEM. Write the rules there with
siem-detection. - Endpoint threats (malware on laptops). Logs from PaaS won't show it; that's EDR territory.