UAE Information Assurance Regulation T7.7.1 Control of Technical Vulnerabilities Priority Applicability P1 Based on risk assessment Control The entity shall obtain and act upon information about technical vulnerabilities of information systems being used Sub-Control The entity shall: 1) identify vulnerabilities in new systems and applications and define a remediation plan before placing them in a production environment 2) test, review, check, and verify the presence of vulnerabilities in production systems throughout the development life-cycle, preferably by the use of automated testing tools 3) perform a Cost-Benefit-Analysis (CBA) for vulnerabilities to determine the proper remediation plan, where appropriate Implementation Guidance (for information purpose only) As a prerequisite, a current and complete inventory of assets is needed (including software vendor, version numbers, current state of deployment, and the person(s) within the entity responsible for the software). The following guidance should be followed to establish an effective management process for technical vulnerabilities: a. the entity should define and establish the roles and responsibilities associated with technical vulnerability management, including vulnerability monitoring, vulnerability risk assessment (see M2.2), patching, asset tracking, and any coordination responsibilities required; b. the entity should identify information resources that will be used to identify relevant technical vulnerabilities and to maintain awareness about them should be identified for software and other technology (based on the asset inventory list); these information resources should be updated based on changes in the inventory, or when other new or useful resources are found; c. the entity should define a timeline to react to notifications of potentially relevant technical vulnerabilities; d. the entity should identify the risks associated to potential technical vulnerability and the actions to be taken; such action could involve patching of vulnerable systems and/or applying other controls; e. depending on how urgently a technical vulnerability needs to be addressed, the action taken should be carried out according to the controls related to change management or by following information security incident response procedures; f. if a patch is available, the risks associated with installing the patch should be assessed (the risks posed by the vulnerability should be compared with the risk of installing the patch); g. patches should be tested and evaluated before they are installed to ensure they are effective and do not result in side effects that cannot be tolerated; if no patch is available, other controls should be considered, such as: 1- turning off services or capabilities related to the vulnerability; 2- adapting or adding access controls, e.g. firewalls, at network borders; 3- increased monitoring to detect or prevent actual attacks; 4- raising awareness of the vulnerability; h. an audit log should be kept for all procedures undertaken; i. the technical vulnerability management process should be regularly monitored and evaluated in order to ensure its effectiveness and efficiency; j. systems at high risk should be addressed first. 190

Select target paragraph3

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