We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

MS Enterprise Risk Manager (ERM)

Does Aspose.Words support generating documents with ERM protection and/or is this being looked at for a future enhancement?

Thanks,
Aaron

Hi Aaron,


Thanks for your inquiry.

Aspose products are very secure. Aspose components run in the same user context as all ASP.NET applications, under the ASPNET user. Therefore, Aspose components do not pose a potential risk to vital system resources. Furthermore, when a document is opened by an Aspose component, macros are not automatically run. Aspose components were built with the goal of allowing developers to create, manipulate and save Office files. None of the risks associated with the Microsoft Office package are inherent to Aspose components.

Aspose.Words is a better alternative to automation in terms of security, stability, scalability/speed, price and features. I suggest you please read following documentation links for your kind reference.

http://www.aspose.com/docs/display/wordsnet/Why+not+Automation
http://www.aspose.com/docs/display/wordsnet/Introducing+Aspose.Words+for+.NET
http://www.aspose.com/docs/display/wordsnet/Protecting+Documents

Tahir,

We have a business need to protect and restrict how a document is used based on security policies set up in ERM. These documents get protected and encrypted at the OS level such that action (print, edit, etc) can not be taken on them if the user isn't given that ACL (see attachment). Our goal is to generate an XPS document and immediately assigned one or more users, groups or policies to the file with the appropriate ACLs. This is a different and more comprehensive level of document security than what is referred to above. I know we could perform these steps on the document immediately after it has been generated, but thought I would check first to see if Aspose provided this functionality.

Thanks,
Aaron

Hi Aaron,


Thanks for your inquiry. We are working over your query and will update you asap.

Hi Aaron,


Thanks for your patience. Please note that Aspose.Words tries to mimic the same behavior as MS Word do.

Aspose.Words supports most document protection features. Using Aspose.Words you can open a document that is password protected even without the password (as long as its not encrypted). Once loaded you can remove any protection from a document.

See the following links in the documentation for further information:
http://www.aspose.com/docs/display/wordsnet/Protecting+Documents
http://www.aspose.com/docs/display/wordsnet/Unprotect+Method
http://www.aspose.com/docs/display/wordsnet/Protect+Method

Please read the features on Document import/export from here: (See the protection section)
http://www.aspose.com/docs/display/wordsnet/Document+Features+Supported+on+DOCX+Import
http://www.aspose.com/docs/display/wordsnet/Document+Features+Supported+on+DOC+Import

http://www.aspose.com/docs/display/wordsnet/Document+Features+Supported+on+DOC+Export
http://www.aspose.com/docs/display/wordsnet/Document+Features+Supported+on+DOCX+Export

Hope this answers your query. Please let us know if you have any more queries.

Tahir,

Thank you for the information, but it unfortunately doesn't address my need. Please let me know if there are any plans to support a more grainular level of document/file control using the capabilities of ERM?

Thanks,
Aaron

Hi Aaron,


Thanks for your inquiry. Please note that Aspose.Words tries to mimic the same behavior as MS Word do. I am afraid, currently Aspose.Words does not support protection of selected ranges (partial protection of document). Your request has been linked to the appropriate feature. We will let you know once this feature is supported. The feature ID is WORDSNET-1067.

Moreover, It would be great if you please apply security on Word documents by using MS Word and share these documents with us for investigation purposes. Please also share the security details along with each document.

The issues you have found earlier (filed as WORDSNET-1067) have been fixed in this .NET update and this Java update.


This message was posted using Notification2Forum from Downloads module by aspose.notifier.
(38)