<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: AA</title>
    <description>The latest articles on DEV Community by AA (@als_admin).</description>
    <link>https://dev.to/als_admin</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4248114%2F4db83f48-c4e2-4181-b39f-f934ae8f0e21.png</url>
      <title>DEV Community: AA</title>
      <link>https://dev.to/als_admin</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/als_admin"/>
    <language>en</language>
    <item>
      <title>I got tired of self-hosting Wazuh and paying enterprise EDR prices, so I built my own Linux host agent</title>
      <dc:creator>AA</dc:creator>
      <pubDate>Mon, 16 Nov 2026 17:27:05 +0000</pubDate>
      <link>https://dev.to/als_admin/i-got-tired-of-self-hosting-wazuh-and-paying-enterprise-edr-prices-so-i-built-my-own-linux-host-4fbf</link>
      <guid>https://dev.to/als_admin/i-got-tired-of-self-hosting-wazuh-and-paying-enterprise-edr-prices-so-i-built-my-own-linux-host-4fbf</guid>
      <description>&lt;p&gt;f you run a handful of Linux servers for a small team and nobody's full-time job is "security" your options for host defense kind of suck.&lt;br&gt;
On one end, you have Wazuh. It's free and powerful, which is great until you realize you now have a second full-time job hosting, tuning, and babysitting an ELK/OpenSearch stack just to figure out why an alert fired. On the other end, you have CrowdStrike or Datadog security add-ons priced for enterprise compliance budgets, built for fleets of 5,000 endpoints, and usually handing you opaque risk scores instead of telling you what actually happened on the box.&lt;br&gt;
I wanted something in the middle: a single lightweight binary I could drop onto a Linux server or Docker host in 60 seconds that watches processes, network connections, files, and SSH logins, explains what's going on in plain English, and takes bounded, reversible actions without bricking production at 3 AM.&lt;br&gt;
So I built Vigilhold.&lt;/p&gt;

&lt;p&gt;The core problem with "autonomous" security tools&lt;/p&gt;

&lt;p&gt;Most developers don't trust automated remediation on production Linux boxes, and honestly, they shouldn't. If an agent hallucinates a threat and kills systemd or locks out your deploy user's IP, your security tool just caused an outage.&lt;br&gt;
When designing Vigilhold (and its backend decision engine, Cortex), I set three hard rules:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Strict autonomy boundaries. You configure what the agent is allowed to do on its own, host by host. By default, it will automatically ban obvious attacking IPs (like SSH brute-forcers), while anything disruptive killing a process, quarantining a file, isolating a host stops and asks for human approval first (you can approve or reject straight from Slack or the dashboard). If you want full Autopilot on non-critical boxes, you can turn it on.&lt;/li&gt;
&lt;li&gt;Everything has an undo button. Bans, file quarantines, and lockdowns are designed to be reversible, and every single step is written to a tamper-evident audit log. When you override or correct a decision, future decisions on that server actually take your feedback into account.&lt;/li&gt;
&lt;li&gt;Offline survival. If the backend goes unreachable, the local agent doesn't go blind it keeps blocking SSH brute-force attempts and already-flagged bad actors locally within your configured limits.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Don't trust my marketing watch a live box get attacked&lt;/p&gt;

&lt;p&gt;Security landing pages are full of fake dashboard screenshots and "AI-powered threat theater." I hate that stuff.&lt;br&gt;
Instead, I spun up a disposable Ubuntu VPS on the public internet, installed the Vigilhold agent on it, and made the feed completely public at vigilhold.com/lab.&lt;br&gt;
There are no customer workloads on it just a bare public IP taking real hits from bots and scanners every few minutes. You can watch the raw SSH attempts, process signals, and automated blocks roll in live (delayed by 30 minutes to the nearest quarter-hour so attackers can't use the feed to time the box).&lt;br&gt;
If you want to test it yourself without creating an account first, there's also an interactive sandbox at vigilhold.com/demo where you can trigger simulated threats and see how the plain-language breakdown and IP banning behave.&lt;/p&gt;

&lt;p&gt;Under the hood &amp;amp; how it runs&lt;/p&gt;

&lt;p&gt;Installing the agent is an outbound-only one-liner (no firewall ports to open, and a single command cleanly uninstalls it):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -fsSL https://vigilhold.com/install &lt;span class="o"&gt;|&lt;/span&gt; sudo bash -s -- --token &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;your-token&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Once it's running:&lt;br&gt;
• Signals watched: Process execution, network sockets, file integrity changes, SSH auth logs, and Docker container activity.&lt;br&gt;
• No hosting overhead: You don't manage collectors, indexers, or rule pipelines.&lt;br&gt;
• Clear shipping status: Because I'm building this independently (no VC bloat, just shipping code out of Utah at Al's-Ops), I keep a public Feature Status page labeling every single capability as LIVE, BETA, or ROADMAP so nobody has to guess what actually works today.&lt;/p&gt;

&lt;p&gt;Try it out (or roast my architecture)&lt;/p&gt;

&lt;p&gt;If you manage 1 to 25 Linux boxes and want host security without hiring a SOC analyst or maintaining an Elastic cluster, you can spin up a 14-day free trial (no credit card required) at vigilhold.com. After that, it's $39/month for up to 5 servers.&lt;br&gt;
If you're a Linux sysadmin or security engineer, I'd genuinely love your feedback:&lt;br&gt;
• What's the one automated action you would never let a host agent take on your servers without human sign-off?&lt;br&gt;
• If you check out the live public lab or demo, what signal or context is missing that you'd want to see during an incident?&lt;br&gt;
Drop a comment below - I'll be hanging around all day to answer questions about how the agent and rule scoring work.&lt;/p&gt;

</description>
      <category>linux</category>
      <category>security</category>
      <category>devops</category>
      <category>showdev</category>
    </item>
    <item>
      <title>How I stopped getting paged at 3am for raw SSH logs (and built a host agent for Linux)</title>
      <dc:creator>AA</dc:creator>
      <pubDate>Mon, 16 Nov 2026 16:15:50 +0000</pubDate>
      <link>https://dev.to/als_admin/how-i-stopped-getting-paged-at-3am-for-raw-ssh-logs-and-built-a-host-agent-for-linux-2ohg</link>
      <guid>https://dev.to/als_admin/how-i-stopped-getting-paged-at-3am-for-raw-ssh-logs-and-built-a-host-agent-for-linux-2ohg</guid>
      <description>&lt;p&gt;If you run your own Linux boxes, you already know what &lt;code&gt;/var/log/auth.log&lt;/code&gt; looks like five minutes after spinning up a fresh VPS. &lt;/p&gt;

&lt;p&gt;Nobody knows the IP. You haven't pointed a domain at it yet. Still, automated scanners find it almost immediately and start hammering port 22 with &lt;code&gt;root&lt;/code&gt;, &lt;code&gt;admin&lt;/code&gt;, &lt;code&gt;ubuntu&lt;/code&gt;, &lt;code&gt;postgres&lt;/code&gt;, and &lt;code&gt;deploy&lt;/code&gt;. &lt;/p&gt;

&lt;p&gt;Most security tools handle this in one of two ways:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;They dump thousands of raw, disconnected logs into a dashboard and leave you to piece together what happened at 3:14 a.m.&lt;/li&gt;
&lt;li&gt;They cost five figures a year and require a dedicated security engineer just to tune the rules.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I got tired of both, so I built &lt;strong&gt;&lt;a href="https://vigilhold.com" rel="noopener noreferrer"&gt;Vigilhold&lt;/a&gt;&lt;/strong&gt; (under &lt;a href="https://alsopss.com" rel="noopener noreferrer"&gt;Al's-Ops LLC&lt;/a&gt;) - a lightweight host agent for Linux servers and Docker hosts that watches process, network, file, and SSH signals, tells you what is actually happening in plain English, and acts only within the boundaries you set.&lt;/p&gt;

&lt;h3&gt;
  
  
  We killed the fake demo and put up a live lab server instead
&lt;/h3&gt;

&lt;p&gt;One thing that always bugged me about security landing pages is the "interactive demo" full of canned, sanitized data where everything looks neat and tidy.&lt;/p&gt;

&lt;p&gt;So we got rid of the demo. Instead, we put up a &lt;strong&gt;live public lab&lt;/strong&gt; right on &lt;a href="https://vigilhold.com" rel="noopener noreferrer"&gt;vigilhold.com&lt;/a&gt;. &lt;/p&gt;

&lt;p&gt;It is an ordinary, unadvertised VPS sitting on the public internet running the actual Vigilhold agent. No login required. You can open the lab feed and watch real bots try to brute-force it around the clock (it averages around 1,600 login attempts a day from over 100 different IPs) with a 30-minute delay. You see the exact signals the agent picks up, how it correlates them, and what it blocks.&lt;/p&gt;

&lt;h3&gt;
  
  
  How it actually works under the hood
&lt;/h3&gt;

&lt;p&gt;I didn't want a bloated agent that opens inbound ports or tries to guess what's malicious using a black-box neural network. Here is how we structured it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Deterministic rules first, not AI guesswork:&lt;/strong&gt; Decisions come from written rules and scoring, not a trained AI model. If you enable it, Claude is used strictly to write out longer plain-language investigation summaries—it never decides whether to ban an IP or kill a process.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Privilege separation &amp;amp; outbound-only:&lt;/strong&gt; The agent runs as an unprivileged user, paired with a small root helper for fixed tasks. It only makes outbound TLS connections, so you don't have to poke holes in your firewall.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;One-command install (including Docker):&lt;/strong&gt; You can drop it onto Ubuntu, Debian, RHEL-compatible distros, Amazon Linux 2023, Arch, or Alpine with a single &lt;code&gt;curl&lt;/code&gt; command. If you run Docker, one &lt;code&gt;docker run&lt;/code&gt; on the host watches both the underlying machine and every container on it—no per-container sidecars needed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Offline resilience:&lt;/strong&gt; If the control plane ever goes unreachable, the agent keeps enforcing the last-synced policy locally and logs everything it does until it reconnects.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Guardrails: Observe, Assist, and Autopilot
&lt;/h3&gt;

&lt;p&gt;Giving a tool permission to kill processes or lock down a production box is nerve-wracking. Every account starts in &lt;strong&gt;Assist&lt;/strong&gt; mode by default:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Observe:&lt;/strong&gt; Watch-only. It alerts you, and you make every call.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Assist (Default):&lt;/strong&gt; Automatically hands out temporary bans to IPs actively brute-forcing SSH, web (WordPress), mail (Dovecot/Postfix/Exim), or FTP. Anything disruptive-like killing a suspicious binary running out of &lt;code&gt;/tmp&lt;/code&gt; or isolating a host—waits for your one-click approval in the dashboard or Slack.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Autopilot:&lt;/strong&gt; Acts automatically on confirmed high-confidence threats within your configured limits, while uncertain stuff still waits for a human.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Every single action—whether triggered by a rule or a teammate—gets written to a hash-chained, tamper-evident audit log. And if it ever bans an office VPN range or quarantines something by mistake, bans, quarantines, and lockdowns are reversible with one click.&lt;/p&gt;

&lt;h3&gt;
  
  
  Pricing &amp;amp; trying it out
&lt;/h3&gt;

&lt;p&gt;We wanted predictable pricing for small teams, agencies, and devs running their own infrastructure-no per-alert overages or "contact sales" gates just to see a number:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Developer ($39/mo):&lt;/strong&gt; Covers up to 5 servers and 3 users. Real-time alerts, port-scanner trapping, SSH config monitoring, encrypted credential vault (AES-256-GCM), and a 1-year audit log.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Business ($149/mo):&lt;/strong&gt; Covers up to 25 servers and 20 users. Adds Autopilot mode, behavioral anomaly baselines, CVE scanning, canary files, webhooks/integrations (Slack, PagerDuty, Datadog, Splunk), and CIS/SOC 2/PCI-DSS compliance reporting.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;There is no anonymous free tier (to keep abuse down), but both plans come with a &lt;strong&gt;14-day free trial with no credit card required&lt;/strong&gt;. &lt;/p&gt;

&lt;p&gt;If you want to see what background internet noise looks like on an unadvertised Linux box right now, check out the &lt;a href="https://vigilhold.com/lab" rel="noopener noreferrer"&gt;live lab feed on Vigilhold&lt;/a&gt; - no signup needed. Would love any feedback from fellow Linux admins on the architecture or what signals you wish your current setup caught faster.&lt;br&gt;
Use code with caution.&lt;/p&gt;

</description>
      <category>linux</category>
      <category>security</category>
      <category>devops</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
