Re: [Panic] notes on Panic Draft

Guy Fedorkow <> Thu, 27 July 2017 15:01 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 65A9913225E for <>; Thu, 27 Jul 2017 08:01:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.02
X-Spam-Status: No, score=-2.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ZS6uvImlRFor for <>; Thu, 27 Jul 2017 08:01:11 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8F49F132253 for <>; Thu, 27 Jul 2017 08:01:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=AvwXMGZRm415qjaBFAZansypZ5Yj+T/LiA+C+an4jqs=; b=cw7jbKZ0Xvf4keMOg+9AUUKCMxiKNXtd4v+J8D1EJXFYTrUb3Z2z+6wdTzHCquYoysEPSuilfHduJxDbvZdvdl+xF3GGPClCe5VSttEeaBv2fpOnyPPqrsM+3EPW8zUgArqLXAhpDgvrW+pkZfxJQfDGksOa8dWIeFRgwrjmbUU=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1304.10; Thu, 27 Jul 2017 15:01:08 +0000
Received: from ([]) by ([]) with mapi id 15.01.1304.016; Thu, 27 Jul 2017 15:01:08 +0000
From: Guy Fedorkow <>
To: Jessica Fitzgerald-McKay <>
CC: "" <>
Thread-Topic: [Panic] notes on Panic Draft
Thread-Index: AdMCY8IYY6zBEz8yT9uERQZ0qXAFnQD26z4AACnFMzA=
Date: Thu, 27 Jul 2017 15:01:08 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN1PR05MB375; 7:FyPTMk2+7pzkQsFh4OBKsjwT7ZkkpM8U0qWWXz4u9BZitwo6r5tJJuCCtwDnWWjdCSVnnLEUKnNjlVWD9Yd86+ERsOBfKxmOThVqcruCqLeqHYhsfzohWwaxFXvzOhtTtDuIQhbdubqiX1KrM6tlUbqTpsPS+t+0iCX0io4dzYGwpaYtYDANwyNZd/zf7vRkC5Eq7USEyga+Zdajl+YMQFVSWABktzSdsl3wiKkZNGuJGnBY8m43QG/22HXeMysbAd1dogsCU2GTMnU8CymSNjlEudh05oF0jG8FOIOyzlkDxuPM1MgY9kgizda9+K4OO9l5GJ2L7sltCkGdoIwysx1MKKLmIXc7QKQYJiMZKvnT9ibOB7y66dCPkD77UjzUPtGdIzA8pHmi0IDUnL42vY6u2xrhSFZVq18FgDHb2S1W4LVN8kGWXNPPlIpPPjsm/v6rlzgjHo37WTiF3WOu+hQpZTEAbuZrXcW29GKtn9WnFWZsnMoMyBjcLvz+7686bo0mnsilXLxq64Tc7TjLxKdGb9l4RqpuQBJcBj25U9LqOHJRZSrPzkjf4ZMkCgNxHF7RY1uWuz+npeEMCOceUPWFQp18TQvWFncS+9UV4fDJjs/RaHdSHDwyPKn79JUL8L/E8r/Sdy1RjZtOxz7IPHetOfchD0CmmM4yUyrD32lFVAfsUa7/kMvCfftPp1UtePkYyJBqBdTEaZYZYO2r9m0QMjvtA+wRYlowOWj6DbSunWzMXxBP7+HcXA08/fcKH3NisW/MUID5femRkyvKtRnyEbmFQEfQ7JqyIjzC/gc=
x-ms-office365-filtering-correlation-id: daf91a1f-0f6d-4357-6f6d-08d4d5005042
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254109)(48565401081)(300000503095)(300135400095)(2017052603031)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:BN1PR05MB375;
x-ms-traffictypediagnostic: BN1PR05MB375:
x-exchange-antispam-report-test: UriScan:(158342451672863)(65766998875637)(72170088055959)(192374486261705)(271806183753584)(138986009662008)(155532106045638)(21748063052155)(68840517438536);
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(10201501046)(100000703101)(100105400095)(3002001)(93006095)(93001095)(920511095)(6055026)(6041248)(20161123558100)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(20161123564025)(20161123560025)(20161123562025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BN1PR05MB375; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BN1PR05MB375;
x-forefront-prvs: 03818C953D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39450400003)(39840400002)(39860400002)(39850400002)(39400400002)(39410400002)(24454002)(51914003)(54094003)(377454003)(189002)(40224003)(199003)(6506006)(53546010)(966005)(9326002)(33656002)(8676002)(236005)(106356001)(6306002)(53936002)(99286003)(19609705001)(189998001)(9686003)(54896002)(25786009)(4326008)(5660300001)(6436002)(3846002)(110136004)(81166006)(790700001)(6116002)(7736002)(55016002)(81156014)(68736007)(3280700002)(38730400002)(2906002)(39060400002)(6246003)(102836003)(478600001)(97736004)(3660700001)(606006)(8936002)(14454004)(2950100002)(6916009)(105586002)(229853002)(76176999)(7696004)(1411001)(77096006)(66066001)(74316002)(50986999)(54356999)(2900100001)(101416001)(86362001)(15398625002)(17260700006); DIR:OUT; SFP:1102; SCL:1; SRVR:BN1PR05MB375;; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None ( does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BN1PR05MB3095A1DCA75B28E45C84F6DBABE0BN1PR05MB309namprd_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Jul 2017 15:01:08.8080 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN1PR05MB375
Archived-At: <>
Subject: Re: [Panic] notes on Panic Draft
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Posture Assessment Through Network Information Collection \(panic\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 27 Jul 2017 15:01:15 -0000

Hi Jessica,
  You asked about 802.1AR and IDevID.
  I’m sure it’s too early to make 802.1AR IDevID a “must”…  the idea is simple enough, but as you say, the workflow is not.  But I do think we should consider how it would fit.
  I think the simplest way to take advantage of a DevID might simply be to use it to authenticate a TLS session to the device, and use that session to carry the rest of the management protocol.
  You asked about the workflow for installing DevID

-          I think the ‘initial’ IDevID has to be installed by the device manufacturer.   There are various plans, depending on privacy concerns, but I think they all depend on the authority of the manufacturer to certify their own devices.

-          The ‘local’ LDevID can use the manufacturer’s IDevID as a trust anchor, but doesn’t have to.  Anyone can make an LDevID with whatever rules they think are appropriate.
  The workflow that could be used for creating DevIDs for TPM1.2 is described in a TCG doc Subject Key Attestation Evidence, and the version for TPM2.0 is under consideration now at TCG.

  As to Things…  I know about relatively large Things, and those obviously run all these protocols.  But we will have to seek new experts to help us see what Small Things can do.


From: Jessica Fitzgerald-McKay []
Sent: Wednesday, July 26, 2017 2:46 PM
To: Guy Fedorkow <>;
Subject: Re: [Panic] notes on Panic Draft

Thanks for the feedback, Guy. Responses in-line. I have more questions than answers, and I'd like others on the list to weigh in. Looking forward to hearing from everyone.

On Fri, Jul 21, 2017 at 5:18 PM, Guy Fedorkow <<>> wrote:

Hi Dave, Jessica,
  Thanks for updating the PANIC draft…  I think it’s starting to take shape!

  It seems that the next step in moving this forward might be to outline the kind of information we want to retrieve from the endpoints.  I’d assume you’d want some kind of info to identify the device – manufacturer, serial number, etc, plus something that shows the software revision of the relevant modules.  Could that be something like a set of SWID tags?

​Personally, I would be delighted if software load could be captured in a SWID tag. Failing that, I would like to be able to collect a swid-like set of information from​ the network device. I took a look at NISTIR 8060 (which you can read here: and it looks like-- ignoring data about the tag itself, like tagID, entity information about the tag creator, etc--  required fields for a primary tag are:

  *   software name and
  *   software version,
which should be easy enough to collect on their own.

But, SWID tags offer additional information that could be useful to us. Evidence and payload fields, for instance, can be used to communicate file hashes that comprise the software. Tag signatures could allow us to have move trust in the entity that created the tag (for example, a tag from the software vendor is potentially more trust worthy than one created by a third party). And SWIDs allow us to easily communicate what patches are installed on the product, which is necessary for vulnerability and compliance assessments.

All things considered, I'd like to use SWID tags. I would like a sense of how widely implemented they are for network device software and operating systems. Anyone have any insight there?

  It might be good to pattern the device information on IEEE 802.1AR.  Using a cryptographic ID might not be a ‘must’, but it’s probably a desirable option, so making sure it would fit might be helpful.

802.1ar requires installation ​
​of an IDevID, from which many LDevIDs can be created. I'm happy to geek out on the added security of cryptographic IDs, but, can we talk though the workflow of getting the initial IDevID installed (who would be responsible for that? Do network equipment vendors use IDevIDs today? If not, could the device owner install one without a lot of hassle?)​.

Also, secure though 802.1ar is, it often has no relation to any observable device identities on the network. I'm thinking about a behavior monitoring use case here, in which I notice a device behaving in an unexpected manner, and want to investigate it's posture while I figure out what is going on. Is there a way to gather many identities from an network device using netconf/yang?

  It might be good to add a note saying whether the draft should extend to virtualized devices, e.g., NFV instances.  I’d assume that it should, but that might make identity a bit more complicated.

​In section 3 of the draft, we say "​Virtualized network functions are currently considered in scope". Of course, I worded it that way because I, too, am concerned about whether their inclusion makes our solution overly complicated. Are there any netconf experts that can speak to this concern?

  On the topic of scope, I suppose it might be good to say if “Things”, as in IoT, are in scope or not.  I can’t guess if that has an impact on the technical spec, but there certainly could be an impact on implied scaling needs, and it might help remind readers that figuring out what’s running in the IoT is a getting to be a big problem.

​Agreed that IoT is a problem. Do many "Things" that compose the Internet of Things implement netconf?​ It's such a broad space, I worry that some "Things" could handle netconf, and others (things like "smart dust", etc.) couldn't handle the added weight.

  The diagram in the front of the draft shows an interconnect between Posture Server and Data Store…  seems like there could be some complicated transactions across that link…  Do you think there’s existing practice that could be used for this?

​Sadly, I know of nothing we could easily point to and say "that is the protocol we will use for server-datastore communication". But, what I do not know could fill volumes. Maybe others have ideas where we can start?
  The draft also mentions methods that Endpoints can use to find Posture servers.  I wonder if Zeroconf or some kind of DHCP trick might work for this?

​Zeroconf is an option. TCG has some prior art here ( I am happy to consider all viable options.​

  Finally, in Security Considerations, I wonder if there should be something about how much we do or don’t trust the endpoint to report its Information truthfully. The combination of 802.1AR and signed SWID tags might help with a way to assess the reliability of the information.

​Agreed, I will add that to the next revision. ​

  Great start, let’s try to start breaking down some of the top-level topics to get to the next level of requirements.

Panic mailing list<>