Locating shadow vulnerable datastores for cloud data table/API/data lake stores
In one aspect, a computerized method for locating one or more shadow vulnerable datastores for cloud-platform datastores includes the step of identifying a cloned data store of an original datastore in a cloud database instance. It includes the step of determining that the cloned datastore comprises a shadow vulnerable datastore. It includes the step of defining a security posture of the cloned datastore. It includes the step of publishing a digitized data clone security differential report comprising the security posture and one or more remediations to fix security posture issues.
1. A computerized method for locating one or more shadow vulnerable datastores for cloud-platform datastores, comprising:
identifying a cloned data store of an original datastore in a cloud database instance;
determining that the cloned datastore comprises a shadow vulnerable datastore;
defining a security posture of the cloned datastore; and
publishing a digitized data clone security differential report comprising the security posture and one or more remediations to fix security posture issues.
2. The computerized method of claim 1 , wherein the step of identifying the cloned datastore of an other datastore further comprises:
with a data clone detection engine:
obtaining one or more operational logs for all datastores within an enterprise; and
using the one or more operation logs to determine a plurality of clone operations and classifications to determine a contents of the data in the original datastore.
3. The computerized method of claim 2 , wherein the step of identifying the cloned datastore of the other datastore further comprises:
obtaining a plurality of identities of a plurality of entities with a datastore; and
identifying a plurality of clone data sets.
4. The computerized method of claim 3 , wherein the step of identifying the cloned datastore of the other datastore further comprises:
mapping all a plurality of relationships of the plurality of cloned datasets to a plurality of specified security properties.
5. The computerized method of claim 3 , wherein the step of identifying the cloned datastore of the other datastore further comprises:
identifying all a plurality of users accessing cloud-based datastore;
identifying each location of the plurality of users accessing cloud-based datastore;
determining whether accesses are encrypted;
determining whether the accesses are public or private, and
determining whether there are different roles utilized in obtaining access.
6. The method of claim 1 , wherein the step of determining that the cloned datastore comprises a shadow vulnerable datastore further comprises:
determining that there is a mismatch in one or more security postures between the original datastore and the cloned datastore.
7. The method of claim 1 , wherein the security posture comprises a plurality of security posture gaps.
8. The method of claim 7 , wherein the step of defining a security posture of the cloned datastore further comprises:
determining that the cloned datastore is not encrypted; and
determining that the cloned datastore is exposed to a different set of users than the original datastore is exposed to.
9. The method of claim 6 , wherein the step of defining a security posture of the cloned datastore further comprises:
determining that the cloned datastore is has a different set of access levels from a public access perspective than the original datastore.
10. The method of claim 7 , wherein the step of defining a security posture of the cloned datastore further comprises:
determining that the cloned datastore is shared with a different set of vendors than the original datastore; and
determining that the cloned datastore is shared with a different set of third-party systems than the original datastore.
11. The method of claim 1 , wherein the cloud database instance is operative in a cloud computing-based data warehouse.