Going from nothing to automation using one of the many tools available can be a daunting task. How can you automate systems when you’re not even 100% sure how they’ve been configured? The documentation is months out of date and the last guy to configure anything on that box has since left the company to ply his trade somewhere that will more fully appreciate his Ops cowboy routine.
Update: This is a preserved post detailing new (at the time) UpGuard product features, enhancements, or tutorials. The screenshots below may be out of date and/or make reference to GuardRail or ScriptRock—old names for the same great product. There are also many newer features that will drive you wild. Node Groups A Node Group is a way of logically grouping Nodes with common functionality. Instead of managing the same set of Policies on each Node you can now manage one set of Policies on the Node Group that will automatically get applied to any Nodes in the Group. Their use is best highlighted with examples. All of your Linux servers might need to comply with an underlying security policy, group them together using a Node Group called "Linux" and apply your security policy there. Your front-end web servers are identical behind a load balancer, add them to a Node Group called "Front-end Web Server." How you organize them is up to you, they can be as general or specific as you like.
Cyber resilience is a fundamental change in understanding and accepting the true relationship between technology and risk. IT risk (or cyber risk, if you prefer) is actually business risk, and always has been. And the cybersecurity industry, for what it's worth, has generally avoided this concept because it goes against the narrative that their respective offerings—whether it's a firewall, IDS, monitoring tool, or otherwise—would be the one-size-fits-all silver bullet that can keep businesses safe. But reality tells a different story.