UAE Information Assurance Regulation T7.2.2 Developer-Provided Training Priority Applicability P4 Based on risk assessment Control The entity shall require the developer of the information system, system component, or information system service to provide the trainings needed. Sub-Control The entity shall require the developer to: 1) identify training requirements based on implemented security functions and in line with the Awareness and Training Policy (refer to M3.1.1) for the correct use and operation of the functions 2) design and execute appropriate training programs to meet these requirements 3) include training provisions in the relevant service delivery agreement Implementation Guidance (for information purpose only) This control applies to external and internal (in-house- developers). Training of personnel is an essential element to ensure the effectiveness of security controls implemented within organizational information systems. Training options include, for example, classroom-style training, web-based/computer-based training, and hands-on training. Entities can also request sufficient training materials from developers to conduct in-house training or offer self-training to organizational personnel. Entities determine the type of training necessary and may require different types of training for different security functions, controls, or mechanisms. T7.3 Correct Processing in Applications Objective To prevent errors, loss, unauthorized modification or misuse of information in applications Performance Indicator Percentage of systems for which data validation controls have been adequately defined, implemented, and proven effective by thorough testing Automation Guidance Source code testing tools, web application security scanning tools, and object code testing tools have proven useful in securing application software, along with manual application security penetration testing by testers who have extensive programming knowledge and application penetration testing expertise. The Common Weakness Enumeration (CWE) initiative is used by many such tools to identify the weaknesses that they find. Entities can also use CWE to determine which types of weaknesses they are most interested in addressing and removing. When evaluating the effectiveness of testing for these weaknesses, MITRE’s Common Attack Pattern Enumeration and Classification can be used to organize and record the breadth of the testing for the CWEs and to enable testers to think like attackers in their development of test cases. Relevant Threats and Vulnerabilities • • • • • 176 Software malfunction Illegal processing of data Injection flaws, such as SQL, OS, and LDAP Broken Authentication and Session Management Cross-Site Scripting (XSS)

Select target paragraph3

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