Use Case

Audit S3 access permissions

Untangle the various access policies, bucket policies, and IAM roles that control access to your data.
The Open Raven data catalog with the filter of "Access: IAM User Terry Crisp can Write, Read"
User icon

Shrinking the scope

Analyzing data lake permissions is painful and often avoided until it simply can’t be put off any longer. HIPAA or PCI-DSS audits are a typical catalyst for the effort, and both first begin with an understanding of where a specific type of data resides, whether it’s patient health information or cardholder data. Open Raven begins by automatically locating all data services and then pinpointing the sensitive data at rest, allowing you to shrink the scope of your efforts to the critical few places that matter. And the definition of sensitive data can be as sophisticated as needed, directly modeling your definition of personal data, patient health information or anything else.
Command says "Find Healthcare Data accessible by Terry Crisp" and shows Open Raven finding assets with healthcare data
Three circles converging icon

Complexity conquered

With the job reduced to a few locations where sensitive data is stored, each repository can be analyzed with a couple of clicks. Who has access to a particular bucket? What access does a particular person or principal have to sensitive data? What peering relationships exist within the VPC storing the data that would allow for transfer elsewhere? Is there external access to the data from a 3rd Party? Open Raven provides clear answers to these questions such that audits that formerly took hours or days are reduced to minutes. And reporting out? The platform’s 3-D map-based visualizations depict external connections and peering relationships effortlessly, and other IAM-related data is stated plainly in the UI or downloadable as detailed JSON.
Open Raven platform with screens of map, asset details, data catalog.