RFC 8248 on Security Automation and Continuous Monitoring (SACM) Requirements
rfc-editor@rfc-editor.org Thu, 21 September 2017 23:36 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07B8A133342; Thu, 21 Sep 2017 16:36:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 OkTkEAubcoT7; Thu, 21 Sep 2017 16:36:43 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9FA61341F8; Thu, 21 Sep 2017 16:36:30 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B244DB817AD; Thu, 21 Sep 2017 16:36:09 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8248 on Security Automation and Continuous Monitoring (SACM) Requirements
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, sacm@ietf.org
Message-Id: <20170921233609.B244DB817AD@rfc-editor.org>
Date: Thu, 21 Sep 2017 16:36:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/8myVmSPV5rvBENHgCY25hu3TM6I>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 23:36:54 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8248
Title: Security Automation and Continuous Monitoring
(SACM) Requirements
Author: N. Cam-Winget,
L. Lorenzin
Status: Informational
Stream: IETF
Date: September 2017
Mailbox: ncamwing@cisco.com,
llorenzin-ietf@1000plus.com
Pages: 20
Characters: 47698
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-sacm-requirements-18.txt
URL: https://www.rfc-editor.org/info/rfc8248
DOI: 10.17487/RFC8248
This document defines the scope and set of requirements for the
Security Automation and Continuous Monitoring (SACM) architecture,
data model, and transfer protocols. The requirements and scope are
based on the agreed-upon use cases described in RFC 7632.
This document is a product of the Security Automation and Continuous Monitoring Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC