Best Practices for TuxCare Radar Security Scans
I wrote this one for TuxCare, and it’s the most personal of my Radar posts. It opens with those dreaded rush-hour phone calls from my manager about the vulnerability that was going to “eat the Internet,” then walks through the daily habits that make Radar actually useful once it’s installed.
Originally published on TuxCare Read the full article →A few things I wanted people to walk away with:
- Tag your systems by risk zone. Labeling hosts as prod, pci, or web in radar.yaml turns a flat CVE list into risk you can read in context, so you know where to look first.
- Ask Radar instead of the forums. The built-in AI assistant is trained on the CVE landscape, so you can ask about a specific CVE or what a zero-day means without stringing together search terms.
- Trade spreadsheets for shareable reports. Filtered, audit-friendly PDF and Excel exports let you show progress over time instead of wrangling thousand-row spreadsheets.
These are the routines I wish I’d had back when triage meant remoting into every server one at a time.