One platform, from the kernel to the auditor

More than twenty-five screens on one stream of data. The panel is grouped the way you work: watch what happens, fix what is weak, know what you run, and respond with a click — from the kernel to malware, threat intel and compliance.

What it watches

One agent per machine reads what the machine already records, adds a sensor in the kernel and sends it all to your hub as one stream. In brackets: where the data comes from.

Attacks as they happen

Streamed to your hub within seconds.

  • Process and file activity

    Shells inside containers, reads of /etc/shadow, replaced binaries, odd outbound connections. (the kernel, through eBPF)

  • Logins

    Every SSH login and failed attempt, new source addresses, a success right after a run of failures. (SSH journal)

  • Attack blocking

    Brute force and scans already stopped, by scenario, country and network. (the machine's blocklist)

  • Web attacks

    Injection probes, path scans and vulnerability scanners, per site and per address. (Traefik and nginx logs)

  • Containers

    Every start, stop, crash and restart, with the image, ports and limits of each container. (Docker)

Weak spots, before someone finds them

A quick check every 10 minutes, a full scan every night.

  • Vulnerabilities

    Known CVEs in packages and images, ranked by real exploitation and how likely it is. (packages, images, CISA KEV and EPSS)

  • System hardening

    An audit of the operating system's settings, with the change to make for each finding. (system settings)

  • Secrets in code

    API keys, tokens and passwords committed to repositories on the machine, reported redacted. (repositories on disk)

  • Configuration drift

    New accounts, SSH keys, open ports, cron jobs, services and packages: what changed since the last look.

The machine itself

A full disk takes a site down as surely as an attack.

  • Host health

    Disk wear, RAID state, temperatures, the age of the last backup and TLS certificates before they expire.

  • Performance

    CPU, memory, network and disk for every host and every container, measured against their limits.

Inside the panel

Simplified views of the panel's screens, filled with example data.

Related events become one incident

A web probe, a shell in a container and an outbound connection two minutes later are one attack, not three alerts. SkyShield joins them into one story with a timeline, the hosts and containers involved, and the MITRE ATT&CK technique behind each step.

IncidentsExample data

Web probe, then a shell in shop-api

web-1.example.com, container shop-api, 4 events in 4 min

Critical Contained
  1. SQL injection probes from 203.0.113.77 on shop.example.com

    T1190 Exploit public-facing application Traefik log

  2. Shell spawned by node in container shop-api

    T1059.004 Unix shell Kernel sensor

  3. Outbound connection to 203.0.113.140 on port 4444

    T1571 Non-standard port Kernel sensor

  4. Blocked both addresses on 6 of 6 hosts

    Approved by you Blocklist

Example incident with four related events, their times, sources and ATT&CK techniques.

Every machine and container on one live map

Hosts, containers and the links between them, drawn from what the agents see. Pick one bundle, such as a shop and its databases, and the rest steps back.

TopologyExample data
Example topology: four hosts with their containers. The shop bundle (traefik, shop-web, shop-api, postgres and redis) is in focus; shop-api has an open alert.

Block an address everywhere, after you say yes

Ask to block 203.0.113.77 and every machine applies it within seconds. Nothing runs without your approval, and every request, approval and result lands in the audit log.

ApprovalsExample data

Block 203.0.113.77 for 7 days

On all 6 hosts, through each host's blocklist. Suggested by incident 412.

Audit log

  1. Applied on 6 of 6 hosts, last one after 3 s
  2. Sent to web-1, web-2, db-1, ci-1, mail-1, backup-1
  3. Approved by you
  4. Requested by incident 412
Example approval request to block one address on all hosts, with the audit log of request, approval, delivery and result.

Fix these ten first

Hundreds of CVEs, sorted by what attackers actually use: known exploitation from CISA KEV, likelihood from EPSS, and how many machines carry each one. The panel shows how much of your risk each fix removes, so the top of the list does most of the work.

VulnerabilitiesExample data

These 10 fixes remove 80 % of the risk

312 open CVEs on 6 hosts and 41 containers

CVE Package Exploited EPSS Hosts
CVE-2021-44228 log4j-core KEV 94 % 2
CVE-2021-4034 polkit KEV 86 % 3
CVE-2023-4911 glibc KEV 71 % 4
CVE-2023-44487 nginx KEV 62 % 2
CVE-2022-0847 linux KEV 45 % 1

and 5 more in the plan

Example fix plan: the first five of ten CVEs that together remove 80 percent of the risk score.

Health and performance next to security

A worn disk, a degraded RAID, a certificate that expires on Sunday or a container near its memory limit are risks too. They sit next to the security findings, per host and per container.

HealthExample data

web-1.example.com

  • Disk nvme0 wear37 %OK
  • RAID md0cleanOK
  • CPU temperature54 °COK
  • Last backup7 h agoOK
  • TLS shop.example.com12 days leftRenew

Memory against limit

  • shop-api1.7 of 2 GB
  • postgres2.4 of 4 GB
  • shop-web220 of 1024 MB
  • traefik92 of 512 MB
Example health checks for one host, all fine except a TLS certificate with 12 days left, and memory use of four containers against their limits.

How it works

  1. Install one agent per machine

    One command on each server. The agent connects out to your hub; it opens no ports. Your enrolment key — the --token below — is ready the moment you sign up: copy it from the panel.

    Install
    curl -fsSL /app/install.sh | sudo bash -s -- --token …
  2. It reads the host, not your containers

    Docker, the system journal, proxy logs and the kernel, all from the host. Nothing to install or change inside your containers.

  3. The hub keeps it, you watch it live

    Events land in a fast event store on your hub, findings and state next to them. The panel streams new events as they arrive.

  • web-1 agent
  • db-1 agent
  • ci-1 agent
  • Docker
  • journal
  • eBPF
  • proxy logs
  • scanners
Hub events, state, rules and incidents
Panel in your browser
Diagram: an agent on each machine sends events outbound to the hub, which stores them and streams them live to the panel in your browser.

Light on your servers

The agent stays out of the way of the services the machine is there for. Measured on a hypervisor and on a Docker host running 110 containers:

Agent memory
70–85 MB
Agent CPU
0.5–2.5 % of one core
Kernel sensor memory
90–125 MB
Full scans
nightly, lowest priority

These are typical numbers, not guarantees: they grow with the number of containers and the volume of events. Limits come from the agent's systemd unit (CPU quota 30 %, memory slowed above 1 GB and stopped at 1.5 GB). Full scans run at 02:30 local time at nice 19 and idle I/O priority, inside the same memory ceiling; a quick check without the heavy scanners runs every 10 minutes.