Skip to main content
Cotool reads your logs as they arrive and records the security-relevant facts in them as signals. A few signal types are promoted to alerts, and the scheduled library detections they replace are retired. You get a searchable record of everything notable, alerts within seconds of Cotool receiving an event instead of on a schedule, and one alert for one event.

How it works

Signal detections read events as they are indexed. Only promoted signals open alerts. Scheduled detections keep running on a timer and can query signals as well as logs.

Signals

A signal is one security-relevant fact taken from one log event, such as “an Okta admin role was granted”. It records what happened, who did it and to what, and makes no judgment about whether it is bad. Every signal has the same fields, whichever tool it came from: Signals are not alerts. Most are never promoted. They stay as context, so the signals around an alert’s user or IP address show what else happened. Signals are selective. Activity that repeats all day, such as token refreshes or CI jobs cloning a repository, stays in the log tables.

Signal detections

A signal detection turns log events into signals. It runs on each batch of events as Cotool indexes them, so a signal is written within seconds of Cotool receiving the event. How soon Cotool receives it depends on how the source delivers its logs. Cotool maintains a library of more than 200 signal detections across more than 40 log sources.
  • Added for you. When you enable a log stream, Cotool adds the signal detections that read it, and new ones it ships later. Add signal detections automatically in the source’s Log Ingest settings controls this.
  • Kept current. Cotool maintains signal detections. You can read their logic and turn them off, but not edit or delete them.
  • Backfilled. A signal detection that is added or updated replays the last 14 days of your logs. When an update narrows a detection, the replay removes the signals it no longer produces.
  • Repaired after gaps. If a batch can’t be processed, for example during an outage, Cotool records the gap and replays it.
  • Off means off. Turning one off on its Settings tab stops new signals and keeps the old ones. Before you confirm, Cotool lists the promotions and detections that depend on it.
Scheduled detections still exist alongside. They run on a timer, read Cotool Logs, connected tools and the signals table, and are best for counts, sequences and checks across tools. See Author and Publish Detections.

Promotions: from signal to alert

A promotion is the rule that turns signals of one type into alerts, which follow alert routing like any other alert. Each signal type has at most one, and Cotool ships a default for every library type. Some start on. Others, such as routine sign-ins, start off because the signal alone is rarely worth triage. Repeats join one alert. While a group’s alert is open, new signals for the same actor or target join it. After you close it, they keep joining for the cooldown. An alert stops taking signals 7 days after it opened, and a signal more than 24 hours older than the one that opened it doesn’t join. Flood breaker. If one signal type creates more than 50 alerts in an hour, Cotool turns its promotion off and marks the type Paused: too many alerts. Signals keep being recorded. Narrow the promotion before you turn it back on. Changing one. On a signal detection’s Settings tab, choose Edit promotion on a signal type. Changes apply to signals recorded from then on. Reset promotion restores the library default.

In the app

The Detections list

Every detection in Detections shows its status, what it produces and its signal and alert counts for the chosen window. Filter by Produces, Status, Log source, Promotes to alerts or Tuning, or by count. The Needs attention and Proposal waiting presets find what needs you.

A signal detection’s page

  • Overview: status, signal and alert counts, the last signal, how far its signals are complete, what it reads and which detections use its signals.
  • Signals: every signal it recorded, filterable by type, source, actor and target. Open one for its attributes, IP address and the detections that read it.
  • Logic: the detection code, read-only.
  • Settings: turn it on or off, see its signal types, edit promotions, and choose whether promotion tuning applies without review.
An alert opened by a promotion shows its severity, grouping and every signal that joined it, with actor, target and IP address. In Log Search, the signals and detection_hits tables sit beside your log tables, and scheduled detections, response agents and the assistant can query them too.

Retired library detections

Many scheduled library detections looked for one kind of event on a timer. A signal detection now records the same event within seconds of Cotool receiving it, so Cotool retires the old one rather than alert twice. Each retired detection says where its alerts come from now: Your copy of a replaced detection is retired once its replacement has caught up: every signal detection that replaces it is running, its signal types are complete through the last 24 hours, and whatever alerts in its place is on. A copy in calibration waits until calibration ends.
  • In the library, a replaced entry can’t be added. It is listed under the Retired filter.
  • A retired copy is turned off, not deleted. Its page shows Retired on a date, links the detections that replace it, and keeps its alerts and hits. It can’t be turned back on or deleted.
  • Copies you or an agent changed are not retired automatically, so your changes aren’t lost. While a changed copy is on, the promotion that would replace it is held off so one event doesn’t alert twice. That promotion is labeled For your changed copy of the detection it replaces, and you can turn it on. Two kinds of promotion are not held, so they can alert on the same event as your changed copy:
    • a promotion your organization already changed, by hand or through tuning, which keeps its setting;
    • a promotion that already took over the alerts of another detection that was retired while it was on, since holding it would stop those alerts.
  • If you had the old copy off, the promotion that replaces it is turned off too.

Tuning

Promotions tune from your verdicts. When promoted alerts you closed as benign or false positive share something no true positive has, Cotool proposes narrowing that promotion, for example to signals where the country is not on a list. It leaves promotions a person set alone. The proposal appears on the signal detection’s page with the conditions now and after the change. Approve it there, or turn on Auto-apply tuning proposals in the detection’s settings to apply proposals without review. An applied change can be undone. Automated tuning knows when to stop. Cotool stops tuning a detection when tuning isn’t the right fix:
  • a library copy that is due to be retired, since a signal detection replaces it;
  • a detection tuned 4 or more times in 90 days whose alert volume didn’t fall.

FAQ

Will I get more alerts? Usually not. Most signal types are never promoted, promotions group repeats, and the detections a promotion replaces are retired. The exception is a changed copy that stays on next to a promotion Cotool doesn’t hold (see Retired library detections): both can alert on one event until you retire the copy or turn the promotion off. Do I need to set anything up? No. Signal detections are added for the log streams you ingest and backfill on their own. For a new tool, enable its log streams. Do my own detections change? No. Detections you wrote, and library detections nothing replaces, keep running. They can now also query the signals table. Can I write my own signal detection? No. To alert on a pattern of signals, write a scheduled detection over the signals table, such as one user with three different signal types in two hours. Why is there a signal but no alert? That is the usual case. An alert needs the type’s promotion to be on and its conditions to match. How long are signals kept? The signals table has its own retention in Cotool Logs, set like any other table’s: your organization’s log retention unless the table has its own setting. Signals don’t inherit the retention of the log table they came from, so when tables have different settings a log can expire before or after the signal taken from it. Back to Detections Platform