IP Library Granted Patent US 8,225,304
Granted Patent B2
US 8,225,304 · App. 12/352,008 · Granted Jul 17, 2012

System and method for remotely securing software updates of computer systems

Assignees: Kabushiki Kaisha Toshiba; Toshiba Tec Kabushiki Kaisha
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,225,304
App. No.
12/352,008
Granted
Jul 17, 2012
Kind
B2
Abstract

The subject application is directed to a system and method for providing a subscription service wherein a remote host enables the automatic receipt at a customer site of the most recent updates, patches, or fixes for services the customer site is running. The remote host uses a secured private port to transfer the updates to the subscribed systems. A remote host server searches an update database for updates of the services from a list configured by an administrator. The host server then downloads the updates and notifies the administrator that an update is available. An update script is subsequently generated, allowing the update to be pushed to a subscribing system. The host server the searches a listing of subscribing systems to determine which subscribing systems run a service for which an update is available. The host server, through a private port, uploads the content to the subscribing system automatically. The communication port is a secured port that will require authentication of the host server by the subscribing system prior to uploading.

Claims (68)

1. A system for updating security software of computer systems via a remote software update source, comprising the steps of:

a primary server adapted to store software updates representative of at least one update of software associated with at least one data processing device;

means adapted for receiving installation scripts, each of which is associated with at least one software update disposed on the primary server;

secured data storage means for storing data representative of a plurality of remote proxy servers;

registration means, disposed in the primary server, adapted for receiving specific registration data from each of the plurality of remote proxy servers inclusive of data representative of a plurality of associated data processing devices associated therewith, wherein the registration data includes:

authentication credentials for establishing a secure data communication path between the server and each of the plurality of remote proxy servers,

identification data corresponding to identification of software of the data processing devices associated with the specific remote proxy server,

update parameter data corresponding to specified timing of software updates, and

data corresponding to selective manual and automatic installation of software updates;

authentication means adapted for receiving a login request from at least one of the plurality of remote proxy servers including means for comparing the received login request with the proxy server data;

means for selectively placing the primary server in secure data communication with the at least one requesting proxy server in accordance with the comparison means, wherein a secure data communication channel is established in accordance with the registration data;

means adapted for testing stored updates to determine which updates are appropriate for the data processing devices associated with the at least one remote proxy server; and

means adapted for selectively pushing software updates from the primary server to the at least one proxy server to be sent to at least one device, along with an associated installation script, in accordance with a received login request and in accordance with associated registration data.

2. The system of claim 1 , further comprising means for digitally signing the determined updates for the data processing devices prior to the communication thereof to the remote data processing device.

3. The system of claim 2 , further comprising:

means adapted for monitoring the software updates selectively pushed to each of the plurality of remote proxy servers;

means adapted for generating log data representative, for each of the plurality of remote proxy servers, representative of the software updates selectively pushed in accordance with an output of the monitoring means; and

storage means for storing the generated log data in association with the registration data specific to each of the plurality of remote proxy servers.

4. The system of claim 3 , further comprising:

means for testing log data against stored updates to determine which updates are appropriate for the data processing devices associated with the at least one remote proxy server; and

means for selectively eliminating at least one software update to be pushed by the primary server upon a determination from the log testing means that the software has previously been pushed to the at least one proxy server.

5. The system of claim 3 , further comprising:

means for receiving, at the primary server from at least one of the plurality of proxy servers, request data representative of at least one software update associated with at least one data processing device associated with the at least one proxy server; and

means for selectively pushing, by the primary server, the at least one requested software update to the at least one proxy server.

6. The system of claim 3 , further comprising:

means for receiving, disposed at least one of the plurality of proxy servers, a software update request from at least one associated data processing device in accordance with a preselected schedule associated therewith;

identification means for identifying at least one software update received by the proxy server from the primary server associated with the at least one associated data processing device; and

means for selectively pulling, disposed on the at least one data processing device, the at least one identified software update from the proxy server.

7. The system of claim 6 , further comprising:

means for authenticating the at least one software update pulled from the proxy server via an associated certification authority; and

installation means adapted for installing the software update on the at least one data processing device upon an authentication of the software update by the associated certification authority.

8. The system of claim 6 , further comprising:

means for monitoring the software updates selectively pulled by the at least one data processing device; and

means for generating log data representative of the selectively pulled software in association with the at data processing device by at least one of the primary server and the proxy server associated with the at least one data processing device in accordance with an output of the monitoring means.

9. A method for updating security software of computer systems via a remote software update source, comprising the steps of:

storing, at a primary server, software updates representative of at least one update of software associated with at least one data processing device;

receiving installation scripts at the primary server, each of which is associated with at least one software update disposed on the primary server;

storing data representative of a plurality of remote proxy servers in a secured data storage;

receiving specific registration data from each of the plurality of remote proxy servers inclusive of data representative of a plurality of associated data processing devices associated therewith, wherein the registration data includes:

authentication credentials for establishing a secure data communication path between the server and each of the plurality of remote proxy servers,

identification data corresponding to identification of software of the data processing devices associated with the specific remote proxy server,

update parameter data corresponding to specified timing of software updates, and

data corresponding to selective manual and automatic installation of software updates;

receiving a login request from at least one of the plurality of remote proxy servers and comparing the received login request with the proxy server data;

selectively placing the primary server in secure data communication with the at least one requesting proxy server in accordance with the comparison, wherein a secure data communication channel is established in accordance with the registration data;

testing stored updates to determine which updates are appropriate for the data processing devices associated with the at least one remote proxy server; and

selectively pushing software updates from the primary server to the at least one proxy server to be sent to at least one device, along with an associated installation script, in accordance with a received login request and in accordance with associated registration data.

10. The method of claim 9 , further comprising the step of digitally signing the determined updates for the data processing devices prior to the communication thereof to the remote data processing device.

11. The method of claim 10 , further comprising the steps of:

monitoring the software updates selectively pushed to each of the plurality of remote proxy servers;

generating log data representative, for each of the plurality of remote proxy servers, representative of the software updates selectively pushed in accordance with an output of the monitoring step; and

storing the generated log data in association with the registration data specific to each of the plurality of remote proxy servers.

12. The method of claim 11 , further comprising the steps of:

testing log data against stored updates to determine which updates are appropriate for the data processing devices associated with the at least one remote proxy server; and

selectively eliminating at least one software update to be pushed by the primary server upon a determination from the log testing that the software has previously been pushed to the at least one proxy server.

13. The method of claim 11 , further comprising the steps of:

receiving, at the primary server from at least one of the plurality of proxy servers, request data representative of at least one software update associated with at least one data processing device associated with the at least one proxy server; and

selectively pushing, by the primary server, the at least one requested software update to the at least one proxy server.

14. The method of claim 11 , further comprising the steps of:

receiving, at the proxy server, a software update request from at least one associated data processing device in accordance with a preselected schedule associated therewith;

identifying at least one software update received by the proxy server from the primary server associated with the at least one associated data processing device; and

selectively pulling, by the at least one data processing device, the at least one identified software update from the proxy server.

15. The method of claim 12 , further comprising the steps of:

authenticating the at least one software update pulled from the proxy server via an associated certification authority; and

installing the software update on the at least one data processing device upon an authentication of the software update by the associated certification authority.

16. The method of claim 14 , further comprising the steps of:

monitoring the software updates selectively pulled by the at least one data processing device; and

generating log data representative of the selectively pulled software in association with the at data processing device by at least one of the primary server and the proxy server associated with the at least one data processing device in accordance with an output of the monitoring step.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 5, 2009
From: SHAHINDOUST, AMIR; YEUNG, MICHAEL
To: KABUSHIKI KAISHA TOSHIBA; TOSHIBA TEC KABUSHIKI KAISHA
Reel/Frame 022211/0334 →
Continuity (2)
Continuation In Part 10806960 · Mar 23, 2004
Related Publication 20090138870A1 · May 28, 2009