the term protection shield or security shield refers herein to software and / or hardware part ( s ) added to a software application for protecting the software application from being used by unauthorized objects . a protection shield can be added to an application during its development , or to the distributed version of the application . the term “ software ” refers in the art to computer instructions and / or data . the term “ software application ” refers in the art to programs and / or data oriented to perform some functionality . for example , word processors , spreadsheets , and database management systems fall under the category of software applications . the term “ part of a software application ” refers herein to less than the entirety of the components of a software application , whether the components are executable code or data . for example , one or more functions , a dll , an executable ( e . g . exe ) file , one or more scripts , one or more data files , one or more records of a database , one or more bytes , and any combination of the above , which includes less than the entirety of a software application , may each be termed as a “ part ” of a software application to which these components collectively belong . fig1 schematically illustrates a typical protected software application , according to the prior art . user &# 39 ; s machine 20 executes a software application 40 . the software application 40 comprises the following modules : part 1 , part 2 and part 3 , a gui ( graphical user interface ), and a protection shield . all the parts are executed on user &# 39 ; s machine 20 . one of the major reasons for the vulnerability of a software application to piracy is that all the parts of a software application are available to the user . the availability to the software parts to a user allows him to amend the files , whether they are executables or data files . one of the methods employed by hackers is tracing the code and data of the application while it is being executed . a hacker may use a debugger , which allows him to execute the application stepwise , to follow the operation it performs in each step , to examine the current content of variables and memory , etc . thus , the availability of the files of a software application to a user , or even availability of the parts of a software application which are stored in the ram while being executed , makes the software application vulnerable to hacking . thus , with the appropriate effort , time and resources , a protection shield of a software application can be removed , resulting with an unprotected software application which can be distributed to other unauthorized users . according to a preferred embodiment of the present invention , this problem is solved by keeping all the parts of the software application on a remote server , and executing these parts by the remote server or by another remote server instead of on the user &# 39 ; s machine . fig2 schematically illustrates a deployment of the parts of the software application illustrated in fig1 , according to a preferred embodiment of the present invention . instead of executing all the parts of the application 40 on the user &# 39 ; s machine 20 as in the prior art , part 1 , part 2 and part 3 are executed on a remote server 10 which in accessible to the user &# 39 ; s machine 20 through the internet 30 via a communication channel 80 . the connection between the user and the application is carried out by the gui module 40 , which is executed by the user &# 39 ; s machine 20 . since the application 40 is deployed on two platforms , the . user &# 39 ; s computer . 20 and the remote server 10 , the role of the protection shield is different than in the prior art . if the application &# 39 ; s owner doesn &# 39 ; t trust the operator of the server 10 , or in order to gain a better protection level , the part of the program that runs on the remote server 10 can also be protected . the protection shield on the user &# 39 ; s machine 20 can be less severe since the remote server 10 can control the way the application is utilized , e . g . how many users execute it , the identity of the users , etc . in addition , the data exchanged between the user &# 39 ; s machine 20 and the remote server can also be protected , especially if the data has a confidential nature . this can be carried out , for example , by cryptographic methods such as encrypting the exchanged data , digitally signing the exchanged data , etc . by preventing from a user to access the software application 40 , the user cannot alter the software application , resulting with a better protection level in comparable to the prior art . in one embodiment of the present invention , since the application does not operate on the user &# 39 ; s machine 20 , the interface with the user may be carried out by a browser or by a dedicated program thereof . this is illustrated in fig2 by the gui module executed by user &# 39 ; s machine 20 . fig3 schematically illustrates a deployment of the parts of the software application illustrated in fig1 , according to another preferred embodiment of the present invention . in this embodiment , part 1 and part 2 of the application are executed by the remote server 10 , while part 3 of the application is executed by the user &# 39 ; s machine 20 . thus , not all parts of the program have to be executed on by remote server 10 . in some cases it is adequate to protect only certain parts of the application , e . g . some core routines or a licensing module , and still obtain a good protection . these parts may be executed by the remote server 10 . according to another preferred embodiment of the present invention , the part of the software application 40 which runs on the remote server 10 relates to licensing of the software application 40 . fig4 schematically illustrates a deployment of the parts of the software application , according to another preferred embodiment of the present invention . the difference between fig3 and fig4 is that in fig3 some parts of the software application 40 are executed by a remote server 10 which is available to the user &# 39 ; s machine 10 over a wide area network 30 ( e . g . internet ), in fig4 some parts of the software application 10 are executed by a local server 70 and are available to the user &# 39 ; s machine 10 over a local area network 60 . the deployment illustrated in fig3 differs from the prior art in at least the following respects : according to the present invention the remote server is accessible over a wide area network whereas according to the prior art the remote server is accessible over a local area network . the difference is substantial since a local server is a part of the local area network , and therefore is more accessible to its users than the users of a wide area network . for example , since the infrastructure of a local area network ( including its servers ) is usually physically available to the users of the local area network , a licensing module operating at a local server can be debugged at least by the operator of the local area network . the deployment illustrated in fig4 differs from the prior art in at least the following respects : a licensing server , whether accessible via a local area network or via a wide area network , does not form an integral part of a protected software application according to the present invention . for example , according to the present invention , some core routines , which may or may not form part of the protection shield , may be executed on the remote server . the prior art , however , deals only with licensing , not with protection . it is appreciated that since in the present invention the parts of a software application may be executed on a plurality of computer systems , it is desirable to allow the different parts of the application on different computers to intercommunicate . it is desirable that the communication channel be secured , i . e . provide encrypted communication or at least ensure that the content of the communicated information will not be understandable to unauthorized objects . fig5 schematically illustrates a deployment of the parts of the software application , according to a further embodiment of the present invention . a group of user machines 20 are connected by local network 60 , and local network 60 is connected to the wide area network 30 . according to this embodiment , the protection activity is divided between the remote server 10 ( the protection - a part ), the local server 70 ( the protection - c part ) and the user &# 39 ; s machine 20 ( the protection - b part ). according to another preferred embodiment of the present invention , the licensing server , either the web licensing server or the local licensing server or both , is operative to verify that the application is being operated according to the licensing terms purchased by the organization . the verification may be performed periodically or at random intervals . in one preferred embodiment , instead of or in addition to checking the authorization of a user to use the application upon activation of the application , the server checks at a given interval , such as every 5 minutes , how many authorized users are using the application simultaneously , and updates the number of available / used licenses in the licensing pool . in the event the number of users exceeds that allowed according to the license agreement , the licensing server may charge the organization for extra use , limit some functionalities of the application ( e . g . suspend the save option ) to some of the users , drop out some users , etc . in contrast to the prior art where the use of a software application is carried out only upon invoking the application , according to this embodiment of the present invention , verifying that the use of a software application complies with its licensing terms is also carried out during execution of the application . fig6 is a flowchart of a process for protecting a software application , according to a preferred embodiment of the present invention . after invoking the software application , the authorization of a user thereof to use the application is interrogated . as seen in fig6 , if use of the application by the user is not authorized , the application may be aborted . alternatively , the user may be allowed to utilize limited features of the application or may be allowed limited use of the application . if use of the application by the user is authorized , an additional check is preformed at 5 minute intervals during the execution of the application . as described hereinabove , the additional check verifies that the user is authorized to use the software application under the licensing terms . in case where more users than allowed according to a license agreement use the application at the same time , the licensing server may charge the organization for additional fee , limit some functionalities of the application ( e . g . suspend the save option ) to some of the users , drop out some users , etc . it is appreciated that a local licensing server is better suited than a web licensing server to provide additional verification during executing of the software application , that it is being used in compliance with the licensing terms thereof . performing such activity on a web licensing server may result in overloading the web server , due to the potentially large volume of users . according to another preferred embodiment of the present invention , both the local and web licensing servers may be operative to provide additional verification during execution of a software application that it is being used in compliance with the licensing terms thereof . in this embodiment , the local licensing server may be operative to measure the use and reports it to the web licensing server , and the web licensing server may be operative to verify that the measured use complies with the licensing terms . since a connection with a server may be intermittent , according to one embodiment of the invention the software application at a user &# 39 ; s site keeps running only for a limited period ( e . g . one hour , one day , etc .) after the connection with the web licensing server has been disconnected , and if during this period no connection with the server is re - established , the software stops running , limits some functionalities , etc . according to one embodiment of the invention , if one of the servers gets suspended ( e . g . because of a system failure ), then the other server , if available , performs the licensing activity ( checking the authorization of a user to use the application ,. checking out that the number of users that use the application simultaneously do not exceed the license terms , etc .). a byproduct of monitoring the use of an application during its . execution over its licensing terms is accumulating information of the use of the application . for example , instead of installing a dedicated system for monitoring the use of the dictionary feature of a word processor , the licensing application can accumulate this information . the accumulated information can provide an organization means to decide whether to purchase a feature or an application , how many licenses to purchase , etc . additionally , the application &# 39 ; s manufacturer can use such information in the same manner . the licensing server of the present invention may be utilized in conjunction with a variety of payment models . for example , according to one embodiment of the present invention , the payment may be based on the number of times a user , or a plurality of users , have activated the application . according to another embodiment of the present invention , the payment may be based on the period of time the application was operating . additionally or alternatively , the payment may be based on any suitable combination of the number of times the application was invoked and the period of time the application was in use . according to another embodiment of the present invention , the payment may be based on the maximum number of instances running simultaneously . in the art it is common to separate the r & amp ; d activity of a software application from the r & amp ; d activity of the protection / licensing , in order to facilitate the r & amp ; d process . moreover , there are firms that specialize in protection / licensing issues . protection shields are designed to be easily added to an existing software application . in addition , protection shields are provided with an api ( application software interface ), by which a software manufacturer can interact with the protection shield . the fact that a protection shield is a tool separate from the rest of the application allows an application software developer to focus its r & amp ; d on subjects which the developer specializes in . preferably , in the present invention , the parts of the software application that are executed on the www server , and thereby kept distant from the end user / organization , belong to the protection shield . envelope protection offers file encoding and advanced anti - debugging features which enhance the overall level of security . for example , the hasp envelope utility is a typical protection envelope . it adds a protective shield around executable and library files of an application . the hasp envelope provides means to counteract reverse engineering and other anti - debugging measures . the hasp envelope wraps the application file with numerous protection layers that are assembled randomly . the random multi - layer wrapping envelope ensures that implemented protection strategies differ from one protected application to another . the hasp envelope establishes a link between the protected software and the hasp key , which is a “ security token ”— a hardware device external to a host which provides protection and security functionality to the host via wired or wireless connection with the host . the link between the protected software and the hasp key is broken whenever the protected software cannot access the required hasp key , in which case the program ceases to function . during the protection process the original file is destroyed and a new one is created . the new file created is the one that is distributed to the users ; the hasp allows detection of both system and user - level debugging measures , which can be activated to be undertaken by the hasp system to block potential attacks that seek to undermine the protection scheme . the user can specify the frequency of hasp key access for scrambling . the setting controls the compactness of the hasp key calls made by the protected application . an encryption level slider is provided to determine the frequency of hasp key access for scrambling . increasing the number of protective modules increases the startup time for a protected application and the resultant file size . there is also a trade - off between encryption level and protected file size and startup speed . a higher encryption level causes a slower startup , and a larger protected application size . according to another embodiment of the present invention , the licensing server is operative to utilize an “ enforcement scheme ”, where a user or organization is limited in its use of the application by the license term purchased . in this embodiment , an organization cannot simultaneously use more licenses than have been purchased . according to another embodiment of the present invention , the licensing server is operative to utilize a “ metering scheme ”, where the use of the program is metered , and the user / organization is charged accordingly . in this embodiment , an organization is charged according to the number of times its users have executed a software application . according to yet another embodiment of the invention , the licensing server is operative to utilize both an enforcement scheme and a metering scheme . in this embodiment , for example , if the licensing term allows up to n simultaneous users , the organization is charged an additional fee if more than n users use the application simultaneously . it is appreciated that according to the present invention a user may activate an application software from outside an organization &# 39 ; s lan , e . g . from home , since the connection with the web licensing server is via the internet . it is further appreciated that the subject of “ selective ” communication over a network is well known in the art . for example , a user browsing a web site is limited to access only certain content that resides on the web server which operates the web site . thus , the fact that a user can access data on the web site does not mean that his access to the data is unlimited . furthermore , the fact that a user communicates with a remote server does not necessarily mean that the remote server has unlimited access to the user &# 39 ; s machine . in fact , the user can prevent the web site server from accessing information stored on his computer . thus , according to a preferred embodiment of the invention , the communication between the parts of a software application that reside on different computer machines is “ selective ”. thus , the server is preferably configured and / or programmed and operative to completely or selectively prevent amendment and / or access by remote workstations of information stored thereupon , while enabling at least selective access by the remote workstations to the information stored on the server . those skilled in the art will appreciate that the invention can be embodied by other forms and ways , without losing the scope of the invention . the embodiments described herein should be considered as illustrative and not restrictive .