Re: [T2TRG] New Version Notification for draft-irtf-t2trg-iot-seccons-02.txt

[Eliot Lear <[e-mail]>]

Hi Oscar,

First of all, I realized I was reading the old version of the draft.  My
apologies.  This having been said, I would suggest the following:

  * In discussing bootstrapping in Section 7.2, assuredly we should talk
    about the work going on in the ANIMA working group
    (draft-ietf-anima-bootstrapping-keyinfra).  Not all devices are so
    constrained as to be unable to use the established PKI, and indeed
    the cost of doing so for onboarding is dropping by the day.
  * Consider refocusing Section 7.11 on the role of firewalls, access
    points, and access switches in protecting IoT (really all) devices. 
    I would resituate it or directly next to E2E security, and then
    discuss the relative merits and risks.  If it is possible to do so,
    match the flow you have built in Section 3.2 (the numbered points)
    in later sections.
  * In Section 4, you've done an excellent job of discussing threat
    vectors.  Without being hyperbolic about it (and this might be
    hard), it might be good to remind people of some consequences of
    penetration.  Broadly speaking I see this as enabling of direct
    attacks (e.g., causing the device to fail to correctly perform its
    function), or indirect attacks (making use of the device to attack
    other devices).  These are obviously not mutually exclusive.
  * I would move the attack discussion in 7.11 into Section 4, and I
    would move Section 4 above Section 3, the logic here being to first
    have the threat discussion, and then discuss how they are remediated.
  * Bullet point 6 on extraction of private information is important to
    include.  However, I would suggest NOT making generalizations as to
    how well a device protects private data.  It is sufficient to say
    that when a device does not go to some pains to protect that data,
    if the device is physically unprotected, so then is the data.

Hope this helps...

Eliot
On 4/6/17 9:28 AM, Garcia-Morchon O, Oscar wrote:
> Hi Eliot,
>
> It is a very good point. Thanks.
>
> IoT involves very different aspects that we try to reflect in the document. One of them is indeed network security with the goal to protect devices from attack but also the network from compromised devices.
>
> In the document, we refer to your ongoing work on MUD. Which other type of methods do you have in mind or do you think that should be included in the document?
>
> Regards, Oscar.
>
> -----Original Message-----
> From: Eliot Lear [mailto:[e-mail]] 
> Sent: Tuesday, April 4, 2017 12:32 PM
> To: Garcia-Morchon O, Oscar <[e-mail]>; [e-mail]; [e-mail]
> Cc: Mohit Sethi <[e-mail]>; Kumar, Sandeep <[e-mail]>
> Subject: Re: [T2TRG] New Version Notification for draft-irtf-t2trg-iot-seccons-02.txt
>
> Hi Oscar,
>
> While I appreciate the draft, there is an elephant in the room.  Not a day passes when we hear of yet another compromise of a so-called "IoT"
> system.  Sometimes these compromises are trivial, and sometimes they are involved.  At the end of the day, the sheer quantity of Things mandates some form of network-level protection that the draft should discuss, to protect those devices from attack.  As was mentioned in the f2f, what if Bob turns out to be, or becomes evil, or is otherwise 0wn3d by Chuck?
>
> Eliot
>
>
> On 4/3/17 9:10 AM, Garcia-Morchon O, Oscar wrote:
>> Hi,
>>
>> we have submitted a new version of the Internet Draft on security considerations for the IoT.
>> Comments are welcome.
>>
>> https://tools.ietf.org/html/draft-irtf-t2trg-iot-seccons-02
>>
>> Regards, Oscar.
>>
>> -----Original Message-----
>> From: [e-mail] [mailto:[e-mail]]
>> Sent: Friday, March 31, 2017 2:11 PM
>> To: Mohit Sethi <[e-mail]>; Kumar, Sandeep 
>> <[e-mail]>; Kumar, Sandeep 
>> <[e-mail]>; Garcia-Morchon O, Oscar 
>> <[e-mail]>; [e-mail]; 
>> [e-mail]
>> Subject: New Version Notification for 
>> draft-irtf-t2trg-iot-seccons-02.txt
>>
>>
>> A new version of I-D, draft-irtf-t2trg-iot-seccons-02.txt
>> has been successfully submitted by Oscar Garcia-Morchon and posted to the IETF repository.
>>
>> Name:draft-irtf-t2trg-iot-seccons
>> Revision:02
>> Title:State of the Art and Challenges for the Internet of Things 
>> Document date:2017-03-31 Group:t2trg
>> Pages:56
>> URL:            https://www.ietf.org/internet-drafts/draft-irtf-t2trg-iot-seccons-02.txt
>> Status:         https://datatracker.ietf.org/doc/draft-irtf-t2trg-iot-seccons/
>> Htmlized:       https://tools.ietf.org/html/draft-irtf-t2trg-iot-seccons-02
>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-irtf-t2trg-iot-seccons-02
>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-irtf-t2trg-iot-seccons-02
>>
>> Abstract:
>>    The Internet of Things concept refers to the usage of standard
>>    Internet protocols to allow for human-to-thing or thing-to-thing
>>    communication.  The security needs are well-recognized and and many
>>    standardization steps have been taken, for example, specification of
>>    CoAP over DTLS.  However, security challenges still exist and there
>>    are some use cases that lack a suitable solution.  This document
>>    first provides an overview of security architecture, its deployment
>>    model, security needs in the context of the lifecycle of a thing, as
>>    well as the state of the art on IoT security.  Then, we discuss the
>>    concept of security profiles for the successful roll-out of secure
>>    IoT applications and describe remaining security challenges in the
>>    IoT.
>>
>>
>>
>>
>> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
>>
>> The IETF Secretariat
>>
>>
>> ________________________________
>> The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.
>> _______________________________________________
>> T2TRG mailing list
>> [e-mail]
>> https://www.irtf.org/mailman/listinfo/t2trg
>>
>
>