Difference between revisions of "Security Boundary"

Revision as of 10:41, 25 July 2018 (view source) Tom (talk | contribs) (→‎Problems) ← Older edit		Revision as of 10:44, 25 July 2018 (view source) Tom (talk | contribs) (→‎References) Newer edit →
Line 11:		Line 11:
	==References==		==References==
−		+	One interesting note about the Glossary term referenced at NIST. It actually comes from the [https://www.cnss.gov/CNSS/issuances/Instructions.cfm Committee on National Security Systems - Instructions] which is on a site with a DoD level 3 certificate, which is not trusted by any of the major browser vendors.
	[[Category:Glossary]]		[[Category:Glossary]]

---

Revision as of 10:44, 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

One interesting note about the Glossary term referenced at NIST. It actually comes from the Committee on National Security Systems - Instructions which is on a site with a DoD level 3 certificate, which is not trusted by any of the major browser vendors.

1. ↑ NIST Glossary https://csrc.nist.gov/Glossary/?term=4819