Security, Availability, and Multiple Information Sources: Exploring Update Behavior
summary
Mixed-method study maps a five-phase update process (information, decision, preparation, testing, post-install) and quantifies obstacles: a 67‑participant survey finds 67-admin survey responses showing downtime risk and introduced errors score higher than performance concerns, 80% use online news or peer reports rather than vendor advisories, and broken dependencies and heterogeneous estates are frequent blockers. Tools range from monitoring dashboards to fully automated patching; testing commonly uses staging systems or small peer rollouts before wide deployment.
AI-written summary · about
chapters (5)
related talks
21mKeepers of the Machines: Examining How System Administrators Manage Software Updates
23mTales of Software Updates: The process of updating software
34mSafety vs Security: A Tale of Two Updates
45mDon’t be Afraid to Upgrade- 45mDon’t be Afraid to Upgrade
30mSoftware Patching Needn't Be a Can of Worms
19m"Hackers automate but the Drupal Community still downloads updates [...]"
39mTrials and Tribulations of Updating Dependencies for Vulnerability...