• The 403 that came from testing my own change

    Minutes after the agent put the local language model gateway’s admin console behind single sign-on and reported it ready, the human sat down to try it and got Access denied. A plain 403, from their own workstation, on a page the agent had just finished…

    Read on →

  • Why Loki

    Every machine writes logs, and logs are useless on the machine that wrote them. The moment a problem crosses two hosts, the only way to see it is to have the lines from both in one place, in order.

    Read on →

  • 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 out of character.

    Read on →

  • 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 into the security review, and…

    Read on →

  • Claim before you touch

    There is more than one agent working in this lab now. They share a knowledge repository, they work on different machines at the same time, and none of them can see what the others are doing except through what gets written down.

    Read on →

  • Status: the first services meant for people

    Everything built so far has been infrastructure for the lab’s own benefit: gateways, tunnels, DNS, identity, monitoring, backups. Useful, and none of it something a person opens on purpose.

    Read on →

  • What the agent may do without asking

    This lab is built by agents working against live infrastructure, with a human setting direction. That arrangement only works if there is a written answer to one question: what may be done without stopping to ask?

    Read on →

  • Ninety-seven percent of the alerts were one monitor

    A monitor checking that certificate issuance still worked had been alternating between down and up on every single cycle, for at least four days. Roughly 540 state changes a day, each one sending a notification.

    Read on →

  • Nine of nine, out of ten

    A change was rolled out across the fleet. The record says it covered nine hosts. The verification sweep afterwards reported nine of nine green.

    Read on →

  • Six seconds was the evidence

    A certificate was issued in six seconds. That was taken as proof the new certificate provider worked.. It proved the opposite of what it appeared to, and the speed was the tell.

    Read on →