Configure, verify and manage Sentinel with clear steps.

Before installation, check the system requirements on the Compatibility. You need administrative privileges, access to system repositories and outgoing connectivity to Sentinel services. Each agent must use the credential generated for its server record.

1. 1
   Create record

   In the panel, open Servers, select “Add server” and enter the required details.

2. 2
   Copy the generated command

   Use the command shown for that server: it contains a dedicated credential and the correct endpoint.

3. 3
   Run it on the machine

   Start the command with administrative privileges. Do not publish the API key, include it in logs or reuse it on another server.

4. 4
   Check the heartbeat

   The record should come online and show a consistent hostname, IP address, version and last connection time.

The agent gRPC endpoint uses the format host:port, without https://. Always copy the value produced by the panel; if you enter it manually, do not turn it into a web URL.

sudo sentinel-agent --check
sudo systemctl status sentinel-agent --no-pager
sudo journalctl -u sentinel-agent -n 50 --no-pager

The main configuration is located in /etc/sentinel/agent.yaml. The file also contains credentials and must remain readable only by administrators. Before editing it, create a backup, preserve the YAML indentation and validate the result with --check.

agent:
  server_url: "sentinel.gtechgroup.it:9090"
  api_key: "<PANEL_GENERATED_API_KEY>"

tls:
  enabled: true
  skip_verify: false

blocker:
  backend: "auto"
  chain: "SENTINEL"
  whitelist_defaults: true
  whitelist_entries:
    - "<ADMIN_IP_OR_NETWORK>"

The WAF protects only traffic that is actually routed through its listener. Enabling the module in the agent does not by itself change the Nginx, Apache or hosting-panel traffic path.

The plugin adds a protection layer inside WordPress and sends inventory, status and security events to the panel. It does not replace updates, backups or server hardening; when the edge WAF is available, the two layers operate at different points.

1. 1
   Register the domain

   In the WordPress section of the panel enter the exact public URL of the site.

2. 2
   Generate the token

   Use the one-time token only on the domain for which it was created.

3. 3
   Install the package

   Download the ZIP available in the panel, upload it in WordPress and activate Sentinel Security.

4. 4
   Complete the link

   Open Sentinel from the WordPress side menu, enter the panel URL and token, then confirm that the site is connected.

5. 5
   Leave Observe initially

   Review charts, events and compatibility before increasing the protection level.

The scanner looks for known indicators and suspicious patterns; the File Integrity Monitoring highlights changes to the monitored files. A result is a signal to verify, not automatic proof that a file is malicious.

Before a full scan check available space, load and maintenance windows. On WordPress sites you can start scanning from the plugin page or from the site detail in the panel when the link is active.

WordPress quarantine isolates a suspicious file in an encrypted, reversible form. The scanner does not delete suspicious files automatically: an administrator must confirm the action after reviewing the context.

Server agent

The panel identifies outdated agents and can request an update when the installed version supports managed updates. If the remote command is not executed, the server details page shows the manual procedure to be performed directly on the machine.

sudo apt-get update
sudo apt-get install --only-upgrade sentinel-agent \
  -o Dpkg::Options::=--force-confold
sudo systemctl restart sentinel-agent
sudo sentinel-agent --check

WordPress Plugin

WordPress queries the Sentinel API for availability, version, package URL and checksum SHA-256. The update is only applied if the downloaded package matches the published checksum. After the update, check the version, connection, heartbeat and events.