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

"Xialiang (Frank)" <frank.xialiang@huawei.com> Tue, 12 September 2017 02:01 UTC

Return-Path: <frank.xialiang@huawei.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 59C3A13292E for <sacm@ietfa.amsl.com>; Mon, 11 Sep 2017 19:01:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 U9tvmh37XV60 for <sacm@ietfa.amsl.com>; Mon, 11 Sep 2017 19:01:34 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD7C9132811 for <sacm@ietf.org>; Mon, 11 Sep 2017 19:01:33 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DVG28631; Tue, 12 Sep 2017 02:01:31 +0000 (GMT)
Received: from DGGEML401-HUB.china.huawei.com (10.3.17.32) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.301.0; Tue, 12 Sep 2017 03:01:30 +0100
Received: from DGGEML502-MBX.china.huawei.com ([169.254.2.131]) by DGGEML401-HUB.china.huawei.com ([fe80::89ed:853e:30a9:2a79%31]) with mapi id 14.03.0301.000; Tue, 12 Sep 2017 10:01:17 +0800
From: "Xialiang (Frank)" <frank.xialiang@huawei.com>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com>
CC: "Waltermire, David A. (Fed)" <david.waltermire@nist.gov>, "Panos Kampanakis (pkampana)" <pkampana@cisco.com>, "sacm@ietf.org" <sacm@ietf.org>, "Linqiushi (Jessica, SCC)" <linqiushi@huawei.com>, "Zhengguangying (Walker)" <zhengguangying@huawei.com>, "dongyue (D)" <dongyue6@huawei.com>
Thread-Topic: [sacm] 答复: new drafts about network infrastructure device's security baseline:
Thread-Index: AQHTKxOPIpC2d8zuEUuNsENU3bksoKKvrOEAgADBQhA=
Date: Tue, 12 Sep 2017 02:01:18 +0000
Message-ID: <C02846B1344F344EB4FAA6FA7AF481F12BB6F46A@DGGEML502-MBX.china.huawei.com>
References: <808ED0DE-508A-47FA-A9F0-CD60CF586A79@cisco.com> <CAHbuEH4a5RKYED9N0Q=v3-gUOd0QnFgqnLNg-dKJpfArDQW0zQ@mail.gmail.com>
In-Reply-To: <CAHbuEH4a5RKYED9N0Q=v3-gUOd0QnFgqnLNg-dKJpfArDQW0zQ@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.134.159.76]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020205.59B73FFC.0014, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.2.131, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 519db8ff5d8c2450a37897dc25e074a1
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/JWu0xivxhT8Ae91ktX__RZeQ-sM>
Subject: [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 02:01:37 -0000

Hi Nancy, Kathleen,
Your point make sense. Let me explain our intention as below:
1. Our objective is to specify the security posture (we call it security baseline in the documents) of network devices, like router, switch or maybe FW. By collecting and evaluating them, to meet the SACM requirements on network device as endpoint. We only focus on the security baseline information;
2. Current -00 version of drafts do not have the contents about: how to encapsulate the security baseline information into SACM Information Model, how to send them to the collector by YANG push and pub/sub mechanisms, and how to adapt these information into SACM protocol, we will address these issues in following updated versions;
3. we do find that some YANG model has been defined in IETF WGs like netmod, i2rs, i2nsf, etc. But we also observe that: there are still some YANG model related with device security baseline are not defined yet (i.e., URPF, CPU defend, Keychain, Remote Login Security, etc); Even some YANG model (i.e., BGP, OSPF, SNMP, etc) has been defined in IETF, their security configuration and status part are not completed and have potential room for improvement. If we find the existing contents as you pointed, we'd like to reference them and will not reinvent the wheel.

In summary, we want to follow the SACM Information Model and protocol, and extend the YANG push and pub/sub mechanisms to systematically specify the security baseline data model in SACM WG.

B.R.
Frank

-----邮件原件-----
发件人: Kathleen Moriarty [mailto:kathleen.moriarty.ietf@gmail.com] 
发送时间: 2017年9月12日 5:26
收件人: Nancy Cam-Winget (ncamwing)
抄送: Xialiang (Frank); Waltermire, David A. (Fed); Panos Kampanakis (pkampana); sacm@ietf.org; Linqiushi (Jessica, SCC); Zhengguangying (Walker); dongyue (D)
主题: Re: [sacm] 答复: new drafts about network infrastructure device's security baseline:

On Mon, Sep 11, 2017 at 11:35 AM, 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.

Yes, I agree with Nancy.  If the work exists already, it should be referenced.  YANG is the preferred method and there appears to be direct copy and paste from IPFIX and other technologies.

Best regards,
Kathleen
>
>
>
> 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] 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-0
> 0
>
>
>
> 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
>
>
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm
>



-- 

Best regards,
Kathleen