Automation framework
US-9177167-B2 · Nov 3, 2015 · US
US10181046B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10181046-B2 |
| Application number | US-201314101883-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 10, 2013 |
| Priority date | Apr 4, 2012 |
| Publication date | Jan 15, 2019 |
| Grant date | Jan 15, 2019 |
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.
An enterprise level data element review system including a data access event collection subsystem operative to collect data access event notifications relating to ones of a multiplicity of data elements, a data element metadata modification subassembly receiving an output from the data access event collection subsystem and providing a script indicating which data elements have had a metadata modification over a given period of time, and a data element dancer operative to collect at least one of metadata and access permissions for a plurality of data elements which is substantially less than the multiplicity of data elements and is selected on the basis of the script.
Opening claim text (preview).
The invention claimed is: 1. A system comprising a non-transitory, tangible computer-readable medium in which computer program instructions are stored, which instructions, when read by a computer, cause the computer to review data elements across an enterprise, said system comprising: a data access event collection failure monitoring subsystem operative to continuously ascertain a data access events collection failure period of time in which collection of data access events of at least some data elements across said enterprise has failed; and a data element crawler operative, in response to said continuously ascertaining said data access events collection failure period of time: to ascertain a multiplicity of data elements across said enterprise which have had a change in access permissions during said data access events collection failure period of time; and to collect only said access permissions of users having access permissions to each of said multiplicity of data elements across said enterprise, which said multiplicity of data elements across said enterprise have had said change in access permissions during said data access events collection failure period of time. 2. A method for enterprise level data element review comprising: continuously ascertaining a data access events collection failure period of time in which collection of data access events of at least some data elements across an enterprise has failed; responsive to said continuously ascertaining said data access events collection failure period of time, ascertaining a multiplicity of data elements across said enterprise which have had a change in access permissions during said data access events collection failure period of time; and responsive to said ascertaining said multiplicity of data elements across said enterprise which have had a change in access permissions over said data access events collection failure period of time, crawling only over said multiplicity of data elements which have had said change in access permissions during said data access events collection failure period of time to collect only said access permissions of users having access permissions to each of said multiplicity of data elements across said enterprise.
Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40) · CPC title
involving long-term monitoring or reporting · CPC title
Error or fault reporting or storing · CPC title
in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems · CPC title
Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.