Security Automation and Continuous Monitoring (SACM) Architecture
draft-mandm-sacm-architecture-01
| Document | Type | Replaced Internet-Draft (sacm WG) | |
|---|---|---|---|
| Last updated | 2018-08-14 (latest revision 2018-03-28) | ||
| Replaced by | draft-ietf-sacm-arch | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-sacm-arch | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-mandm-sacm-architecture-01.txt
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
Adam Montville
(adam.w.montville@gmail.com)
Bill Munyan
(bill.munyan.ietf@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)