The most secure server is one that is disconnected from the Internet and unplugged. And the most convenient environment for devs is where they have admin access to production and the freedom to do what they want. Sometimes it feels hard to reconcile these two ideals, allowing devs to be free to use whatever dependencies they want while making sure their setup and software are as secure as possible. Hence the term - Software Supply Chain Security, which looks at securing the entire process of getting software from devs to production.
Let's look at a real-world scenario of a cloud-native fintech platform on GKE. The vision? A robust, flexible, and secure foundation that supports SOC2-compliant deployments and empowers developers to be as productive as possible, contrary to the typical for the financial sector blown-out processes and approval chases.
This solution is powered by Google Kubernetes Engine (GKE) and the cloud's niftiest security tools from the Secure Supply Chain toolkit.

When DevOps emerged around 15 years ago, it aimed to bridge the gap between Developers and Operations. Today - it is safe to say that devs and infra/platform people understand each other reasonably well.
Now it’s time to make the case for data and platform engineers.
Does “We need access to prod” mean the same to both sides?
Can data products be truly tested and have a lifecycle?
How do you build a partnership between the teams who provide data infrastructure and those who work with the data?