SharePoint Security

https://i0.wp.com/www.titus.com/blog/wp-content/uploads/2013/01/take_control_sharepoint_security_sm.pngRecently, TITUS had the opportunity to ask over 200 SharePoint users about their top SharePoint security concerns. The survey confirmed for us what we had been hearing from our customers over the past number of years – organizations are storing a wide variety of sensitive information in SharePoint, from financial and HR information, to intellectual property, to personally identifiable information (PII).

This raises a number of security challenges for organizations. From our survey, we found that 79% of organizations see permissions management and site ownership as the top SharePoint security challenge. Not surprising considering that while new SharePoint deployments very often attempt to segregate sensitive content, most organizations find that users prefer to store information based on topic, function or project.

What are the most pressing SharePoint security challenges in your organization?

You can see more results from our survey, and learn more about how the TITUS approach to SharePoint security helps to address the issues raised, by having a look at our infographic on the topic.

Get the Infographic

Trackbacks

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of the author. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided "as-is". The author shall not be liable for any damages whatsoever arising out of the content or use of this blog.
%d bloggers like this: