US 9,069,885 B1Granted

Systems and methods for automated retrieval, monitoring, and storage of online content

AssigneeCodeGuard, Inc.

InventorsDavid Moeller, Jonathan Manuzak, Jonah Stein, Jonathan Hochman

Life of this patent

Estimating the term…

Loading patent…

Abstract

Systems and methods for automated retrieval, monitoring, and storage of online digital content, wherein such content includes source code and files for hosting websites, audio files, video files, data files, system files, image files, or any other content that is typically stored in third party servers. A content retrieval system hosted on a physical server or a cloud continuously monitors user data hosted on a third party server for changes to the data. The method involves creation of an index list that is updated periodically to keep track of changes to the metadata associated with the user's content. Such an approach saves time and valuable resources to individuals and/or organizations enabling them to perform periodic monitoring of their data, and enabling rollback to a previous version of their data whenever needed. The system additionally monitors user content for malicious attacks and hacks, and provides notification alerts relating to the same.

Claims13

Dependent claims

A computer-implemented method for automated monitoring and storage of digital website content maintained at a third party server, wherein the third party server is operated independently of and is in wireless communications with a Content Retrieval System (CRS) that is authorized to access the digital website content, comprising the steps of:

automatically retrieving from a CRS database a first index list comprising metadata associated with a first version of a particular digital website;
automatically communicating to the third party server a request for current metadata associated with a second version of the particular digital website;
in response to receipt at the CRS of the current metadata associated with the second version of the particular digital website, automatically comparing the current metadata to the first index list of metadata associated with the first version of the particular digital website;
identifying one or more changes in the second version of the particular digital website as compared to the first version of the particular digital website based on the comparison between the current metadata associated with the second version of the particular digital website and the first index list;
retrieving from the third party server digital website content corresponding only to the identified one or more changes between the second version and the first version of the particular digital website;
generating a second index list comprising the current metadata associated with the second version of the particular digital website;
associating the retrieved digital website content corresponding only to the identified one or more changes between the second version and the first version of the particular digital website with the second index list in the CRS database;
automatically and periodically comparing the retrieved digital website content corresponding only to the identified one or more changes between the second version and the first version of the particular digital website to one or more predefined phishing, malware, or hacking activities;
and
upon determination that the retrieved digital website content corresponding only to the identified one or more changes between the second version and the first version of the particular digital website matches at least one of the one or more predefined phishing, malware, or hacking activities, reverting the second version of the particular digital website back to the first version of the particular digital website.

7 more elements

automatically and periodically receiving current metadata associated with a current version of a particular digital website from the third party server;
automatically and periodically retrieving from a CRS database a prior index list comprising pre-stored metadata associated with a prior version of the particular digital website;
comparing via the CRS the current metadata to the prior index list to detect one or more differences between the current metadata and the pre-stored metadata, wherein the one or more differences between the current metadata and the pre-stored metadata are indicative of one or more differences between the current version of the particular digital website and the prior version of the particular digital website;
if the one or more differences between the current metadata and the pre-stored metadata are detected, retrieving from the third party server one or more specific website digital content files associated only with the current metadata corresponding to the one or more differences between the current metadata and the pre-stored metadata;
automatically generating a current index list via the CRS corresponding to the current metadata associated with the current version of the particular digital website;
associating the current index list with the retrieved one or more specific website digital content files;
storing the current index list and the retrieved one or more specific website digital content files in the CRS database;
automatically and periodically comparing the retrieved one or more specific website digital content files to one or more predefined phishing, malware, or hacking activities;
and
upon determination that the retrieved one or more specific website digital content files matches at least one of the one or more predefined phishing, malware, or hacking activities, reverting the current version of the particular digital website back to the prior version of the particular digital website.

7 more elements

Dependencies are inferred from the claim text.

Facts

Application: 13/303,629Filed 23 Nov 2011 · us provisional application
Priority: 26 Nov 2010
Granted: 30 Jun 2015
Term ends: Not estimatedThe source records don’t support an estimate.

Classification6 codes

G06F 11/1448
Point-in-time backing up or restoration of persistent data: management of the data involved in backup or backup restore
G06F 11/3034
Monitoring arrangements specially adapted to the computing system or computing system component being monitored: where the computing system…
G06F 11/3089
Monitoring: monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors,…
G06F 16/907
Details of database functions independent of the retrieved data types: retrieval characterised by using metadata, e.g. metadata not derived from…