Interfacing Applications Software / Systems

Many software packages can exchange data and link with a variety of popular systems. Such interfaces often need to be specially developed for bespoke or legacy systems. Interfacing can be a complex process requiring data first to be exported from one system, then massaged, and finally imported into the target system. This process puts your data at great risk.

To view the related Policy click      

  • The purchase of a new system may have been agreed on the basis of the apparent ease of interfacing to your current system(s). Interfacing problems can result in substantial delays and even cause entire projects to fail, especially where complex data massaging is required.

There are multiple Key Actions providing safeguards against this Information Security Issue. These are available in the registered version of RUSecure™.

  • Where an interface program is required to reformat the data to meet the needs of the target system, such data massaging poses a risk of data modification (possibly maliciously) and, thereby, inaccurate processing.

There are multiple Key Actions providing safeguards against this Information Security Issue. These are available in the registered version of RUSecure™.

  • Temporary files, created by interface program processing, and saved in a temporary location, may contain sensitive data which unauthorised persons might access, thus compromising the confidentiality of your information.

  • Store and execute both the interface program(s)and the input and output files within the 'live' Program Library and Data areas (respectively) on your system, thereby offering appropriate levels of security from unauthorised intrusion.
Previous PageTop of this pageNext Page


Information Security Policies from US$595

 From
 US$595

Use of the guidance contained within RUSecure™ is subject to the End User Licence Agreement
This site created with EasyHTMLHelp(tm) for MS Word

 

Next PageUpPrevious Page