CryptoCollaboration For SharePoint 2007

COMMENTED ISSUE: Server Error in '/' Application.

AdamBuenz — Wed, 28 May 2008 19:37:27 GMT

After deployment I only get:

Server Error in '/' Application.
--------------------------------------------------------------------------------

Required permissions cannot be acquired.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Security.Policy.PolicyException: Required permissions cannot be acquired.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[PolicyException: Required permissions cannot be acquired.]
System.Security.SecurityManager.ResolvePolicy(Evidence evidence, PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset, PermissionSet& denied, Boolean checkExecutionPermission) +2709488
System.Security.SecurityManager.ResolvePolicy(Evidence evidence, PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset, PermissionSet& denied, Int32& securitySpecialFlags, Boolean checkExecutionPermission) +57

[FileLoadException: Could not load file or assembly 'CryptoCollab.Core.Cryptography, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a736d58e7eb2362e' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)]
System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +0
System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +211
System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +141
System.Reflection.Assembly.Load(String assemblyString) +25
System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +32

[ConfigurationErrorsException: Could not load file or assembly 'CryptoCollab.Core.Cryptography, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a736d58e7eb2362e' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)]
System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +596
System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory() +3596761
System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai) +46
System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig) +177
System.Web.Compilation.BuildProvidersCompiler..ctor(VirtualPath configPath, Boolean supportLocalization, String outputAssemblyName) +180
System.Web.Compilation.CodeDirectoryCompiler.GetCodeDirectoryAssembly(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories, Boolean isDirectoryAllowed) +350
System.Web.Compilation.BuildManager.CompileCodeDirectory(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories) +125
System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +378

[HttpException (0x80004005): Could not load file or assembly 'CryptoCollab.Core.Cryptography, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a736d58e7eb2362e' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)]
System.Web.Compilation.BuildManager.ReportTopLevelCompilationException() +57
System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +612
System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters) +521

[HttpException (0x80004005): Could not load file or assembly 'CryptoCollab.Core.Cryptography, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a736d58e7eb2362e' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +3540923
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +69
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +275

--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832
Comments: ** Comment from web user: AdamBuenz **

This look like a CAS error for the bin deployment. I am investigating this now, it might have been specific to my environment.

CREATED ISSUE: Server Error in '/' Application.

mmiekkon — Tue, 15 Apr 2008 16:29:50 GMT

UPDATED RELEASE: Alpha Release V4 - Non-Production v 0.0.0.4 (Mar 29, 2008)

Sat, 29 Mar 2008 15:00:37 GMT

The largest changes that exist in version 0.0.0.4 of CryptoCollaboration is the support for Microsoft word documents as opposed to just simple text files, as was the case in version 0.0.0.3. If you want to view the changes that were made to the code outside of the support for Microsoft Word documents, view the 0.0.0.3 release.

For a screen shot diary regarding the support of Microsoft Word documents, see the home page of the project site, which details the operations.

For a more detailed list and summary of the changes in this revision, visit:
[url:http://www.sharepointsecurity.com/blog]

There were also some minor code changes that occurred while the code is appropriately retrofitted in order to support more robust exception handling.

The initial documentation for installation and operations will be updated accordingly, however for the time being is not my focus. However, it is coming.

UPDATED WIKI: Home

AdamBuenz — Fri, 28 Mar 2008 19:23:49 GMT

Project Description
CryptoCollaboration for SharePoint 2007 (works for both Microsoft Office Server 2007 as well as Windows SharePoint Services 3.0) presents a native end-to-end encryption solution targeted at SharePoint lists and their related metadata.

One of the largest tribulations that exists within current collaboration systems is the reliance on making objects security aware based solely on provided principle attributes, characteristically noticed in SharePoint through its indigenous options for security trimming the interface. While this is certainly a method that promotes some level of privacy, security, and data integrity, it does not account for data storage while information is considered in a transitional state. Furthermore, this is amplified by the fact that numerous industry regulations require that when organizational data is stored in a system as SharePoint, that it is not directly callable in plain text, however promotes a secondary layer of privacy

CryptoCollaboration is broken up into two primary segments, the CryptoCollaboration Encryption Engine (CEE) and its related SharePoint interface components. The CEE is called directly from the ECB (Edit Content Block) menu provided by the native SharePoint ListFormWebPart (your orthodox SharePoint list interface), pooling all the fields that are considered encryption worthy and encrypting or decrypting them based on user interaction. Since there are current limitations to the fields out of an arbitrary list item that can be harvested (field types such as URL’s demand that certain formats be used and therefore cannot be subject to encryption operations).

Once the encryption / decryption operations are triggered, the CEE will encrypt / decrypt the stored fields with an algorithm that the user selects out of the interface (currently supported encryption algorithms are RC2, Rijndael (AES), Triple DES, or BlowFish). All code that the CEE leverages is CLS-Compliant and 100% managed.

Adam Buenz
http://sharepointsecurity.com

CHANGES TO EXCEPTION HANDLING

There have been some brief modifications that were done to the exception handling in order to support failure and success pages within the CryptoCollaboration operations page. This was the reason that the latest release was delayed. As such, I am going to be releasing the new version this evening. The exception handling changes are visible when working with the cryptographic operations.

When successful encryption or decryption occurs, you will see a success screen that brings you to the the operations success page. Once you click ok, you will be kicked to the list view page similar to the past operations.

When an cryptographic operation fails for any reason, you are brought to a similar page, however relaying that a general application exception has occurred. Usually this type of error is encountered if there is a mismatch between the encryption key and initialization parameters provided during encryption, and the subsequent offering during decryption.

CryptoCollaboration NOW SUPPORTS MICROSOFT WORD DOCUMENTS!!!

Here Is An Example Of THE EVEN NEW Document Level Encryption For Document Libraries (this is Alpha Version 0.0.0.4, Being Released On March 26 at 6:00 p.m. PST):

CryptoCollaboration now supports Microsoft Word Documents! This should bring full circle several of the aggregate encryption problems that have lead to the creation of CryptoCollaboration in the first place. So, let me demonstrate the encryption of a stored Microsoft Word document, and then its subsequent decryption back to plain text directly within a SharePoint environment.

Here, I am creating a new document from a SharePoint document library on a test instance:

And then, I am saving the document back to the server since this is where the encryption is going to take place:

Once the document is stored, I am going to call the CryptoCollaboration operations page so that I can interact with the CryptoCollaboration Encryption Engine. Once I am in the operations page, since I am just testing the file, I am going to restrict the encryption operations to the file of the list item, and then set the algorithm Rijndael:

Now, when I open the document from the SharePoint document library, the contents of the document are subsequently encrypted:

As you can see, the document contents are now unreadable.

Now, let's decrypt the document. Once in the operations page, as similar to past versions, the interface will be trimmed with the options as selected through previous operations:

After decryption, we can see that Microsoft Word contents are then converted to back to plain-text:

Here Is An Example Of THE NEW Document Level Encryption For Document Libraries (this is Alpha Version 0.0.0.3, Being Released On March 26 at 6:00 p.m. PST):

One of the largest changes in version 0.0.0.3 is the option to not solely use OOB lists, but document libraries as well. Document libraries are now supported through three main levels of operations:

1) Encrypt Fields
2) Encrypt Files
3) Encrypt Files and Fields

The operations page has been adjusted to compensate for said available selections.

The only limitation right now is it has only been tested with standards text documents, while the testing and code compensation that is required for Microsoft Word files will most likely be released at a later occasion. If you want to just view standard list encryption, you can view the screenshots provided in the secondary section that show Task List encryption, this will briefly go over the document level encryption for stored text documents.

Firstly, as was unavailable in the previous versions, the "Encrypt / Decrypt This Item" menu item is available from the document library ECB menus and toolbars.

Here is the encryption option as available from the Toolbar within a SharePoint document library:

Here is the encryption option as available from the ECB menu within a SharePoint document library

On the old CryptoCollaboration Operations page, there was no granular selection for files and metadata since files were not supported. However, when a SharePoint document library is now selected (i.e. we look whether the parent list is of Microsoft.SharePoint.SPDocumentLibrary), there are more selections that are available from the operations page.

So, you have one of three options to select when working with encryption in document libraries. I am going to choose to encrypt both the fields in the list as well as the file that is held within the document library. I could also choose to piece meal encrypt the pieces as I want.

In this document library, I am storing a document named "test.txt" which contains the string "test" within it. This is a piece of mutable data that I want to encrypt, as well as the column "test" which also contains the string "test". Here is the document contents.

And here is the list item and its related field values:

Now, after running the encryption operations, when I get kicked to the list item view, I can see my fields are encrypted:

As well the text file content. which contained the string "test", has also been encrypted:

Now, when I go to decrypt the list item, the field selection out of the interface is trimmed, to only include the action that was initially chosen is populated as the only selection in order to reduce confusion, as well similar to previous version of the the encryption engine, it will feed the algorithm that was initially chosen when tripping the encryption algorithm.

After the decryption is run, we can immediately see that the fields are decrypted:

As well, the file contents are also unscrambled back to the original plaintext:

THIS IS VERSION 0.0.0.2 WHICH HAS BEEN DEPRECATED IN FAVOR OF 0.0.0.3 WHICH SUPPORTS FILE ENCRYPTION (Being Released On March 26 at 6:00 p.m. PST)

Here Is An Example Of Some Task List Encryption (this is Alpha Version 0.0.0.2, Being Released On March 25 at 6:00 p.m. PST):

First, I Visit A List That I Would Like To Encrypt, In This Case A Task List With A New Test Item:

Secondly, Once The Item Is Created, I Call The Encryption Engine (CEE) From Either The List ECB or The List Form ToolBar:

From The ECB:

From The ToolBar:

Then After Selecting Entering The Operations Page:

The Selecting Your Available Encryption Options:

Now The Values Are Encrypted:

The Decryption Looks At The Algorithm, And Trims The Radio Button List For You:

The SharePoint List Item Is Then Returned To Plain Text:

UPDATED RELEASE: Alpha Release V2 - Non-Production v 0.0.0.2 (Mar 25, 2008)

Wed, 26 Mar 2008 19:29:52 GMT

*This release has been deprecated, and therefore abandoned for v 0.0.0.4 since it supports Microsoft Word Documents as well as orthodox file encryption operations.*

The largest change that you will notice in this revision of CryptoCollaboration is the toggling of objects out of the interface. The code has been adjusted to accommodate the following process:

1) If an item is encrypted with an arbitrary encryption algorithm, there are two hidden properties that are set, IsEncrypted and Algorithm. IsEncrypted tells CEE whether the item has been encrypted, and Algorithm gets that last known encryption algorithm used when encrypting the SPListitem field values. When an item is encrypted now, it toggles the interface so that you are only offered the decrypt button if it has been encrypted, and the encrypt value if the properties return that it is fit for encryption. Furthermore, since the CEE is aware of your last known algorithm when encrypting, it adjusts the RadioButtonList selection interface so that you are only offered the encryption algorithm that was used during the encryption process. Thanks to Gary LaPointe for pointing out that this would be useful!

2) Andrew Connell gave me the advice that it would also be nice if the encryption operations page was available from the ToolBar on the view and edit list form pages. I have adjusted the feature now so natively for all the appended list types the encryption button is available now. When you firstly encrypt an item, you will see that this option is available. The permissions trimming that was natively offered in the first revision of the feature still applies (requires Edit List rights since you will be modifying the value of the fields).

There were also some ascetic changes, like the List Specifics panel was returning the SPListItem name as opposed to the parent list item, etc. These have also been corrected.

In this revision, the cryptography base library also has the new methods that target doing native file encryption directly from the SharePoint interface. However, the elements required for the UI to be complete (namely, selecting whether you want metadata, file, or both encrypted) is not complete so is scheduled to be released with the next revision.

THE DOCUMENTATION FOR THIS RELEASE IS STILL BEING DEVELOPED!!! THE V1 DOCUMENTATION IS *STILL* AVAILABLE IN THE V1 RELEASE!!!

UPDATED RELEASE: Alpha Release V2 - Non-Production v 0.0.0.2 (Mar 25, 2008)

Wed, 26 Mar 2008 19:28:59 GMT

The largest change that you will notice in this revision of CryptoCollaboration is the toggling of objects out of the interface. The code has been adjusted to accommodate the following process:

1) If an item is encrypted with an arbitrary encryption algorithm, there are two hidden properties that are set, IsEncrypted and Algorithm. IsEncrypted tells CEE whether the item has been encrypted, and Algorithm gets that last known encryption algorithm used when encrypting the SPListitem field values. When an item is encrypted now, it toggles the interface so that you are only offered the decrypt button if it has been encrypted, and the encrypt value if the properties return that it is fit for encryption. Furthermore, since the CEE is aware of your last known algorithm when encrypting, it adjusts the RadioButtonList selection interface so that you are only offered the encryption algorithm that was used during the encryption process. Thanks to Gary LaPointe for pointing out that this would be useful!

2) Andrew Connell gave me the advice that it would also be nice if the encryption operations page was available from the ToolBar on the view and edit list form pages. I have adjusted the feature now so natively for all the appended list types the encryption button is available now. When you firstly encrypt an item, you will see that this option is available. The permissions trimming that was natively offered in the first revision of the feature still applies (requires Edit List rights since you will be modifying the value of the fields).

There were also some ascetic changes, like the List Specifics panel was returning the SPListItem name as opposed to the parent list item, etc. These have also been corrected.

In this revision, the cryptography base library also has the new methods that target doing native file encryption directly from the SharePoint interface. However, the elements required for the UI to be complete (namely, selecting whether you want metadata, file, or both encrypted) is not complete so is scheduled to be released with the next revision.

THE DOCUMENTATION FOR THIS RELEASE IS STILL BEING DEVELOPED!!! THE V1 DOCUMENTATION IS *STILL* AVAILABLE IN THE V1 RELEASE!!!

UPDATED RELEASE: Alpha Release V3 - Non-Production v 0.0.0.3 (Mar 26, 2008)

Wed, 26 Mar 2008 19:24:03 GMT

*This release has been deprecated, and therefore abandoned for v 0.0.0.4 since it supports Microsoft Word Documents as well as these provided operations.*

The largest change in this release (v 0.0.0.3) is the support for SPFile objects as opposed to just working with standards OOB list types. There has also been some performance adjustments made against the encryption engine (CEE) in order to handle threading better based on the passed parameters that are assimilated into the engine. Exact metrics have not been gathered for this release in terms of aggregate encryption performance, however the change is notable even directly within the interface when invoking certain functions.

SPFile operations have only been tested with very rudimentary text documents created through NotePad, testing and support for other documents will be supported in later revisions in the product, since the Alpha versions of CryptoCollaboration are only meant to target the verification of approach and methods. For the time being, standard, simple documents will remain supported.

The operations page has been adjusted in order to support various types of encryption approaches when working with document libraries, either encrypting metadata, the file, or metadata and the file. These selections are records in hidden property locations in order to trim the interface when decryption operations are later run on encrypted functions.

UPDATED RELEASE: Alpha Release V3 - Non-Production v 0.0.0.3 (Mar 26, 2008)

Wed, 26 Mar 2008 19:21:55 GMT

This release has been deprecated, and therefore abandoned for v 0.0.0.4 since it supports Microsoft Word Documents as well as these provided operations.

The largest change in this release (v 0.0.0.3) is the support for SPFile objects as opposed to just working with standards OOB list types. There has also been some performance adjustments made against the encryption engine (CEE) in order to handle threading better based on the passed parameters that are assimilated into the engine. Exact metrics have not been gathered for this release in terms of aggregate encryption performance, however the change is notable even directly within the interface when invoking certain functions.

SPFile operations have only been tested with very rudimentary text documents created through NotePad, testing and support for other documents will be supported in later revisions in the product, since the Alpha versions of CryptoCollaboration are only meant to target the verification of approach and methods. For the time being, standard, simple documents will remain supported.

The operations page has been adjusted in order to support various types of encryption approaches when working with document libraries, either encrypting metadata, the file, or metadata and the file. These selections are records in hidden property locations in order to trim the interface when decryption operations are later run on encrypted functions.

UPDATED WIKI: Home

AdamBuenz — Wed, 26 Mar 2008 19:18:31 GMT

Project Description
CryptoCollaboration for SharePoint 2007 (works for both Microsoft Office Server 2007 as well as Windows SharePoint Services 3.0) presents a native end-to-end encryption solution targeted at SharePoint lists and their related metadata.

One of the largest tribulations that exists within current collaboration systems is the reliance on making objects security aware based solely on provided principle attributes, characteristically noticed in SharePoint through its indigenous options for security trimming the interface. While this is certainly a method that promotes some level of privacy, security, and data integrity, it does not account for data storage while information is considered in a transitional state. Furthermore, this is amplified by the fact that numerous industry regulations require that when organizational data is stored in a system as SharePoint, that it is not directly callable in plain text, however promotes a secondary layer of privacy

CryptoCollaboration is broken up into two primary segments, the CryptoCollaboration Encryption Engine (CEE) and its related SharePoint interface components. The CEE is called directly from the ECB (Edit Content Block) menu provided by the native SharePoint ListFormWebPart (your orthodox SharePoint list interface), pooling all the fields that are considered encryption worthy and encrypting or decrypting them based on user interaction. Since there are current limitations to the fields out of an arbitrary list item that can be harvested (field types such as URL’s demand that certain formats be used and therefore cannot be subject to encryption operations).

Once the encryption / decryption operations are triggered, the CEE will encrypt / decrypt the stored fields with an algorithm that the user selects out of the interface (currently supported encryption algorithms are RC2, Rijndael (AES), Triple DES, or BlowFish). All code that the CEE leverages is CLS-Compliant and 100% managed.

Adam Buenz
http://sharepointsecurity.com

CryptoCollaboration NOW SUPPORTS MICROSOFT WORD DOCUMENTS!!!

Here Is An Example Of THE EVEN NEW Document Level Encryption For Document Libraries (this is Alpha Version 0.0.0.4, Being Released On March 26 at 6:00 p.m. PST):

CryptoCollaboration now supports Microsoft Word Documents! This should bring full circle several of the aggregate encryption problems that have lead to the creation of CryptoCollaboration in the first place. So, let me demonstrate the encryption of a stored Microsoft Word document, and then its subsequent decryption back to plain text directly within a SharePoint environment.

Here, I am creating a new document from a SharePoint document library on a test instance:

And then, I am saving the document back to the server since this is where the encryption is going to take place:

Once the document is stored, I am going to call the CryptoCollaboration operations page so that I can interact with the CryptoCollaboration Encryption Engine. Once I am in the operations page, since I am just testing the file, I am going to restrict the encryption operations to the file of the list item, and then set the algorithm Rijndael:

Now, when I open the document from the SharePoint document library, the contents of the document are subsequently encrypted:

As you can see, the document contents are now unreadable.

Now, let's decrypt the document. Once in the operations page, as similar to past versions, the interface will be trimmed with the options as selected through previous operations:

After decryption, we can see that Microsoft Word contents are then converted to back to plain-text:

Here Is An Example Of THE NEW Document Level Encryption For Document Libraries (this is Alpha Version 0.0.0.3, Being Released On March 26 at 6:00 p.m. PST):

One of the largest changes in version 0.0.0.3 is the option to not solely use OOB lists, but document libraries as well. Document libraries are now supported through three main levels of operations:

1) Encrypt Fields
2) Encrypt Files
3) Encrypt Files and Fields

The operations page has been adjusted to compensate for said available selections.

The only limitation right now is it has only been tested with standards text documents, while the testing and code compensation that is required for Microsoft Word files will most likely be released at a later occasion. If you want to just view standard list encryption, you can view the screenshots provided in the secondary section that show Task List encryption, this will briefly go over the document level encryption for stored text documents.

Firstly, as was unavailable in the previous versions, the "Encrypt / Decrypt This Item" menu item is available from the document library ECB menus and toolbars.

Here is the encryption option as available from the Toolbar within a SharePoint document library:

Here is the encryption option as available from the ECB menu within a SharePoint document library

On the old CryptoCollaboration Operations page, there was no granular selection for files and metadata since files were not supported. However, when a SharePoint document library is now selected (i.e. we look whether the parent list is of Microsoft.SharePoint.SPDocumentLibrary), there are more selections that are available from the operations page.

So, you have one of three options to select when working with encryption in document libraries. I am going to choose to encrypt both the fields in the list as well as the file that is held within the document library. I could also choose to piece meal encrypt the pieces as I want.

In this document library, I am storing a document named "test.txt" which contains the string "test" within it. This is a piece of mutable data that I want to encrypt, as well as the column "test" which also contains the string "test". Here is the document contents.

And here is the list item and its related field values:

Now, after running the encryption operations, when I get kicked to the list item view, I can see my fields are encrypted:

As well the text file content. which contained the string "test", has also been encrypted:

Now, when I go to decrypt the list item, the field selection out of the interface is trimmed, to only include the action that was initially chosen is populated as the only selection in order to reduce confusion, as well similar to previous version of the the encryption engine, it will feed the algorithm that was initially chosen when tripping the encryption algorithm.

After the decryption is run, we can immediately see that the fields are decrypted:

As well, the file contents are also unscrambled back to the original plaintext:

THIS IS VERSION 0.0.0.2 WHICH HAS BEEN DEPRECATED IN FAVOR OF 0.0.0.3 WHICH SUPPORTS FILE ENCRYPTION (Being Released On March 26 at 6:00 p.m. PST)

Here Is An Example Of Some Task List Encryption (this is Alpha Version 0.0.0.2, Being Released On March 25 at 6:00 p.m. PST):

First, I Visit A List That I Would Like To Encrypt, In This Case A Task List With A New Test Item:

Secondly, Once The Item Is Created, I Call The Encryption Engine (CEE) From Either The List ECB or The List Form ToolBar:

From The ECB:

From The ToolBar:

Then After Selecting Entering The Operations Page:

The Selecting Your Available Encryption Options:

Now The Values Are Encrypted:

The Decryption Looks At The Algorithm, And Trims The Radio Button List For You:

The SharePoint List Item Is Then Returned To Plain Text:

UPDATED WIKI: Home

AdamBuenz — Wed, 26 Mar 2008 18:56:42 GMT

Project Description
CryptoCollaboration for SharePoint 2007 (works for both Microsoft Office Server 2007 as well as Windows SharePoint Services 3.0) presents a native end-to-end encryption solution targeted at SharePoint lists and their related metadata.

One of the largest tribulations that exists within current collaboration systems is the reliance on making objects security aware based solely on provided principle attributes, characteristically noticed in SharePoint through its indigenous options for security trimming the interface. While this is certainly a method that promotes some level of privacy, security, and data integrity, it does not account for data storage while information is considered in a transitional state. Furthermore, this is amplified by the fact that numerous industry regulations require that when organizational data is stored in a system as SharePoint, that it is not directly callable in plain text, however promotes a secondary layer of privacy

CryptoCollaboration is broken up into two primary segments, the CryptoCollaboration Encryption Engine (CEE) and its related SharePoint interface components. The CEE is called directly from the ECB (Edit Content Block) menu provided by the native SharePoint ListFormWebPart (your orthodox SharePoint list interface), pooling all the fields that are considered encryption worthy and encrypting or decrypting them based on user interaction. Since there are current limitations to the fields out of an arbitrary list item that can be harvested (field types such as URL’s demand that certain formats be used and therefore cannot be subject to encryption operations).

Once the encryption / decryption operations are triggered, the CEE will encrypt / decrypt the stored fields with an algorithm that the user selects out of the interface (currently supported encryption algorithms are RC2, Rijndael (AES), Triple DES, or BlowFish). All code that the CEE leverages is CLS-Compliant and 100% managed.

Adam Buenz
http://sharepointsecurity.com

CryptoCollaboration NOW SUPPORTS MICROSOFT WORD DOCUMENTS!!!

Here Is An Example Of THE EVEN NEW Document Level Encryption For Document Libraries (this is Alpha Version 0.0.0.4, Being Released On March 26 at 6:00 p.m. PST):

CryptoCollaboration now supports Microsoft Word Documents! This should bring full circle several of the aggregate encryption problems that have lead to the creation of CryptoCollaboration in the first place. So, let me demonstrate the encryption of a stored Microsoft Word document, and then its subsequent decryption back to plain text directly within a SharePoint environment.

Here, I am creating a new document from a SharePoint document library on a test instance:

And then, I am saving the document back to the server since this is where the encryption is going to take place:

Once the document is stored, I am going to call the CryptoCollaboration operations page so that I can interact with the CryptoCollaboration Encryption Engine. Once I am in the operations page, since I am just testing the file, I am going to restrict the encryption operations to the file of the list item, and then set the algorithm Rijndael:

Now, when I open the document from the SharePoint document library, the contents of the document are subsequently encrypted:

As you can see, the document contents are now unreadable.

Now, let's decrypt the document. Once in the operations page, as similar to past versions, the interface will be trimmed with the options as selected through previous operations:

After decryption, we can see that Microsoft Word contents are then converted to back to plain-text:

Here Is An Example Of THE NEW Document Level Encryption For Document Libraries (this is Alpha Version 0.0.0.3, Being Released On March 26 at 6:00 p.m. PST):

One of the largest changes in version 0.0.0.3 is the option to not solely use OOB lists, but document libraries as well. Document libraries are now supported through three main levels of operations:

1) Encrypt Fields
2) Encrypt Files
3) Encrypt Files and Fields

The operations page has been adjusted to compensate for said available selections.

The only limitation right now is it has only been tested with standards text documents, while the testing and code compensation that is required for Microsoft Word files will most likely be released at a later occasion. If you want to just view standard list encryption, you can view the screenshots provided in the secondary section that show Task List encryption, this will briefly go over the document level encryption for stored text documents.

Firstly, as was unavailable in the previous versions, the "Encrypt / Decrypt This Item" menu item is available from the document library ECB menus and toolbars.

Here is the encryption option as available from the Toolbar within a SharePoint document library:

Here is the encryption option as available from the ECB menu within a SharePoint document library

On the old CryptoCollaboration Operations page, there was no granular selection for files and metadata since files were not supported. However, when a SharePoint document library is now selected (i.e. we look whether the parent list is of Microsoft.SharePoint.SPDocumentLibrary), there are more selections that are available from the operations page.

So, you have one of three options to select when working with encryption in document libraries. I am going to choose to encrypt both the fields in the list as well as the file that is held within the document library. I could also choose to piece meal encrypt the pieces as I want.

In this document library, I am storing a document named "test.txt" which contains the string "test" within it. This is a piece of mutable data that I want to encrypt, as well as the column "test" which also contains the string "test". Here is the document contents.

And here is the list item and its related field values:

Now, after running the encryption operations, when I get kicked to the list item view, I can see my fields are encrypted:

As well the text file content. which contained the string "test", has also been encrypted:

Now, when I go to decrypt the list item, the field selection out of the interface is trimmed, to only include the action that was initially chosen is populated as the only selection in order to reduce confusion, as well similar to previous version of the the encryption engine, it will feed the algorithm that was initially chosen when tripping the encryption algorithm.

After the decryption is run, we can immediately see that the fields are decrypted:

As well, the file contents are also unscrambled back to the original plaintext:

THIS IS VERSION 0.0.0.2 WHICH HAS BEEN DEPRECATED IN FAVOR OF 0.0.0.3 WHICH SUPPORTS FILE ENCRYPTION (Being Released On March 26 at 6:00 p.m. PST)

Here Is An Example Of Some Task List Encryption (this is Alpha Version 0.0.0.2, Being Released On March 25 at 6:00 p.m. PST):

First, I Visit A List That I Would Like To Encrypt, In This Case A Task List With A New Test Item:

Secondly, Once The Item Is Created, I Call The Encryption Engine (CEE) From Either The List ECB or The List Form ToolBar:

From The ECB:

From The ToolBar:

Then After Selecting Entering The Operations Page:

The Selecting Your Available Encryption Options:

Now The Values Are Encrypted:

The Decryption Looks At The Algorithm, And Trims The Radio Button List For You:

The SharePoint List Item Is Then Returned To Plain Text:

UPDATED WIKI: Home

AdamBuenz — Wed, 26 Mar 2008 17:28:26 GMT

UPDATED WIKI: Home

AdamBuenz — Wed, 26 Mar 2008 17:27:42 GMT

UPDATED RELEASE: Alpha Release V2 - Non-Production v 0.0.0.2 (Mar 25, 2008)

Tue, 25 Mar 2008 22:38:55 GMT

UPDATED RELEASE: Alpha Release V2 - Non-Production v 0.0.0.2 (Mar 25, 2008)

Tue, 25 Mar 2008 22:38:24 GMT

UPDATED RELEASE: Alpha Release V2 - Non-Production v 0.0.0.2 (Mar 25, 2008)

Tue, 25 Mar 2008 21:27:52 GMT

UPDATED RELEASE: Alpha Release - Non-Production v 0.0.0.1 (Mar 23, 2008)

Tue, 25 Mar 2008 17:56:17 GMT

This is the alpha release of CryptoCollaboration that is not fit for production use, however is strictly targeted to broaden the testing base of the current code to ensure fitness of some of the proposed approaches. Limitations of the current version are currently being noted within the Issue Tracker list, and that list will remain the location for current software issues, as well as feature integration requests.

The current version has only been tested in two different environments, one for operational software testing, the other meant to test the given deployment packages.

While this is considered an alpha release of the software, from a basic testing perspective a majority of all methods appear to working correctly, while the main testing targets have been standard custom SharePoint lists using the default field types that are provided OOB. I would be interested in verifying the encryption of custom field types, however for this revision it has been limited to testing against custom field types that inherit from the SPFieldText base class.

There are three files that are included in this release.

CryptoCollaboration Installation v 0.0.0.1.doc - This document contains the instructions for installing the CryptoCollaboration SharePoint Solution file.

CryptoCollaboration Operations Instructions v 0.0.0.1.doc - This document contains the operations guide for using the CryptoCollaboration product itself.

CryptoCollaboration.zip - Contains the SharePoint solution file and the deployment files that are required to use CryptoCollaboration in your environment.

UPDATED WIKI: Home

AdamBuenz — Tue, 25 Mar 2008 17:53:55 GMT

UPDATED WIKI: Home

AdamBuenz — Tue, 25 Mar 2008 17:53:02 GMT

UPDATED WIKI: Home

AdamBuenz — Tue, 25 Mar 2008 17:51:51 GMT

UPDATED WIKI: Home

AdamBuenz — Tue, 25 Mar 2008 17:39:51 GMT