Security Automation and Continuous Monitoring (SACM) Architecture
draft-mandm-sacm-architecture-01
| Document | Type |
Replaced Internet-Draft
(sacm WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Adam W. Montville , Bill Munyan | ||
| Last updated | 2018-08-14 (Latest revision 2018-03-28) | ||
| Replaced by | draft-ietf-sacm-arch | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-sacm-arch | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This memo documents an exploration of a possible Security Automation and Continuous Monitoring (SACM) architecture. This work is built upon [I-D.ietf-mile-xmpp-grid], and is predicated upon information gleaned from SACM Use Cases and Requirements ([RFC7632] and [RFC8248] respectively), and terminology as found in [I-D.ietf-sacm-terminology].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)