Watchbill, the full simulation.

A company that monitors US SMEs’ systems day and night, whose analysts are swamped with alerts. The case followed on this page, a suspicious login to an accountant's account, at a financial client, in the middle of the night.

A company that monitors US SMEs’ systems day and night, whose analysts are swamped with alerts.

Every alert reaches the analyst with its case file.

What remains with the analysts

Analysts decide each response, from isolating a workstation to blocking an account, and the agent never acts alone on a system. The client alone decides to notify the regulator.

Monthly reports

Each client receives a monthly report detailing incidents during the period, pending patches, accounts to monitor and analyst recommendations.

The analyst responsible for the client reviews each report before it is sent.

Tuning detection rules

The agent identifies the rules that generate the most unactioned alerts and suggests adjustments, each accompanied by the alerts that justify it.

The detection engineer accepts or rejects each adjustment, and no rule is deactivated without them.

Emails reported by employees

Client employees forward suspicious emails to a dedicated address. The agent analyses each one and replies to the employee. Any malicious email is immediately escalated to an analyst.

The analyst decides whether to block the sender for the entire client.

Security questionnaires

Watchbill clients themselves receive security questionnaires from their own customers. The agent prepares the responses based on each client's documentation.

The client's head of security signs off each response.

a suspicious login to an accountant's account, at a financial client, in the middle of the night

A night-time alert, before and after.

NYDFS, incident notification

FBI IC3, 2025 annual report