SG
Safe Guard Live Demo demo.security.clients.help
CONTROLLED LAB
LIVE DEMONSTRATION LAB

Safe Guard Live Demo

A real Linux host, real scenarios, real timelines — and labels on every claim.

CONTROLLED LAB EVENT VERIFIED ON THIS LAB OBSERVED IN PROVIDED REPORT MANUFACTURER CLAIM NOT REPRODUCED
Clients.Help Security audits, installs, configures and monitors. The technology layer is powered by E-ZETTA Safe Guard. Clients.Help is not the original vendor of the technology.
Read this before you read anything else.

No E-ZETTA Safe Guard agent is installed on this host. No official installer, package or enrollment mechanism was available to us, so we did not invent one. Everything you can trigger below is a controlled lab scenario that we wrote and that runs on this machine. It is labelled CONTROLLED LAB EVENT everywhere it appears. It is not a Safe Guard product detection, and we will not present it as one.

01

Laboratory status

Live state of this demonstration host, read from the machine you are talking to.

DEMO APPLICATION
LAB TARGET
LIVE STREAM
ACTIVE RUN
RUN BUDGET
APP UPTIME
02

Detection → Response → Recovery

Live mode streams events from the host as a scenario runs. Replay mode plays back a finished run, event by event, from its stored evidence.

DETECTION
RESPONSE
RECOVERY
Connecting to the live stream…
03

Safe scenarios

CONTROLLED LAB EVENT

Six scenarios, allowlisted by id. They touch loopback and a disposable lab directory — nothing else. You cannot supply a command, a URL, an IP or a file path: the API accepts an allowlisted scenario id and nothing more.

Guards on every run

Allowlist · timeout · rate limit · queue · one active run at a time · automatic reset to baseline · append-only audit trail. A run that fails or times out still resets the lab.

04

What you are actually looking at

Written for the person deciding whether to spend money, not for a search engine.

QuestionHonest answer
05

Claims, with their evidence class

Every capability carries exactly one label. Labels are the product here — a claim without one is marketing.

ClaimClassBasis
06

Where this fits — and where it does not

The second column is the one worth reading. Most vendors do not print it.

✓ GOOD FIT
    ✕ NOT A FIT
      07

      DevOps technical details

      How this box is actually wired. Verified on this lab.

      ComponentDetail
      08

      Evidence downloads

      Every completed run writes a bundle: timeline, scenario definition, requested action, events, logs, before/after state, an HTML report, a zip, and SHA256SUMS so you can verify none of it changed after we handed it to you. Bundles contain no secrets.

      EVIDENCE BUNDLES
      09

      Sample customer report

      This is the shape of what a client receives after an audit engagement. Run a scenario above and this becomes a real, downloadable report for that run.

      10

      Next step

      The offer is a human-run server audit. There is no self-serve trial, and we are not going to pretend there is one.

      SERVER AUDIT

      Request a server audit

      A human looks at your Linux server and tells you what is already hitting it. We will show you the log lines, labelled — including the ones that did not turn up anything.

      security.clients.help →
      CLIENTS.HELP

      Clients.Help

      The wider Clients.Help practice: the people who audit, install, configure and monitor the defence layer for you.

      clients.help →