Difference between revisions of "Integrity (glossary)"

From SEBoK
Jump to navigation Jump to search
(Definition of integrity)
m (Definition of integrity)
Line 10: Line 10:
  
 
===Discussion===
 
===Discussion===
None.
+
 
 +
In a resilience context integrity is an attribute of a system before, during and after an encounter with a threat.
  
 
[[Category:Glossary of Terms]]
 
[[Category:Glossary of Terms]]
  
 
{{DISQUS}}
 
{{DISQUS}}

Revision as of 20:27, 22 May 2017

[1] the state of being whole and undivided. (Oxford Online Dictionary 2016)

[2] Degree to which a system or component prevents unauthorized access to, or modification of, computer programs or data. (ISO/IEC 2011)

Sources

[1] Oxford On-line Dictionary (2016)

[2]ISO/IEC. 2011. Systems and Software Engineering - Systems and Software Quality Requirements and Evaluation (SQuaRE) - Systems and Software Quality Models. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC). ISO/IEC 25010:2011.

Discussion

In a resilience context integrity is an attribute of a system before, during and after an encounter with a threat.


SEBoK v. 1.9.1 released 30 September 2018

SEBoK Discussion

Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.

If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.

blog comments powered by Disqus