Groove's Built-In Security


Updated: April 1, 2008

Applies To: Groove Server 2007

This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.


Topic Last Modified: 2009-01-05

Securing Internet communications is based on achieving four main objectives: authentication of users and devices, confidentiality of communications, data integrity, and authorization. How you set up your network to obtain these objectives depends mostly on the software you are managing.

Groove client software addresses fundamental security issues via the following built-in mechanisms:

  • Data encryption helps assure confidentiality of all information exchanges, whether on a LAN or across the Internet.

  • Groove accounts can be password or smart card-protected.

  • Built-in authentication systems allow Groove users to verify the identity of other Groove users.

  • Role-based access control, defined by Groove workspace creators, determines how workspace members access and interact with content.

  • Progressive slow-down of the password window display after repeated incorrect password attempts protects against external parties using password discovery scripts to access Groove.

  • Users with Office-compatible antivirus software on their Groove devices can enable automatic virus filtering of files in their Groove account preferences.

  • Workspace version restrictions allow users to create workspaces supported only in the current or a later version of Groove, and to accept invitations only to workspaces that were created in the current or a later version of Groove. Administrators can enable this restriction by setting a Groove Manager domain policy accordingly.

  • File type restrictions limit the types of allowed files to those specified in Microsoft Office as “safe for sharing.” Administrators can enable this restriction by setting a Groove Manager domain policy.

  • Groove users can select options for restricting the delivery of Groove messages from other Groove users. For example, Groove can be configured to accept messages from only “known Groove contacts”, that is, contacts who are either in a user’s contact list, verified by the user or administrator, or who are members of at least one of the user’s workspaces.