New

Hi HN.

I am a "sys-admin/software dev/anything IT" for some smaller companies. Recently I've been doing a lot of work securing our infra following the PHP madness, weekly GitLab CVEs, and yesterday Tailscale's issues (though they didn't require intervention directly, they prompted me to do research), etc.

Mostly I become aware of these issues through some of my favorite blogs, like HN, but also the Dutch (and very excellent) tweakers.net.

But I think I can automate this more using an agent. I was thinking to give one of my Hermes agents a list of the software we use and regularly check online if there are issues, then if there are, prepare an action plan for me (with sources) and ping me on my mobile phone (ie via ntfy.sh which I already use with Uptime Kuma). Perhaps I could even publish this on my public website, saving others the trouble. Later on I could have the agent manage some interventions directly (though I'm not ready for that yet.)

But, I know scraping LLMs are killing the internet, so I was wondering how I can do this responsible. How can I instruct (or rather: build) the agent (or rather: the set of scripts that will become the agent [always minimize LLM involvement in recurring tasks, unless edge cases arise!]) best? Are there known APIs equipped to handle the scraping, perhaps even tailored to cybersecurity incidents?

Or maybe I should go about this some other way entirely?

Whatever the case, I was wondering how you people out there handle the CVE load.

All the best out there and stay safe!

You can check for server or web vulnerabilities—including issues like PHP2Shell, React2Shell, and GitLab RCE—by entering an IP address, domain, or URL. Although the site is in Korean, it should be easy to use.

Since everyone and their agents are building apps, there is not time to stop and search for vulnerabilities on our machine. Built an open source tool that monitors new vulnerabilities every 15 mins and lets you or your agent know on what to fix.