Skip to main content

Software Update as a Mechanism for Resilience and Security Proceedings of a Workshop (2017) / Chapter Skim
Currently Skimming:

11 Discussion
Pages 63-65

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 63...
... The workshop surfaced some important differences in terms of the technical factors and the business factors at play in various types of situations, she noted, highlighting, as an example, the differences between Linux and Microsoft in terms of how updates are created and deployed. While open-source development allows for a lot of innovation and iteration, staging and rolling out updates in a closed system, such as Microsoft, has its own distinct advantages.
Read the entire page →
From page 64...
... If a device can't be For example, a "gatekeeper" could contain vulnerable software and compel a user to patch it, giving people updated, explore both an education and an incentive to attend to updates ways to limit the while adding a layer of protection. While "cutting off" a device could frustrate users, it might be necessary to damage of a craft a cybersecurity policy that defines the situations in which doing so is justified in order to protect the greater potential breach society as whole, Mulligan suggested.
Read the entire page →
From page 65...
... Other important related issues that were only touched on briefly but that could warrant further discussion include privacy implications, future business models, new software trends such as ephemeral code, and the need for a mechanism to involve the public in advancing conversations about what the appropriate limits to monitoring might be, Mulligan concluded. Launching the discussion session, Butler Lampson, Microsoft Corporation, suggested that the workshop focused too much on how software operated in the past, when it was downloaded and expected to perform one function.
Read the entire page →

Key Terms

  • mulligan suggested
  • discussion session
  • supports updates
  • light bulb
  • cisco supports

  • update challenges
  • potential threats
  • butler lampson
  • advancing conversations
  • future business

  • own distinct
  • mulligan highlighted
  • potential breach
  • gain control
  • software updates

  • mulligan reflected
  • help limit
  • allow users
  • organizations perceive
  • landscape influences

  • distinct advantages
  • software trends
  • discussion include
  • external landscape
  • technical factors

  • privacy implications
  • business factors
  • mulligan concluded
  • development allows
  • multiple occasions


    • This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
    More information on Chapter Skim is available.