BCSEC3006: Managing Group Security


Groups can be an often overlooked part of security. While some groups and channels used to be vital and full of important information, they can be left abandoned to form another Group. Other times, Groups are made for specific projects, and following the project's completion, everyone will leave. No matter the circumstance, Groups left empty may have sensitive data in them. Ensuring that Group permissions are properly set at the point of creation, and that they are removed when vacated, is a critical part of IT security. 

By the end of the video, you will be able to:

  • Find empty Groups via the Groups Grid
  • Archive/Delete Groups based on their application
  • Set up Group policies by default when they're created (for Google)
  • Notify stakeholders of empty Groups

Using the Groups Grid, Alerts, and Workflows

What Type of Groups Can BetterCloud Find?

This very much depends on the full integration and their naming conventions. You can find a list below:

  • 365: Distribution List**, Mail-Enabled Security**, O365 (Unified), Security
    • **Cannot take action on these Groups due to API restrictions
  • Box: Group
  • DropBox: User Manager, Company Managed, System Managed
  • Google: Group
  • Namely: Group, Team, Office Location
  • OneLogin: Group, Role
  • Okta: App Group, Everyone, Okta Group
  • Salesforce: All Customer Portal, PRM Organization, Regular, Role, Role and Subordinates Intern
  • Slack: Public Channels and User Groups
  • ZenDesk: Groups and Organizations

Now that you know how to remediate issues via Workflows moving forward, let's take a look at how you can discover files that have already been shared outside your organization, potentially with sensitive information, through Content Scanning. You can move on to this next module by clicking here.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request