Security 360 · Code analysis
Every night, the SOC reads each website's logs and code: errors, SQL, insecure code, malware and server errors, file by file. When it finds a flaw, it prepares the exact change and waits for you to approve it. And if the server suffers a load spike, it tells you whether it was an attack or your own code.
- $total = $precio * $_GET['cantidad'];- echo $total / $descuento;+ $cantidad = isset($_GET['cantidad']) ? (int) $_GET['cantidad'] : 0;+ $total = $precio * $cantidad;+ echo $descuento > 0 ? $total / $descuento : $total;
Every night
The SOC reads the web server logs and each website's code. It scores the risk, counts errors by type and takes you to the file and the line.
SOC › Code
Risk from 0 to 100, code and SQL errors, insecure code warnings, files with malware and server errors. Beside it, how the website responds and the trend of the latest analyses.
Code fixing
When the analysis finds an error it knows how to fix, it prepares the change. It shows you which lines change, why and what risk it carries. Until you approve it, your website isn't touched.
Code fixes
A division by zero, an SQL query that pastes the URL's id without escaping it, or a website that shows its PHP errors to visitors. Each fix with its file and its diff, in red and green.
Fix details
The problem, the change's risk, the language, the file and the fix's history step by step: who proposed it, who approved it and when it was applied.
The analysis prepares the change. Your website hasn't been touched.
You've reviewed it and it's ready to apply.
The file now has the green lines. With who did each step.
If something goes wrong, you undo it and the file goes back to the red lines.
Errors versus load spikes
Failing code also burns CPU. The SOC takes each server spike and looks at what was happening that hour: attacks, crawls, a single IP or a website's errors. And it suggests what to do.
SOC › Trends
Nine spikes in 30 days on a test Cloud. One was a website that was failing: 35 code errors, 12 5xx responses and 3 timeouts in that hour. From the spike you go to that website's code.
AI plan
The AI reviews the spike and proposes: block the IP or bot that caused it, apply server adjustments or, if needed, block a country or add resources. Everything it applies expires.
Vulnerability scans or injections from one or several IPs.
Code errors, 5xx responses and timeouts from a specific website.
One IP hogs the hour without being flagged as an attack: usually an aggressive crawler.
Many requests to pages that don't exist.
Web traffic doesn't explain it: time to look at processes, backups or scheduled tasks.
It's a coincidence, not a measurement: the logs don't say how much CPU each request used. They say what was happening on the website at the hour the server was suffering.
Reports
To show a customer or keep for an audit. They're real examples on swpanel.com with fictitious data, in Spanish, Catalan and English.
The programming errors left in Apache or Nginx logs, file by file, with each fix and the malware analysis. Premium version, with an executive security summary.
SW-COD-… 73 pages
A service's security month: NGFW threats, SOC findings, blocked countries and bots, code analysis, adaptive WAF, what was done and next month's plan.
SW-S36-… 47 pages
What the NGFW detected and blocked in a period: by severity, type and origin, the changes over the last six months and what to do first.
SW-NGF-… 29 pages
Each document carries a unique number and token linking it to the original stored in SWPanel. How it's verified.
All the reports and certificates SWPanel issues, in Reports and certificates. For a complete one-off report of a website, the code audit.
Compared
Frequently asked questions
The Security module comes already enabled at no cost in your account. Add Security 360 to each hosting, Cloud or server you want to protect.
