Keepers of the Machines: Examining How System Administrators Manage Software Updates
summary
Study surveys 102 administrators and interviews 17, maps updates into five stages and documents concrete pain points: admins use Ansible or Chef plus custom scripts to deploy, prefer staggered deployment that often takes weeks and delays security patches, and only 10% skip testing while interviewees all test. 98% report recent buggy updates, most rollback to snapshots rather than debug (only 5–15% attempt fixes in-place), showing automation and testing infrastructure gaps that cause deliberate delays in patching.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:55Consequences of Poor Updating Behavior
- 1:31Security Breaches
- 1:50System Administrators
- 2:42Research Questions
- 3:00Methodology
- 10:10Automatic Updates
- 12:37Buggy Updates
- 15:18Next Steps
- 18:01Questions
related talks
05mSecurity, Availability, and Multiple Information Sources: Exploring Update Behavior
30mSoftware Patching Needn't Be a Can of Worms
23mTales of Software Updates: The process of updating software
48mDevOps Patterns and Antipatterns for Continuous Software Updates
45mSoftware Updates for Connected Devices: Key Considerations
30mDevOps Patterns and Antipatterns for Continuous Software Updates
19m"Hackers automate but the Drupal Community still downloads updates [...]"
47mWhy keeping your system secure is a bit like decluttering