!!! Overview
[{$pagename}] is the degree of resistance to encountering an [unfortunate event][{$pagename}] is only required when you do not have [Trust][{$pagename}] exists to facilitate [Trust].[1] 

[{$pagename}] is distinct and separate from [Privacy].

[{$pagename}] is way too broad to be an objective of any endeavor. Sure an end-user may use the term but any project manager must determine what [{$pagename}] implies in the [context] of the project and provide appropriate details.

[{$pagename}] implies there are [Protected Resources] and the requirement of [Access Control] to prevent an [unfortunate event].

[Information security] is the degree of resistance to encountering an [unfortunate event] involving [data]

!! [{$pagename}] Objectives ([CIA]): 
Many sources, including NIST.SP.800-53, imply the Security Objectives are:
* [confidentiality]
* [integrity]
* [availability]
Some of them even claim advanced security goals like [Perfect Forward Secrecy].

Interestingly [{$pagename}] Objectives and [Cryptography Objectives] are the same except for possibly [Authenticity] and [availability].

!! perfect [{$pagename}]
There is no such thing as [Perfect Security]

!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
* [#1] - [Bruce Schneier on Trust|https://www.schneier.com/news/archives/2012/02/bruce_schneier_on_tr.html|target='_blank'] - based on data observed: 2012-09-16