Re: [Iotops] WG Adoption Call on draft-moran-iot-nets-02

Russ Housley <housley@vigilsec.com> Thu, 02 March 2023 16:57 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: iotops@ietfa.amsl.com
Delivered-To: iotops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 513AFC15DF69; Thu, 2 Mar 2023 08:57:39 -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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JS64Vy8vNTvx; Thu, 2 Mar 2023 08:57:35 -0800 (PST)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4C22C152F0F; Thu, 2 Mar 2023 08:57:35 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 8A56F18F330; Thu, 2 Mar 2023 11:57:34 -0500 (EST)
Received: from [10.0.1.2] (pfs.iad.rg.net [198.180.150.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 74D4218E6EB; Thu, 2 Mar 2023 11:57:34 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <2b042daf-a7a4-84b4-bd9a-bb293849ca43@isode.com>
Date: Thu, 02 Mar 2023 11:57:33 -0500
Cc: iotops@ietf.org, "iotops-chairs@ietf.org" <iotops-chairs@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2C446A21-E61A-408A-99EA-5B3B34CA9AFA@vigilsec.com>
References: <2b042daf-a7a4-84b4-bd9a-bb293849ca43@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.3445.104.21)
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/iotops/g91IAYglmefrVfZXifePyvygsWc>
Subject: Re: [Iotops] WG Adoption Call on draft-moran-iot-nets-02
X-BeenThere: iotops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IOT Operations <iotops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iotops>, <mailto:iotops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iotops/>
List-Post: <mailto:iotops@ietf.org>
List-Help: <mailto:iotops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iotops>, <mailto:iotops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Mar 2023 16:57:39 -0000

I have no objection to the adoption of this document, but I would like to see the discussion also cover protection of data at rest in the IoT device.  Currently, it talks about "information in transit on the networks or stored in the IoT application or in the Cloud."  However, the protections for data at rest are not really covered in the subsections that follow.

This document is highly aligned with ENISA.  It mentions a NIST document, but it ignores other sources of reasonable requirements, such as https://ctiacertification.org/program/iot-cybersecurity-certification/.  I think that pulling together a superset of the requirements (as long as they are not in conflict) would be a real service to the community.

Russ


> On Mar 2, 2023, at 7:34 AM, Alexey Melnikov <alexey.melnikov@isode.com> wrote:
> 
> Dear IOTOPS participants,
> 
> This message starts a 3 week call for Working Group Adoption of "A summary of security-enabling technologies for IoT devices" (draft-moran-iot-nets-02 <https://datatracker.ietf.org/doc/draft-moran-iot-nets/>)
> 
> ending on Thursday, March 23rd.
> 
> 
> Please reply to this email with your support (or lack thereof) and especially any substantive comments you may have. When including comments, please consider whether or not they need to be resolved before document adoption by the WG.
> 
> Alternatively you can email chairs directly at <iotops-chairs@ietf.org>.
> 
> 
> Best Regards,
> 
> Alexey,
> For the IOTOPS co-chairs,
> 
> -- 
> Iotops mailing list
> Iotops@ietf.org
> https://www.ietf.org/mailman/listinfo/iotops