equal
deleted
inserted
replaced
36 </li> |
36 </li> |
37 <li id="GUID-3D7F3A95-635E-4D9C-9883-BBD36263401D"><p>Repeat these |
37 <li id="GUID-3D7F3A95-635E-4D9C-9883-BBD36263401D"><p>Repeat these |
38 steps until the necessary level of protection is achieved.</p></li> |
38 steps until the necessary level of protection is achieved.</p></li> |
39 </ol> |
39 </ol> |
40 <p/> |
40 <p/> |
41 <fig id="GUID-A41ADA16-6D0B-4EA4-BBF2-67C2CFED68F3"><title>Security development process</title><image href="GUID-316D7B85-F827-4479-B5EE-81F210614236_d0e10243_href.png"/></fig> |
41 <fig id="GUID-A41ADA16-6D0B-4EA4-BBF2-67C2CFED68F3"><title>Security development process</title><image href="GUID-316D7B85-F827-4479-B5EE-81F210614236_d0e11518_href.png"/></fig> |
42 <p>The security development process is guided by <i>cost</i>, <i>efficiency,</i> and <i>usability</i>. |
42 <p>The security development process is guided by <i>cost</i>, <i>efficiency,</i> and <i>usability</i>. |
43 If security is too tight, this may be expensive and affect both performance |
43 If security is too tight, this may be expensive and affect both performance |
44 and the user's experience of the system or software. On the other hand, if |
44 and the user's experience of the system or software. On the other hand, if |
45 security is too slack, this may result in severe damage and, in the long run, |
45 security is too slack, this may result in severe damage and, in the long run, |
46 be even more costly.</p> |
46 be even more costly.</p> |