The latest News and Information on DevOps, CI/CD, Automation and related technologies.
The practice of cybersecurity is undergoing radical transformation in the face of new threats introduced by new technologies. As a McKinsey & Company survey notes, “an expanding attack surface is driving innovation in cybersecurity.” Kubernetes and the cloud are infrastructure technologies with many moving parts that have introduced new attack surfaces and created a host of new security challenges.
Collaboration: the secret sauce of every software project. But let’s be honest, mastering the communication needed for seamless teamwork is like trying to herd cats wearing roller skates – sounds amusing, but feels impossible. From navigating multiple time zones and illegible pull requests to juggling so many tasks simultaneously that your brain feels like a browser with fifty tabs open – teamwork isn’t always a walk in the park.
The curtain rose and fell on another spectacular Black Hat USA, the conference set against the backdrop of fabulous Las Vegas in the Mandalay Bay Convention Center. We knew upon hitting the Strip that all the glamor and neon lights were just the preshow for the main event: innovation and the latest in cybersecurity. We couldn’t wait to show attendees and fellow vendors what we had to offer.
In my last blog post, I wrote about the explicit costs of incidents — the ones you can easily track based on dollars lost. But the cost of incidents goes beyond the time spent resolving them. While we’re spending our time managing incidents (that includes mitigating and retrospectives), we’re incurring a large opportunity cost in terms of releasing the next big thing.
User expectations — those of employees and customers alike — are turning up the heat for businesses and their IT departments. Could the demand for nonstop, fast, and basically flawless digital services be any higher?
Imagine the following situation: You are on call, and your monitoring dashboard has flickering red lights due to an increased number of 5xx HTTP responses from one or more of your Kubernetes services. Now it is time to start to troubleshoot 500 Errors. Instead of panicking, you can use this blog as a guide.