MyMIS Chapter 4 TECHNICAL OPERATIONS This chapter discusses the management and the use of safeguards incorporated in ICT assets and other related devices. This chapter seek to explain in more detail the various option available that could be use to further enhance the management of ICT security. It covers the various aspects of computer systems, operating systems, application systems and network systems. 4.1 ICT assets component Computer Systems As defined in the Public Sector ICT Security Policy Framework, the ICT asset component comprises of information processing facilities such as mainframes, minicomputers, microcomputers, laptops, notebooks, palmtops, servers, workstations, departmental, corporate and personal computers as well as communication facilities and network equipment such as the facsimile, fixed line telephones, mobile telephone systems, power supplies, environmental control units, routers, bridges, switches, computer and communication hardware and software, utility programs, operating systems, documentation and applications software. The housing facility is also part and parcel of the public sector ICT asset. With regard to the ICT security of these systems and sub-systems, the following controls need to be exercised: 4.1.1 Change Control Change control procedure should exist for hardware, software, manual procedure and emergency changes Change Control can be defined as the processes initiated to manage and control planned changes about to occur and that the changes will affect ICT operations or its environment. The triggering Change Control events may be scheduled or in response to an emergency. ICT being volatile, Change Control is necessary to protect the integrity of information processing systems and should exist to meet changes in hardware configuration, software changes, manual procedure changes or other changes that will affect service delivery. Establish effective change control procedure Change control is established to ensure smooth migration and minimal operational disturbance. As such, it should be well thought off and effective. Change control should consist of at least the followings: (a) formal change request; (b) formal authorisation process; (c) test and system acceptance procedure for every change to consist at least unit test, component test and integration test; (d) fully documented changes and expected outcome; (e) virus checks before and after changes are made, where appropriate; (f) back-up and restore procedures to capture the system image prior to the new environment; and (g) explanatory exercise for user buy-in. Copyright MAMPU Chapter 4 - 1

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents