Do you stay awake at night, wondering what might be going wrong on your corporate network? Are the unknown vulnerabilities and mysterious-yet-critical applications haunting your dreams? Do you wake in a sweat over those subscription products business users are secretly using? Don’t just stand back and watch what is happening through regular, passive observability, but engage in powerful active observability.
Unwanted complexity is the curse of modern businesses. Organic growth and constant change both inside and outside the organization inevitably will tangle things no matter how neatly they were put together in the first place. Observability is a critical approach to understanding what is on the network, but active observability takes it a step further by taking a role in keeping a lid on the ever-threatening chaos. Here are a few considerations to achieve it.
1. Expand your asset classes
It sounds obvious to say that the first step is to catalog the assets on the network, but the first step is to actually identify the different classes of assets that need managing. In the past it used to be a case of sticking asset numbers onto boxes, but in our multi-cloud, federated world we need to broaden our concept of assets to include the virtual as well as physical. Ideally that list will include: applications, servers, networks, cloud providers, subscription services, data in all its forms, configurations for everything, certificates and chains, security tools and appliances, operating environments, development pipelines, API endpoints, serverless compute, source code and more. Include it if it is involved in computing.
We must reflect the blurring boundaries between capital and operational assets in how executives think about their business. While this change has been going on for many years, all too many people still think of servers as “the computer in the cupboard” and networks as simply cabling. This model precludes an understanding of the inherent vulnerabilities in our modern networks full of edges and connections, let alone the implications of including software in the mix.
2. Watch and learn
Observability tools are night sights for CIOs, letting them peer into the darkest recesses of their organization. As I mentioned before, documentation cannot keep up with change — staff often do not have the time, or indeed the inclination, to record every update. Each one feels small and unimportant, but they accumulate rapidly to the point where those lovingly-created Visio charts become more dangerous than useful when navigating the resources out there.