English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

System administrators, similar to end users, may delay or avoid softwarepatches, also known as updates, despite the impact their timely application canhave on system security. These admins are responsible for large, complex,amalgamated systems and must balance the security related needs of theirorganizations, which would benefit from the patch, with the need to ensure thatsystems must continue to run unimpeded. In this paper, we present a case studywhich follows the online life-cycle of a pair of Microsoft patches. We findthat communities of sysadmins have evolved sophisticated mechanisms to performrisk assessments that are centred around collecting, synthesizing, andgenerating information on patches. These communities span different VirtualCommunities of Practice, as well as influencers who monitor and report on theimpact of new patches. As information is propagated and aggregated acrossblogs, forums, web sites, and mailing lists, eventually resulting in aconsensus around the risk of a patch. Our findings highlight the role thatthese communities play in informing risk management decisions: Patchinformation is not static, and it transforms as communities collaborate tounderstand patch issues.

To Patch, or not To Patch? That is the Question: A Case Study of System Administrators' Online Collaborative Behaviour