Difference between revisions of "Security Boundary"
From MgmtWiki
(→Full Title or Meme) |
(→Problems) |
||
| Line 6: | Line 6: | ||
==Problems== | ==Problems== | ||
| + | All security boundaries have gateways that allow access to the protected [[Resource]]s. Determination of what accesses are permitted across a boundary is never more than an approximation of an impenetrable boundary. | ||
==Solutions== | ==Solutions== | ||
Revision as of 10:41, 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
All security boundaries have gateways that allow access to the protected Resources. Determination of what accesses are permitted across a boundary is never more than an approximation of an impenetrable boundary.
Solutions
References
- ↑ NIST Glossary https://csrc.nist.gov/Glossary/?term=4819
