Portfolio Site Auditor
Every server reports daily — silence is an alert too
Our in-house service for the servers and sites we deploy and maintain. An agent on each server collects what needs updating, which packages are vulnerable and whether there are suspicious files, and the panel brings it all into one picture and messages Telegram at once when something is urgent.
Project
Site Auditor
- Client
- Asign — for the servers and sites we maintain More than 25 servers with sites, and we are responsible for the security and updates of each one.
- System
- Agents on servers and a central audit panel Agents only report, the panel only shows and warns: access to the panel gives no way to change anything on the servers.
- Our role
- Architecture, agent, back end and panel Plus alert rules, the daily summary, agent tests against false positives, and deployment.
- Technologies
-
- PHP
- Laravel
- Filament
- Livewire
- MariaDB
- Redis
- Control
- History of changes and alerts You can see when an alert opened, who reviewed it and when the problem was closed.
Task
Dozens of servers, and something ages on each
Every server lived its own life: one was waiting for system updates, another had a site library with a known vulnerability, a third wanted a reboot. Seeing this meant logging into each one separately.
One picture instead of rounds
The state of all servers and sites must be visible in one place, without checking each by hand.
Vulnerabilities before attackers
A vulnerable package in a site must be known as soon as it becomes public, not after an incident.
Suspicious files
Malicious code in a site’s files must be noticed, even if the site works as usual.
Not drowning in notifications
Urgent things must arrive at once, while small ones must not wake anyone at night or bury the important among noise.
Solution
The agent reports, the panel decides, Telegram warns
An agent on every server
A light agent collects system updates, reboot needs, service and disk health, and vulnerable and outdated site packages every day, and checks site files for malicious code twice a day. It always reports, even with an error — so a server that went silent is an alert too.
The panel only reads
The panel receives reports and changes nothing on the servers. Each server has its own token, and data from a server is treated as untrusted and validated before it reaches the database or a message.
An alert is a state
An alert opens, reminds while the problem persists, and closes with a separate message. Critical and high go to Telegram at once, the rest to the morning summary and the dashboard.
Capabilities
Audit of every server in one panel
01 · 4
Server
- System and security updates
- Reboot required
- Service health
- Free disk space
02 · 4
Sites
- Vulnerable packages with severity
- Outdated packages by update type
- Malicious code check of files twice a day
- “Reviewed” and “false positive” marks
03 · 4
Alerts
- Critical — to Telegram at once
- Reminders until the problem is closed
- A message when the problem is fixed
- Morning summary of all servers
04 · 4
Control
- Dashboard of servers needing attention
- Statistics and charts by period
- A separate token for each server
- Admin and viewer roles, activity log
Result
Every server’s state is visible each morning
Instead of rounds of servers — one panel showing what to update, what is vulnerable and what looks suspicious. Urgent things arrive in Telegram at once, the rest waits in the morning summary.
And if a server stops reporting, that is noticed the same day too.