Definition of the ROLIE configuration checklist ExtensionCenter for Internet Security31 Tech Valley DriveEast Greenbush, NY12061USAbill.munyan.ietf@gmail.comCenter for Internet Security31 Tech Valley DriveEast Greenbush, NY12061USAadam.w.montville@gmail.comThis document extends the Resource-Oriented Lightweight Information Exchange (ROLIE) core by defining a new information-type to ROLIE’s atom:category pertaining to security configuration checklists. Additional supporting requirements are also defined which describe the use of specific formats and link relations pertaining to the new information-type.This document defines an extension to the Resource-Oriented Lightweight Information Exchange (ROLIE) protocol to support the publication of configuration checklist information. Many enterprises operate according to guidance provided to them by a control framework (, , 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. These configuration checklists contain a set of configuration recommendations for a given endpoint. A configuration recommendation prescribes expected values pertaining to one or more discrete endpoint attributes.Configuration Checklist
A configuration checklist is an organized collection of rules about a particular kind of system or platform.
Generally synonymous with endpoint attribute.Configuration Recommendation
A configuration recommendation is an expression of the desired posture of one or more configuration items. A configuration recommendation generally includes the description of the recommendation, a rationale statement, and the expected state of collected posture information.
TBDTODO: There needs to be a “normative” reference to the SCAP 1.2/3 specifications and schema definitionsThis document defines a new “information-type” value of “configuration-checklist”.The “configuration-checklist” information type represents a body of information describing a set of configuration recommendations. A configuration recommendation is, minimally, a single configuration item paired with a recommended value or range of values. Depending on the source, a configuration recommendation may carry with it additional information (i.e. description, references, rationale, etc.). Provided below is a non-exhaustive list of information that may be considered as components of a configuration checklist.A “Data Stream”:A “Benchmark”A “Profile”A “Value”A “Rule” or “Group” of Rules
DescriptionRationaleRemediation InstructionsInformation, described in the dialect of a supported “check system”, indicating the method(s) used to audit the checklist configuration item.Applicable Platform InformationInformation regarding a set of patches to be evaluatedAny supported “tailoring” information, providing a method for evaluating entities to refine the recommendations in the data stream without modifying the published data stream content. (WKM NOTE: Does “tailoring” need to be here? Why would any tailoring be included in a published feed? Unless the organization is re-publishing the content with their tailoring included.)These requirements apply when a ROLIE repository contains any Collections, who’s href points to an atom:feed who’s atom:category element contains a scheme attribute of “urn:ietf:params:rolie:category:information-type” and a term attribute of the new “configuration-checklist” information-type.The following sections describe the various requirements for the atom:entry element, and it’s child elements, when publishing configuration checklist information to a ROLIE repository.Information about the proposed serialization types for configuration checklistsPDFTextWordExcelXML via DSCJSON?A configuration checklist may be published by an organization using numerous formats, such as PDF, Word or Excel documents, and automation content using XML or JSON data models.This document does not specify any additional requirements for use of the rolie:format element.A breadth of metadata may be included with a configuration checklist as identifying information. A publishing organization may wish to recognize or attribute checklist authors or contributors, or maintain a revision/version history over time. Other metadata that may be included could indicate the various categories of products to which the checklist applies, such as Operating System, Network Device, or Application Server.The following list describes various ‘rolie:property’ constructs.author (0..n)
An unbounded number of rolie:property elements with a name attribute of “author” may be included to indicate those individuals noted as the authors of the configuration checklist.contributor (0..n)
An unbounded number of rolie:property elements with a name attribute of “contributor” may be included to indicate those individuals noted as recognized contributors to the configuration checklist and/or the recommendations contained within.checklist version: The value of the “checklist version” property indicates the version number of the configuration checklist, such as 3.1.1title: The value of the “title” property indicates the document title of the configuration checklist, such as “CIS Benchmark for Microsoft Windows Server 2012 R2”publication dateoverviewProduct category (0..n), such as
Antivirus SoftwareApplication ServerAuditingAuthenticationAutomation/Productivity Application SuiteClient and Server EncryptionConfiguration Management SoftwareDatabase Management SystemDesktop ApplicationDesktop ClientDHCP ServerDirectory ServiceDNS ServerEmail ServerEncryption SoftwareEnterprise ApplicationFile EncryptionFirewallFirmwareHandheld DeviceIdentity ManagementIntrusion Detection SystemKVMMail ServerMalwareMobile SolutionMonitoringMulti-Functional PeripheralNetwork RouterNetwork SwitchOffice SuiteOperating SystemPeripheral DeviceSecurity ServerServerVirtual MachineVirtualization SoftwareWeb BrowserWeb ServerWireless EmailWireless NetworkTODO: Can there be multiple of these links? For example, I really want more than one target-platform and more than one profile.NameDescriptionConformanceancestorLinks to a configuration checklist supersceded by that described in this entryMAYtarget-platformLinks to a software descriptor resource defining the software subject to this configuration checklist entrySHOULDversionLinks to a text resource indicating the version of the configuration checklistMUSTPer this document, IANA has added an entry to the “ROLIE Security Resource Information Type Sub-Registry” registry located at https://www.iana.org/assignments/rolie/category/information-type.New IANA table for “ROLIE Entry Format”scap-1.2PDFxccdf-1.2-collectionovalcvrfcve (should we reuse the enumref?); Look at the “enumref” and see if we can copy/paste configuration checklist-specific information in a similar manner? Can we then include that enum reference in the ROLIE extension document or should we create a new “enumref” document separately?vulnerability
configuration-checklist
TBD
TBDTBDTBDResource-Oriented Lightweight Information ExchangeThis document defines a resource-oriented approach for security automation information publication, discovery, and sharing. Using this approach, producers may publish, share, and exchange representations of software descriptors, security incidents, attack indicators, software vulnerabilities, configuration checklists, and other security automation information as web-addressable resources. Furthermore, consumers and other stakeholders may access and search this security information as needed, establishing a rapid and on- demand information exchange network for restricted internal use or public access repositories. This specification extends the Atom Publishing Protocol and Atom Syndication Format to transport and share security automation resource representations.NIST 800-53CIS Critical Security ControlsPCI Data Security Standard