We claim:
1. A method for predicting connectivity of seismic objects determined from seismic data collected from a subterranean region, said method comprising the steps of:
a) dividing said subterranean region into cells and determining from said seismic data the value of a pre-selected seismic attribute in each cell;
b) choosing a threshold criterion for the value of said seismic attribute;
c) determining for each cell in said subterranean region whether the value of said seismic attribute satisfies said threshold criterion;
d) identifying seismic objects containing only connected cells that satisfy the attribute criterion, using a pre-selected definition of connectivity;
e) repeating steps b-d for at least one different value of said attribute value threshold; and
f) tracking each identified seismic object for changes in its size, spatial position, and connections to other seismic objects, all as a function of attribute threshold value.
2. The method of claim 1, wherein the results from step f are used to predict connectivity of geologic features in said subterranean region.
3. The method of claim 1, wherein all seismic objects defined in step d smaller than a pre-selected minimum size are discarded from consideration.
4. The method of claim 1, wherein all seismic objects defined in step d larger than a pre-selected maximum size are discarded from consideration.
5. The method of claim 1, wherein a 3-D visual display is used to present the results in step d, thereby aiding said tracking in step f.
6. The method of claim 1, wherein a 2-D hierarchical tree display is used to graphically depict the results of step f.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A method for security checking in a database environment having multiple heterogeneous database servers, the method comprising:
receiving first configuration information and second configuration information from a database security skin, wherein the first configuration information identifies a first set of one or more security checks to be run against a first database server within the multiple heterogeneous database servers and wherein the second configuration information identifies a second set of one or more security checks to be run against a second database server within the multiple heterogeneous database servers;
running the first set of one ore more security checks against the first database server based on the first configuration information;
running the second set of one or more security checks against the second database server based on the second configuration information; and
determining a security state for the first database server and the second database server.
2. The method of claim 1, wherein running the first set of one or more security checks includes:
sending data requests to the first database server; and
receiving return data from the first database server.
3. The method of claim 1, wherein a given security check within the first set of one or more security checks is added through a pluggable security check module.
4. The method of claim 1, wherein the database security skin includes instructions for how to report security state information.
5. The method of claim 4, wherein the instructions for how to report security state information include instructions for sending security state information to a remote device.
6. The method of claim 4, wherein the instructions for how to report security state information include statistics or metrics to be collected.
7. The method of claim 1, wherein determining a security state includes identifying at least one security violation.
8. The method of claim 7, wherein the database security skin includes instructions for how to resolve the at least one security violation.
9. The method of claim 1, wherein the first configuration information identifies a frequency with which the set of one or more security checks is to be executed.
10. The method of claim 1, further comprising:
reporting errors that occur during execution to an error file.
11. An apparatus for security checking in a database environment, the apparatus comprising:
a database security skin that includes first configuration information and second configuration information from a database security skin, wherein the first configuration information identifies a first set of one or more security checks to be run against a first database server within the multiple heterogeneous database servers and wherein the second configuration information identifies a second set of one or more security checks to be run against a second database server within the multiple heterogeneous database servers; and
a security mechanism, wherein the security mechanism receives the database security skin, runs the first set of one or more security checks against the first database server based on the first configuration information, runs the second set of one or more security checks against the second database server based on the second configuration information, and determines a security state for the first database server and the second database server.
12. The apparatus of claim 11, wherein the security mechanism runs the first set of one or more security checks by sending data requests to the first database server and receiving return data from the first database server.
13. The apparatus of claim 11, wherein the security mechanism includes a pluggable security check module and wherein a given security check within the first set of one or more security checks is added through the pluggable security check module.
14. The apparatus of claim 11, wherein the database security skin includes instructions for how to report security state information.
15. The apparatus of claim 14, wherein the security mechanism sends security state information to a remote device based on the instructions for how to report security state information.
16. The apparatus of claim 14, wherein the instructions for how to report security state information include statistics or metrics to be collected.
17. The apparatus of claim 11, wherein the security mechanism identifies at least one security violation.
18. The apparatus of claim 17, wherein the database security skin includes instructions for how to resolve the at least one security violation.
19. The apparatus of claim 11, wherein the database security skin identifies a frequency with which the at least one security check is to be executed.
20. A computer program product, in a computer readable medium, for security checking in a database environment, the computer program product comprising:
instructions for receiving first configuration information and second configuration information from a database security skin, wherein the first configuration information identifies a first set of one or more security checks to be run against a first database server within the multiple heterogeneous database servers and wherein the second configuration information identifies a second set of one or more security checks to be run against a second database server within the multiple heterogeneous database servers;
instructions for running the first set of one ore more security checks against the first database server based on the first configuration information;
instructions for running the second set of one or more security checks against the second database server based on the second configuration information; and
instructions for determining a security state for the first database server and the second database server.