Patent Grant
9721115
Reference is made to U.S. patent application Ser. No. 13/014,762, filed Jan. 27, 2011, and entitled “AUTOMATIC RESOURCE OWNERSHIP ASSIGNMENT SYSTEMS AND METHODS”, the disclosure of which is hereby incorporated by reference and priority of which is hereby claimed pursuant to 37 CFR 1.78(a)(1) and (2)(i).
Reference is also made to the following patents and patent applications, owned by assignee, the disclosures of which are hereby incorporated by reference:
U.S. Pat. Nos. 7,555,482 and 7,606,801;
U.S. Published Patent Application Nos. 2007/0244899, 2008/0271157, 2009/0100058, 2009/0119298; 2009/0265780; 2011/0060916 and 2011/0061111; and
U.S. patent application Ser. No. 12/673,691.
The present invention relates to automatic resource ownership assignment systems and methods.
The following patent publications are believed to represent the current state of the art:
U.S. Pat. Nos. 5,465,387; 5,899,991; 6,338,082; 6,393,468; 6,928,439; 7,031,984; 7,068,592; 7,403,925; 7,421,740; 7,555,482, 7,606,801 and 7,743,420; and
U.S. Published Patent Application Nos.: 2003/0051026; 2004/0249847; 2005/0108206; 2005/0203881; 2005/0086529; 2006/0064313; 2006/0184530; 2006/0184459; 2007/0203872; 2007/0244899; 2008/0271157; 2009/0100058; 2009/0119298 and 2009/0265780.
The present invention provides improved systems and methodologies for automatic resource ownership assignment.
There is thus provided in accordance with a preferred embodiment of the present invention a system for automatic folder ownership assignment in an enterprise computer network, the system including modify/write permissions scrutinizing functionality operative for ascertaining which first folders, among a first multiplicity of folders in an enterprise computer network, have at least one of modify and write permissions to entities other than IT administration entities, and adding the first folders to a list of base-folder candidates for ownership assignment, first pruning functionality operative for defining a second multiplicity of folders, the second multiplicity of folders being a subset of the first multiplicity of folders which does not include the first folders, all descendents of the first folders and all ancestors of the first folders, permissions scrutinizing functionality operative for ascertaining which second folders among the second multiplicity of folders, have permissions to entities other than IT administration entities and adding the second folders to the list of base-folder candidates for ownership assignment, second pruning functionality operative for defining a third multiplicity of folders, the third multiplicity of folders being a subset of the second multiplicity of folders which does not include the second folders, all descendents of the second folders and all ancestors of the second folders, topmost folder scrutinizing functionality operative for ascertaining which third folders among the third multiplicity of folders are topmost folders and adding the third folders to the list of base-folder candidates for ownership assignment, and possible ownership assignment recommendation functionality operative for recommending possible assignment of ownership of at least one of the list of base-folder candidates.
Preferably, the possible ownership assignment recommendation functionality includes functionality operative for recommending possible assignment of ownership of at least one of the list of base-folder candidates to an entity which has been most active with regard to the at least one of the list of base-folder candidates.
Preferably, the modify/write permissions scrutinizing functionality is also operative for ascertaining which first additional folders, among the first multiplicity of folders in the enterprise computer network include at least sensitive content, and adding the first additional folders to the list of base-folder candidates for ownership assignment. Additionally or alternatively, the permissions scrutinizing functionality is also operative for ascertaining which second additional folders among the second multiplicity of folders include at least sensitive content, and adding the second additional folders to the list of base-folder candidates for ownership assignment.
There is also provided in accordance with another preferred embodiment of the present invention a system for automatic folder ownership assignment in an enterprise computer network, the system including modify/write permissions scrutinizing functionality operative for ascertaining which first folders, among a first multiplicity of folders in an enterprise computer network, have at least one of modify and write permissions to entities other than IT administration entities and include at least sensitive content, and adding the first folders to a list of base-folder candidates for ownership assignment, first pruning functionality operative for defining a second multiplicity of folders, the second multiplicity of folders being a subset of the first multiplicity of folders which does not include the first folders, all descendents of the first folders and all ancestors of the first folders, permissions scrutinizing functionality operative for ascertaining which second folders among the second multiplicity of folders, have permissions to entities other than IT administration entities and include at least sensitive content, and adding the second folders to the list of base-folder candidates for ownership assignment, second pruning functionality operative for defining a third multiplicity of folders, the third multiplicity of folders being a subset of the second multiplicity of folders which does not include the second folders, all descendents of the second folders and all ancestors of the second folders, topmost folder scrutinizing functionality operative for ascertaining which third folders among the third multiplicity of folders are topmost folders and adding the third folders to the list of base-folder candidates for ownership assignment, and possible ownership assignment recommendation functionality operative for recommending possible assignment of ownership of at least one of the list of base-folder candidates.
Preferably, the possible ownership assignment recommendation functionality includes functionality operative for recommending possible assignment of ownership of at least one of the list of base-folder candidates to an entity which has been most active with regard to the at least one of the list of base-folder candidates.
There is further provided in accordance with yet another preferred embodiment of the present invention a system for automatic folder ownership assignment in an enterprise computer network, the system including actual modification scrutinizing functionality operative for ascertaining which first folders, among a first multiplicity of folders in an enterprise computer network, have been at least actually modified by entities other than IT administration entities, and adding the first folders to a list of base-folder candidates for ownership assignment, first pruning functionality operative for defining a second multiplicity of folders, the second multiplicity of folders being a subset of the first multiplicity of folders which does not include the first folders, all descendents of the first folders and all ancestors of the first folders, actual access scrutinizing functionality operative for ascertaining which second folders among the second multiplicity of folders, have been at least actually accessed by entities other than IT administration entities and adding the second folders to the list of base-folder candidates for ownership assignment, second pruning functionality operative for defining a third multiplicity of folders, the third multiplicity of folders being a subset of the second multiplicity of folders which does not include the second folders, all descendents of the second folders and all ancestors of the second folders, topmost folder scrutinizing functionality operative for ascertaining which third folders among the third multiplicity of folders are topmost folders and adding the third folders to the list of base-folder candidates for ownership assignment, and possible ownership assignment recommendation functionality operative for recommending possible assignment of ownership of at least one of the list of base-folder candidates.
Preferably, the possible ownership assignment recommendation functionality includes functionality operative for recommending possible assignment of ownership of at least one of the list of base-folder candidates to an entity which has been most active with regard to the at least one of the list of base-folder candidates.
Preferably, the actual modification scrutinizing functionality is also operative for ascertaining which first additional folders, among the first multiplicity of folders in the enterprise computer network include at least sensitive content, and adding the first additional folders to the list of base-folder candidates for ownership assignment. Additionally or alternatively, the actual access scrutinizing functionality is also operative for ascertaining which second additional folders among the second multiplicity of folders include at least sensitive content, and adding the second additional folders to the list of base-folder candidates for ownership assignment.
There is further provided in accordance with yet another preferred embodiment of the present invention a system for automatic folder ownership assignment in an enterprise computer network, the system including actual modification scrutinizing functionality operative for ascertaining which first folders, among a first multiplicity of folders in an enterprise computer network, have been at least actually modified by entities other than IT administration entities and include at least sensitive content, and adding the first folders to a list of base-folder candidates for ownership assignment, first pruning functionality operative for defining a second multiplicity of folders, the second multiplicity of folders being a subset of the first multiplicity of folders which does not include the first folders, all descendents of the first folders and all ancestors of the first folders, actual access scrutinizing functionality operative for ascertaining which second folders among the second multiplicity of folders, have been at least actually accessed by entities other than IT administration entities and include at least sensitive content, and adding the second folders to the list of base-folder candidates for ownership assignment, second pruning functionality operative for defining a third multiplicity of folders, the third multiplicity of folders being a subset of the second multiplicity of folders which does not include the second folders, all descendents of the second folders and all ancestors of the second folders, topmost folder scrutinizing functionality operative for ascertaining which third folders among the third multiplicity of folders are topmost folders and adding the third folders to the list of base-folder candidates for ownership assignment, and possible ownership assignment recommendation functionality operative for recommending possible assignment of ownership of at least one of the list of base-folder candidates.
Preferably, the possible ownership assignment recommendation functionality includes functionality operative for recommending possible assignment of ownership of at least one of the list of base-folder candidates to an entity which has been most active with regard to the at least one of the list of base-folder candidates.
There is further provided in accordance with yet another preferred embodiment of the present invention a system for automatic folder ownership assignment in an enterprise computer network, the system including sensitive content scrutinizing functionality operative for ascertaining which first folders, among a first multiplicity of folders in an enterprise computer network, include at least sensitive content, and adding the first folders to a list of base-folder candidates for ownership assignment, first pruning functionality operative for defining a second multiplicity of folders, the second multiplicity of folders being a subset of the first multiplicity of folders which does not include the first folders, all descendents of the first folders and all ancestors of the first folders, topmost folder scrutinizing functionality operative for ascertaining which second folders among the second multiplicity of folders are topmost folders and adding the second folders to the list of base-folder candidates for ownership assignment, and possible ownership assignment recommendation functionality operative for recommending possible assignment of ownership of at least one of the list of base-folder candidates.
Preferably, the possible ownership assignment recommendation functionality includes functionality operative for recommending possible assignment of ownership of at least one of the list of base-folder candidates to an entity which has been most active with regard to the at least one of the list of base-folder candidates.
There is yet further provided in accordance with still another preferred embodiment of the present invention a method for automatic folder ownership assignment in an enterprise computer network, the method including maintaining a list of base-folder candidates for ownership assignment, ascertaining which first folders, among a first multiplicity of folders in an enterprise computer network, have at least one of modify and write permissions to entities other than IT administration entities, and adding the first folders to the list of base-folder candidates for ownership assignment, defining a second multiplicity of folders, the second multiplicity of folders being a subset of the first multiplicity of folders which does not include the first folders, all descendents of the first folders and all ancestors of the first folders, ascertaining which second folders among the second multiplicity of folders, have permissions to entities other than IT administration entities and adding the second folders to the list of base-folder candidates for ownership assignment, defining a third multiplicity of folders, the third multiplicity of folders being a subset of the second multiplicity of folders which does not include the second folders, all descendents of the second folders and all ancestors of the second folders, ascertaining which third folders among the third multiplicity of folders are topmost folders and adding the third folders to the list of base-folder candidates for ownership assignment, and recommending possible assignment of ownership of at least one of the list of base-folder candidates.
Preferably, the recommending includes recommending possible assignment of ownership of at least one of the list of base-folder candidates to an entity which has been most active with regard to the at least one of the list of base-folder candidates.
Preferably, the method also includes ascertaining which first additional folders, among the first multiplicity of folders in the enterprise computer network include at least sensitive content, and adding the first additional folders to the list of base-folder candidates for ownership assignment. Additionally or alternatively, the method also includes ascertaining which second additional folders among the second multiplicity of folders include at least sensitive content, and adding the second additional folders to the list of base-folder candidates for ownership assignment.
There is also provided in accordance with another preferred embodiment of the present invention a method for automatic folder ownership assignment in an enterprise computer network, the method including maintaining a list of base-folder candidates for ownership assignment, ascertaining which first folders, among a first multiplicity of folders in an enterprise computer network, have at least one of modify and write permissions to entities other than IT administration entities and include at least sensitive content, and adding the first folders to the list of base-folder candidates for ownership assignment, defining a second multiplicity of folders, the second multiplicity of folders being a subset of the first multiplicity of folders which does not include the first folders, all descendents of the first folders and all ancestors of the first folders, ascertaining which second folders among the second multiplicity of folders, have permissions to entities other than IT administration entities and include at least sensitive content, and adding the second folders to the list of base-folder candidates for ownership assignment, defining a third multiplicity of folders, the third multiplicity of folders being a subset of the second multiplicity of folders which does not include the second folders, all descendents of the second folders and all ancestors of the second folders, ascertaining which third folders among the third multiplicity of folders are topmost folders and adding the third folders to the list of base-folder candidates for ownership assignment, and recommending possible assignment of ownership of at least one of the list of base-folder candidates.
Preferably, the recommending includes recommending possible assignment of ownership of at least one of the list of base-folder candidates to an entity which has been most active with regard to the at least one of the list of base-folder candidates.
There is further provided in accordance with yet another preferred embodiment of the present invention a method for automatic folder ownership assignment in an enterprise computer network, the method including maintaining a list of base-folder candidates for ownership assignment, ascertaining which first folders, among a first multiplicity of folders in an enterprise computer network, have been at least actually modified by entities other than IT administration entities, and adding the first folders to the list of base-folder candidates for ownership assignment, defining a second multiplicity of folders, the second multiplicity of folders being a subset of the first multiplicity of folders which does not include the first folders, all descendents of the first folders and all ancestors of the first folders, ascertaining which second folders among the second multiplicity of folders, have been at least actually accessed by entities other than IT administration entities and adding the second folders to the list of base-folder candidates for ownership assignment, defining a third multiplicity of folders, the third multiplicity of folders being a subset of the second multiplicity of folders which does not include the second folders, all descendents of the second folders and all ancestors of the second folders, ascertaining which third folders among the third multiplicity of folders are topmost folders and adding the third folders to the list of base-folder candidates for ownership assignment, and recommending possible assignment of ownership of at least one of the list of base-folder candidates.
Preferably, the recommending includes recommending possible assignment of ownership of at least one of the list of base-folder candidates to an entity which has been most active with regard to the at least one of the list of base-folder candidates.
Preferably, the method also includes ascertaining which first additional folders, among the first multiplicity of folders in the enterprise computer network include at least sensitive content, and adding the first additional folders to the list of base-folder candidates for ownership assignment. Additionally or alternatively, the method also includes ascertaining which second additional folders among the second multiplicity of folders include at least sensitive content, and adding the second additional folders to the list of base-folder candidates for ownership assignment.
There is yet further provided in accordance with still another preferred embodiment of the present invention a method for automatic folder ownership assignment in an enterprise computer network, the method including maintaining a list of base-folder candidates for ownership assignment, ascertaining which first folders, among a first multiplicity of folders in an enterprise computer network, have been at least actually modified by entities other than IT administration entities and include at least sensitive content, and adding the first folders to the list of base-folder candidates for ownership assignment, defining a second multiplicity of folders, the second multiplicity of folders being a subset of the first multiplicity of folders which does not include the first folders, all descendents of the first folders and all ancestors of the first folders, ascertaining which second folders among the second multiplicity of folders, have been at least actually accessed by entities other than IT administration entities and include at least sensitive content, and adding the second folders to the list of base-folder candidates for ownership assignment, defining a third multiplicity of folders, the third multiplicity of folders being a subset of the second multiplicity of folders which does not include the second folders, all descendents of the second folders and all ancestors of the second folders, ascertaining which third folders among the third multiplicity of folders are topmost folders and adding the third folders to the list of base-folder candidates for ownership assignment, and recommending possible assignment of ownership of at least one of the list of base-folder candidates.
Preferably, the recommending includes recommending possible assignment of ownership of at least one of the list of base-folder candidates to an entity which has been most active with regard to the at least one of the list of base-folder candidates.
There is yet further provided in accordance with still another preferred embodiment of the present invention a method for automatic folder ownership assignment in an enterprise computer network, the method including maintaining a list of base-folder candidates for ownership assignment, ascertaining which first folders, among a first multiplicity of folders in an enterprise computer network, include at least sensitive content, and adding the first folders to the list of base-folder candidates for ownership assignment, defining a second multiplicity of folders, the second multiplicity of folders being a subset of the first multiplicity of folders which does not include the first folders, all descendents of the first folders and all ancestors of the first folders, ascertaining which second folders among the second multiplicity of folders are topmost folders and adding the second folders to the list of base-folder candidates for ownership assignment, and recommending possible assignment of ownership of at least one of the list of base-folder candidates.
Preferably, the recommending includes recommending possible assignment of ownership of at least one of the list of base-folder candidates to an entity which has been most active with regard to the at least one of the list of base-folder candidates.
The present invention will be understood and appreciated more fully from the following detailed description, taken in conjunction with the drawings in which:
Reference is made to
The term “ownership” is used throughout to designate authority and accountability within an enterprise as distinct to legal ownership in the normal sense of the word. “Ownership” of a data element, an organization function, a resource, whether IT related or not, a service, a workflow or any other element in an enterprise designates authority and accountability with respect thereto within the enterprise. The definitions of “owner” and “owning” are of corresponding meaning.
The automatic folder ownership assignment system of
The modify/write permissions scrutinizing functionality ascertains which first folders, among a first multiplicity of folders in an enterprise computer network, have at least one of modify and write permissions to entities other than IT administration entities, and adds the first folders to a list of base-folder candidates for ownership assignment. The first pruning functionality defines a second multiplicity of folders, which is a subset of the first multiplicity of folders that does not include the first folders, all descendents of the first folders and all ancestors of the first folders.
The permissions scrutinizing functionality ascertains which second folders among the second multiplicity of folders, have permissions to entities other than IT administration entities and adds the second folders to the list of base-folder candidates for ownership assignment. The second pruning functionality defines a third multiplicity of folders which is a subset of the second multiplicity of folders that does not include the second folders, all descendents of the second folders and all ancestors of the second folders.
The topmost folder scrutinizing functionality ascertains which third folders among the third multiplicity of folders are topmost folders and adds the third folders to the list of base-folder candidates for ownership assignment.
The automatic folder ownership assignment system also includes possible ownership assignment functionality for designating possible assignment of ownership of at least one of the list of base-folder candidates.
As shown in
Subsequently, a second folder tree is defined (104) as a subset of the folder tree of the enterprise from which the first set of topmost folders, all descendents of each of the first set of topmost folders and all ancestors of each of the first set of topmost folders are removed. Thereafter, the second folder tree is preferably scrutinized (106) to identify a second set of topmost folders, each of which second set having at least read permissions to entities other than IT administration entities. Each of the second set of topmost folders is added (108) to the list of base-folder candidates for ownership assignment.
Subsequently, a third folder tree is defined (110) as a subset of the second folder tree from which the second set of topmost folders, all descendents of each of the second set of topmost folders and all ancestors of each of the second set of topmost folders are removed. Thereafter, the third folder tree is preferably scrutinized (112) to identify a third set of topmost folders, and each the third set is added (114) to the list of base-folder candidates for ownership assignment.
Thereafter, for each folder in the list of base-folders, the system identifies entities who have been most active with regard to the folder and then recommends (116) that ownership of the folder of all descendent folders thereof be assigned to one of the entities who have been most active with regard to the folder.
Reference is now made to
The automatic folder ownership assignment system of
The actual modification scrutinizing functionality ascertains which first folders, among a first multiplicity of folders in an enterprise computer network, have been at least actually modified by entities other than IT administration entities, and adds the first folders to a list of base-folder candidates for ownership assignment. The first pruning functionality defines a second multiplicity of folders, which is a subset of the first multiplicity of folders that does not include the first folders, all descendents of the first folders and all ancestors of the first folders.
The actual access scrutinizing functionality ascertains which second folders among the second multiplicity of folders, have been at least actually accessed by entities other than IT administration entities and adds the second folders to the list of base-folder candidates for ownership assignment. The second pruning functionality defines a third multiplicity of folders which is a subset of the second multiplicity of folders that does not include the second folders, all descendents of the second folders and all ancestors of the second folders.
The topmost folder scrutinizing functionality ascertains which third folders among the third multiplicity of folders are topmost folders and adds the third folders to the list of base-folder candidates for ownership assignment.
The automatic folder ownership assignment system also includes possible ownership assignment recommendation functionality for designating possible assignment of ownership of at least one of the list of base-folder candidates.
As shown in
Subsequently, a second folder tree is defined (204) as a subset of the folder tree of the enterprise from which the first set of topmost folders, all descendents of each of the first set of topmost folders and all ancestors of each of the first set of topmost folders are removed. Thereafter, the second folder tree is preferably scrutinized (206) to identify a second set of topmost folders, each of which second set having been at least actually accessed by entities other than IT administration entities. Each of the second set of topmost folders is added (208) to the list of base-folder candidates for ownership assignment.
Subsequently, a third folder tree is defined (210) as a subset of the second folder tree from which the second set of topmost folders, all descendents of each of the second set of topmost folders and all ancestors of each of the second set of topmost folders are removed. Thereafter, the third folder tree is preferably scrutinized (212) to identify a third set of topmost folders, and each the third set is added (214) to the list of base-folder candidates for ownership assignment.
Thereafter, for each folder in the list of base-folders, the system identifies entities who have been most active with regard to the folder and then recommends (216) that ownership of the folder of all descendent folders thereof be assigned to one of the entities who have been most active with regard to the folder.
Reference is now made to
The automatic folder ownership assignment system of
The sensitive content scrutinizing functionality ascertains which first folders, among a first multiplicity of folders in an enterprise computer network, comprise at least sensitive content, and adds the first folders to a list of base-folder candidates for ownership assignment. Sensitive content may be, for example, confidential financial information or confidential personal information. The first pruning functionality defines a second multiplicity of folders, which is a subset of the first multiplicity of folders that does not include the first folders, all descendents of the first folders and all ancestors of the first folders.
The topmost folder scrutinizing functionality ascertains which second folders among the second multiplicity of folders are topmost folders and adds the second folders to the list of base-folder candidates for ownership assignment.
The automatic folder ownership assignment system also includes possible ownership assignment recommendation functionality for designating possible assignment of ownership of at least one of the list of base-folder candidates.
As shown in
Subsequently, a second folder tree is defined (304) as a subset of the folder tree of the enterprise from which the first set of topmost folders, all descendents of each of the first set of topmost folders and all ancestors of each of the first set of topmost folders are removed. Thereafter, the second folder tree is preferably scrutinized (306) to identify a second set of topmost folders, and each the second set is added (308) to the list of base-folder candidates for ownership assignment.
Thereafter, for each folder in the list of base-folders, the system identifies entities who have been most active with regard to the folder and then recommends (310) that ownership of the folder of all descendent folders thereof be assigned to one of the entities who have been most active with regard to the folder.
It will be appreciated by persons skilled in the art that the present invention is not limited by what has been particularly shown and described hereinabove. Rather, the invention also includes various combinations and subcombinations of the features described hereinabove as well as modifications and variations thereof, which would occur to persons skilled in the art upon reading the foregoing and which are not in the prior art.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5465387 | Mukherjee | Nov 1995 | A |
| 5729734 | Parker | Mar 1998 | A |
| 5889952 | Hunnicutt et al. | Mar 1999 | A |
| 5899991 | Karch | May 1999 | A |
| 6308173 | Glasser et al. | Oct 2001 | B1 |
| 6338082 | Schneider | Jan 2002 | B1 |
| 6393468 | McGee | May 2002 | B1 |
| 6772350 | Belani et al. | Aug 2004 | B1 |
| 6928439 | Satoh | Aug 2005 | B2 |
| 7017183 | Frey et al. | Mar 2006 | B1 |
| 7031984 | Kawamura et al. | Apr 2006 | B2 |
| 7068592 | Duvaut et al. | Jun 2006 | B1 |
| 7305562 | Bianco et al. | Dec 2007 | B1 |
| 7403925 | Schlesinger et al. | Jul 2008 | B2 |
| 7421740 | Fey et al. | Sep 2008 | B2 |
| 7555482 | Korkus | Jun 2009 | B2 |
| 7606801 | Faitelson et al. | Oct 2009 | B2 |
| 7716240 | Lim | May 2010 | B2 |
| 7743420 | Shulman et al. | Jun 2010 | B2 |
| 8533787 | Faitelson et al. | Sep 2013 | B2 |
| 8805884 | Faitelson et al. | Aug 2014 | B2 |
| 8875246 | Faitelson et al. | Oct 2014 | B2 |
| 8875248 | Faitelson et al. | Oct 2014 | B2 |
| 9146929 | Faitelson et al. | Sep 2015 | B2 |
| 9275061 | Faitelson et al. | Mar 2016 | B2 |
| 9372862 | Faitelson et al. | Jun 2016 | B2 |
| 20030048301 | Menninger | Mar 2003 | A1 |
| 20030051026 | Carter et al. | Mar 2003 | A1 |
| 20030231207 | Huang | Dec 2003 | A1 |
| 20040030915 | Sameshima et al. | Feb 2004 | A1 |
| 20040186809 | Schlesinger et al. | Sep 2004 | A1 |
| 20040249847 | Wang et al. | Dec 2004 | A1 |
| 20040254919 | Giuseppini | Dec 2004 | A1 |
| 20050086268 | Rogers | Apr 2005 | A1 |
| 20050086529 | Buchsbaum | Apr 2005 | A1 |
| 20050108206 | Lam et al. | May 2005 | A1 |
| 20050120054 | Shulman et al. | Jun 2005 | A1 |
| 20050203881 | Sakamoto et al. | Sep 2005 | A1 |
| 20050246762 | Girouard et al. | Nov 2005 | A1 |
| 20050278334 | Fey et al. | Dec 2005 | A1 |
| 20060064313 | Steinbarth et al. | Mar 2006 | A1 |
| 20060184459 | Parida | Aug 2006 | A1 |
| 20060184530 | Song et al. | Aug 2006 | A1 |
| 20060277184 | Faitelson et al. | Dec 2006 | A1 |
| 20070027872 | Johnson et al. | Feb 2007 | A1 |
| 20070061487 | Moore et al. | Mar 2007 | A1 |
| 20070073698 | Kanayama et al. | Mar 2007 | A1 |
| 20070094265 | Korkus | Apr 2007 | A1 |
| 20070101387 | Hua et al. | May 2007 | A1 |
| 20070112743 | Giampaolo et al. | May 2007 | A1 |
| 20070143859 | Ogi | Jun 2007 | A1 |
| 20070156659 | Lim | Jul 2007 | A1 |
| 20070156693 | Soin et al. | Jul 2007 | A1 |
| 20070203872 | Flinn et al. | Aug 2007 | A1 |
| 20070244899 | Faitelson et al. | Oct 2007 | A1 |
| 20070266006 | Buss | Nov 2007 | A1 |
| 20070282855 | Chen et al. | Dec 2007 | A1 |
| 20080034402 | Botz et al. | Feb 2008 | A1 |
| 20080162707 | Beck et al. | Jul 2008 | A1 |
| 20080172720 | Botz et al. | Jul 2008 | A1 |
| 20080270462 | Thomsen | Oct 2008 | A1 |
| 20080271157 | Faitelson et al. | Oct 2008 | A1 |
| 20090100058 | Faitelson et al. | Apr 2009 | A1 |
| 20090119298 | Faitelson et al. | May 2009 | A1 |
| 20090150981 | Amies et al. | Jun 2009 | A1 |
| 20090198892 | Alvarez et al. | Aug 2009 | A1 |
| 20090249446 | Jenkins et al. | Oct 2009 | A1 |
| 20090265780 | Korkus et al. | Oct 2009 | A1 |
| 20090320088 | Gill et al. | Dec 2009 | A1 |
| 20100037324 | Grant et al. | Feb 2010 | A1 |
| 20100070881 | Hanson et al. | Mar 2010 | A1 |
| 20100262625 | Pittenger | Oct 2010 | A1 |
| 20110010758 | Faitelson et al. | Jan 2011 | A1 |
| 20110060916 | Faitelson et al. | Mar 2011 | A1 |
| 20110061111 | Faitelson et al. | Mar 2011 | A1 |
| 20110184989 | Faitelson et al. | Jul 2011 | A1 |
| 20120221550 | Korkus et al. | Aug 2012 | A1 |
| 20120291100 | Faitelson et al. | Nov 2012 | A1 |
| 20130017314 | Yang et al. | Jan 2013 | A1 |
| 20130117315 | Faitelson et al. | May 2013 | A1 |
| 20140006453 | Faitelson et al. | Jan 2014 | A1 |
| 20150012572 | Faitelson et al. | Jan 2015 | A1 |
| 20150012573 | Faitelson et al. | Jan 2015 | A1 |
| 20150186392 | Faitelson et al. | Jul 2015 | A1 |
| 20150363427 | Faitelson et al. | Dec 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 1588889 | Mar 2005 | CN |
| 1248178 | Oct 2002 | EP |
| 2005-267237 | Sep 2005 | JP |
| 2010-287171 | Dec 2010 | JP |
| 2011030324 | Mar 2011 | WO |
| Entry |
|---|
| Varonis; DatVantage User Guide Version 1,0, Aug. 30, 2005, 71 pages. |
| Varonis: DatVantage User Guide Version 2.0, Aug. 24, 2006; 118 pages. |
| Varonis: DatVantage User Guide Version 2.5, Nov. 27, 2006; 124 pages. |
| Varonis: DatVantage User Guide Version 2.6, Dec. 15, 2006; 127 pages. |
| Varonis: DatVantage User Guide Version 2.7, Feb. 6, 2007; 131 pages. |
| Varonis: DatVantage User Guide Version 3.0, Jun. 20, 2007; 153 pages. |
| List of DataBase Tables in DatAdvantage 2.7, Feb. 6, 2007 1 page. |
| List of DataBase Tables in DatAdvantage 3.0, Jun. 20, 2007 1 page. |
| Sahadeb De, et al, “Secure Access Control in a Multi-user Geodatabase”, available on the Internet at the URL http://www10.giscafe.com.2005, 10 pages. |
| Findutils—GNU Project—Free Software Foundation (FSF), 3 pages, Nov. 2006. |
| Genunix: “Writing Filesystems—VFS and Vnode Interfaces” 5 pages, Oct. 2007. |
| S.R. Kleiman; “Vnodes: An Architecture for Multiple File System Types in Sun UNIX”, USENIX Association: Summer Conference Proceedings, Atlanta 1986, 10 pages. |
| Varonis: “White Paper: The Business Case for Data Governance”, Mar. 27, 2007, 8 pages. |
| Sara C Madeira, et al: “Biclustering Algorithms for Biological Data Analysis: A Survey”, IEEE Transactions on Computational Biology and Bioinformatics, vol. 1, No. 1, Jan.-Mar. 2004, 22 pages; http://www.cs.princeton.edu/courses/archive/spr05/cos598E/bib/bicluster,pdf. |
| Sara C. Madeira; Clustering, Fuzzy Clustering and Biclustering: An Overview; pp. 31-53, Jun. 27, 2003. |
| Varonis; “Accelerating Audits with Automation: Understanding Who's Accessing Your Unstructured Data”, Oct. 8, 2007; 7 pages. |
| Varonis; “Entitlement Review: A Practitioner's Guide”, 2007; 16 pages. |
| Edgar Weippl, et al; “Content-based Management of Document Access Control”, 14th International Conference on Applications of Prolog (INAP), 2001, 9 pages. |
| Alex Woodie; “Varonis Prevents Unauthorized Access to Unstructured Data”, Four Hundred Stuff, vol. 7, No. 29, Jul. 31, 2007, 4 pages. |
| English Translation of German Office Action dated Sep. 14, 2012; Appln. No. 11 2006 0001 378.5. |
| International Preliminary Report on Patentability issued Jul. 30, 2013; PCT/IL2011/000902. |
| International Preliminary Report on Patentability issued Jul. 30, 2013; PCT/IL2011/000903. |
| International Search Report and Written Opinion both dated May 23, 2011; PCT/IL11/00065. |
| International Search Report and Written Opinion both dated May 20, 2010; PCT/IL10/00069. |
| International Search Report and Written Opinion both dated May 24, 2011; PCT/IL11/00077. |
| International Search Report and Written Opinion both dated Nov. 15, 2011; PCT/IL11/00408. |
| International Search Report and Written Opinion both dated Apr. 13, 2013; PCT/IL11/00902. |
| U.S. Appl. No. 60/688,486, filed Jun. 7, 2005. |
| U.S. Appl. No. 61/240,726, filed Sep. 9, 2009. |
| USPTO NFOA mailed Feb. 12, 2008 in connection with U.S. Appl. No. 11/258,256. |
| USPTO FOA mailed Aug. 1, 2008 in connection with U.S. Appl. No. 11/258,256. |
| USPTO NFOA mailed Oct. 31, 2008 in connection with U.S. Appl. No. 11/635,736. |
| USPTO NFOA mailed Dec. 14, 2010 in connection with U.S. Appl. No. 11/786,522. |
| USPTO NFOA mailed Jul. 9, 2010 in connection with U.S. Appl. No. 11/789,884. |
| USPTO FOA mailed Dec. 14, 2010 in connection with U.S. Appl. No. 11/789,884. |
| USPTO NFOA dated Sep. 16, 2010 in connection with U.S. Appl. No. 11/871,028. |
| USPTO FOA dated Apr. 28, 2011 in connection with U.S. Appl. No. 11/871,028. |
| USPTO NFOA dated Sep. 14, 2012 in connection with U.S. Appl. No. 12/861,967. |
| USPTO NFOA dated Jul. 11, 2012 in connection with U.S. Appl. No. 13/014,762. |
| USPTO FOA dated Feb. 14, 2013 in connection with U.S. Appl. No. 13/014,762. |
| USPTO AA dated Aug. 30, 2013 in connection with U.S. Appl. No. 13/014,762. |
| USPTO NFOA dated Dec. 16, 2013 in connection with U.S. Appl. No. 13/014,762. |
| USPTO NOA mailed Mar. 28, 2014 in connection with U.S. Appl. No. 13/014,762. |
| USPTO RR dated Nov. 21, 2012 in connection with U.S. Appl. No. 13/106,023. |
| USPTO NFOA dated Mar. 1, 2013 in connection with U.S. Appl. No. 13/106,023. |
| USPTO NOA dated May 15, 2013 in connection with U.S. Appl. No. 13/106,023. |
| USPTO FOA dated Mar. 25, 2013 in connection with U.S. Appl. No. 13/303,826. |
| USPTO FOA dated Sep. 6, 2013 in connection with U.S. Appl. No. 13/378,115. |
| USPTO NFOA dated Feb. 6, 2015 in connection with U.S. Appl. No. 13/724,121. |
| USPTO NOA mailed May 22, 2015 in connection with U.S. Appl. No. 13/724,121. |
| USPTO NFOA dated May 14, 2014 in connection with U.S. Appl. No. 14/018,835. |
| USPTO NOA mailed Aug. 21, 2014 in connection with U.S. Appl. No. 14/018,835. |
| USPTO NFOA dated Apr. 10, 2015 in connection with U.S. Appl. No. 14/456,373. |
| USPTO FOA dated Oct. 6, 2015 in connection with U.S. Appl. No. 14/456,373. |
| USPTO NFOA dated Jun. 4, 2015 in connection with U.S. Appl. No. 14/498,189. |
| USPTO NOA mailed Oct. 26, 2015 in connection with U.S. Appl. No. 14/498,189. |
| USPTO NFOA dated Jun. 5, 2015 in connection with U.S. Appl. No. 14/498,373. |
| USPTO NOA mailed Apr. 26, 2016 in connection with U.S. Appl. No. 14/498,373. |
| USPTO NFOA dated Apr. 7, 2016 in connection with U.S. Appl. No. 14/834,864. |
| USPTO NFOA dated May 8, 2014 in connection with U.S. Appl. No. 13/724,028. |
| USPTO NOA mailed Aug. 19, 2014 in connection with U.S. Appl. No. 13/724,028. |
| Number | Date | Country | |
|---|---|---|---|
| 20160140142 A1 | May 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13106023 | May 2011 | US |
| Child | 13724028 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14498189 | Sep 2014 | US |
| Child | 15006482 | US | |
| Parent | 13724028 | Dec 2012 | US |
| Child | 14498189 | US |
