This project is read-only.

Security Blueprints release 20090913

Rating: No reviews yet
Downloads: 161
Released: Sep 13, 2009
Updated: Nov 5, 2009 by tonstgmn
Dev status: Stable Help Icon

Recommended Download

Application TST.SharePointObjects.SecurityBluePrint_1.0.0.0_Build20090913.zip
application, 81K, uploaded Sep 16, 2009 - 161 downloads

Release Notes

This is the first release of Security Blueprints.
See the SharePoint Objects weblog for a more detailed introduction: http://www.tonstegeman.com/so/Lists/Posts/Post.aspx?ID=3
Installation and configuration instructions are available here: http://www.tonstegeman.com/so/Lists/Posts/Post.aspx?ID=2

Security Blueprints
SharePoint 2007 contains a lot of options for security configuration. In larger site collections, it is very easy to loose the overview of how the security in your site collections is configured. Publishing parts of the content in your site collections for anonymous users, makes this even harder. And if you grant your power users the permissions to manage the security settings themselves, it suddenly is impossible to keep an overview. If you have done support for a SharePoint environment and have tried to solve security issues, you probably are familiar with this problem. Security blueprints can help you in this scenario. These blueprints are a report of all security related settings in your sites. In the first version of the product, these reports are published as XML files. By creating your own XSLT stylesheets, you can use this product to create your own reports on the security setup of your SharePoint sites.

A number of sample support questions that can be addressed easier using Security Blueprints:
  • I am getting all these request e-mails asking me to grant users permissions. How do I find all places where my e-mail address is configured to be the contact for access requests?
  • The Table of Contents web part does not take permissions into account. We have a number of sub sites with unique permissions, but my users see all subsites. In my other site collection, this works as expected. Using a security blueprint, you can easily check the permissions on these sites and find out users see the subsites in the navigation, because anonymous access is turned on for these sites.
  • I have granted my project managers our custom permission level that allows them to add people to specific SharePoint groups, but it does not work. They cannot add users. In another site collection, this works as described. By comparing security blue prints from the 2 site collections, you can quickly find out the custom permission level misses one of the critical permissions.

The most important settings that are (currently) included in the report:
  • SharePoint sitegroups and their permissions
  • Permission levels
  • Lists / Document libraries and their security settings
  • Anonymous settings
  • Request Access settings
  • Activated Site Features
  • Activated Site Collection Features
  • Site Collection Administrators

Reviews for this release

No reviews yet for this release.