Digital Content Security - FAQ

1) What kind of files can I protect using Digilox?

Currently only pdf files can be protected using Digilox. However, we are working towards providing protection for various types of files.

2) Which Operating System does Digilox work with?

Digilox Demo can work with Windows 98 and Windows NT. The original Digilox product can work in Windows and Macintosh.

3) Do I need to maintain a server?

For big content publishers, Digilox can be installed as a product on their server.
For small publishers, we use Digilox as a Web service.

4) Can I protect content on CDs or Web based content too?

Currently only Web based content can be protected using Digilox. However, we are working towards providing protection for the content on your CDs too. This shall be available shortly. 

E-security network  - FAQ

Instant financial messaging system (IFMS)

Q. Where is IFMS useful?

A. Any financial organization or institution that has remote and distributed branch locations and needs to exchange digital information with the same can benefit from IFMS. Communication between computerized bank branches is an example. 

Q. Do I need a special network to take advantage of IFMS?

A – No, IFMS works with your existing network, for example using dialup connections, leased lines, financial networks like INFINET, or the Internet.

Q. Do I need a very powerful server for implementing IFMS?

A – A regular personal computer running Linux can handle intensive communication between hundreds or even thousands of branch locations. IFMS is built such that it requires no third party software or hardware, other than the computers and the operating system.

Q. What should be the configuration of the client computers?

A. Client computers at this time can be regular PCs running Windows 95 or higher. Requests for customizing IFMS to clients running other operating systems can be accommodated.
 
Q. What is “client registration”? Can arbitrary, non-registered client machines communicate securely using IFMS?

A. A corner stone of the IFMS solution is the requirement that a client computer is known in advance. Hence it is necessary for a client to register itself with the server computer before any communication can be made. Multiple individual users can be authenticated on registered clients using biometric, password, smart card or other techniques.

Q. Is all IFMS communication restricted to be client-to-server and back? Does IFMS support client-to-client communication?

A. Yes, IFMS supports client-to-client communication. Because of the hub-and-spoke architecture of IFMS, all client-to-client communication is routed through the server.
 
Q. Why should I prefer IFMS to solutions like Public Key Infrastructure (PKI)?

A. Solutions like PKI suffer from known risks such as genuineness of the Certification Authority, weakness due to an unfamiliar verifying computer, lack of Single Sign-On capability, etc. For its chosen domain, namely communication between known clients and a server, IFMS provides a much stronger, versatile and easy-to-maintain messaging infrastructure.

Q. Is the IFMS system very expensive to implement?
 
A. The server and client computer capabilities needed by IFMS are commonplace, as detailed above. Further, the communication happens through a channel that is already in place, such as the Internet. The most expensive part of the solution, should you choose to implement it, is the biometric authentication. A standard biometric device such as a mouse from a third party vendor, costs about USD 120. One mouse needs to be purchased for every client machine for which you need this authentication option.

Q. How do I keep track of what messages have been exchanged and processed on this infrastructure?

A. Every message necessarily passes through the server in IFMS, because of its hub-and-spoke architecture. IFMS comes with a secure and automatic archiving utility on the server side. Older transactions can be viewed, can be backed up on removable media or can be printed as reports by authorized persons on the server side.