Access your Pro+ Content below.
How SharePoint 2010 simplifies e-discovery
This article is part of the SharePoint Insider issue of February 2011
For organizations that are subject to federal regulations, those regs apply no matter where an organization’s data is actually stored. As such, SharePoint data is subject to the same regulatory controls as any other type of data. In some ways, this can be problematic. Earlier versions of SharePoint were not created with regulatory compliance in mind. In fact, e-discovery capabilities and other compliance-related features were only first introduced in SharePoint 2007. That being the case, it’s important to consider how organizations that use SharePoint will comply with e-discovery requests. Deploying SharePoint with e-discovery in mind The key to complying with e-discovery requests is to deploy and manage SharePoint in a way that facilitates e-discovery. When it comes to the initial SharePoint deployment, the best thing you can do is to deploy it as a single farm rather than allowing multiple, independent SharePoint servers. That way, even if your SharePoint data exists on multiple servers within multiple lists and document ...
Access this PRO+ Content for Free!
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
Features in this issue
You still can‘t manage individual sites and site collections from Central Administration in SharePoint 2010; but there are eight sections that you can manage.
SharePoint 2010 gives you access to far more e-discovery features than any previous release -- features that will ease compliance issues when they arise.
Get a handle on broad and granular permission management techniques to keep critical SharePoint 2010 data safe.