Un de mes podcasts favoris depuis quelques années !
Voici quelques épisodes que je recommande en particulier :
- Episode 421 - RETEX Incident de sécurité au CHU de Brest
- Episode 409 - Retour d’expérience sur la gestion d’une crise cyber par le RSSI de Thalès (déjà partagé sur ce shaarli)
- Episode 397 consacré au blog/newsletter
- Episode 395 consacré aux aspects « Cyber » de la guerre en Ukraine
- Episode 331 consacré au « Software Sandboxing » avec Jean-Baptiste Kempf de VLC
Je recommande cet épisode en particulier, avec un excellent REX / PostMortem de Stéphane Lenco sur une gestion de crise à Thalès, ciblé par le rançongiciel / ransomware LockBit
Also provides a reverse SLA uptime percentage calculation base on downtime duration
More details from a former Site Reliability Engineer at Facebook: https://twitter.com/RenaudGuerin/status/1445114486457880582
Not very insightful, but I'm retaining some quotes:
But IT operations includes much more than the limited “ops” functions we typically fold into a DevOps team. I’m talking about things like ticket management, incident handling, user management and authorization, backups and recovery, network management, security operations, infrastructure procurement and cost optimization, compliance reporting, and much more. In today’s IT organization, where do these responsibilities fall?
You want DevOps teams to have a streamlined, low lead-time, lean pipeline to production. Devoting team capacity to this broader set of operational functions may slow down this pipeline. There are also efficiencies to be gained by sharing these practices across the work of all the DevOps teams.
All of this is to say that a portion of IT operations still exists independently of the DevOps teams, performing those “ops” functions that are not in “DevOps” while the DevOps teams focus on that subset of ops functions specifically related to deploying code and responding to code-related incidents