Security Concerns and Account Permissions in SharePoint 2010 Explained

June 5, 2012

Robert Schifreen brings us the tenth installment of his SharePoint 2010 series in his ZDNet.co.uk post, “Security on the Farm: Accounts and Permissions.” Shifreen explains that SharePoint’s most important database is SharePoint_config but that if it breaks, you’re best bet is to rebuild from your notes and restore backed-up content databases. Why? Schifreen points out that restoring a backup of SharePoint_config isn’t actually supported by Microsoft and rarely works in practice.

The author also has this to share about the nuances of a SharePoint deployment:

When you start building and running a SharePoint farm, you will come across dozens of seemingly unsolvable problems that turn out to be merely down to permissions.

He goes on to say,

Best practice is then to use separate accounts for installing various underlying services, databases, and so on…The most tempting option, of course, is to forget best practice and just use one account for running all the SharePoint internal stuff. The upside is that things will work a little better, with fewer permission-related errors. There are two downsides. First, if a hacker manages to penetrate the account he’ll have access to the entire farm rather than just a half or a third of it. Secondly, splitting everything across multiple accounts can actually aid troubleshooting in some cases because, by glancing at the server’s security log, the account that caused the problem will give you a clue as to why things are going wrong.

Schifreen’s topic of security is a valuable one in the world of big data that is continuously growing across on-premise and cloud platforms. Consider a comprehensive out of the box solution, like Fabasoft Mindbreeze, to extend your SharePoint system with the added certified security benefits.

Fabasoft Mindbreeze Enterprise “finds every scrap of information within a very short time, whether document, contract, note, e-mail or calendar entry, in intranet or internet, person- or text-related. The software solution finds all required information, regardless of source, for its users.” Further, Mindbreeze offers certified security and reliability with regular external audits of their relevant standards ISO 27001, ISO 20000, ISO 9001, and SAS 70 Tup II. The solution is worth a second look at www.mindbreeze.com.

Philip West, June 5, 2012

Sponsored by Pandia.com

Comments

One Response to “Security Concerns and Account Permissions in SharePoint 2010 Explained”

  1. Security Concerns and Account Permissions in SharePoint 2010 … | ARB Security Solutions on June 5th, 2012 7:11 am

    […] SharePoint Blog Post From SharePoint Security – Google Blog Search: Robert Schifreen brings us the tenth installment of his SharePoint 2010 series in his ZDNet.co.uk […]

  • Archives

  • Recent Posts

  • Meta