[sacm] Request for a SACM BOF at IETF-86

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 23 January 2013 15:35 UTC

Return-Path: <dromasca@avaya.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 D1F9721F86DE for <sacm@ietfa.amsl.com>; Wed, 23 Jan 2013 07:35:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.432
X-Spam-Level:
X-Spam-Status: No, score=-103.432 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y12MKlNKh07B for <sacm@ietfa.amsl.com>; Wed, 23 Jan 2013 07:35:22 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 0AA5C21F8739 for <sacm@ietf.org>; Wed, 23 Jan 2013 07:35:13 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAIbQt1DGmAcF/2dsb2JhbABEgX9tgz+4ZnQWc4IgAQEDAQEBDxEROgYFEgEVBQgCBgIeAgQlCxUCDwEEDgUIARIHh24BC6F7iiqSYoEiizmDEzJhA5cdhHGKN4JygWw1
X-IronPort-AV: E=Sophos;i="4.84,186,1355115600"; d="scan'208";a="385674506"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 23 Jan 2013 10:25:14 -0500
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by co300216-co-erhwest-out.avaya.com with ESMTP; 23 Jan 2013 10:29:49 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.02.0318.004; Wed, 23 Jan 2013 10:35:13 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Sean Turner <turners@ieca.com>
Thread-Topic: Request for a SACM BOF at IETF-86
Thread-Index: Ac35fzuXxqrjpoecRem+k4kRabEaVA==
Date: Wed, 23 Jan 2013 15:35:12 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA069439@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "sacm@ietf.org" <sacm@ietf.org>
Subject: [sacm] Request for a SACM BOF at IETF-86
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion List for IETFers interested in the Security Content Automation Protocol \(SCAP\)." <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jan 2013 15:35:27 -0000

Hi Sean,

Please accept our request for a second, WG-forming SACM BOF at IETF-86, as follows: 

•Description: Securing information and the systems that store, process, and transmit that information has become a challenging task for organizations of all sizes, and we find that security practitioners spend most of their time on manual processes relegating them to ineffectiveness. Security automation to verify system configurations with the ability to prioritize risk based on increased situational awareness from shared intelligence is the key to escaping this rut. This working group will develop security automation protocols and data format standards in support of information security processes and practices where practical. These standards will help security practitioners to be better utilized within their organizations by automating routine tasks related to client and server security so that practitioners can focus on more advanced tasks. The initial focus of this work is to address enterprise use cases pertaining to the assessment of endpoint posture (using the definitions of Endpoint and Posture from RFC 5209).

•Responsible AD: Sean Turner 

•BoF Chairs: Kathleen Moriarty & Dan Romascanu

•Number of people expected to attend: 80 

•Length of session; 90 mins 

•Conflicts to avoid: SEC area WGs especially MILE, XRBLOCK, EMAN, OPSAWG 

•Does it require WebEX? No 

•Does it require Meetecho? Yes 

•Mailing list: ​sacm@ietf.org 

•List archive: ​https://www.ietf.org/mailman/listinfo/sacm 

•Draft charter: ​

Name: Security Automation and Continuous Monitoring (SACM)
AREA: Security

Chairs:
TBD
TBD

Security Area Directors:
     Stephen Farrell <stephen.farrell at cs.tcd.ie>
     Sean Turner <turners at ieca.com>

Security Area Advisor:
     Sean Turner <turners at ieca.com>

Mailing Lists:
     General Discussion: sacm at ietf.org
     To Subscribe:       http://www.ietf.org/mailman/listinfo/sacm
     Archive:            http://www.ietf.org/mail-archive/web/sacm

Description of Working Group

Securing information and the systems that store, process, and transmit that information has become a challenging task for organizations of all sizes, and we find that security practitioners spend most of their time on manual processes relegating them to ineffectiveness. Security automation to verify system configurations with the ability to prioritize risk based on increased situational awareness from shared intelligence is the key to escaping this rut. This working group will develop security automation protocols and data format standards in support of information security processes and practices where practical. These standards will help security practitioners to be better utilized within their organizations by automating routine tasks related to client and server security so that practitioners can focus on more advanced tasks. The initial focus of this work is to address enterprise use cases pertaining to the assessment of endpoint posture (using the definitions of Endpoint and Posture from RFC 5209).

The working group will achieve this by enabling the exchange of shared intelligence regarding endpoint posture and continuing the security automation work already performed by various organizations around the world. The initial work has been fruitful, and the data formats previously published are ready for expansion on the international stage. Of particular interest to this working group are the security automation specifications supporting asset, change, configuration, and vulnerability management.

By undertaking this work, we recognize that there are multiple categories of problems in the security automation domain: enabling interoperable data exchanges through standardized protocols, defining expressions for particular domain concepts (i.e. data formats), establishing a standards-based foundation supporting the curation and exchange of security automation content collections in content repositories, and enabling interoperability through the development and use of standard interfaces and communications protocols. Content based on rich data standards and protocols will provide the authoritative instructions needed by data-driven tools to enable the automated collection and exchange of configuration and vulnerability data pertaining to enterprise assets. Information produced by these tools will provide accurate and timely situational awareness in support of organizational decision making.

The data exchange protocols will need to meet several exchange types including requesting assessments and reporting on assessment results.
Exchanging information across organizational boundaries will not be within scope for this effort at this time.

This working group will provide solutions to these categories of problems and the main areas of focus for this working group are described as follows:

1. Define, either by normative reference, adoption, or creation, a set of standards to enable assessment of endpoint posture. This area of focus provides for necessary language and data format specifications.

2. Define, either by normative reference, adoption, or creation, a set of standards for interacting with repositories of content related to assessment of endpoint posture.

This working group will achieve the following milestones:

- An Informational document on Use Cases and Requirements
- An Informational document on SACM Architecture
- A Standards Track document to define a protocol for interacting
  with content repositories
- Standards Track documents specifying communication protocols and
  data formats used for assessment of endpoint posture

After this work is completed, complementary deliverables may be defined.
 

•Internet-Drafts:
https://datatracker.ietf.org/doc/draft-waltermire-sacm-use-cases/
https://datatracker.ietf.org/doc/draft-booth-sacm-vuln-model/
https://datatracker.ietf.org/doc/draft-davidson-sacm-asr/
https://datatracker.ietf.org/doc/draft-hanna-sacm-assessment-protocols/
https://datatracker.ietf.org/doc/draft-montville-sacm-asset-identification/