Digital Rights Management (DRM)
Digital Rights Management (or DRM for short) is the term applied to the protection of digital assets using a centralized rights management service. In the Drumlin system these assets are PDF documents - books, reports, technical manuals, training materials and more...
The Drumlin DRM service (standard edition) uses AUTHORIZATION CODES (authcodes) as its principal means of asset management (see diagram, below). The Drumlin DRM service (Corporate/Pro edition) uses LICENSES and/or AUTHORIZATION CODES (authcodes) as its means of asset management - see ourCorporate/Proedition page for more details). Authcodes (for PCs and Macs) are text strings that relate to a specific secure PDF (a DRMX or DRMZ file) or packaged DRMX file (an EXE file). Each authcode is unique and is stored in a table on the DRM server together with the identity (DocID) of the PDF document it relates to, plus a usage count which is generally set to 1 but can be any value>0 (this value decrements by 1 if it is used and when it reaches 0 it is no longer available). Please see the Store pages and About page for more details on codes and their usage. Authcodes are created and managed by an application called AdminApp. They may be ordered via theonline store.
Our secured PDF files are designed to be viewed using the Javelin reader (PC, Mac, Android or iPAD/iPhone version) and do not require user registration. Authcode usage is still tracked with this arrangement. The diagram below shows the main elements and data flows involved in the Drumlin and Javelin DRM services for PDF security:
"Basic DRM" files do not require authorization codes, but can be made user-specific via the UserLists facility. In this case the identify of users who have permission to view the document is included in encrypted form within the document itself. All such users must be existing Drumlin service users, so have pre-installed and registered the Drumlin reader software and have unique UserIDs assigned to them. These IDs are required for the creation of user-specific DRM files. When secure PDFs in the form of DRM or DRMX/DRMZ files are used, Drumlin tracks their creation and usage via a server-based Activity Log and locally on the end user's PC. Authorization events are logged, as are failed attempts.
The Drumlin Digital Rights Management (DRM) Server is comprised of a Microsoft Windows server host configuration offering Web hosting, ASP/.NET and SQLServer facilities. Service management is conducted via FTP and SQLServer management facilities. In the latter case this is typically Microsoft SQLServer Management Studio (or Studio Express) and Microsoft Access (connection via ODBC to SQLServer host). The latter is principally of use for ad hoc queries and management report generation, but may also be used for data updating where appropriate. The SQLServer configuration may be shared with many other databases and is typically very lightly loaded. This is because the data stored is fairly small (normally no documents are stored in the database, just document and user related data), and interaction between the client and host server is typically occasional, short and fast. Almost the only occasion where larger volumes of data are handled is when a large bulk publishing exercise is run (e.g. for 100s of files at one go)