Subject: [sacm] FW: New Version Notification for draft-waltermire-sacm-use-cases-03.txt

From: "Waltermire, David A." <[email-masked]>
Date: Fri, 18 Jan 2013 23:18:30 -0500

I just posted an update of the use cases document (link below).

Changes in this version include:

·         Revised abstract

·         Removed sections (functional components, data exchange models and communication protocols) as these are more appropriate in the architecture document.

·         Keep use cases 2 and 3, but added a note that they are currently out-of-scope.

·         Updated UC1 to reflect current list conversations.

·         Revised UC1 capabilities sections to capture requirements from list discussions.

·         Fixed various typos and spelling errors.

·         Updated references to RFCs and IDs to reflect current revisions.

If anyone has any concerns or comments on these edits, please post them to the list.

Sincerely,

Dave

-----Original Message-----
From: [email-masked] [mailto:[email-masked]]
Sent: Friday, January 18, 2013 11:05 PM
To: Waltermire, David A.
Cc: [email-masked]
Subject: New Version Notification for draft-waltermire-sacm-use-cases-03.txt

A new version of I-D, draft-waltermire-sacm-use-cases-03.txt

has been successfully submitted by David Waltermire and posted to the IETF repository.

Filename:            draft-waltermire-sacm-use-cases

Revision:              03

Title:                      Analysis of Security Automation and Continuous Monitoring (SACM) Use Cases

Creation date:   2013-01-19

WG ID:                  Individual Submission

Number of pages: 17

URL:             http://www.ietf.org/internet-drafts/draft-waltermire-sacm-use-cases-03.txt

Status:          http://datatracker.ietf.org/doc/draft-waltermire-sacm-use-cases

Htmlized:        http://tools.ietf.org/html/draft-waltermire-sacm-use-cases-03

Diff:            http://www.ietf.org/rfcdiff?url2=draft-waltermire-sacm-use-cases-03

Abstract:

   This document identifies foundational use cases, derived functional

   capabilities, and requirements needed to provide a foundation for

   creating interoperable automation tools and continuous monitoring

   solutions that provide visibility into the state of assets, user

   activities, and network behavior.  Stakeholders will be able to use

   these tools to aggregate and analyze relevant security and

   operational data to understand the organizations security posture,

   quantify business risk, and make informed decisions that support

   organizational objectives while protecting critical information.

   Organizations will be able to use these tools to augment and automate

   information sharing activities to collaborate with partners to

   identify and mitigate threats.  Other automation tools will be able

   to integrate with these capabilities to enforce policies based on

   human decisions to harden systems, prevent misuse and reduce the

   overall attack surface.

The IETF Secretariat