|
|
Secure Separation
The purpose of the secure separation design pattern is to secure information by separating it in individual sites and lists. Ideally, people want to secure specific information, such as classified documents. To do this, they typically look for “item level security.” While this is logical and the only means in typical large database systems, such as document management systems, it is both a) challenging to implement and b) challenging to maintain.
Using the secure separation design pattern within SharePoint, you have an extraordinarily elegant way to secure information in a way that is very obvious to users and very easy to maintain. The result is that this pattern actually delivers much higher levels of security.
The basic design is to put information into separate sites or lists based upon how secure you want the information. Thus, for instance, you could have a site for Top Secret, one for Classified, and one for Unclassified. Each could have its own document library. Then, by using a standard Tiered or Matrix design, you can have a dashboard that presents the information from all of these secure separate sites to make it look like one site.
Partner Extranet
Our scenario within Breeze is a Partner Extranet. Each Partner has their own workspace where they work on projects with the organization. Below is a screenshot of a site for a Joint Venture project with a partner. It is a project workspace. This resides in the Extranet that is a separate Web Application.
Click here to access the Joint Venture workspace in the Partner Extranet of Breeze.
Because of the integration of the Breeze design, employees can see information from the Extranet within the Intranet (a separate Web Application).
Their dashboards provide an integrated view across the different partner workspaces of the Extranet. Below is a screenshot of the Issues for a Project Manager.
Note that this display contains Issues from the Extranet, as well as, issues from internal projects.
Click here to see the Issues display.
|
|