RFC 8248: Security Automation and Continuous Monitoring (SACM) Requirements

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID

RFC8248

Published

September 2017

Authors

N. Cam-Winget; L. Lorenzin

Status

INFORMATIONAL

Stream

IETF

Area

sec

Pages

20

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC8248

Topics

• posture assessment
• posture validation
• software integrity
• network authorization
• software compliance

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 7632Endpoint Security Posture Assessment: Enterprise Use CasesCurrent

  September 2015

• RFC 8247Algorithm Implementation Requirements and Usage Guidance for the Internet Key Exchange Protocol Version 2 (IKEv2)Updated

  September 2017

• RFC 8252OAuth 2.0 for Native AppsCurrent

  October 2017

• RFC 8229TCP Encapsulation of IKE and IPsec PacketsObsoleted

  August 2017

• RFC 8268More Modular Exponentiation (MODP) Diffie-Hellman (DH) Key Exchange (KEX) Groups for Secure Shell (SSH)Current

  December 2017

• RFC 8270Increase the Secure Shell Minimum Recommended Diffie-Hellman Modulus Size to 2048 BitsCurrent

  December 2017

• RFC 8274Incident Object Description Exchange Format Usage GuidanceCurrent

  November 2017

• RFC 8221Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH)Updated

  October 2017

Also filed under

• INFORMATIONAL
• 2017
• IETF stream
• sec area