UAE Information Assurance Regulation T7.5 Security of System Files Objective To ensure the security of system files Performance Indicator Percentage of systems assessed as fully compliant with the information systems acquisition, development and maintenance policy Automation Guidance Security of system files can only be achieved through the use of automated controls, including but not limited to file permission restrictions, file access log, and file hashing for integrity check. Relevant Threats and Vulnerabilities • • T7.5.1 Unauthorized access to system files Corruption of data Control of Operational Software Priority Applicability P4 Based on risk assessment Control The entity shall control the installation of software on operational systems. Sub-Control The entity shall: 1) allow the installation of software only by authorized administrators 2) inhibit installation of software by users, unless justified by their role/ business need 3) keep an original copy of every installed software, including previous versions 4) have a rollback strategy 5) have an audit log of all software installations Implementation Guidance (for information purpose only) To minimize the risk of corruption to operational systems, the following guidelines should be considered to control changes: a. the updating of the operational software, applications, and program libraries should only be performed by trained administrators upon appropriate management authorization; b. operational systems should only hold approved executable code, and not development code or compilers; c. applications and operating system software should only be implemented after extensive and successful testing; the tests should include tests on usability, security, effects on other systems and user-friendliness, and should be carried out on separate systems; it should be ensured that all corresponding program source libraries have been updated; d. a configuration control system should be used to keep control of all implemented software as well as the system documentation; e. a rollback strategy should be in place before changes are implemented; f. an audit log should be maintained of all updates to operational program libraries; g. previous versions of application software should be retained as a contingency measure; h. old versions of software should be archived, together with all required information and parameters, procedures, configuration details, and supporting software for as long as the data is retained in archive. 182

Select target paragraph3

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