IETF Logo Mail Archive

Re: [Mud] [OPSAWG] SBOMs and version non-specific MUD files

Dick Brooks <dick@reliableenergyanalytics.com> Fri, 04 February 2022 21:19 UTC

Return-Path: <dick@reliableenergyanalytics.com>
X-Original-To: mud@ietfa.amsl.com
Delivered-To: mud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B32433A23B1; Fri, 4 Feb 2022 13:19:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.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 H1VdQvqt3uOa; Fri, 4 Feb 2022 13:19:18 -0800 (PST)
Received: from forward3-smtp.messagingengine.com (forward3-smtp.messagingengine.com [66.111.4.237]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05A773A23AF; Fri, 4 Feb 2022 13:19:13 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailforward.nyi.internal (Postfix) with ESMTP id 680201940DC8; Fri, 4 Feb 2022 16:19:12 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 04 Feb 2022 16:19:12 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=wiwGoe79pqb0OKI2JDToy6PAOwNNwh0teSUsd1XXs I4=; b=JjdpTdSM2/JuJrp8p9iJ4Ps17YC19cPvlJlGrSTPnOWNzWqVFVSpLASgE FL6lJK323lM2evv2NzoyTVbV8UUBvoDGJrMt0LcRBLdMbsihaWW5TJ668kw8rIfj KHUpuGaPAwfpAVpQ5FwC+tnDTta+vM2IYgQDyk15Aip50tCmW+RYASAhCDffiUL7 XvisYvw25ARyHuUC5u16k8X7ek1adVVdo14SYLFM7dLVTJkYKPxTm5OgZ2kC9dRN qj4VQs1iZFDf72Iv8kEigDO9SQAHFnwzwhQEMGSq9nz1qmyXA3mzpos566HR7azq dfSL3xa74HYzqbYjMbPFuF2wZcCjA==
X-ME-Sender: <xms:T5j9YdHXtNkYWy_E_oKDLILQ_B0F_M_HlZSG0f0kZWzrzLl0rpH_tg> <xme:T5j9YSXGh6YQWm5WDRqR3GJgJGli8gUkjPLGJzPCbJcNMQShV0xdCvbzIKk8HRIn6 ycwa18ijnjBn34Ujg>
X-ME-Received: <xmr:T5j9YfLzUJs7La8I0izz5OE26NZPY0w-nCjxsNsORCqPgedZ8DfxW7o>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrgeelgddugeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpehrhffvfhgjufffohfkgggtgffoth esthhqghdtvddtjeenucfhrhhomhepfdffihgtkhcuuehrohhokhhsfdcuoeguihgtkhes rhgvlhhirggslhgvvghnvghrghihrghnrghlhihtihgtshdrtghomheqnecuggftrfgrth htvghrnhepvdeuledvffdttdeutdffveejueektedtlefggfektefgudetjefggedvjeei gfeunecuffhomhgrihhnpehrvghlihgrsghlvggvnhgvrhhghigrnhgrlhihthhitghsrd gtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep ughitghksehrvghlihgrsghlvggvnhgvrhhghigrnhgrlhihthhitghsrdgtohhm
X-ME-Proxy: <xmx:T5j9YTG2nuASEM17crMXFnIc7c0FE510qAUNkcfZv--iQLd4W8lMlQ> <xmx:T5j9YTVds-qO5tzM2BtDaXNZOVymLLKQlPeNk5XvYz6mQraq8Px4Fg> <xmx:T5j9YePp3neUg1rJGbk5QFLAXYs5fNectscMRK3Sdm5rGZ4s_kW6LA> <xmx:UJj9YUfdOQXbyPNcMt5DvdeMyJR98CSXMYaeVIInOyYmkOpnH4mPlg>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 4 Feb 2022 16:19:11 -0500 (EST)
Reply-To: dick@reliableenergyanalytics.com
From: Dick Brooks <dick@reliableenergyanalytics.com>
To: 'Michael Richardson' <mcr+ietf@sandelman.ca>, mud@ietf.org, opsawg@ietf.org
References: <282926.1643996393@dooku> <686901d819f9$8ffc5720$aff50560$@reliableenergyanalytics.com> <27407.1644006641@localhost>
In-Reply-To: <27407.1644006641@localhost>
Date: Fri, 04 Feb 2022 16:19:10 -0500
Organization: Reliable Energy Analytics LLC
Message-ID: <401a01d81a0c$db2feaf0$918fc0d0$@reliableenergyanalytics.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQKKKG9YQSV0Fk837yYvHefh3I71dwGBqSaeAWr2vPCrCGJ80A==
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/mud/-v_86Y80kGmqfybLy30PSZRiJW4>
Subject: Re: [Mud] [OPSAWG] SBOMs and version non-specific MUD files
X-BeenThere: mud@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of Manufacturer Ussage Descriptions <mud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mud>, <mailto:mud-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mud/>
List-Post: <mailto:mud@ietf.org>
List-Help: <mailto:mud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mud>, <mailto:mud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Feb 2022 21:19:23 -0000

True, some IoT devices will "auto update" using MUD/SUIT capabilities and a customer may never see, or have access to, the SBOM. 

Thanks,

Dick Brooks

Never trust software, always verify and report! ™
http://www.reliableenergyanalytics.com
Email: dick@reliableenergyanalytics.com
Tel: +1 978-696-1788

-----Original Message-----
From: Michael Richardson <mcr+ietf@sandelman.ca> 
Sent: Friday, February 4, 2022 3:31 PM
To: dick@reliableenergyanalytics.com; mud@ietf.org; opsawg@ietf.org
Subject: Re: [OPSAWG] SBOMs and version non-specific MUD files


Dick Brooks <dick@reliableenergyanalytics.com> wrote:
    > The predominant "SBOM delivery channel" I see is through access controlled
    > customer portals where customers can download SBOM's Vulnerability
    > Disclosures and other artifacts needed to perform a NIST C-SCRM risk
    > assessment for Executive Order 14028.

For hospitals, sure.
For baby monitors, maybe not.


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email