Set the address Guard servers should use. FQDN is preferred when supplied. Names are added to the HTTPS certificate without replacing your trusted CA.
Save before exporting. Changing the advertised port does not change the listening port or firewall. Use a different port only when a trusted TLS passthrough proxy or port mapping is already configured. DNS resolution must work on every Guard server.
Enter the Datacenter administrator token. It can be recovered or reset locally by an administrator while the Datacenter service is stopped.
Only enable in your private browser profile on a trusted device. The token is not stored in plaintext browser storage.
Packages expire after one hour and enroll one server only. Copy them through a trusted administrator channel. Never include private CA keys.
| Server | Status | Version | License / lease | Blocks | Events | Collectors | TLS / certificates | Policy |
|---|
A lightweight operational view across all enrolled Guard servers. Events stay on-premises in Datacenter and are grouped for rapid triage.
| Source | Country | Events | Blocked | Last seen |
|---|
| Server | Events | Blocked | Unique sources |
|---|
| First / last | Server | Source / attempts | Country | Collector | Summary | Outcome |
|---|
| First / last | Source / attempts | Country | Collector | Protocol | Summary | Decision | Score | Enforcement |
|---|
| IP | Country | Created | Expires | Reason |
|---|
Public IP addresses here are distributed as desired state to Guard servers whose policy enables shared blacklist application. Permanent blocks can also be promoted automatically from selected Guard servers.
| IP | Created | Source | Reason |
|---|
Trusted addresses are learned from repeated successful authentications on Guard servers and distributed as desired state. These addresses are protected from ordinary blocking and are reserved as panic-room exemptions.
| IP | First seen | Last seen | Source | Reason |
|---|
Distributes the AbuseIPDB API key and reputation policy to managed Guards. Saved credentials remain in Datacenter; leaving the API-key field blank preserves the existing key.
Correlates attacker IP addresses with OTX pulses and tags. OTX is enrichment-first; automatic blocking remains opt-in and Guard safelists always win.
Distributes CrowdSec LAPI/bouncer settings to managed Guards. Guard consumes IP ban decisions and applies them through its own firewall provider while retaining CrowdSec provenance.
Global Reputation is a licensed Scantide service. Datacenter automatically provisions and retains its service identity; administrators do not manage client UUIDs or secrets.
Credentials used by managed Guards for Scantide CVE, lifecycle and supported enrichment services.
Optional read-only CMDB integration. Leaving the secret/token blank preserves the saved value.
Datacenter is a licensed Scantide product. Requesting a license establishes the installation identity used to enroll Scantide-hosted services such as Global Reputation. Service credentials are provisioned automatically and are not normally shown to administrators.
The license key is also emailed to the account address. Global Reputation client IDs and secrets are created and stored automatically when the feature is enabled.
This separate Scantide Guard fleet license is distributed to managed Guard agents and controls their floating seats. It is distinct from the Datacenter product license above and from the Scantide API account used for assessments and enrichment.
Includes servers and supported workstation endpoints enrolled in this Datacenter. A host appears here while it reports a Licensed or Trial state with an active lease.
| Host | OS | Version | State | Lease expires | Last seen |
|---|---|---|---|---|---|
| No seat data loaded. | |||||
Saving updates the central Guard licensing credentials and bumps policy revisions so managed agents receive them on their next normal policy poll. Existing server-specific policy overrides do not override these licensing credentials.
Datacenter verifies the SHA-256 in the Scantide HTTPS manifest before launching the installer. Notify-only is the beta default.
Scantide Guard and Datacenter are actively developed and tested in operational environments, but have not been validated across every infrastructure, application stack, network topology or deployment scenario. Administrators should test potentially disruptive functionality where practical and maintain backups, recovery procedures and alternative administrative access.
Security detections, vulnerability/reputation intelligence and automated decisions may be incomplete, delayed or affected by third-party services. No security product can guarantee detection or prevention of every threat.
To the maximum extent permitted by applicable law, Scantide and its owners, developers, affiliates, partners, licensors and service providers are not responsible for service interruption, outages, loss of availability, data loss, blocked access, missed detections, false positives, certificate/TLS/firewall effects, business interruption or other direct or indirect consequences arising from installation, configuration, use, misuse or inability to use Scantide software or services.
Operational disclaimer revision 2026-10-01 · Scantide Guard Datacenter 0.8.4Install Scantide Verified or community monitor packs into Datacenter, review them, then enable them for managed Guards. Installed packages are distributed as policy without replacing locally created monitors.
Maximum catch window: 30 days. Username matches are case-insensitive and restricted to trusted authentication sources; successful logins and protected addresses are exempt. When fleet propagation is enabled, the first trusted match on one server becomes a permanent shared Datacenter block for the managed fleet.
Editable policy: removing a built-in rule is persistent. Guard will not silently add it back on restart or Datacenter refresh. A bare * rule is rejected because it would match every request. Use the reset buttons to restore the Scantide baseline.
Separate from Datacenter's internal shared blacklist. Choose whether managed Guards contribute eligible high-confidence threat observations to Scantide Global Reputation.