Skip to main content

Dashboard

Sentinel > Dashboard is the first entry of the Sentinel menu. Under its title, Sentinel Dashboard, the page says what it gives: Security overview of your PrestaShop store. It starts with the getting started guide, as long as a required step is left, and the security score, then gives the figures, what protects the shop and what is left to do, the prerequisites check, and the other cards, ending with the latest events.

The blocks of the page​

From top to bottom:

  1. The Getting started guide card, as long as a required step is left, described in Getting started guide.
  2. The Security score card, described in Security score.
  3. The figures: Total Events, Attacks Blocked, Failed Logins and Pages Not Found over the last days, and DDoS Requests Blocked over the last 24 hours when the plan of the shop includes the DDoS protection (during an outage of the Sentinel service, see When the Sentinel service does not answer). Each one opens the matching events in Sentinel > Security Logs, except DDoS Requests Blocked, which opens Sentinel > DDoS Protection.
  4. Your protections and To do, side by side, described below.
  5. The Prerequisites Check card, described in Prerequisites Check.
  6. The other cards: Event Distribution, Top Suspicious IPs, Last Vulnerability Scan, Last Integrity Check, Brute-force Protection, DDoS Protection, Top attempted emails and Recent Activity.

Your protections​

The Your protections card gives the state of six protections, one row each, always in this order:

Above the rows, the counts sum them up: Active protections, Monitored protections and Inactive protections, then Protections requiring Pro when at least one row is Pro required.

States​

Each row gives its state with an icon and a word, so that it never depends on a colour alone:

StateIconWhat it means
ActiveA tick in a circleThe protection is on and acts.
MonitoringAn eyeThe protection records what it sees, but blocks nothing.
InactiveA circle with a dashThe protection is off, or on but unable to act.
Pro requiredA padlockThe plan of the shop does not include the protection.

Pro required only concerns the four Pro protections — threat detection, direct PHP file access, brute force and DDoS — on a plan that does not include them; access control and two-factor authentication are free and never show it.

Monitoring only exists for two rows:

  • Direct PHP File Access Protection, when the Auto Prepend protection is in place but threat detection is not active (see Signature detection on direct accesses).
  • DDoS Protection, when its Protection setting is on Monitor.

Notes under a row​

Under a row, a note sometimes says more about its state:

  • Waiting for signatures: threat detection is switched on, but the signatures it compares the requests with have not been downloaded yet.
  • Activation In Progress: the Auto Prepend protection is written but PHP has not read it yet, or an installation from the command line is waiting for the back office.
  • Needs fixing: the automatic installation of the Auto Prepend protection did not succeed.
  • Conflict with another auto_prepend_file: another auto_prepend_file is already configured on the server and prevents the automatic installation of the Auto Prepend protection (see Conflict with an existing prepend).
  • Empty list: nobody is blocked: the back office IP whitelist is switched on but its list is empty, and an empty list never blocks anyone.
  • No profile is required to use it: the two-factor authentication policy is switched on, but no profile is Required.
  • Subscription not verified: Sentinel service unreachable: the brute-force or DDoS protection is switched on, but the Sentinel service has not confirmed its subscription: at most 5 minutes after the service stops answering for the brute-force protection, after 7 days without an answer for the DDoS protection. The protection is suspended until the service responds.

A row with one of these notes is Inactive.

The two-factor authentication row​

The Two-factor authentication row follows the policy of the shop, not your own two-factor authentication: it is Active when the Enforce two-factor authentication on this shop switch is on and at least one profile is Required, on the Two-factor authentication tab of Sentinel > Configuration. Turning on two-factor authentication for your own account does not change it.

Adjust settings​

A row that is not Active carries an Adjust settings button, which opens its tab of Sentinel > Configuration: the Threat detection tab for the first two rows, then the Brute force, DDoS, Access control and Two-factor authentication tabs. A row that is Pro required has it too: its tab shows the Pro invitation. The button is only shown to an employee who can configure the Sentinel module (see Who can change the settings).

To do​

Next to Your protections, the To do card lists what is left to do to raise the security score: one entry per action of the score, in the same order as under the score, the action that gains the most points first.

Each entry gives the label of the action, sometimes a note under it, the points it would add to the score as +%points% pts, and a button that leads where to act:

  • Adjust settings: an action on one of the six protections, such as Enable threat detection or Require two-factor authentication. It opens the tab of the protection, like the button of its row in Your protections, and is only shown to an employee who can configure the Sentinel module.
  • Security Scanner: an action on the vulnerability scan, such as Run a scan. It opens Sentinel > Security Scanner.
  • Integrity Check: an action on the integrity check, such as Run a check. It opens Sentinel > Integrity Check.
  • Upgrade Now: the Upgrade to Pro action, which gathers the protections the plan does not include and lists them in its note. It opens the Pro offer in a new browser tab or, when no offer is known, the General tab of Sentinel > Configuration for an employee who can configure the Sentinel module.

The note under an entry says more when there is more to say: under the threat detection action, The signature database has not been downloaded yet. Threat detection is inactive until signatures are available. as long as the signatures are missing; under Fix the direct PHP file access protection, Its automatic installation could not be completed on this server. when its row has the note Needs fixing, and Another auto_prepend_file already configured on this server prevents its automatic installation. when it has the note Conflict with another auto_prepend_file.

Once the prerequisites check has run, each of its categories that is not met joins the end of the list: PHP Configuration, Directories or Secure origin, with the number of items not met followed by issue(s) detected (2 issue(s) detected, for example), and a View Details button that opens the details of the category, as its row in the Prerequisites Check card does. These entries add no points: the prerequisites do not count in the security score.

When nothing is left to do, the card says Nothing to do for now.