Remote Access

How safe is Tally’s Remote Access ?

The most typical question is relating to safety of data - and the ease with which people understand WHY it will be safe.

Basic statement:

We are using our path-breaking Trusted Remote technology to make data from one machine available to a Remote User.

What does this mean?

It means several important things:

1. We ensure that the data is NEVER stored anywhere but on your own machine. which you have the full ability to TRUST .. since your machine is in your control.
2. We ensure that your machine is never 'visible' on the Internet ... in fact, it works as if you are using a normal E-Mail program or Browser ..where YOU can get something from the Web, but not the other way around. Again, this adds to your TRUST of machine security. (Some people mistakenly believe that giving access to the Internet makes their machine vulnerable to viruses. Not true. It is ONLY if they download wrong things from the web, that this happens. Connecting a machine is harmless).
3. We ensure that only people YOU TRUST get access to your data. YOU decide who gets it, and if you have any suspicion that someone has accidentally given away their password, you can immediately switch off the company from WHERE EVER YOU ARE.
   The key behind this magic is Tally.NET

The principal problem of Remote Access and associated Security concerns is this. For data to be accessible from any machine, that machine needs to become a Server. This means, it will allow people to connect to it, and request for information. Whenever a machine becomes a server, it has the potential of getting hacked ... which is what is meant when we say the Security was breached.

Many of you would have found similar situations for your own machines. If you have a LAN, then the only way to make 'use' of the LAN is to share data. Until you share data, the LAN is simply a piece of hardware. Whenever you share data, your machine becomes a server.

In the case of our Trusted Remote technology - this is the specific problem that we were solving. That is, how to give Remote Access without needing to make the machine a Server. Simultaneously, we need to solve the problem of who will control the access to the data, etc. - but which were simpler problems.

What we have done is, ensured that even the machine which is holding the data NEVER becomes a server - but becomes a client to Tally.NET. On the other side, the machine which is requesting the data, ALSO becomes a client to Tally.NET.

Effectively, BOTH machines remain fully protected.