|(14 intermediate revisions by 4 users not shown)|
DEFINITION'' ( Citation)</blockquote> |+|
| || |
|−|If more than one definition, please copy/paste the code for the definition (above) and insert a number in parentheses at the beginning of each definition (i.e. (1), (2), (3), etc.) ‘’’Make sure to include the source citation at the end of the definition.’’’ |+|
. . . : .. .
=Source(s)==== | |
|−|Please include the source(s) for the definition(s) above. The sources should be formatted using Chicago Manual of Style (15th ed. ). Please see the [http: //www.bkcase.org/fileadmin/bkcase/files/Wiki_Files__for_linking_/BKCASE_Reference_Guidance. pdf BKCASE Reference Guidance] for formatting. | |
|−|If there is more than one definition, the source for each definition must be provided. Sources should be listed in alphabetical order by author. | |
| || |
|−|'''This area is for the ''Glossary Term Owner'' to provide discussion on the context and uses of the term. This is ''not'' where you should provide comments. ''' Please use the “Discussion” tab (above) to provide feedback if you are not the term owner. |+|
is on the and to .
| || |
|−|Please note that if there is more than one definition, it is very important to provide information on the context of the different terms and to explain to the user why it is not possible to identify only one definition. For example, is this an emerging concept for which there is still much research to be done? Or have two different definitions emerged as the result of two different disciplines interacting with systems engineering? |+|
| || |
|−|[[Category:Glossary of Terms]] |+|
Latest revision as of 08:49, 28 October 2019
…the justified confidence that the system functions as intended and is free of exploitable vulnerabilities, either intentionally or unintentionally designed or inserted as part of the system at any time during the life cycle... This confidence is achieved by system assurance activities, which include a planned, systematic set of multi-disciplinary activities to achieve the acceptable measures of system assurance and manage the risk of exploitable vulnerabilities. (NATO February 2010, p. 1)
NATO. 2010. Engineering for system assurance in NATO programs. Washington, DC: NATO Standardization Agency, DoD 5220.22M-NISPOM-NATO-AEP-67. February 2010.
The NATO document is organized based on the life cycle processes in ISO/IEC 15288:2008 and provides process and technology guidance to improve system assurance.
SEBoK v. 2.1, released 31 October 2019