Managing update attempts by a guest operating system to a host system or device
US-9349010-B2 · May 24, 2016 · US
US9934022B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9934022-B2 |
| Application number | US-201514866643-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 25, 2015 |
| Priority date | Sep 4, 2009 |
| Publication date | Apr 3, 2018 |
| Grant date | Apr 3, 2018 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
When providing a user with native access to at least a portion of device hardware, the user can be prevented from modifying firmware and other configuration information by controlling the mechanisms used to update that information. For example, a clock or a timer mechanism can be used by a network interface card to define a mutability period. During the mutability period, firmware update to a peripheral device can be allowed. Once the mutability period has expired, firmware update to a peripheral device will no longer be allowed.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method comprising: triggering, by a network interface component of a host system, initiation of a mutability period; receiving firmware update information on a network port of the network interface component; enabling, during the mutability period, firmware update of a peripheral device of the host system based on the firmware update information; disabling the firmware update of the peripheral device after the mutability period has elapsed; and loading a guest operating system after the mutability period has elapsed. 2. The computer-implemented method of claim 1 , wherein the network port receiving the firmware update information is a dedicated firmware update port. 3. The computer-implemented method of claim 1 , wherein the peripheral device is the network interface component, and the firmware update information is for updating firmware of the network interface component. 4. The computer-implemented method of claim 1 , further comprising: routing the firmware update information to the peripheral device via a routing component of the host system. 5. The computer-implemented method of claim 1 , wherein the mutability period is determined by a secure timer that is isolated from unauthorized modification. 6. The computer-implemented method of claim 5 , wherein the secure timer is implemented in the network interface component. 7. The computer-implemented method of claim 1 , wherein initiation of the mutability period is triggered by power-up of the host system. 8. The computer-implemented method of claim 1 , wherein initiation of the mutability period is triggered during an initial booting phase of the host system. 9. The computer-implemented method of claim 1 , wherein a duration of the mutability period is varied based on a device type of the peripheral device. 10. The computer-implemented method of claim 1 , wherein a duration of the mutability period is adjusted based on a policy received over a network. 11. A network interface device comprising: a peripheral interface configured to be coupled to a host processor of a host system; a network communications port; a firmware update port configured to receive firmware update information; and a clock configured to countdown a mutability period until the mutability period expires, wherein a firmware update of a peripheral device of the host system based on the firmware update information is allowed only during the mutability period, and wherein a guest operating system is loaded onto the host system after the mutability period has elapsed. 12. The network interface device of claim 11 , wherein the peripheral device is the network interface device, and the firmware update information is for updating firmware of the network interface device. 13. The network interface device of claim 11 , further comprising: routing the firmware update information to the peripheral device via the peripheral interface. 14. The network interface device of claim 11 , wherein the clock is a secure clock that is isolated from unauthorized modification. 15. The network interface device of claim 11 , wherein countdown of the mutability period is initiated by power-up of the host system. 16. The network interface device of claim 11 , wherein countdown of the mutability period is initiated during an initial booting phase of the host system. 17. The network interface device of claim 11 , wherein a duration of the mutability period is varied based on a device type of the peripheral device. 18. The network interface device of claim 11 , wherein a duration of the mutability period is adjusted based on a policy received over a network. 19. The network interface device of claim 11 , wherein a duration of the mutability period is configurable based on identity of a guest user of the host system.
Updates (security arrangements therefor G06F21/57) · CPC title
for managing network security; network security policies in general (filtering policies H04L63/0227) · CPC title
wherein the data content is protected, e.g. by encrypting or encapsulating the payload · CPC title
Secure firmware programming, e.g. of basic input output system [BIOS] · CPC title
to features or functions of an application · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.