Select Page

SharePoint Insecurity

Trish Crespo | | January 22, 2014

Read the headlines and you will find yet another business that has fallen victim to a data leak. There have even been a couple of headliners that have named SharePoint as the cause or reason behind a data leak. Is it really fair to blame a non-security product for a leak? Let’s point the finger at the real reason behind these leaks: lack of security planning and proper implementation. In the following text, I will discuss some of the major points that should be considered for applying security within a SharePoint environment.

Disclaimer: Any system, or environment, can be hacked, even with proper configurations in place. The goal is to make it difficult and down-right inconvenient for a hacker to pursue your data.

What Do You Know?

Before you can start planning security measures for SharePoint, you need to know what your SharePoint environment will be used for. This is important because it gives you an idea of where and how security should be applied. For example, if your business will be utilizing SharePoint for an external facing website there are a few things to consider such as identifying an authentication method for external access, locking down entry fields to mitigate SQL injections, and configuring the firewall. You will also need to know what type of content will be stored in SharePoint. For example, if you are using SharePoint to store sensitive information such as classified documents, financial information, or personally identifiable information, you will need to ensure those storage locations have stringent access control.

So, how can I apply security to SharePoint without hindering its purpose?

Great question! Yes, SharePoint is all about sharing, but that does not mean its contents are free to distribute outside of set boundaries. Further, it also does not mean that anything can be uploaded. SharePoint has a number of security features that should be enabled to maintain control over the data and minimize exploitation.


Guess what? SharePoint and antivirus are friends! Every version of SharePoint has the capability of integrating with your existing antivirus software. This integration allows for antivirus scanning of documents upon upload and download. It can also attempt to clean or delete infected files. There are other features that are included in the antivirus protection, such as scheduled scans, which should be reviewed and considered when configuring the antivirus settings.

A couple things to keep in mind:

  • The antivirus application must be installed on all machines running Windows SharePoint Services.
  • Some folders may need to be excluded from scanning to keep from unexpected behaviors, details here: MS Support Article.

For configuration instructions, please check out this TechNet document.

SQL Security

No one needs to tell you how important databases are to the functionality of SharePoint. Don’t let them fall victim to malicious attacks. You can apply security to your SQL databases in a couple of ways. One way is to change the default TCP ports. Hackers know about the default ports, so it is a great idea to change the default listening ports and manually configure the firewall to allow access. Another security measure is to run SQL Server services by using an account with minimal permissions.

Least-Privileged Administration

No one likes too much overhead administration, but when it means lessening the chance of exploit, it may be worth the extra effort. Implementing Least-Privileged administration requires that accounts are only created with the permissions required to perform its task. The reasoning behind this type of administration is to ensure that no single account can take down the environment. This is accomplished by organizing certain roles to specific accounts. Normally there will be a couple of standard accounts used for the installation and configuration of SharePoint; however, with a Least-Privileged implementation, you will have accounts dedicated to Service Apps, Web Apps, Farm service, and even an account for Crawl.


To increase security across your SharePoint environment you may need to start using AD Federation Service and look at configuring zones in your web applications. AD Federation Service will integrate with your existing AD and expand out to provide claims-based authentication for external users. Forms-based claims are not recommended for authentication due to credentials being sent as plaintext. Plaintext data is very easy for sniffers to capture, so you want to stick with a method that will provide some layer of defense. Regarding zones, it is a good idea to configure additional zones to control paths to your sites. The additional zones available are Intranet, Extranet, Internet, and Custom. The good news is that claims-based authentication works across all zones!

Microsoft’s SharePoint collaboration software is an excellent tool for enterprise users. Six ideas are offered in this white paper to help IT professionals bolster their SharePoint security.

Content Control

Let me tell you about a little known security measure called IRM. SharePoint offers file security through IRM (Information Rights Management) and it does this by enabling the following features:

  • Encrypts downloaded files
  • Limits who and what can decrypt files
  • Limits user rights to files (example: User can’t print or copy text from the file.)

Implementing IRM for SharePoint does require a server with the Rights Management Service role. IRM can be applied to any Library or List within SharePoint.

Patching & Updates

The last point of interest I want to cover is the good ole patching and updating of the SharePoint environment. Keeping systems up to date is critical to any environment, because it ensures that system flaws are corrected. If you fail to apply critical patches and updates in a timely fashion, you will definitely be leaving your environment open to exploitation. In a SharePoint environment you will need to stay on top of updates for SQL, SharePoint, Windows Server, and any other applicable enterprise software.  Keep in mind that these patches and updates should be installed onto a testing environment first prior to applying them to a development or production environment. This will ensure that any breaks due to the patch or upgrade will not affect business operations.

As you can see there are quite a few security measures that can be implemented across a SharePoint environment, and these are not all inclusive. Remember, with SharePoint you can find a way to balance the need for sharing against the need to secure. It is very easy to install SharePoint, but it is quite the opposite to find and cover all the bases in terms of security. I hope this post will get you started in the right direction and also get rid of your SharePoint insecurity!

Subscribe to Our Blog

Never miss a post! Stay up to date with the latest database, application and analytics tips and news. Delivered in a handy bi-weekly update straight to your inbox. You can unsubscribe at any time.

ORA-12154: TNS:could not resolve the connect identifier specified

Most people will encounter this error when their application tries to connect to an Oracle database service, but it can also be raised by one database instance trying to connect to another database service via a database link.

Jeremiah Wilton | March 4, 2009

Oracle EPM Cloud Vs. On-Premises: What’s the Difference?

EPM applications help measure the business performance. This post will help you choose the best EPM solutions for your organization’s needs and objectives.

Bobby Ellis | April 10, 2018

12c Upgrade Bug with SQL Tuning Advisor

Learn the steps to take on your Oracle upgrade 11.2 to 12.1 if you’re having performance problems. Oracle offers a patch and work around to BUG 20540751.

Megan Elphingstone | March 22, 2017

Work with Us

Let’s have a conversation about what you need to succeed and how we can help get you there.


Work for Us

Where do you want to take your career? Explore exciting opportunities to join our team.