IETF Logo Mail Archive

Re: [Iot-onboarding] SBOM : Basic question on how it will be used

Eliot Lear <lear@cisco.com> Thu, 26 March 2020 18:07 UTC

Return-Path: <lear@cisco.com>
X-Original-To: iot-onboarding@ietfa.amsl.com
Delivered-To: iot-onboarding@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58E1C3A0C16 for <iot-onboarding@ietfa.amsl.com>; Thu, 26 Mar 2020 11:07:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level:
X-Spam-Status: No, score=-9.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j__B83l4MbVi for <iot-onboarding@ietfa.amsl.com>; Thu, 26 Mar 2020 11:07:26 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A68B3A0BFA for <iot-onboarding@ietf.org>; Thu, 26 Mar 2020 11:07:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1331; q=dns/txt; s=iport; t=1585246045; x=1586455645; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=K2OOYJ8+qHkPY82b/BK+F/BHOO5pgp6bY2f8cEA36nE=; b=X1urOOHBzPfEb5Gp8/XaD+ID5iMLfvlY7hu3WdUlM2VW1qEnIBoZKZxo /BZHSizXRBmUf/S74m0afQQ6H6/NUPL0P56l0S+ju65cig84SdGs/LgIC 4NVah2/4+HIPfybFnaGg/jZhcQd8wPX3FKzmFmwXpUEKpjstekOKaSosv I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DCAADv7nxe/xbLJq1mHAEBAQEBBwEBEQEEBAEBgWoEAQELAYNpIBIqhBqJAodnJYlskVsKAQEBDAEBLwQBAYFQgnQCglM3Bg4CAwEBCwEBBQEBAQIBBQRthWKFYwEBAQECASNWBQsLGAICJgICITYGExkGgweCTAMOIK0TdYEyhUuCcA2CIIEOKgGMSIIAgREnDBSCHy4+ghuCMIMRMoIsBI4SoX9EgkaCVo92hD0dm1+KQJAYjHqDNAIEBgUCFYFoI4FYMxoIGxVlAYJBPhIYDZxmQAMwjyUBAQ
X-IronPort-AV: E=Sophos;i="5.72,309,1580774400"; d="scan'208";a="24791897"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 26 Mar 2020 18:07:23 +0000
Received: from ams3-vpn-dhcp5615.cisco.com (ams3-vpn-dhcp5615.cisco.com [10.61.85.238]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id 02QI7M9D027503 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 26 Mar 2020 18:07:22 GMT
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Eliot Lear <lear@cisco.com>
In-Reply-To: <CAHiu4JOOMpLmZ9RmOu4KBFf7kLOkiHKDDaYw-dc24gJDtq_Dcg@mail.gmail.com>
Date: Thu, 26 Mar 2020 19:07:22 +0100
Cc: iot-onboarding@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <FA84BA0B-E2F4-4029-8DC9-E9E6E6882978@cisco.com>
References: <CAHiu4JOOMpLmZ9RmOu4KBFf7kLOkiHKDDaYw-dc24gJDtq_Dcg@mail.gmail.com>
To: "M. Ranganathan" <mranga@gmail.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-Outbound-SMTP-Client: 10.61.85.238, ams3-vpn-dhcp5615.cisco.com
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-onboarding/NIOnv-q4qEb_Pk0J0R7gc9STP-s>
Subject: Re: [Iot-onboarding] SBOM : Basic question on how it will be used
X-BeenThere: iot-onboarding@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of IoT onboarding mechanisms <iot-onboarding.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iot-onboarding>, <mailto:iot-onboarding-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iot-onboarding/>
List-Post: <mailto:iot-onboarding@ietf.org>
List-Help: <mailto:iot-onboarding-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iot-onboarding>, <mailto:iot-onboarding-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Mar 2020 18:07:29 -0000

Hi Ranga,

I think you ask a good question.  There is a broader picture of how you tie this to an entire software life cycle, that includes things like repeatable builds, remote attestation, etc.  This is just one component.  Having a good view of the whole picture is something that the NCCOE and others should definitely engage on.

> On 26 Mar 2020, at 18:55, M. Ranganathan <mranga@gmail.com> wrote:
> 
> I am starting this new thread on the subject as I am confused about
> how an SBOM will actually be used on a network and I don't want to
> divert the other thread.  Before I understand how it will get
> distributed, I'd like to start with some basic questions.
> 
> Given that there is no automated mechanism to actually check if the
> SBOM is consistent with the software that is bundled with the device
> is it regarded as being just informational (i.e. an additional piece
> of information about the device that the manufacturer ships)?  If the
> SBOM is informational and specific to the software that is actually on
> the device and you trust the software that is on the device, then I'd
> imagine the device could publish its own SBOM.

It can do this when it has the interfaces to do it.  In some cases it won’t.  That’s why I proposed three methods.

Eliot

v2.23.0 | Report a Bug | By Email