KEYnote 33 English - Spring 2017 - Page 5

Publisher
User
Adobe Acrobat
SmartShelter | PDF Author
Adobe Acrobat / Acrobat Reader
Standard documents When you are working with your own type of document , you can integrate cryptographic capabilities in your software . But what happens if you are using standard files that a user can access with a run-of-the-mill viewer or other standard application ? In these cases , SmartShelter | SDL is the solution . SDL stands for Secure Data Layer . SmartShelter | SDL slips a layer of insulation between the operating system and the application handling the protected document .
SmartShelter | PDF Reader
SmartShelter | PDF uses another Protection Suite technology to identify disallowed applications . It immediately closes protected documents when it notices that a screenshot application is running .
With CodeMeter as licensing system , all CodeMeter licensing options can be used , including time-bound licenses or licenses with a usage counter .
Proprietary documents Your documents might come in a proprietary format , like settings files , construction blueprints , design patterns , or audio and video files . Your reasons for protecting them might be just as diverse . Common use cases include :
■■
Your software needs custom settings that you adjust specifically for each user . Different users should not be able to share these settings .
■■
You sell documents as an additional revenue source on top of your software . These should only be used by the people who actually bought them .
■■
Your software produces certain types of data , like live recordings of concerts . This has to work anytime and anywhere . Artists like Peter Gabriel will not sit and wait backstage , because you have to go and get your license . However , back in the studio , the resulting recording should only be readable and editable with the right license . Or more generally : A license is needed to open the document .
■■
Your software processes data , e . g . by cutting sheet metal based on a specific design pattern . Your software should only process data coming from somebody with the right entitlements , be it for financial reasons or for reasons of liability . Again put more generally : A license is needed to save the document .
These use cases can be combined as preferred with the legitimate protection needs of your partners . For instance , a partner should also have the right to produce documents that your software can open .
CodeMeter can handle all four use cases and their many combinations . With the CodeMeter Core API , you have a powerful API for encrypting , decrypting , and signing data . The toolkit is versatile enough to cover all of the above scenarios .
Individual settings can be encrypted with a unique key that is created for each client . Protected in this manner , the data cannot simply be shared anymore .
Companies in the business of selling documents can use the same concept that is used to sell software features on demand . Each individual package is given its own product code for encryption , which is accomplished either by AxProtector or by another custom tool . Just like software features , the licenses are activated in CodeMeter License Central . Again , all license options are available .
When it comes to managing the rights for saving or opening files , CodeMeter Core API offers asymmetric methods . Data can be signed with a private key that requires a valid license , and the data can only be read if the signature is present and correct . In this scenario , the author of the file needs to have a license . In asymmetric encryption , the data is encrypted with a public key and can only be opened again with the right license and the right private key . Now , it is the user that needs to have a license to open the document .
Our Professional Services Team is available to help you choose the optimum concept for your specific use case and to assist you , if you wish , with implementing your chosen solution .
SmartShelter | SDL can configure which operations are allowed and which are prohibited . This is easily done for viewer applications . Encrypted documents can be decrypted if the right license is available . Unencrypted documents can be loaded into the application , but saving is prohibited . It gets more complex if the application in question should also be able to save data . You can define whether saving is allowed at all and whether saved files have to be encrypted or can be unencrypted . This is where it gets challenging : Let ’ s imagine a user opening a protected document . He then creates a new document in the same application . SmartShelter | SDL cannot recognize whether the new document is a copy of the protected file ( which can only be saved in encrypted form ) or a completely different file that should stay unencrypted . This is why using SmartShelter | PDF in a write mode is technically possible , but limited to very specific use cases . By contrast , a readonly mode in a viewer application is always and easily enforceable .
Summary Protecting documents is a far more complex task than protecting software applications , because the question always comes down to the specific application that is using the documents . CodeMeter can shield PDF files from prying eyes in a simple , safe , and fully conformant manner . It is also easy to protect other standard document types with a readonly mode in a viewer application . Whether write modes are possible often depends on the specific procedures and use cases in question . If you are using proprietary formats with proprietary software , CodeMeter gives you a powerful API to cover all use cases imaginable : Licenses for opening files only , licenses for saving files , or licenses for any type of access . The level of flexibility offered by CodeMeter is without rival .
5