UAE Information Assurance Regulation f. people, and their qualifications, skills, and experience g. intangibles, such as reputation and image of the entity The identified assets are summarized in the Asset Inventory (refer to T1.2.1). It might be useful to summarize assets in suitable groups (e.g. all PCs in a call center, processing the same type of information), but care should be taken to only group “like with like” when doing so. It is also helpful to take account of business processes, as they often can help to understand the information flow and how assets are working in the entity. Identification of threats: Threats are not very dependent on the entity and its business; they are just out there trying to succeed. When identifying threats, it can be helpful to use threat lists (e.g. those provided in this Regulation, or in other standards, such as ISO/IEC 27005), and to look into incident reports (incidents are always related to threats that have been successful- and audit reports, and to keep an open mind to the latest development as new threats will continue to emerge. It is also important to not only look at threats from the outside, such as hackers or malware, but also consider inside threats. A disgruntled employee with given access rights can often do more damage as outsiders. Identification of vulnerabilities: The identification of vulnerabilities should be based on an assessment of the existing controls. To do so, it is recommended to conduct a gap analysis, which checks the controls in place against this Regulation. The results of the gap analysis form an input in the identification of vulnerabilities as well as into the assessment of the risk likelihood (see also M2.2.2 below). Any control, which has been identified as missing, not completely in place, not fully documented or not complied with identifies at least one (if not more- vulnerabilities, which might be exploited by the identified threats. Please note: The identification of threats and vulnerabilities takes place per each identified asset, so this easily produces a lot of information. To keep the amount of information manageable, it is recommended to: a. identify threats and vulnerabilities with the existing controls in mind b. identify only threat/vulnerability pairs where the threat will actually exploit the vulnerability See also T 7.7 on Technical Vulnerability Management 52

Select target paragraph3

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