Managing Operational Program Libraries

Managing the directories within your computer system(s) in which operational (live) software is stored.

To view the related Policy click      

  • If your operational program libraries are poorly protected, your software and configuration files could be modified without authorisation, resulting in disruption to your system and / or other incidents.

  • Operational libraries should only be updated by designated staff, independent of those developing software and those using the system for production.
  • Updates should only be undertaken on receipt of a formally authorised request.
  • Enforce standards using technical safeguards, including those within your operating system.
  • Procedures should provide an audit trail to permit scrutiny.
  • IT staff should not normally have 'execute' authority for software in your operational object or source libraries.
  • Unauthorised use of production software can cause disruption to your systems or fraud against your organisation.

  • Permit access to software based upon genuine need.
  • Restrict access using technical safeguards, including those within your operating system, to inhibit unauthorised entry to the operational library.
  • IT staff should not normally have 'execute' authority for software in your operational object or source libraries.
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