ISO 27001 Annex : A.9.4.4 Use of Privileged Utility Programs & A.9.4.5 Access Control to Program Source Code
In this article ISO 27001 Annex : A.9.4.4 Use of Privileged Utility Programs & A.9.4.5 Access Control to Program Source Code this two topics are explain.
A.9.4.4 Use of Privileged Utility Programs
Control- The use of utility programs that could bypass system and application controls should be limited and tightly controlled.
Implementation Guidance- The following guidelines should be taken into account when using utility programs that could override system and application controls:
- the use of procedures for identification, authentication, and authorization of utility programs;
- Segregation of the utility programs from software applications;
- Limiting the availability of utility services to the minimum practicable number of reliable, authorized users (refer to 9.2.3);
- Approval for the ad hoc use of utility programs;
- Limiting the availability of utilities, e.g. for the time of the approved amendment;
- Logging the use of utility programs;
- Definition and documentation of levels of authorisation for utility programs;
- Deletion or disabling of all unused utilities;
- Not allowing utility programs accessible to users accessing applications on systems requiring segregation of duties.
Other Information- Most computer installations have one or more utility programs that can bypass application controls and systems.
Related Product : ISO 27001 Lead Auditor Training And Certification ISMS
A.9.4.5 Access Control to Program Source Code
Control- Access should be limited to the source code of the program.
Implementation Guidance- To prevent the introduction of unauthorized functionality and to avoid unintended changes, and to maintain the confidentiality of valuable intellectual property, it is necessary to strictly control access to source code and related items (such as designs, specifications, verification plans, and validation plans). For program source code, this can be achieved by controlling the central storage of such code, preferably in program source libraries. In order to minimize the potential for misuse of computer applications, the following guidelines will then be considered to control access to these source libraries:
- Where appropriate, software source libraries should not be kept in operating systems;
- The source code of the program and the source library of the program should be administered according to procedures;
- Support staff should have restricted access to program source libraries;
- The updating of program source libraries and related objects, and therefore the issuing of software sources to programmers, should be carried out only after sufficient authorization has been received;
- The program listings should be stored in a safe environment;
- The audit log of all accesses to program source libraries should be maintained;
- Strict change control procedures may refer to the management and copying of software source libraries.
If the source code of the program is to be published, additional controls (e.g. digital signature) should be taken into account to ensure its integrity.
--------------------------------------------------------------------------------------------------------------------------
This Blog Article is posted by
Infosavvy, 2nd Floor, Sai Niketan, Chandavalkar Road Opp. Gora Gandhi Hotel, Above Jumbo King, beside Speakwell Institute, Borivali West, Mumbai, Maharashtra 400092
Contact us – www.info-savvy.com
Thanks for given detail information to me. keep posting like this. iso-22000-2018
ReplyDelete