Remote Attestation Procedures for Network Security Functions (NSFs) through the I2NSF Security Controller
draft-pastor-i2nsf-nsf-remote-attestation-01
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-03-13
|
|
Replaces |
|
draft-pastor-i2nsf-vnsf-attestation
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Interface to Network Security Functions A. Pastor
Internet-Draft D. Lopez
Intended status: Experimental Telefonica I+D
Expires: September 14, 2017 A. Shaw
Hewlett Packard Labs
March 13, 2017
Remote Attestation Procedures for Network Security Functions (NSFs)
through the I2NSF Security Controller
draft-pastor-i2nsf-nsf-remote-attestation-01
Abstract
This document describes the procedures a client can follow to assess
the trust on an external NSF platform and its client-defined
configuration through the I2NSF Security Controller. The procedure
to assess trustworthiness is based on a remote attestation of the
platform and the NSFs running on it performed through a Trusted
Platform Module (TPM) invoked by the Security Controller.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 14, 2017.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
Pastor, et al. Expires September 14, 2017 [Page 1]
Internet-Draft Remote Attestation for NSFs March 2017
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. Establishing Client Trust . . . . . . . . . . . . . . . . . . 4
3.1. First Step: Client-Agnostic Attestation . . . . . . . . . 4
3.2. Second Step: Client-Specific Attestation . . . . . . . . . 5
3.3. Trusted Computing . . . . . . . . . . . . . . . . . . . . 5
4. NSF Attestation Principles . . . . . . . . . . . . . . . . . . 7
4.1. Requirements for a Trusted NSF Platform . . . . . . . . . 8
4.1.1. Trusted Boot . . . . . . . . . . . . . . . . . . . . . 8
4.1.2. Remote Attestation Service . . . . . . . . . . . . . . 9
4.1.3. Secure Boot . . . . . . . . . . . . . . . . . . . . . 10
5. Remote Attestation Procedures . . . . . . . . . . . . . . . . 11
5.1. Trusted Channel with the Security Controller . . . . . . . 12
5.2. Security Controller Attestation . . . . . . . . . . . . . 13
5.3. Platform Attestation . . . . . . . . . . . . . . . . . . . 14
6. Security Considerations . . . . . . . . . . . . . . . . . . . 14
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
8.1. Normative References . . . . . . . . . . . . . . . . . . . 15
8.2. Informative References . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
Pastor, et al. Expires September 14, 2017 [Page 2]
Internet-Draft Remote Attestation for NSFs March 2017
1. Introduction
As described in [I-D.ietf-i2nsf-problem-and-use-cases], the use of
externally provided NSF implies several additional concerns in
security. The most relevant threats associated with a externalized
platform are detailed in [I-D.ietf-i2nsf-framework]. As stated
there, mutual authentication between the user and the NSF environment
and, more importantly, the attestation of the components in this
environment by clients, could address these threats and provide an
Show full document text