This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| Software Update | |
|---|---|
| Name | Software Update |
| Developer | Various |
| Released | Continuous |
| Operating system | Cross-platform |
| License | Proprietary and Free and Open Source |
Software Update is the process of delivering modifications, enhancements, bug fixes, and security patches to deployed Microsoft Windows, macOS, Android, and iOS devices, as well as to server platforms like Linux, Unix, and IBM AIX. Software updates are managed by vendors such as Microsoft, Apple Inc., Google LLC, Red Hat, and Canonical (company) and are distributed through channels like Windows Update, Apple Software Update, Google Play, and package managers such as APT (Debian), YUM, and Snap. The practice intersects with standards and institutions including the Open Web Application Security Project, the Internet Engineering Task Force, and the National Institute of Standards and Technology.
Software updates encompass incremental patches, feature releases, and complete upgrades delivered by companies like Oracle Corporation, SAP SE, and Adobe Inc. to systems ranging from mainframe computers at IBM sites to embedded firmware in Intel and ARM Holdings-based devices. Updates address issues identified through channels such as CVE (Common Vulnerabilities and Exposures), bug trackers like Bugzilla, and incident reports by organizations including CERT Coordination Center and US-CERT. Update practices are influenced by events like the WannaCry ransomware attack and policies from regulatory bodies including the European Commission and the Federal Communications Commission.
Common categories include security patches for vulnerabilities listed in CVE (Common Vulnerabilities and Exposures), hotfixes deployed by Microsoft Support, cumulative updates used by Windows Server Update Services, feature updates exemplified by Android 11 and iOS 14, and service packs historically provided by Microsoft Windows XP and Microsoft Office. Firmware updates for devices from Cisco Systems, Juniper Networks, and Netgear coexist with driver updates for NVIDIA, AMD, and Intel Corporation hardware. In enterprise contexts, vendors such as VMware and Oracle supply critical patch updates alongside quarterly or monthly release cadences inspired by the Patch Tuesday model.
Delivery channels include centralized services like Microsoft Update Catalog, app stores such as Google Play and the App Store (iOS), content delivery networks operated by Akamai Technologies and Cloudflare, and peer-to-peer techniques used by BitTorrent-based updaters. Package managers—DPKG, APT (Debian), RPM, and Homebrew—enable repository-based distribution for projects like Debian, Ubuntu, Fedora, and macOS. Containerized deployments use registries such as Docker Hub and orchestration platforms like Kubernetes and OpenShift to roll updates across clusters. Enterprise update management can involve SCCM from Microsoft System Center and mobile device management suites from AirWatch and MobileIron.
Update mechanisms must mitigate risks exemplified by supply-chain attacks like the SolarWinds hack and code-signing compromises such as incidents involving Shadow Brokers. Cryptographic assurances from PKI and signatures using RSA or ECDSA are enforced by vendors including Apple Inc. and Microsoft to prevent tampering. Privacy implications arise when telemetry collected by Google LLC, Microsoft, or Apple Inc. is transmitted during updates; oversight by regulators like the European Data Protection Board and legal instruments such as the General Data Protection Regulation shape vendor obligations. Vulnerability disclosure policies from MITRE and coordinated disclosure processes involving Zero Day Initiative and Google Project Zero influence patch prioritization.
Semantic versioning conventions used by Node.js and open-source projects hosted on GitHub coexist with vendor-specific schemes like Windows build numbers and macOS release codenames. Release engineering teams at Facebook, Amazon (company), and Netflix employ continuous integration tools—Jenkins, Travis CI, and GitLab CI/CD—and use feature-flag systems pioneered in firms such as Facebook and Google to stage rollouts. Branching strategies from Git (software) and milestone tracking in JIRA (software) help coordinate deployments across distributed teams and downstream ecosystems including Debian and Red Hat Enterprise Linux.
Rollback mechanisms rely on snapshots from LVM (Linux Logical Volume Manager), filesystem features like ZFS and Btrfs, and backup systems such as Veeam and Acronis. Virtualization platforms—VMware ESXi, Microsoft Hyper-V, and KVM—provide checkpointing to revert updates, while container orchestrators like Kubernetes support rollbacks via deployment revisions. Incident response frameworks from SANS Institute and disaster recovery plans in standards like ISO/IEC 27001 guide recovery procedures after failed updates or incidents like the NotPetya attack.
Updates affect end users on platforms like Xbox and PlayStation as well as employees using productivity suites from Microsoft Office and collaboration tools from Slack (software) and Zoom Video Communications. Organizations such as Banks (e.g., JPMorgan Chase), healthcare providers under Health Insurance Portability and Accountability Act regimes, and public institutions including NASA and European Space Agency must coordinate updates to manage downtime, compliance, and risk. Economic and operational impacts are studied by analysts at Gartner and Forrester Research and have been shaped by high-profile outages at companies like Facebook and Amazon Web Services.
Category:Software maintenance