Security monitoring

Report sign-in attempts and Blipit turns bursts and unusual locations into security issues with their own alerts. Sending is covered under Login attempts; Odoo does it for you once login monitoring is ticked. This page explains the rules.

1Thresholds

Alerts, Security thresholds, per project or for the whole workspace: set how many failed logins, blocked logins, password reset requests and privileges granted in how many minutes raise a security issue. Successful logins have no count; they feed the new-IP and new-country checks. Thresholds go up to 1,000 and windows up to 1,440 minutes, and each kind can be turned off. Only owners and admins can change this; members can see it.

2What raises an issue

By actor: one login name goes over your threshold within the window (brute force on one account). By IP: one address goes over it across several accounts (spraying). New IP: a known person signs in from an address never seen for them. New country: the same, for a country never seen for them.

3Alerts

One security alert per issue per window, sent to your email rules, Slack, Teams and webhooks, or to the owners when you have none. Snooze does not apply. Security events always keep their full payload.

Good to know

  • Security events must be sent with the secret key; the public key gets 403 security_needs_secret_key, so a visitor cannot poison the baseline of known addresses.
  • On a plan without security monitoring, ingest answers 403 security_monitoring_not_in_plan and the Odoo module pauses login reports for ten minutes.
  • The Security page lists the security issues of the workspace; the country comes from the IP.

Stuck? Email support@blipit.io. Keys and the project id for each project are under API keys in app.blipit.io.