Definition of the ROLIE configuration checklist Extension
draft-mandm-sacm-rolie-configuration-checklist-02

Document Type Active Internet-Draft (candidate for sacm WG)
Last updated 2020-07-13
Stream IETF
Intended RFC status Informational
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream WG state Call For Adoption By WG Issued
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        S. Banghart
Internet-Draft                                                      NIST
Intended status: Informational                                 B. Munyan
Expires: January 14, 2021                                   A. Montville
                                            Center for Internet Security
                                                               G. Alford
                                                           Red Hat, Inc.
                                                           July 13, 2020

       Definition of the ROLIE configuration checklist Extension
           draft-mandm-sacm-rolie-configuration-checklist-02

Abstract

   This document extends the Resource-Oriented Lightweight Information
   Exchange (ROLIE) core to add the information type categories and
   related requirements needed to support security configuration
   checklist use cases.  Additional categories, properties, and
   requirements based on content type enables a higher level of
   interoperability between ROLIE implementations, and richer metadata
   for ROLIE consumers.  Additionally, this document discusses
   requirements and usage of other ROLIE elements in order to best
   syndicate security configuration checklists.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 14, 2021.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Banghart, et al.        Expires January 14, 2021                [Page 1]
Internet-Draft                rolie-cc-ext                     July 2020

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  The 'configuration-checklist' information-type  . . . . . . .   3
   4.  rolie:property Extensions . . . . . . . . . . . . . . . . . .   4
   5.  Handling Existing Checklist Formats . . . . . . . . . . . . .   7
   6.  atom:link Extensions  . . . . . . . . . . . . . . . . . . . .   8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  configuration-checklist information-type  . . . . . . . .   8
     7.2.  checklist:constributor property . . . . . . . . . . . . .   9
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   9.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  10
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     10.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Appendix A.  Examples . . . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   Default configurations for endpoints (operating systems,
   applications, etc.) are normally geared towards ease-of-use or ease-
   of-deployment, not security.  As such, many enterprises operate
   according to guidance provided to them by a control framework
   ([CIS_Critical_Controls], [PCI_DSS], [NIST_800-53] etc.), which often
   prescribe that an enterprise define a standard, security-minded
   configuration for each technology they operate.  Such standard
   configurations are often referred to as configuration checklists.
   This document defines an extension to the Resource-Oriented
   Lightweight Information Exchange (ROLIE) protocol
   [I-D.ietf-mile-rolie] to support the publication of configuration
   checklist information.  Configuration checklists contain a set of
   configuration recommendations for a given endpoint.  A configuration
   recommendation prescribes expected values pertaining to one or more
Show full document text