Managing Backup and Recovery Procedures

The need for, and creation of, end of day backup files cannot be over emphasised as they allow you to restore either the whole system or perhaps selected data files, to a specified 'end of day' position. However, the procedures used to initiate such a 'recovery' must be clearly documented and tested - the Information Security implication of an inappropriate or incorrect file restore, are significant.

To view the related Policy click      

  • If restore procedures have not been tested, a partial or invalid restore can corrupt the entire system, which may partly or extensively terminate business operations.

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

  • Where backup procedures are inadequate or lacking, data may be lost or, effectively, unavailable, this compromising the organisation's business processes.

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

  • Opportunistic or malicious modification of the daily backup sequence results in a failure to safeguard all required data.

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

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