IRM SECURE

FAQ

  1. What File Formats Are Supported?

    IRM Secure FileSecure currently supports more than 140 different file formats. The most commonly used document formats are:

    • All MS-Office documents (doc., docx., xls., xlsx., ppt., pps., ppt., ...)
    • Open Office documents (odt., ods., odp., odf., odg.)
    • PDF
    • Text and Text based formats (txt., csv., xml.., html, ...)
    • Images (Jpeg., BMP., TIFF., GIF., ...)
    • Engineering design (dwg., dxf.., dwf, ...)
  2. Do I Have To Install Anything To Protect The Document?

    Yes. For document protection, you will need the IRM Secure FileSecure Desktop Client. This utility will allow authorized users to protect documents which can then be shared with others.

  3. Does The Recipient Of The Protected Documents Need To Install Anything?

    Yes. The recipients of the document will also need to install IRM Secure FileSecure Desktop Client, which is available free of cost and can be downloaded from this website, or freely distributed by the document owners.

  4. Will IRM Secure Filesecure Force Me To Change My Existing Infrastructure?

    No! IRM Secure FileSecure is designed to integrate with all major infrastructure setups. There will be minimal integration required to be made by the IT team and virtually no change by the end-user.

  5. What Impact Will IRM Secure Filesecure Have On My Existing Network Utilization?

    Virtually none. The data exchanged between the client and server is negligible (a few kilobytes). Furthermore, this traffic is not a continuous stream, but occurs only when documents are accessed.

  6. Once I Protect A File, Can I Remove The Protection Later?

    Yes. The owner or anyone who has "Full Control" usage rights for the document can remove the file protection.

  7. What Method Of Communication Is Used Between The Client And Server? How Do I Ensure That My Security Is Not Compromised During This Communication Process?

    All client-server communication is via secure HTTP (https) protocol. This is the standard and industry-recognized mode of secure communication on the internet.

  8. What Encryption Standard Is Used For Protection Of Data?

    AES and Blowfish (256 bit) are the default standards. Higher bit encryption is available on demand.

  9. Can I Share Data With People Outside Of My Organization?

    Yes. IRM Secure FileSecure enables you to track and control document usage even when it is shared with people like Vendors, Business Partners, Customers etc., who may not be part of your organization. A rich set of API's enable integration with non-LDAP based systems for User Authentication. Other systems where Users may be authenticated such as CRM, Vendor Management Systems etc., can easily be integrated with IRM Secure FileSecure, so that document usage can be controlled with users who are not part of the organization.

  10. Will IRM Secure Have Access To My Data?

    No! The protected documents will always reside in the File server or the Desktops/Laptops where the original document was present. IRM Secure Policy Server only holds the Usage Policies for the document. The actual document is not stored on the Policy Server.

  11. Does The Data Get Stored Centrally?

    No. The protected document is available at the same location as where the document was before it was protected, namely the Desktop/Laptop or File Server.

  12. Can IRM Secure Filesecure Control Distribution Of Data By CDs, USB Drives, Email Etc?

    IRM Secure FileSecure helps you to control the usage of your data no matter how it is distributed. While it cannot restrict distribution of the data, the risk of the distribution itself is negated. IRM Secure FileSecure enables tight control over the usage of all protected documents, so even if they are distributed unintentionally, the owner of the document can have full confidence that the data will not be accessible to any unauthorized recipients.

  13. What differentiates IRM Secure FileSecure with other security systems?

    Since IRM Secure FileSecure is not aligned to any specific format or application, new formats can be supported very quickly. Document rights are persistent and security travels with the document within and outside of the enterprise. Modification of usage rights can be applied remotely, without the need to resend the documents. Complete and real-time audit trailing can be provided for all protected documents. User Management and Server Administration can be de-linked. Specific Users can be assigned the rights to manage users in their department or unit, while the central policy server can be maintained by system administrators. This helps to reduce the dependency on IT teams and quickly align security policies to any business dynamics.

  14. What Operating Systems Are Supported?

    IRM Secure FileSecure currently operates on all major versions of the Windows operating systems.

  15. What If I Want To Change The Rights For A Document After I Have Already Sent It? Would I Need To Change The Rights And Send The Document Again?

    No. This is what makes IRM Secure FileSecure so useful! If you need modification in the usage rights for users to either give them new rights or reduce the permissible actions, all you have to do is change the rights on the document you have on your Desktop / Laptop. The new rights will automatically be applicable on all copies of the document, even the copies that were distributed earlier. From then onwards, whenever any person accesses the document or it’s copy, the new usage rights will be enforced! Simple, isn't it?

  16. hat Are The System Requirements For Running IRM Secure Filesecure?

    IRM Secure FileSecure runs on standard systems without the need for any specialized hardware or software. The system requirements are as follows:

    There are 3 different components to IRM Secure FileSecure and the system requirements are specific to each.

    System requirements for IRM Secure FileSecure Policy Server class machine with Dual Core Pentium 2.4 GHz processor, 2 GB RAM, 80 GB HDD, Windows server OS with latest service pack, J2EE compliant web server, MSSQL Database Server. The system requirements on the server may vary on the load and usage patterns within the enterprise. The specification provided here will support 1500 named users.

    Server class machine with Dual Core Pentium 2.4 GHz processor, 2 GB RAM, HDD based on the storage requirements, Windows server OS with latest service pack, NTFS file system.

    System requirements for IRM Secure FileSecure Desktop Client 512 MB RAM, Pentium 4 processor, Windows XP or Windows Vista OS with latest Service Pack, Microsoft Office 2003 or 2007, Acrobat Reader or Acrobat Professional.

  17. Does The Policy Server Need A Live Connection To My LDAP Server / Active Directory Or Other User Repository?

    Yes, the authentication is done directly by the LDAP server / Active Directory. The Policy server can also be integrated with other User Repositories such as CRM system, Vendor management Portals etc. For such users to be able to use protected documents, the Policy Server will require live connection to the specific user repository.

  18. Does The Desktop Client Need To Be Connected To The LDAP Server / Active Directory / User Repository To Be Able To Use IRM Secure Filesecure?

    No, IRM Secure FileSecure Desktop Client only needs connectivity to the Policy Server which will internally manage the authentication. The Desktop Client may prompt for credentials (username/password) and Policy Server will internally validate this with the Active Directory or other user repository. If you are granted offline rights then you need not be connected to the Policy Server, after having accessed or opening the document at least once when you were connected to the Policy Server.

  19. Can IRM Secure Filesecure Integrate With User Authentication System Other Than LDAP Systems?

    Yes. IRM Secure FileSecure is very flexible when it comes to integrating with the organizations existing infrastructure. It’s rich set of API's allow IRM Secure FileSecure to seamlessly integrate with any user authentication system including vendor portals, CRM systems etc.

  20. Does IRM Secure Filesecure Have Support For Multi-Factor Authentication?

    Yes. To support multi-factor authentication, IRM Secure FileSecure can be integrated with other systems for Token based authentication.

  21. Do You Have API's Available To Integrate With Other Systems?

    Yes. IRM Secure has developed a comprehensive set of API's to integrate with other systems. IRM Secure FileSecure has been integrated with a variety of different information management systems like ECM, DMS, CMS, ERP, Workflow, Disk Encryption, DLP, Content archiving, etc. By integrating IRM Secure FileSecure with other systems, a comprehensive information security framework can be established which will provide end-to-end persistent security.

  22. How Does The Authentication Mechanism For IRM Secure Filesecure Desktop Client Work?

    For users who are logged on to a domain where the domain server or AD is integrated with the IRM Secure FileSecure Policy Server, the credentials are picked up from the domain logon. For users who are not logged on to the domain or are connecting from outside of the enterprise, Username / Password are prompted for and the user name / credentials are sent to the Policy Server for authentication over a secure (SSL) connection.

    If the user is an LDAP user, the Policy Server connects to the LDAP server for authentication. If the user is an external user the Policy Server will authenticate the user via specific User Repositories like CRM, Vendor Portals etc. On the basis of this authentication, the Policy Server proceeds with protecting / displaying the document.

  23. Does The System Prevent Print Screen / Screen Grabbing Tools?

    Yes, the IRM Secure FileSecure Desktop Client prevents any kind of screen grabbing tool like the Operating system Print Screen functionality as well as screen grabbing tools like GoToMeeting / Camtasia from remotely displaying the content / document. IRM Secure can also prevent data capture using remote desktop sessions.

  24. How Does The Offline Usage Right Work?

    Offline usage is relevant when users need to use the content / document even when there is no connectivity with the Policy server.

    Here is an example:

    1. User A defines “view” and “edit” privileges on a document for User B, and allows Offline access too.
    2. User A sends the document to User B through any mechanism (email, pen drive, shared folders, CD etc).
    3. User B receives the document, saves it on a laptop and opens the document once while remaining connected to the IRM Secure FileSecure Policy Server (via internet / intranet).
    4. The IRM Secure FileSecure Desktop Client identifies that Offline Usage is allowed for User B for this document, and downloads the document rights to User B’s laptop.
    5. User B disconnects from the network and goes offline
    6. User B opens the document while being offline. The document is available for usage (viewing + editing) in the offline mode.
      1. If User B tries to copy the document from the laptop to another computer while being offline, the document will not open on the other computer if that is not online.
      2. If User B tries to go beyond the defined rights i.e., tries to print the document, it will not be allowed.
    7. The next time User B is online (connection available to Policy Server) and tries to open the document, the latest permissions get applied to the document from the Policy Server.
    8. The things to note about offline usage rights are:

      1. User needs to open the protected document at least once while he is online before he can use it offline.
      2. Any changes in the permissions for the document in the Policy Server will not be applied on the document that is being accessed offline. New permissions will be applied the next time the user opens the document online.
  25. What Is The Information Exchanged Between My Desktop And The Policy Server While Protecting Or Using A Protected Document?

    The IRM Secure FileSecure Desktop Client and the Policy Server exchange authentication and activity information during the usage of the document.

  26. Does IRM Secure Filesecure Only Work With Windows? Is There A Linux / Unixversion?

    As of now, there is no Linux/Unix version of IRM Secure FileSecure. It is only available on Windows.

  27. I Have A Protected Document And When I Try To Open It I See A Message, But Not The Content Of The Document?

    Most likely, you do not have the IRM Secure FileSecure Desktop Client installed on your machine. Please download the client from the link provided to you by the sender of the document or your system administrator and install it on your machine. The message displayed has information about other situations which may prevent the document from opening, and suggestions on how to address the same. Please check for the condition relevant to you and take actions accordingly.

  28. If I Have Protected A Word Document Can I Open The Protected Document By Opening It Directly In MS Word?

    No. Microsoft Word by itself can not decrypt the protected document. You need to open it using IRM Secure FileSecure Desktop Client which in turn will render the document in MS Word. Hence the end user experience remains the same. In fact, this applies to all file formats supported by IRM Secure FileSecure.