Re: [sacm] 答复: new drafts about network infrastructure device's security baseline:

Jerome Athias <jerome.athias@protonmail.com> Tue, 12 September 2017 07:08 UTC

Return-Path: <jerome.athias@protonmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A15A6132D50 for <sacm@ietfa.amsl.com>; Tue, 12 Sep 2017 00:08:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=protonmail.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 2T6FkedtlasW for <sacm@ietfa.amsl.com>; Tue, 12 Sep 2017 00:08:25 -0700 (PDT)
Received: from mail1.protonmail.ch (mail1.protonmail.ch [185.70.40.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 730BA1331B4 for <sacm@ietf.org>; Tue, 12 Sep 2017 00:08:24 -0700 (PDT)
Date: Tue, 12 Sep 2017 03:08:12 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=default; t=1505200098; bh=Hq24XXga341O7BBsuzpnsbImNM+HLgcsRiNLUQLuITw=; h=To:From:Cc:Reply-To:Subject:In-Reply-To:References:Feedback-ID: From; b=HGwo7pg8q6BovIF1lFOHmm0HWrbS0K2VlLfaM/ccxHIcetCtqWC3G8Z32UEXc9yrN YSEfMl85OD7jB+TDa+RI+5TQ+jQLmMSzMbblwEs0yLPP2NRqVt0nawe4onkxn3Bdrp jDA5SUQeK8c4fPB6uNTQR8oFEHdnQb+6aWNqn6bE=
To: "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com>, "Xialiang (Frank)" <frank.xialiang@huawei.com>, "Waltermire, David A. (Fed)" <david.waltermire@nist.gov>, "Panos Kampanakis (pkampana)" <pkampana@cisco.com>, "sacm@ietf.org" <sacm@ietf.org>
From: Jerome Athias <jerome.athias@protonmail.com>
Cc: "Linqiushi \\(Jessica, SCC\\)" <linqiushi@huawei.com>, "Zhengguangying \\(Walker\\)" <zhengguangying@huawei.com>, "dongyue \\(D\\)" <dongyue6@huawei.com>
Reply-To: Jerome Athias <jerome.athias@protonmail.com>
Message-ID: <tqvzUCyeKnAQyw3CC-AfqT7LV3x8UQxzx4LXCRo-tB3p_uaHBK3Cr9ngpFVzF9ZB-Jr4v-XJfSuPvSIOLW6A5w6lXDMYbWIkZu-J3D2x4l4=@protonmail.com>
In-Reply-To: <808ED0DE-508A-47FA-A9F0-CD60CF586A79@cisco.com>
References: <808ED0DE-508A-47FA-A9F0-CD60CF586A79@cisco.com>
Feedback-ID: 0pNaUpQyJcJ_FqKgvRh59kNH9tw1YU9Hb7-41TF1UFya4DA0ft6-ejYSrPjLLQWz-KcGUoHsZH8z6Hzy-ZW3EA==:Ext:ProtonMail
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="b1_d08fbf844e3c1fbfdab53feaddb4bdc7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/rh-vmVGJerBcIv3k4tYH-HHy0g8>
Subject: Re: [sacm] 答复: new drafts about network infrastructure device's security baseline:
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2017 07:08:28 -0000

OVAL

On Mon, Sep 11, 2017 at 6:35 PM, Nancy Cam-Winget (ncamwing) <ncamwing@cisco.com> wrote:

> Hi Frank,
>
> It is not clear to me why we couldn’t reference the work and attributes already being worked on in NETMOD and perhaps i2nsf?  While I agree that SACM includes network elements as endpoints, I think we can leverage work already being defined by other working groups.
>
> Warm regards, Nancy
>
> From: sacm <sacm-bounces@ietf.org> on behalf of "Xialiang (Frank)" <frank.xialiang@huawei.com>
> Date: Thursday, September 7, 2017 at 7:39 PM
> To: "Waltermire, David A. (Fed)" <david.waltermire@nist.gov>, Panos Kampanakis <pkampana@cisco.com>, "sacm@ietf.org" <sacm@ietf.org>
> Cc: "Linqiushi (Jessica, SCC)" <linqiushi@huawei.com>, "Zhengguangying (Walker)" <zhengguangying@huawei.com>, "dongyue (D)" <dongyue6@huawei.com>
> Subject: [sacm] 答复: new drafts about network infrastructure device's security baseline:
>
> Hi Dave and Panos,
>
> I think Dave gives a very clear and detailed clarification about the definition of endpoints in SACM and the latest SACM plan, thanks.
>
> I will follow the SACM information model and the latest decision to update these drafts.
>
> Any comments are welcome!
>
> B.R.
>
> Frank
>
> 发件人: Waltermire, David A. (Fed) [mailto:david.waltermire@nist.gov]
> 发送时间: 2017年9月8日 3:01
> 收件人: Panos Kampanakis (pkampana); Xialiang (Frank); sacm@ietf.org
> 抄送: Linqiushi (Jessica, SCC); Zhengguangying (Walker); dongyue (D)
> 主题: RE: new drafts about network infrastructure device's security baseline:
>
> Panos,
>
> At the last IETF meeting we started discussing a charter update. I believe we are currently waiting on the chairs to start this discussion on the list. This will give the working group an opportunity to clarify this issue in the charter.
>
> As far as endpoints, the definition that has been used for endpoints in the SACM charter is the one from RFC 5209, which is "
>
> Any computing device that can be connected to a network.
>
>       Such devices normally are associated with a particular link layer
>
>       address before joining the network and potentially an IP address
>
>       once on the network.  This includes: laptops, desktops, servers,
>
>       cell phones, or any device that may have an IP address."
>
> As most network devices are connected to networks, and often expose a management interface that is IP addressable, I’d say they qualify as endpoints. This view is also reflected in the SACM terminology, which states "
>
> To further clarify the [
> [RFC5209](https://tools.ietf.org/html/rfc5209)
> ] definition, an endpoint is any
>
>       physical or virtual device that may have a network address.  Note
>
>       that, network infrastructure devices (e.g. switches, routers,
>
>       firewalls), which fit the definition, are also considered to be
>
>       endpoints within this document."
>
>
>
> This text squares with my original view of endpoints way back when we were working on the original SACM charter.
>
>
>
> Regards,
>
> Dave
>
> From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Panos Kampanakis (pkampana)
> Sent: Thursday, September 07, 2017 2:11 PM
> To: Xialiang (Frank) <frank.xialiang@huawei.com>; sacm@ietf.org
> Cc: Linqiushi (Jessica, SCC) <linqiushi@huawei.com>; Zhengguangying (Walker) <zhengguangying@huawei.com>; dongyue (D) <dongyue6@huawei.com>
> Subject: Re: [sacm] new drafts about network infrastructure device's security baseline:
>
> When checking the SACM charter, I do not see any references to network infrastructure or network elements. I believe SACM’s initial focus was on endpoints. Do these three drafts even fall in SACM’s charter as it is right now?
>
> Panos
>
> From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Xialiang (Frank)
> Sent: Thursday, September 07, 2017 4:05 AM
> To: sacm@ietf.org
> Cc: Linqiushi (Jessica, SCC) <linqiushi@huawei.com>; Zhengguangying (Walker) <zhengguangying@huawei.com>; dongyue (D) <dongyue6@huawei.com>
> Subject: [sacm] new drafts about network infrastructure device's security baseline:
>
> Hi all,
>
> We just submit 3 drafts to specify the yang data model of network infrastructure devices (i.e., router, switch, firewall, etc) security posture, or call it security baseline. Each draft covers one of the three planes of network infrastructure devices: data plane, control plane, management plane.
>
> https://tools.ietf.org/html/draft-xia-sacm-nid-dp-security-baseline-00
>
> https://tools.ietf.org/html/draft-dong-sacm-nid-cp-security-baseline-00
>
> https://tools.ietf.org/html/draft-lin-sacm-nid-mp-security-baseline-00
>
> The goal is to facilitate the collection and assessment of the overall security posture of the network infrastructure devices, in order to realize the whole lifecycle security automation for the infrastructure network.
>
> Your comments are warmly welcome!
>
> B.R.
>
> Frank