---
# System prepended metadata

title: Untitled

---

Secure Channel:
: {{NIST-SP800-90Ar1}} defines a Secure Channel as follows:

  {:aside}
  > <!-- This really is a block quote, but RFCXMLv3 doesn't allow that -->
  "A path for transferring data between two entities or components that
  ensures confidentiality, integrity and replay protection, as well as
  mutual authentication between the entities or components. The secure
  channel may be provided using approved cryptographic, physical or
  procedural methods, or a combination thereof"

  For the purposes of the present document, we focus on a protected communication
  channel used for conveyance that can ensure the same qualities as CWT without
  the COSE protection. For example, encrypted conveyance via PCIe, a TLS tunnel,
  or other object security than COSE, such as CMS or X.509 v3 certificate. 
  Note that this means that, in specific cases, the Secure Channel as defined here
  does not itself provide mutual authentication.  See {{secchan}}.
