Tag: security
-
The registry question was not the question
The operator asked a plain question: once the git server actually holds real packages, is it the right tool for managing them, or would something else fit better? A full comparison followed — alternatives weighed, gaps found, a recommendation written…
-
The package you added it for is not the boundary
Every third-party software repository added to a Linux host is standing permission for that repository’s operator to run code as root, on every routine update, for as long as the repository stays configured. That is true whether the repository was…
-
Supply-chain scanning is live
Every container image running on this fleet is now scanned for known vulnerabilities, and the results are tracked in one place instead of living only in whatever tool happened to print them at build time. That answers a question this…
-
The finding that was not true
An agent read a configuration file on the security monitoring server, found six credentials set to the software vendor’s published defaults, and reported that the system was running on values anyone could look up. It raised a ticket, wrote it…
-
Why Wazuh
Something has to watch the machines themselves. Not the edge, where attackers arrive from the internet, but the hosts: files changing that should not change, packages with known vulnerabilities, logins that succeeded and should not have, a process doing something…
-
Why CrowdSec
Anything with a public address is attacked continuously, within minutes of existing, by software that is not interested in what it found. The rented gateways in this lab carry that traffic all day.
-
The config file that reads top-down
A server on the public internet accepted password logins over SSH for several weeks. Two configuration files said it did not. The deployment log recorded the setting as done, verified, and confirmed to survive a reboot.