Re: [Smart] Draft Charter For SMART Proposed RG

Bret Jordan <jordan.ietf@gmail.com> Fri, 28 September 2018 22:25 UTC

Return-Path: <jordan.ietf@gmail.com>
X-Original-To: smart@ietfa.amsl.com
Delivered-To: smart@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB7AD130EC0 for <smart@ietfa.amsl.com>; Fri, 28 Sep 2018 15:25:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.01
X-Spam-Level:
X-Spam-Status: No, score=-0.01 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, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 XwBkpWR3eOFA for <smart@ietfa.amsl.com>; Fri, 28 Sep 2018 15:25:09 -0700 (PDT)
Received: from mail-yb1-xb2e.google.com (mail-yb1-xb2e.google.com [IPv6:2607:f8b0:4864:20::b2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05EDD130EE5 for <smart@irtf.org>; Fri, 28 Sep 2018 15:25:09 -0700 (PDT)
Received: by mail-yb1-xb2e.google.com with SMTP id w80-v6so3312588ybe.10 for <smart@irtf.org>; Fri, 28 Sep 2018 15:25:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=a77lIji11Qug1fU6slDkKmJMHZF9ggRq6OjOAERfgUQ=; b=HwEpnNhKFqjYqJxEImpMmNBzmNzf5jZvlNbcTQd5BEb90vGCXB8S6p6j3BBqGUMtkQ rPVZSEVgit2tJIW7asCgw+BNohVJWKHi/igXpsGTjT+YM1+b1w1+9ePyDqs7uzj7Ab8k l4wtFHH7Asoxg6FdLlq/AYdx7YncqLwm4szEQ+37bFBBMO6a3HqUcd6bzu0cD7b14oo/ 9pMLvAk82RKQzjh7w0O7hL4+86ji1zzhSVCDYEi1eXkkcWzfkCpPpeh4cSUtf05ih852 pEf8ZZIg9bY/TQdn/mY6BVWS07ZBhaWsvAZJziF78tOLPXbT5Muf+HLXPLPhKBMddOdn QJpQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=a77lIji11Qug1fU6slDkKmJMHZF9ggRq6OjOAERfgUQ=; b=IXIH2Ag3k9F3gmuPecvOYKjMTBgRmoMPfQjhKuRU4cugNUrELT98ih7fFildOTANFs NfvjOZPq5sZsk6Zi0grSSxRZI/YmmTSXvKpb5HGMUQa7hnZ/SeaTMD1tD9gqSNElhff/ pFIVHAVfCvF7yluI05O/Gp2s4YSN+pH81bXeAyV0FV1OXkzjhTu9dibKaLufdgTh8+Ts y+YiKk1bSmdWdqDZpaAca7/ciB7YV8giZ0blnJBcyihS5k+3teGOkJNr+zKeyfnwP4tB BijrbHsP4kD13S+YDtoBCSTqc3zYdXiOUWkcWd7u22MrGF8eSEVxtupW1F0y6EHqv+0/ 78SA==
X-Gm-Message-State: ABuFfoiqVzVLemJfd85WMtHxnuLId/YgOXdnNQKtpKdxR0P9TWkGHKXT QLD86MROCfQbKUFnO4G1WtPekwHi
X-Google-Smtp-Source: ACcGV60E6F1qkhWDIEPb1oU85MGOgEDZttgIghV3OtifxXH4iNmX0YlOAI4dVtGAfzNnF/GFzxHkiQ==
X-Received: by 2002:a25:483:: with SMTP id 125-v6mr402572ybe.280.1538173508269; Fri, 28 Sep 2018 15:25:08 -0700 (PDT)
Received: from ?IPv6:2605:a601:3260:266:5d7b:d07e:94bf:2baa? ([2605:a601:3260:266:5d7b:d07e:94bf:2baa]) by smtp.gmail.com with ESMTPSA id j202-v6sm2098656ywb.69.2018.09.28.15.25.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Sep 2018 15:25:07 -0700 (PDT)
From: Bret Jordan <jordan.ietf@gmail.com>
Message-Id: <2F1B2EF1-C107-49F5-B6B9-853FF44AC740@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_62F9AB5E-DE03-40F6-9EAF-66F07422356B"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Fri, 28 Sep 2018 16:24:14 -0600
In-Reply-To: <MMXP123MB0847FC36BF3080A4939B7E19D7EC0@MMXP123MB0847.GBRP123.PROD.OUTLOOK.COM>
Cc: "smart@irtf.org" <smart@irtf.org>
To: Kirsty P <Kirsty.p@ncsc.gov.uk>
References: <MMXP123MB0847E55749751AA12D26DBFAD7150@MMXP123MB0847.GBRP123.PROD.OUTLOOK.COM> <B681C76A-CE1F-4C4B-8389-658A01D0E77E@gmail.com> <MMXP123MB0847039938CDA4581DC9AA65D7EC0@MMXP123MB0847.GBRP123.PROD.OUTLOOK.COM> <6B23EBEE-AD68-4FDE-87C1-4ECF1D9A08AF@gmail.com> <MMXP123MB0847FC36BF3080A4939B7E19D7EC0@MMXP123MB0847.GBRP123.PROD.OUTLOOK.COM>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/smart/r7G-TGVr_cVqUuyRaMH-XYRpJd0>
Subject: Re: [Smart] Draft Charter For SMART Proposed RG
X-BeenThere: smart@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Stopping Malware And Researching Threats <smart.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/smart>, <mailto:smart-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/smart/>
List-Post: <mailto:smart@irtf.org>
List-Help: <mailto:smart-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/smart>, <mailto:smart-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Sep 2018 22:25:21 -0000

Kristy,

I hope the work products from this research group can impact and influence many working groups, technical committees, and study groups across various SDOs. As we move forward I think we need to ensure the digestibility of the content we produce and ensure that we can have maximum impact across the entire eco-system. 

Thanks,
Bret
PGP Fingerprint: 63B4 FC53 680A 6B7D 1447  F2C0 74F8 ACAE 7415 0050
"Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg."

> On Sep 28, 2018, at 11:45 AM, Kirsty P <Kirsty.p@ncsc.gov.uk> wrote:
> 
> Bret,
> 
> Yes - we are! Kathleen and I are planning a initial meeting in Bangkok at IETF103 to discuss the draft charter and discuss initial problems that the group might research. This meeting won't be one of our three meetings that we are allocated as a Proposed RG - it's just for planning purposes. When we have a date and time for this meeting, I'll post on the list.
> 
> I thought it's just worth pointing out here that, though CACAO and SMART have very similar end goals (of protecting users and improving defence against attacks), I really hope that the output from this RG will benefit many other IETF working groups too - such as MILE, DOTS and SACM. In future, these WGs and CACAO might receive output from the research work in a similar way to how the CFRG assists other IETF groups - different work items, but with coordination between our efforts to do much more than we could do alone. We could discuss in Bangkok how best to do such a co-ordination.
> 
> Kirsty
> 
> 
> From: Bret Jordan <jordan.ietf@gmail.com <mailto:jordan.ietf@gmail.com>>
> Sent: 28 September 2018 16:16
> To: Kirsty P
> Cc: smart@irtf.org <mailto:smart@irtf.org>
> Subject: Re: [Smart] Draft Charter For SMART Proposed RG
>  
> Kristy, et al.,
> 
> Are we planning on a meet up in Bangkok?  This work along with the work in the CACAO project could really help protect end users and keep them safe. 
> 
> Bret 
> 
> Sent from my Commodore 128D
> 
> PGP Fingerprint: 63B4 FC53 680A 6B7D 1447  F2C0 74F8 ACAE 7415 0050
> 
> On Sep 28, 2018, at 7:24 AM, Kirsty P <Kirsty.p@ncsc.gov.uk <mailto:Kirsty.p@ncsc.gov.uk>> wrote:
> 
>> Bret,
>> 
>> Thanks for your encouraging words! If you have ideas for more topics that should be covered in the short-term, please feel free to share with the list.
>> 
>> Kirsty
>> 
>> From: Bret Jordan <jordan.ietf@gmail.com <mailto:jordan.ietf@gmail.com>>
>> Sent: 27 September 2018 22:59:04
>> To: Kirsty P
>> Cc: smart@irtf.org <mailto:smart@irtf.org>
>> Subject: Re: [Smart] Draft Charter For SMART Proposed RG
>>  
>> Kristy and RG ET al.,
>> 
>> I think this charter sounds great and covers most of the areas we need to address in the short-term.  Great work. The deliverables outlined so far will greatly assist the community for years to come.
>> 
>> Bret 
>> 
>> Sent from my Commodore 128D
>> 
>> PGP Fingerprint: 63B4 FC53 680A 6B7D 1447  F2C0 74F8 ACAE 7415 0050
>> 
>> On Sep 26, 2018, at 9:36 AM, Kirsty P <Kirsty.p=40ncsc.gov.uk@dmarc.ietf.org <mailto:Kirsty.p=40ncsc.gov.uk@dmarc.ietf.org>> wrote:
>> 
>>> This is the draft charter for the Proposed Research Group: Stopping Malware and Researching Threats (SMART).
>>> Your thoughts and suggestions are very welcome - please post to the list with your comments! - and keep an eye out for a list of proposed research problems soon...
>>> 
>>> 
>>> # Stopping Malware and Researching Threats (SMART) Proposed RG - Draft Charter
>>> 
>>> ## BACKGROUND
>>> The Stopping Malware and Researching Threats Research Group (or SMART RG) will investigate how cyber attack defence requirements can be met in a world of encrypted data. It will research the effects, both positive and negative, of existing, proposed and newly published protocols and Internet standards on attack defence. It will gather evidence from information security practitioners on methods used to defend against attacks and make this available to protocol designers. As a result, designers, implementers and users of new protocols will be better informed about the possible impact on attack prevention and mitigation.
>>> 
>>> The IRTF is in a unique position to provide this research and evidence to the IETF. This research group aims to describe the effect of protocol changes where relevant and stimulate methodical research into attack defence methods for new protocols. Protocols are already rigorously assessed for their security properties, but ensuring attack defence methods are also rigorously assessed alongside protocol design changes would provide a fuller understanding of the value for such change, enabling a better engineered Internet. 
>>> 
>>> 
>>> ## AIMS
>>> This research group has these major aims:
>>> To bring evidence on attacks and the methods that are or could be used to defend against them to the attention of the IETF.
>>> To highlight the attack mitigation impact, both positive and negative, of new protocols and updates to existing protocols. 
>>> To stimulate and generate research into attack defence methods for new protocols, and to increase awareness in the technical community of new and existing methodology for detecting and mitigating attacks. 
>>> To provide systematic guidance to designers of new protocols as to what attack defence considerations to review, and to inform implementers by default about the effects of new protocols on attack defence.
>>> To produce problem statements that describe key issues in cyber security for the group to research (initial research project ideas are listed below).
>>>  
>>> ## OUTPUTS
>>> The research group plans to create documents that may include, but are not limited to, the following:
>>> Internet drafts, some of which may be published through the IRTF RFC stream. These will include outline problem statements, use cases, case studies and convey research results. They will be written for use by other groups to inform protocol design. 
>>> Policy papers, for in-depth analysis and discussion of the relationship between attack defence and the Internet architecture and protocols.
>>> Research papers, containing quantitative evidence of actual attacks and the success of defence methods against them, as well as theoretical and formal analyses of the implications of proposed protocols on attack defence. Defence methods will be analyzed to determine if there are ways to optimize in order to better scale attack detection and mitigation.
>>> Survey of current and historic IETF material to discover existing deliberations on attack defence.
>>> Best practice papers, describing methodologies that will enable researchers to conduct experiments and report results that are useful to designers of protocols. These methodologies will give descriptions of the effects of protocols on attack defence backed by evidence from real-world attacks, laboratory-based testing and theoretical analysis of protocols, through the analysis lens of attacks, detection methods and systematic assessment methodologies.
>>> Within the first year, the research group aims to:
>>> Survey existing attack detection methods and determine the relative effectiveness of these methods against different attack defence threats (e.g. phishing, DDoS, spambots, C&C, endpoint malware)
>>> Publish case studies of historical attacks and make recommendations where attacks could have been stopped more quickly, or even prevented
>>> Publish an Informational RFC, titled: "Important Attack Defence Considerations for Protocol Design and Deployment".
>>> 
>>> ## MEMBERSHIP
>>> Membership is open to any interested parties who intend to remain current with the published documents and mailing list issues. Wide participation from industry, academia, government and non-profits is encouraged.
>>> 
>>> 
>>> 
>>> 
>>> This information is exempt under the Freedom of Information Act 2000 (FOIA) and may be exempt under other UK information legislation. Refer any FOIA queries toncscinfoleg@ncsc.gov.uk <mailto:ncscinfoleg@ncsc.gov.uk>-- 
>>> Smart mailing list
>>> Smart@irtf.org <mailto:Smart@irtf.org>
>>> https://www.irtf.org/mailman/listinfo/smart <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.irtf.org%2Fmailman%2Flistinfo%2Fsmart&data=02%7C01%7CKirsty.p%40ncsc.gov.uk%7C8f19ccb106cc4dcd7f8608d625557372%7C14aa5744ece1474ea2d734f46dda64a1%7C0%7C0%7C636737446273966857&sdata=%2B8RA4ZvcMz0nnNKCPR2ez%2BSQ02fc8ocWHMXkOSt0x58%3D&reserved=0>
>> This information is exempt under the Freedom of Information Act 2000 (FOIA) and may be exempt under other UK information legislation. Refer any FOIA queries toncscinfoleg@ncsc.gov.uk <mailto:ncscinfoleg@ncsc.gov.uk>This information is exempt under the Freedom of Information Act 2000 (FOIA) and may be exempt under other UK information legislation. Refer any FOIA queries to ncscinfoleg@ncsc.gov.uk <mailto:ncscinfoleg@ncsc.gov.uk>