DLP for Google Workspace™

Welcome to SpinOne!

Today, we are going to be talking about SpinDLP for Google Workspace™.

Spin’s data loss, and leak prevention Data Protection solution.

Coming here to data audit, we’re greeted with full visibility, actionability, and automation around all shared data and all sensitive data.

Being able to see at a high level file sharing events, data that’s being flagged as sensitive, and how many security policies we’ve created to look for sensitive data or specific file sharing events to see how many have been triggered.

As with everything on Spin, nothing is one-size-fits all, and with that in mind, all our customers can customize what they believe to be high exposure, high risk, medium exposure, or medium risk for their shared and sensitive data.

Coming into the shared data section.

This is visibility into every single file sharing event. The ability to search for a document.

See that it’s being shared, see who the owner is, Rainier, who it’s being shared with, Andre, is an editor, that’s fine, he’s an employee.

But have the understanding that it’s also being shared to a user that’s outside of your organization.

In the specific instance, it looks like this data’s being shared to a personal email address.

If for whatever reason, you’re not comfortable with that, you would be able to select this data, stop selected sharing, not to your trusted employee, but only to that external user.

Of course, this is the manual way to go about things, but as with everything on Spin, you can automate this entire workflow to proactively look for a shared data events that contains sensitive data, that’s being shared to external users or entities that you’re not comfortable with and have Spin automatically revoke access .

Coming into sensitive data, every event that you see here is only appearing because it’s breaching a security policy that you would have created to look for specific types of sensitive data, whether it be PII, PHI, or PCI, even regular expressions using your own data dictionary, Spin can detect it and show you that event here.

Coming to shared users, this is giving you visibility on a user by user basis and even a domain basis of all the file sharing events that have occurred.

Coming here to security policies, this is where we have the automation backbone of SpinOne, and the ability to create DLP policies to look for, let’s say, data, coming from a user’s Google Drive™ that’s being shared by link to anyone with a link that contains sensitive data that we believe to be PI, PHI, PCI, any of these preset checkers and of course, if what we want to detect isn’t appearing here, we can, of course, utilize a regular expression using your own data dictionary and search for a specific keywords to keep it simple today, we’ll go ahead and say credit card number.

Now, what would you like Spin to do on your behalf when this data is detected?

We can make it private, we can transfer ownership, we can suspend the user, remove external users, and even remove public links, as well as a variety of other things.

To keep it simple, we can say, yeah, go ahead and remove external users.

Do you want Spin to do this action as soon as we detect it?

Or do you want us to give those entities access for let’s say, 90 days and at the end of the 90 days, then go ahead and revoke access?

Do you want to be notified that the security policy’s been triggered?

If so, which integration for notification would you like to utilize for notifications?

And lastly, to whom should the security policy apply, should apply to everyone? Only a handful of users?

Should it apply to only specific org units ?

Or maybe we want to apply it to only specific groups within our Google Workspace™.

The choice is yours, but the visibility, actionability, and automation, is here with your SpinDLP solution.