Difference between revisions of "Security Boundary"
From MgmtWiki
(Created page with "==Full Title or Meme== An imaginary definable perimeter encompassing all the critical functions in an INFOSEC product and separating them from all other functions within the p...") |
(→Full Title or Meme) |
||
| Line 1: | Line 1: | ||
==Full Title or Meme== | ==Full Title or Meme== | ||
| − | An imaginary definable perimeter encompassing all the critical functions in an INFOSEC product and separating them from all other functions within the product.< | + | An imaginary definable perimeter encompassing all the critical functions in an INFOSEC product and separating them from all other functions within the product.<ref>NIST ''Glossary'' https://csrc.nist.gov/Glossary/?term=4819</ref> |
| + | |||
==Context== | ==Context== | ||
Since the very first [[Trusted Execution Environment]] in 1961 there has been the desire to place only a part of the [[Resource]]s of an enterprise in a location that is secure from attack. | Since the very first [[Trusted Execution Environment]] in 1961 there has been the desire to place only a part of the [[Resource]]s of an enterprise in a location that is secure from attack. | ||
Revision as of 09:39, 25 July 2018
Full Title or Meme
An imaginary definable perimeter encompassing all the critical functions in an INFOSEC product and separating them from all other functions within the product.[1]
Context
Since the very first Trusted Execution Environment in 1961 there has been the desire to place only a part of the Resources of an enterprise in a location that is secure from attack.
Problems
Solutions
References
- ↑ NIST Glossary https://csrc.nist.gov/Glossary/?term=4819
