As companies adopt container technologies, they face a significant challenge - how do we secure this new attack surface? It’s an issue that you often see backlogged in favor of solving storage, networking and monitoring issues. Add on the challenge of educating the workforce on one of the fastest-growing open source projects to date, and it’s no wonder security has lagged as the primary focus for teams.
Cloud environments are always susceptible to security issues. A significant contributor to this problem is misconfigured resources. Traditional IT Infrastructure was somewhat static; server hardware only changed every few years. With few changes occurring, security was also more static. The modern cloud environment is a much different challenge. In cloud environments, servers, services, and storage are created with automation, resulting in a dynamic and potentially ever-changing server environment.
In 2020 ‘pivot’ has become the trendy word of the business class, referring mainly to a company’s willingness to adopt technology to maintain internal team communication and productivity. Apart from front-line workers across disciplines who have courageously put others before themselves to provide healthcare and daily necessities, shelter in place, and work from home orders forced businesses to reassess their needs…and quickly.
Cloud native observability is at a watershed moment. The explosion of microservices has created previously unseen amounts of monitoring data, limiting the ability of humans and computer systems to extract meaning from data with last-generation tools. Debugging is often a process of detecting correlation, and then turning correlations into causal connections. This is where modern cloud native tooling comes in.
