Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

The previous year (2018) witnessed an overwhelming number of cyber-attacks and data breaches that affected millions of customers across companies, including customers of household names like Uber, Facebook, Reddit, British Airways, and the Marriott hotel chain. Even governmental organizations were no exception.

France’s national data protection authority (CNIL — Commission Nationale de l’informatique et des Libertés) ordered its first sanction under the EU’s General Data Protection Regulation, or as commonly called as the GDPR. In this sanction, the CNIL fined Google a whopping €50 million because of Google’s failure to comply with the GDPR provisions when a user sets up his new Android phone and follows the subsequent process.

One of the key Kubernetes security concepts is that workload identity is tied back to information that the orchestrator has. The orchestrator is actually the authoritative entity for what the actual workloads are in the platform. Kubernetes uses labels to select objects and to identify collections of objects that satisfy certain conditions. We, and others in the Kubernetes networking space, often talk about using Kubernetes ‘labels’ as identity bearers.

With the constant barrage of headlines regarding breaches in the last few years, it seems that society in general has become numb to losing personal data. This year’s overarching cybersecurity theme is clear: We’re all in this together because we simply can’t do it alone. Effective defense demands a team effort where employees, enterprises, and end users alike recognize their shared role in reducing cybersecurity risks.

A few weeks ago, I woke up one morning to discover that Android had 34 software updates waiting for me. This was followed by my laptop wanting to reboot after installing the latest patches from Microsoft; my tablet needing a reboot after its latest firmware update; and my server screaming for me to put “yum” into action to install the latest patches available from Red Hat – all before 10:00 am in the morning!