Free trial
EN

Alert example

A Tocsin24 alert, from start to finish

A code file is changed on the demo B2B workshop store although no deployment has been declared. Here is what the person in charge receives, and what they find when they open the incident.

  1. Detection

    The module finds that pub/index.php no longer matches the fingerprint of the official version. The incident is rated critical.

    pub/index.php Critical

  2. The alert

    Email, push notification and SMS from “Tocsin24”, all at the same time.

    Tocsin24 · [Critique] Fichier modifié hors déploiement
    Critical alert email: file changed outside a deployment, pub/index.php
    Push notification

    TOCSIN2419:25

    Critique · Atelier B2B de démonstration

    Fichier modifié hors déploiement : pub/index.php

    SMS, sender “Tocsin24”

    Text message · SMS · 19:25

    Tocsin24 : CRITIQUE Atelier B2B de démonstration, fichier modifié hors déploiement (pub/index.php). Détail sur app.tocsin24.com

  3. The explanation

    The incident page says what happened, why it matters and what to do, with the file concerned.

    Critical incident: file changed outside a deployment, pub/index.php, affected files section

    For an attack attempt, it also gives the data involved, the type of attempt, its outcome and our advice.

    Page of an attack attempt: detection, occurrences, IP addresses and the section explaining the incident
    Rest of the page: type of attempt, outcome Blocked, advice, history and evidence

  4. Resolution

    The person in charge closes the incident (“Legitimate” or “Fixed”) or shares it with their developer or agency; everything is kept in the history.

    • Legitimate or Fixed
    • Shared with your agency
    • Kept in the history
Start your free trial Book a demo