Observability vs. Visibility: Key reasons they are not the same

Observability vs. Visibility: Key reasons they are not the same

 

05 December 2019

Observability vs. Visibility: Key reasons they are not the same

Author: Sean Everson, Chief Technology Officer, Certes Networks

As published in CCR Magazine, Oct 11, 2019 and Continuity Central, Oct 11, 2019

 

 

 

 

In today’s increasingly complex cyber landscape, it is now more important than ever for organizations to be able to analyze contextual data in order to make informed decisions regarding their network security policy. This is not possible without network observability. Organizations can now see inside the whole network architecture to explore problems as they happen. Observability is a property of the network system and should not be confused with visibility which provides limited metrics for troubleshooting. 

With observability, organizations can make the whole state of the network observable and those limitations no longer exist. Observability provides the contextual data operators need to analyze and gain new and deeper insights into the network. This enables teams to proactively make more informed decisions to improve network performance and to strengthen their overall security posture because context is now available to troubleshoot incidents and make policy changes in real-time.

Unfortunately, observability is often miscommunicated and misunderstood, as visibility is repackaged by some vendors and sold as observability, when the two are not the same. Visibility and monitoring have an important role to play but observability is different. Visibility and the metrics it provides limits troubleshooting, whereas observability provides rich contextual data to gain deeper insights and understanding based on the raw data collected from the network or system. 

With research showing that the average lifecycle of a data breach is 279 days, it is clear that organizations are slowly putting observability into practice and adopting observability as a culture. In the case of some well-known breaches, however, the timescales were much longer than that. The Marriott International breach, which was discovered in November 2018, saw hackers freely access the network since 2014. During this time, no unusual activity was detected and no alerts of the hacker’s access were raised.

Additionally, in the British Airways data breach in 2018, data was compromised over a two-week period, affecting 500,000 customers. This resulted in the Information Commissioner’s Office (ICO) announcing that it intended to fine British Airways £183.39M for infringements of the General Data Protection Regulation (GDPR).

These two examples alone demonstrate how essential it is for organizations to begin to value the ability to understand their systems and behavior by making their network observable.

Understanding Observability

Simply defined, observability is a measure of how well something is working internally, concluded from what occurs externally. Observability is creating applications with the idea that someone is going to observe them with the aim of strengthening and making system access decisions. The right combination of contextual data can be used to gain a deeper understanding of network policy deployment and every application that tries to communicate across the network. With an observability capability, attackers will therefore have a hard time attempting to lateral ‘east-west’ movements or remaining hidden in the data center or across the WAN. In turn, observability can provide a global view of the network environment and visual proof that the security strategy is effective and working.

Unfortunately, it’s not uncommon for infiltrations to go undetected in networks for days, weeks or months. This means infiltrations are active longer and networks systems are more increasingly vulnerable. To effectively deter and prevent incidents real-time, all roles need to see inside the entire architecture. And, when this capability is built in, it is observability that enables greater insight into the overall reliability, impact and success of systems, workloads and their behavior.

Conclusion

Research shows that companies who are able to detect and contain a breach in less than 200 days spend $1.2 million less on the total cost of a breach. That’s a figure no organization can – or should – ignore. Organizations need a cyber security solution that can be measured and traced. Observability provides the contextual data so organizations can take measurable steps towards controlling system access of the network environment. With this type of observable analysis, organizations can gain deeper insights into how to enhance their security policy and detect unwanted access as it occurs.