]> Pivotal Software, Inc.

625 Avenue of the Americas New York New York USA (646)792-5770 jfield@pivotal.io

National Institute of Standards and Technology

100 Bureau Drive Gaithersburg Maryland USA (301)975-4288 stephen.banghart@nist.gov

National Institute of Standards and Technology

100 Bureau Drive Gaithersburg Maryland 20877 USA david.waltermire@nist.gov

Security MILE Working Group This 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. The source for this draft is being maintained on GitHub. Suggested changes should be submitted as pull requests at . Instructions are on that page as well. Editorial changes can be managed in GitHub, but any substantial issues need to be discussed on the MILE mailing list.

This document defines a resource-oriented approach to security automation information sharing that follows the Representational State Transfer (REST) architectural style . In this approach, computer security resources are maintained in web-accessible repositories structured as Atom Syndication Format Feeds. Within a given Feed, which may be requested by the consumer, representations of specific types of security automation information are organized, categorized, and described. Furthermore, all collections available to a given user are discoverable, allowing the consumer to search all available content they are authorized to view, and to locate and request the desired information resources. Through use of granular authentication and access controls, only authorized consumers may be permitted the ability to read or write to a given Feed. The goal of this approach is to increase the communication and sharing of security information between providers and consumers that can be used to automate security processes (e.g., incident reports, vulnerability assessments, configuration checklists, and other security automation information). Such sharing allows human operators and computer systems to leverage this standardized communication system to gather information that supports the automation of security processes. To support new types of security automation information being used as time goes on, this specification defines a number of extension points that can be used either privately or globally. These global extensions are IANA registered by ROLIE extension specifications, and provide enhanced interoperability for new use cases and domains. Sections and of this document define the core requirements of all implementations of this specification, and is resource representation agnostic. An overview of the extension system is provided in . Implementers seeking to provide support for specific security automation information types should refer to the specification for that domain described by the IANA registry found in section .

The key words "MUST," "MUST NOT," "REQUIRED," "SHALL," "SHALL NOT," "SHOULD," "SHOULD NOT," "RECOMMENDED," "MAY," and "OPTIONAL" in this document are to be interpreted as described in . The previous key words are used in this document to define the conformance requirements for implementations of this specification. This document does not give any recommendations for the use of ROLIE, it only provides conformance requirements for implementations of this specification. Definitions for some of the common computer security-related terminology used in this document can be found in Section 2 of . The following terms are unique to this specification: A class of security automation information having one or more associated data models. Often such security automation information is used in the automation of a security process. See section for more information.

This specification uses XML Namespaces to uniquely identify XML element names. It uses the following namespace prefix mappings for the indicated namespace URI: "app" is used for the "http://www.w3.org/2007/app" namespace defined in . "atom" is used for the "http://www.w3.org/2005/Atom" namespace defined in . "rolie" is used for the "urn:ietf:params:xml:ns:rolie:1.0" namespace defined in section of this specification.

Some sections of this specification are illustrated with fragments of a non-normative RELAX NG Compact schema . The text of this specification provides the definition of conformance. Schema for the "http://www.w3.org/2007/app" and "http://www.w3.org/2005/Atom" namespaces appear in RFC5023 appendix B and RFC4287 appendix B respectively. A complete informative RELAX NG Compact Schema for the new elements introduced by ROLIE is provided in .

In order to automate security process, tools need access to sufficient sources of structured, security information that can be used to drive security processes. Thus, security information sharing is one of the core components of automating security processes. Vulnerabilities, configurations, software identification, security incidents, and patch data are just a few of the classes of information that are shared today to enable effective security on a wide scale. However, as the scale of defense broadens as networks become larger and more complex, and the volume of information to process makes humans-in-the-loop difficult to scale, the need for automation and machine-to-machine communication becomes increasingly critical. ROLIE seeks to address this need by providing four major information sharing benefits: ROLIE is not bound to any given data format or category of information. Instead, information categories are extensible, and entries declare the format of the referenced data. In cases where several formats or serializations are available, ROLIE can use link relations to communicate how a consumer can access these formats. For example, clients may request that a given resource representation be returned as XML, JSON, or in some other format or serialization. This approach allows the provider to support multiple, compatible formats allowing the consumer to select the most suitable version. Using the Atom Publishing Protocol, ROLIE feeds can easily aggregate feeds and accept information POSTed to them from other sources. Webs of communicating ROLIE servers form ad-hoc sharing communities, increasing data availability and the ability to correlate linked data across sources for participating consumers. ROLIE servers needn't be distributed however, as large ROLIE repositories can function as a central or federated collections. ROLIE, as a RESTful system, is stateless. That is, the server doesn't keep track of client sessions, but rather uses link relations for state transitions. In practice, this means that any consumer can find and share information at any organizational level and at any time without needing to execute a long series of requests. ROLIE provides a number of mechanisms to allow clients to programmatically discover and navigate collections of information in order to dynamically discover new or revised content. Extensible information types and other categories provide one way of determining content that is desirable. Link elements, each with a target URI and an established relationship type, provide a means for ROLIE providers to link other information that is relevant to the current entry or feed. These benefits result in an information sharing protocol that is lightweight, interactive, open, and most importantly, machine readable. The requirements in this specification are broken into two major sections, extensions to the Atom Publishing Protocol (AtomPub) , and extensions to the Atom Syndication Format . All normative requirements in AtomPub and Atom Syndication are inherited from their respective specifications, and apply here unless the requirement is explicitly overridden in this document. In this way, this document may upgrade the requirement (e.g., make a SHOULD a MUST), but will never downgrade a given requirement (e.g., make a MUST a SHOULD).

This section describes a number of restrictions of and extensions to the Atom Publishing Protocol (AtomPub) that define the use of that protocol in the context of a ROLIE-based solution. The normative requirements in this section are generally oriented towards client and server implementations. An understanding of the Atom Publishing Protocol specification is helpful to understand the requirements in this section.

As described in RFC5023 section 8, a Service Document is an XML-based document format that allows a client to dynamically discover the Collections provided by a publisher. A Service Document consists of one or more app:workspace elements that may each contain a number of app:collection elements. The general structure of a service document is as follows (from RFC5023 section 4.2):

In AtomPub, a Workspace, represented by the "app:workspace" element, describes a group of one or more Collections. Building on the AtomPub concept of a Workspace, in ROLIE a Workspace represents an aggregation of Collections pertaining to security automation information resources. This specification does not restrict the number of Workspaces that may be in a Service Document or the specific Collections to be provided within a given Workspace. A ROLIE implementation can host Collections containing both public and private information entries. It is RECOMMENDED that implementations segregate public and private Collections into different app:workspace elements. By doing this, Workspaces that contain private information can be ignored by clients or can be omitted from the Service Document provided to a client that lacks the appropriate privilege to access the set of Collections associated with the Workspace.

In AtomPub, a Collection in a Service Document, represented by the "app:collection" element, provides metadata that can be used to point to a specific Atom Feed that contains information Entries that may be of interest to a client. The association between a Collection and a Feed is provided by the "href" attribute of the app:collection element. Building on the AtomPub concept of a Collection, in ROLIE a Collection represents a pointer to a group of security automation information resources pertaining to a given type of security automation information. Collections are represented as Atom Feeds as per RFC 5023. Atom Feed specific requirements are defined in section . ROLIE defines specialized data requirements for Collections, Feeds, and Entries containing security automation related data. The difference between a ROLIE and a non-ROLIE Collection defined in a Service Document can be determined as follows: For an app:collection to be considered a ROLIE Collection, the app:collection MUST contain an app:categories element that contains only one atom:category element with the "scheme" attribute value of "urn:ietf:params:rolie:category:information-type". This category MUST have an appropriate "term" attribute value as defined in section . This ensures that a given Collection corresponds to a specific type of security automation information. For an app:collection to be considered a non-ROLIE Collection, the app:collection MUST NOT contain an atom:category element with a "scheme" attribute value of "urn:ietf:params:rolie:category:information-type". By distinguishing between ROLIE and non-ROLIE Collections in this way, implementations supporting ROLIE can host Collections pertaining to security automation information alongside Collections of other non-ROLIE information within the same AtomPub instance. The following are additional requirements on the use of the app:collection element for a ROLIE Collection: The child atom:category elements contained in the app:categories element MUST be the same set of atom:category elements used in the Atom Feed resource referenced by the app:collection "href" attribute value. This ensures that the category metadata associated with the Collection and the associated Feed is discoverable in both of these resources. The app:categories element in an app:collection MAY include additional atom:category elements using a scheme other than "urn:ietf:params:rolie:category:information-type". This allows other category metadata to be included.

This specification requires that an implementation MUST publish an Atom Service Document that describes the set of security information Collections provided by the service. The Service Document MUST be retrievable using the standardized URI template "https://{host:port}/.well-known/rolie/servicedocument", where {host:port} is the authority portion of the URI. Dereferencing this URI MAY result in a redirect based on an appropriate HTTP 3xx status code to direct the client to the actual Service Document. This allows clients to have a well-known location to find a ROLIE service document, while giving implementations flexibility over how the service is deployed. This document registers the "rolie/servicedocument" well-known URI as per in . A mechanism to determine which host and port to use is not specified in this document. Use of a mechanism such as DNS SRV Records can provide a secure and reliable discovery mechanism for determining a specific host and port to use for retrieving a Service Document for a given DNS domain.

As described in RFC5023 section 7, a Category Document is an XML-based document format that allows a client to dynamically discover the Categories used within AtomPub Service Documents, and Atom Syndication Feed and Entry documents provided by a publisher. A Category Document consists of one app:categories element that contains a number of inline atom:category elements, or a URI referencing a Category Document. A ROLIE implementation MUST publish a Category Document that describes the set of atom:category elements and associated terms currently used by the service. The Category Document MUST be retrievable using the standardized URI template "https://{host:port}/.well-known/rolie/categorydocument", where {host:port} is the authority portion of the URI. Dereferencing this URI MAY result in a redirect based on an appropriate HTTP 3xx status code to direct the client to the actual Category Document. This allows clients to have a well-known location to find a ROLIE category document, while giving implementations flexibility over how the service is deployed. This document registers the "rolie/categorydocument" well-known URI as per in .

ROLIE is intended to be handled with TLS. The following requirements have been in part derived from . TLS version 1.2 MUST be supported. TLS 1.2 SHOULD be implemented according to all recommendations and best practices present in . It is RECOMMENDED that the most recent published version of TLS is supported. If this version is TLS 1.3 , it is recommended that 0-RTT (Zero Round Trip Time Resumption) is not used, as there is a replay attack that is possible with that option. The server MUST support certificate-based client authentication. An implementation MUST support the set of TLS cipher suites that are REQUIRED by the latest published version of the TLS specification. An implementation MUST also support the TLS cipher suites that provide support for mutual authentication of clients and servers. During the TLS negotiation, the client MUST carefully examine the certificate presented by the server to determine if it meets the client’s expectations. Particularly, the client MUST check its understanding of the server hostname against the server’s identity as presented in the server Certificate message, in order to prevent man-in-the-middle attacks. Matching is performed according to the rules laid out in the Security Considerations section of . If the match fails, the client MUST either ask for explicit user confirmation or terminate the connection and indicate the server’s identity is suspect. If the client has external information as to the expected identity of the server, the hostname check MAY be omitted. Clients MUST verify the binding between the identity of the servers to which they connect and the public keys presented by those servers. Client implementations SHOULD support a certificate validation approach based on section 6 of . The server MUST be capable of verifying the identity of the client with certificate-based authentication according to local policy to ensure that the incoming client request is legitimate before any configuration or state data is sent to or received from the client.

Implementations MUST support user authentication. However, a given implementation MAY allow user authentication to be disabled on a feed by feed basis. Servers participating in an information sharing consortium and supporting interactive user logins by members of the consortium SHOULD support client authentication via a federated identity scheme. This document does not mandate the use of any specific user authorization mechanisms. However, service implementers SHOULD provide appropriate authorization checking for all resource accesses, including individual Atom Entries, Atom Feeds, and Atom Service Documents.

The "/" resource MAY be supported for compatibility with existing deployments that are using Transport of Real-time Inter-network Defense (RID) Messages over HTTP/TLS. The following additional requirements apply for implementations supporting handling of the "/" resource:: Consistent with RFC6546 errata, a client requesting a GET on the "/" resource SHOULD receive an HTTP status code 405 Method Not Allowed. An implementation MAY provide full support for such that a POST to the "/" resource containing a recognized RID message is handled correctly as a RID request. Alternatively, a client requesting a POST to "/" MAY receive an HTTP status code 307 Temporary Redirect. In this case, the location header in the HTTP response will provide the URL of the appropriate RID endpoint, and the client may repeat the POST method at the indicated location. If the "/" resource is unsupported, then a request for this resource MUST provide a 404 HTTP status code.

Servers MAY accept request methods beyond those specified in this document. Clients MUST be capable of recognizing and processing any standard HTTP status code, as defined in Section 5.

This section describes a number of restrictions of and extensions to the Atom Syndication Format that define the use of that format in the context of a ROLIE-based solution. The normative requirements in this section are generally oriented towards any content to be published to a ROLIE server. An understanding of the Atom Syndication Format specification is helpful to understand the requirements in this section.

As described in RFC4287 section 4.1.1, an Atom Feed is an XML-based document format that describes a list of related information items. The list of Atom Feeds provided by a ROLIE service are listed in the service's Service Document through one or more app:collection elements. Each Feed document, represented using the atom:feed element, contains a listing of zero or more Entries. When applied to the problem domain of security automation information sharing, an Atom Feed may be used to represent any meaningful collection of security automation information resources. Each Entry in an atom:feed represents an individual resource (e.g., a specific checklist, a software vulnerability record). Additional Feeds can be used to represent other collections of security automation resources. As discussed in section , ROLIE defines specialized data requirements for Feeds containing security automation related data. The difference between a ROLIE and a non-ROLIE Feed can be determined as follows: For an atom:feed to be considered a ROLIE Feed, the atom:feed MUST contain only one child atom:category element with the "scheme" attribute value of "urn:ietf:params:rolie:category:information-type". This category MUST have an appropriate "term" attribute value as defined in section . This ensures that a given Feed corresponds to a specific type of security automation information. For an atom:feed to be considered a non-ROLIE Feed, the atom:feed MUST NOT contain an atom:category element with a "scheme" attribute value of "urn:ietf:params:rolie:category:information-type". By distinguishing between ROLIE and non-ROLIE Feeds in this way, implementations supporting ROLIE can host Feeds pertaining to security automation information alongside Feeds of other non-ROLIE information within the same AtomPub instance. This is parallel to the handling of collections ealier in this specification in section . The following Atom Feed definition represents a stricter definition of the atom:feed element defined in RFC 4287 when used as a ROLIE Feed. Any element not specified here inherits its definition and requirements from .

The following subsections contain requirements for a ROLIE Feed.

An atom:feed can contain zero or more atom:category elements. In Atom the naming scheme and the semantic meaning of the terms used to identify an Atom category are application-defined. The following are additional requirements on the use of the atom:category element when used in a ROLIE Feed: All member Entries in the Feed MUST represent security automation information records of the provided information type category. An atom:feed MAY include additional atom:category elements using a scheme other than "urn:ietf:params:rolie:category:information-type". This allows other category metadata to be included.

Link relations defined by the atom:link element are used to represent state transitions using a stateless approach. In Atom a type of link relationship can be defined using the "rel" attribute. A ROLIE atom:feed MUST contain one or more atom:link elements with rel="service" and href attribute whose value is a IRI that points to an Atom Service Document associated with the atom:feed. If a client accesses a Feed without first accessing the service's service document, a link with the "service" relationship provides a means to discover additional security automation information. The "service" link relationship is defined in the IANA Link Relations Registry. An atom:feed can contain an arbitrary number of Entries. In some cases, a complete Feed may consist of a large number of Entries. Additionally, as new and updated Entries are ordered at the beginning of a Feed, a client may only be interested in retrieving the first N entries in a Feed to process only the Entries that have changed since the last retrieval of the Feed. As a practical matter, a large set of Entries will likely need to be divided into more manageable portions, or pages. Based on RFC5005 section 3, link elements SHOULD be included in all Feeds to support paging using the following link relation types: "first" - Indicates that the href attribute value of the link identifies a resource IRI for the furthest preceding page of the Feed. "last" - Indicates that the href attribute value of the link identifies a resource IRI for the furthest following page of the Feed. "previous" - Indicates that the href attribute value of the link identifies a resource IRI for the immediately preceding page of the Feed. "next" - Indicates that the href attribute value of the link identifies a resource IRI for the immediately following page of the Feed. For example:

b7f65304-b63b-4246-88e2-c104049c5fd7 2012-05-04T18:13:51.0Z ]]>

A reference to a historical Feed may need to be stable, and/or a Feed may need to be divided into a series of defined epochs. Implementations SHOULD support the mechanisms described in RFC5005 section 4 to provide link-based state transitions for maintaining archiving of Feeds. An atom:feed MAY include additional link relationships not specified in this document. If a client encounters an unknown link relationship type, the client MUST ignore the unrecognized link and continue processing as if the unrecognized link element did not appear. The definition of new Link relations that provide additional state transition extensions is discussed in section .

The atom:updated element identifies the date and time that an Entry was last updated. The atom:updated element MUST be populated with the current time at the instant the Feed representation was last updated by adding, updating, or deleting an Entry; or changing any metadata for the Feed.

Each Entry in an Atom Feed, represented by the atom:entry element, describes a single referenced information record, along with descriptive information about its format, media type, and other publication metadata. The following atom:entry schema definition represents a stricter representation of the atom:entry element defined in for use in a ROLIE-based Atom Feed as defined in section .

The following subsections contain requirements for Entries in a ROLIE Feed.

An atom:content element associates its containing Entry with a content resource identified by the src attribute. There MUST be exactly one atom:content element in the Entry. The content element MUST adhere to this definition, which is a stricter representation of the atom:content element defined in :

The type attribute MUST identify the serialization type of the content, for example, application/xml or application/json. A prefixed media type MAY be used to reflect a specific model used with a given serialization approach (e.g., application/rdf+xml). The src attribute MUST be an IRI that can be dereferenced to retrieve the related content data.

Link relations can be included in an atom:entry to represent state transitions for the Entry. If there is a need to provide the same information in different data models and/or serialization formats, separate Entry instances can be included in the same or a different Feed. Such an alternate content representation can be indicated using an atom:link having a rel attribute with the value "alternate". An atom:feed MAY include additional link relationships not specified in this document. If a client encounters an unknown link relationship type, the client MUST ignore the unrecognized link and continue processing as if the unrecognized link element did not appear. The definition of new Link relations that provide additional state transition extensions is discussed in section .

As mentioned earlier, a key goal of this specification is to allow a consumer to review a set of published security automation information resources, and then identify and retrieve any resources of interest. The format of the data is a key criteria to consider when deciding what information to retrieve. For a given type of security automation information, it is expected that a number of different formats may be used to represent this information. To support this use case, both the serialization format and the specific data model expressed in that format must be known by the consumer. The rolie:format element is used to describe the data model used to express the information referenced in the atom:content element of an atom:entry. It also allows a schema to be identified that can be used when parsing the content to verify or better understand the structure of the content. There MUST be exactly one rolie:format element in an atom:entry. The element MUST adhere to this definition:

The rolie:format element MUST provide a "ns" attribute that identifies the data model of the resource referenced by the atom:content element. For example, the namespace used may be an XML namespace URI, or an identifier that represents a serialized JSON model. The URI used for the "ns" attribute value MUST be an absolute or opaque URI. The resource identified by the URI need not be resolvable. The rolie:format element MAY provide a "version" attribute that identifies the version of the format used for the related atom:content. The rolie:format element MAY provide a "schema-location" attribute that is a URI that identifies a schema resource that can be used to validate the related atom:content. The rolie:format element MAY provide a "schema-type" attribute, which is a mime type identifying the format of the schema resource identified by the "schema-location" attribute. The following nominal example shows how these attributes describe the format of the content:

]]>

The previous element provides an indication that the content of the given entry is using the IODEF v2 format.

An atom:category element provides a way to associate a name/value pair of categorical information using the scheme and term attributes to represent the name, and the label attribute to represent the value. When used in this way an atom:category allows a specific label to be selected from a finite set of possible label values that can be used to further classify a given atom:entry or atom:feed. Within ROLIE, there may be a need to associate additional metadata with an atom:entry. In such a case, use of an atom:category is not practical to represent name/value data for which the allowed values are unbounded. Instead, ROLIE has introduced a new rolie:property element that can represent non-categorical metadata as name/value pairs. Examples include content-specific identifiers, naming data, and other properties that allow for unbounded values. There MAY be zero or more rolie:property elements in an atom:entry. The element MUST adhere to this definition:

The name attribute provides a URI that identifies the namespace and name of the property as a URI. The value attribute is text that provides a value for the property identified by the name attribute. For example, the nominal element <rolie:property name="urn:ietf:params:rolie:property:csirt-iodef-id" value="12345"/> would expose an IODEF ID value contained in a given entry's content. The name used in the example also demonstrates the use of a registered ROLIE property extension, which is described in . Implementations MAY use locally defined and namespaced elements in an Entry in order to provide additional information. Clients that do not recognize a property with an unregistered name attribute MAY ignore the rolie:property.

If an Entry is ever shared as a standalone resource, separate from its containing Feed, then the following additional requirements apply: The Entry MUST have an atom:link element with rel="collection" and href="[IRI of the containing Collection]". This allows the Feed or Feeds for which the Entry is a member to be discovered, along with the related information the Feed may contain. In the case of the Entry have multiple containing Feeds, the Entry MUST have one atom:link for each related Feed. The Entry MUST declare the information type of the content resource referenced by the Entry (see ).

This specification does not require particular information types or data formats; rather, ROLIE is intended to be extended by additional specifications that define the use of new categories and link relations. The primary point of extension is through the definition of new information type category terms. Additional specifications can register new information type category terms with IANA that serve as the main characterizing feature of a ROLIE Collection/Feed or Resource/Entry. These additional specifications defining new information type terms, can describe additional requirements for including specific categories, link relations, as well as, use of specific data formats supporting a given information type term.

The atom:category element, defined in RFC 4287 section 4.2.2, provides a mechanism to provide additional categorization information for a content resource in ROLIE. The ability to define new categories is one of the core extension points provided by Atom. A Category Document, defined in RFC 5023 section 7, provides a mechanism for an Atom implementation to make discoverable the atom:category terms and associated allowed values. ROLIE further defines the use of the existing Atom extension category mechanism by allowing ROLIE specific category extensions to be registered with IANA, and additionally has assigned the "urn:ietf:params:rolie:category:information-type" category scheme that has special meaning for implementations of ROLIE. This allows category scheme namespaces to be managed in a more consistent way, allowing for greater interoperability between content producers and consumers. The namespace "urn:ietf:params:rolie:category:local" has been reserved in the IANA ROLIE Parameters table for private use as defined in . Any category whose "scheme" attribute uses this as a prefix MUST be considered private use. Implementations encountering such a category MUST parse the content without error, but MAY otherwise ignore the element. Use of the "atom:category" element is discussed in the following subsections.

The atom:category element can be used for characterizing a ROLIE Resource. As discussed earlier in this document, an atom:category element has a "term" attribute that indicates the assigned category value, and a "scheme" attribute that provides an identifier for the category type. The "scheme" provides a means to describe how a set of category terms should be used and provides a namespace that can be used to differentiate terms provided by multiple organizations with different semantic meaning. To further differentiate category types used in ROLIE, an IANA sub-registry has been established for ROLIE protocol parameters to support the registration of new category "scheme" attribute values by ROLIE extension specifications. Use of this extension point is discussed in section using the name field with a type parameter of "category" to indicate a category extension.

A ROLIE specific extension point is provided through the atom:category "scheme" value "urn:ietf:params:rolie:category:information-type". This value is a Uniform Resource Name (URN) that is registered with IANA as described in section . When used as the "scheme" attribute in this way, the "term" attribute is expected to be a registered value as defined in section . Through this mechanism a given security automation information type can be used to: identify that an "app:collection" element in a Service Document points to an Atom Feed that contains Entries pertaining to a specific type of security automation information (see section ), or identify that an "atom:feed" element in an Atom Feed contains Entries pertaining to a specific type of security automation information (see section ). identify the information type of a standalone Resource (see section ). For example, the notional security automation information type "incident" would be identified as follows:

]]>

A security automation information type represents a class of information that represents the same or similar information model . Notional examples of information types include: Computing device- or network-related "observable features and phenomenon that aid in the forensic or proactive detection of malicious activity; and associated meta-data" (from ). Information pertaining to and "derived analysis from security incidents" (from ). Information identifying and describing a vulnerability in hardware or software. Content that can be used to assess the configuration settings related to installed software. Metadata used to identify and characterize installable software. This is a short list to inspire new engineering of information type extensions that support the automation of security processes. This document does not specify any information types. Instead, information types in ROLIE are expected to be registered in extension documents that describe one or more new information types. This allows the information types used by ROLIE implementations to grow over time to support new security automation use cases. These extension documents may also enhance ROLIE Service, Category, Feed, and Entry documents by defining link relations, other categories, and Format data model extensions to address the representational needs of these specific information types. New information types are added to ROLIE through registrations to the IANA ROLIE Security Resource Information Type registry defined in section .

Security automation data pertaining to a given information type may be expressed using a number of supported formats. As described in section , the rolie:format element is used to describe the specific data model used to represent the resource referenced by a given "atom:entry". The structure provided by the rolie:format element, provides a mechanism for extension within the atom:entry model. ROLIE extensions MAY further restrict which data models are allowed to be used for a given information type. By declaring the data model used for a given Resource, a consumer can choose to download or ignore the Resource, or look for alternate formats. This saves the consumer from downloading and parsing resources that the consumer is not interested in or resources expressed in formats that are not supported by the consumer.

This document uses several link relations defined in the IANA Link Relation Types registry. Additional link relations can be registered in this registry to allow new relationships to be represented in ROLIE according to RFC 4287 section 4.2.7.2. Based on the preceding reference, if the link relation is too specific or limited in the intended use, an absolute IRI can be used in lieu of registering a new simple name with IANA.

As discussed previously in , many formats contain unique identifying and characterizing properties that are vital for sharing information. In order to provide a global reference for these properties, this document establishes an IANA registry in that allows ROLIE extensions to register named properties using the name field with a type parameter of "property" to indicate a property extension. Implementations SHOULD prefer the use of registered properties over implementation specific properties when possible. ROLIE extensions are expected to register new and use existing properties to provide valuable identifying and characterizing information for a given information type and/or format. The namespace "urn:ietf:params:rolie:property:local" has been reserved in the IANA ROLIE Parameters table for private use as defined in . Any property whose "name" attribute uses this as a prefix MUST be considered private use. Implementations encountering such a property MUST parse the content without error, but MAY otherwise ignore the element. This document also registers a number of general use properties that can be used to expose content information in any ROLIE use case. The following are descriptions of how to use these registered properties: The "value" attribute of this property is a text representation indicating the individual or organization that authored the content referenced by the "src" attribute of the entry's atom:content element. The "value" attribute of this property is a text representation of an identifier pertaining to or extracted from the content referenced by the "src" attribute of the entry's atom:content element. The "value" attribute of this property is a text representation indicating the original publication date of the content referenced by the "src" attribute of the entry's atom:content element. This date may differ from the published date of the ROLIE Entry because publication of the content and the ROLIE Entry represent different events. The date MUST be formatted as specified in . The "value" attribute of this property is a text representation indicating the date that the content, referenced by the "src" attribute of the entry's atom:content element, was last updated. This date may differ from the updated date of the ROLIE Entry because updates made to the content and to the ROLIE Entry are different events. The date MUST be formatted as specified in .

This document has a number of IANA considerations described in the following subsections.

This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in . The ROLIE namespace (rolie-1.0) has been registered in the "ns" registry. URI: urn:ietf:params:xml:ns:rolie-1.0 Registrant Contact: IESG XML: None. Namespace URIs do not represent an XML specification. The ROLIE schema (rolie-1.0) has been registered in the "schema" registry. URI: urn:ietf:params:xml:schema:rolie-1.0 Registrant Contact: IESG XML: See section of this document.

IANA has added an entry to the "IETF URN Sub-namespace for Registered Protocol Parameter Identifiers" registry located at as per RFC3553. The entry is as follows: Registry name: rolie Specification: This document Repository: ROLIE URN Parameters. See [TO BE REMOVED: This registration should take place at the following location: https://www.iana.org/assignments/rolie] Index value: See

A new top-level registry has been created, entitled "Resource Oriented Lightweight Information Exchange (ROLIE) Parameters". [TO BE REMOVED: This registration should take place at the following location: https://www.iana.org/assignments/rolie] In this top-level registry, a sub-registry entitled "ROLIE URN Parameters" has been created. Registration in this repository is via the Specification Required policy . Designated Expert reviews should be routed through the MILE WG mailing list. Failing this, the Designated Expert will be assigned by the IESG. Each entry in this sub-registry must record the following fields: Name: A URN segment that adheres to the pattern {type}:{label}. The keywords are defined as follows: {type}: The parameter type. The allowed values are "category" or "property". "category" denotes a category extension as discussed in . "property" denotes a property extension as discussed in . {label}: A required US-ASCII string that conforms to the URN syntax requirements (see ). This string must be unique within the namespace defined by the {type} keyword. The "local" label for both the "category" and "property" types has been reserved for private use. Extension IRI: The identifier to use within ROLIE, which is the full URN using the form: urn:ietf:params:rolie:{name}, where {name} is the "name" field of this registration. Reference: A static link to the specification and section that the definition of the parameter can be found. Sub-registry: An optional field that links to an IANA sub-registry for this parameter. If the {type} is "category", the sub-registry must contain a "name" field whose registered values MUST be US-ASCII. The list of names are the allowed values of the "term" attribute in the atom:category element. (See ). This repository has the following initial values: Name Extension IRI Reference Sub-Registry category:information-type urn:ietf:params:rolie:category:information-type This document, [TO BE REMOVED: This registration should take place at the following location: https://www.iana.org/assignments/rolie/category/information-type] property:local urn:ietf:params:rolie:property:local This document, None category:local urn:ietf:params:rolie:category:local This document, None property:content-author-name urn:ietf:params:rolie:property:content-author-name This document, None property:content-id urn:ietf:params:rolie:property:content-id This document, None property:content-published-date urn:ietf:params:rolie:property:content-published-date This document, None property:content-updated-date urn:ietf:params:rolie:property:content-updated-date This document, None

A new sub-registry has been created to store ROLIE information type values. Name of Registry: "ROLIE Information Types" Location of Registry: https://www.iana.org/assignments/rolie/category/information-type Fields to record in the registry: name: The full name of the security resource information type as a string from the printable ASCII character set with individual embedded spaces allowed. The ABNF syntax for this field is: 1*VCHAR *(SP 1*VCHAR) index: This is an IANA-assigned positive integer that identifies the registration. The first entry added to this registry uses the value 1, and this value is incremented for each subsequent entry added to the registry. reference: A list of one or more URIs from which the registered specification can be obtained. The registered specification MUST be readily and publicly available from that URI. The URI SHOULD be a stable reference. Allocation Policy: Specification required as per

This document makes the follow two registrations to the Well-Known URI Registry at https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml. Service Document registration: URI suffix: rolie/servicedocument Change controller: IETF Specification document: This document, Related information: None Category Document registration: URI suffix: rolie/categorydocument Change controller: IETF Specification document: This document, Related information: None

This document defines a resource-oriented approach for lightweight information exchange using HTTP over TLS, the Atom Syndication Format, and the Atom Publishing Protocol. As such, implementers must understand the security considerations described in those specifications. All that follows is guidance, more specific instruction is out of scope for this document. To protect the confidentiality of a given resource provided by a ROLIE implementation, requests for retrieval of the resource need to be authenticated to prevent unauthorized users from accessing the resource (see section ). It can also be useful to log and audit access to sensitive resources to verify that proper access controls remain in place over time. The approach described herein is based upon all policy enforcements being implemented at the point when a resource representation is created. As such, producers sharing cyber security information using this specification must take care to authenticate their HTTP clients using a suitably strong user authentication mechanism. Sharing communities that are exchanging information on well-known indicators and incidents for purposes of public education may choose to rely upon HTTP Authentication or similar. A number of authentication schemes are defined in the HTTP Authentication Schemes Registry. Of these, HOBA and SCRAM-SHA-256 provide improved security properties over HTTP Basic and Digest Authentication Schemes. However, sharing communities that are engaged in sensitive collaborative analysis and/or operational response for indicators and incidents targeting high value information systems should adopt a suitably stronger user authentication solution, such as a risk-based or multi-factor approach. In general, trust in the sharing consortium will depend upon the members maintaining adequate user authentication mechanisms. Collaborating consortiums may benefit from the adoption of a federated identity solution, such as those based upon OAuth with JWT, or SAML-core, SAML-bind, and SAML-prof for Web-based authentication and cross-organizational single sign-on. Dependency on a trusted third party identity provider implies that appropriate care must be exercised to sufficiently secure the Identity provider. Any attacks on the federated identity system would present a risk to the consortium, as a relying party. Potential mitigations include deployment of a federation-aware identity provider that is under the control of the information sharing consortium, with suitably stringent technical and management controls. Authorization of resource representations is the responsibility of the source system, i.e. based on the authenticated user identity associated with an HTTP(S) request. The required authorization policies that are to be enforced must therefore be managed by the security administrators of the source system. Various authorization architectures would be suitable for this purpose, such as RBAC and/or ABAC, as embodied in XACML. In particular, implementers adopting XACML may benefit from the capability to represent their authorization policies in a standardized, interoperable format. Note that implementers are free to choose any suitable authorization mechanism that is capable of fulfilling the policy enforcement requirements relevant to their consortium and/or organization. Additional security requirements such as enforcing message-level security at the destination system could supplement the security enforcements performed at the source system, however these destination-provided policy enforcements are out of scope for this specification. Implementers requiring this capability should consider leveraging, e.g. the <RIDPolicy> element in the RID schema. Refer to RFC6545 section 9 for more information. Additionally, the underlying serialization approach used in the message (e.g., XML, JSON) can offer encryption and message authentication capabilities. For example, XMLDSig for XML, and JSON Web Encryption and JSON Web Signature for JSON can provide such mechanisms. When security policies relevant to the source system are to be enforced at both the source and destination systems, implementers must take care to avoid unintended interactions of the separately enforced policies. Potential risks will include unintended denial of service and/or unintended information leakage. These problems may be mitigated by avoiding any dependence upon enforcements performed at the destination system. When distributed enforcement is unavoidable, the usage of a standard language (e.g. XACML) for the expression of authorization policies will enable the source and destination systems to better coordinate and align their respective policy expressions. A service discovery mechanism is not explicitly specified in this document, and there are several approaches available for implementers. When selecting this mechanism, implementations need to ensure that their choice provides a means for authenticating the server. As described in the discovery section, DNS SRV Records are a possible secure solution to discovery.

The optional author field may provide an identification privacy issue if populated without the author's consent. This information may become public if posted to a public feed. Special care should be taken when aggregating or sharing entries from other feeds, or when programmatically generating ROLIE entries from some data source that the author's personal info is not shared without their consent. When using the Atom Publishing Protocol to POST entries to a feed, attackers may use correlating techniques to profile the user. The request time can be compared to the generated "updated" field of the entry in order to build out information about a given user. This correlation attempt can be mitigated by not using HTTP requests to POST entries when profiling is a risk, and rather use backend control of the feeds. Adoption of the information sharing approach described in this document will enable users to more easily perform correlations across separate, and potentially unrelated, cyber security information providers. A client may succeed in assembling a data set that would not have been permitted within the context of the authorization policies of either provider when considered individually. Thus, providers may face a risk of an attacker obtaining an access that constitutes an undetected separation of duties (SOD) violation. It is important to note that this risk is not unique to this specification, and a similar potential for abuse exists with any other cyber security information sharing protocol. However, the wide availability of tools for HTTP clients and Atom Feed handling implies that the resources and technical skills required for a successful exploit may be less than it was previously. This risk can be best mitigated through appropriate vetting of the client at account provisioning time. In addition, any increase in the risk of this type of abuse should be offset by the corresponding increase in effectiveness that this specification affords to the defenders. Proper usage of TLS as described in will in many cases aid in the mitigation of these issues. Overall, ROLIE introduces few privacy concerns above and beyond those present in any other HTTP protocol. Those that exist can be mitigated by following security considerations and carefully using the optional identifying elements.

The authors gratefully acknowledge the valuable contributions of Tom Maguire, Kathleen Moriarty, and Vijayanand Bharadwaj. These individuals provided detailed review comments on earlier drafts, and made many suggestions that have helped to improve this document. The authors would also like to thank the MILE Working Group, the SACM Working Group, and countless other people from both within the IETF community and outside of it for their excellent review and effort towards constructing this draft.

&RFC0020;&RFC2119; &RFC3339; &RFC3688; &RFC3986; &RFC4287; &RFC5005; &RFC5023; &RFC7970; &RFC6546; &RFC3553; &RFC8126; &xml-names; &RFC7589; &RFC5280; &RFC7525; &RFC4642; &RFC5785;

jjc@jclark.com

&RFC8141; &RFC2782; &RFC3275; &RFC7516; &RFC7515; &RFC7486; &RFC7804; &RFC7616; &RFC6749; &RFC7617; &RFC3444; &RFC5234; &RFC7797; Internet2

cantor.2@osu.edu

Nokia

John.Kemp@nokia.com

RSA Security

rphilpott@rsasecurity.com

Sun Microsystems

eve.maler@sun.com

Altos Origin

Internet2

cantor.2@osu.edu

NeuStar

Jeff.Hodges@neustar.biz

Nokia

Frederick.Hirsch@nokia.com

Principal Identity

pmishra@principalidentity.com

RSA Security

rphilpott@rsasecurity.com

Sun Microsystems

eve.maler@sun.com

Internet2

cantor.2@osu.edu

Nokia

Frederick.Hirsch@nokia.com

Nokia

John.Kemp@nokia.com

RSA Security

rphilpott@rsasecurity.com

Sun Microsystems

eve.maler@sun.com

This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery. University of California, Irvine; Department of Information and Computer Science

This appendix is informative. The Relax NG schema below defines the rolie:format element.

This section provides a non-normative example of a client doing service discovery. An Atom Service Document enables a client to dynamically discover what Feeds a particular publisher makes available. Thus, a provider uses an Atom Service Document to enable authorized clients to determine what specific information the provider makes available to the community. While the Service Document is accessible at a pre-determined location, the Service Document can also be made accessible from any well known location, such as via a link from the producer's home page. A client may format an HTTP GET request to retrieve the service document from the specified location:

Notice the use of the HTTP Accept: request header, indicating the MIME type for Atom service discovery. The response to this GET request will be an XML document that contains information on the specific Collections that are provided. Example HTTP GET response:

Vulnerabilities Vulnerabilities Feed ]]>

This simple Service Document example shows that the server provides one workspace, named "Vunerabilities". Within that workspace, the server makes one Collection available. A server may also offer a number of different Collections, each containing different types of security automation information. In the following example, a number of different Collections are provided, each with its own category and authorization scope. This categorization will help the clients to decide which Collections will meet their needs.

Public Security Information Sharing Public Vulnerabilities Private Consortium Sharing Incidents ]]>

In this example, the provider is making available a total of two Collections, organized into two different workspaces. The first workspace contains a Collection consisting of publicly available software vulnerabilities. The second workspace provides an incident Collection for use by a private sharing consortium. An appropriately authenticated and authorized client may then proceed to make HTTP requests for these Collections. The publicly provided vulnerability information may be accessible with or without authentication. However, users accessing the Collection restricted to authorized members of a private sharing consortium are expected to authenticate before access is allowed.

This section provides a non-normative example of a client retrieving an vulnerability Feed. Having discovered the available security information sharing Collections, a client who is a member of the general public may be interested in receiving the Collection of public vulnerabilities. The client may retrieve the Feed for this Collection by performing an HTTP GET operation on the URL indicated by the Collection's "href" attribute. Example HTTP GET request for a Feed:

The corresponding HTTP response would be an XML document containing the vulnerability Feed: Example HTTP GET response for a Feed:

2a7e265a-39bc-43f2-b711-b8fd9264b5c9 2016-05-04T18:13:51.0Z dd786dba-88e6-440b-9158-b8fae67ef67c 2015-08-04T18:13:51.0Z 2015-08-05T18:13:51.0Z

A vulnerability issue identified by CVE-...

]]>

This Feed document has two Atom Entries, one of which has been elided. The first Entry illustrates an atom:entry element that provides a summary of essential details about one particular vulnerability. Based upon this summary information and the provided category information, a client may choose to do an HTTP GET request, on the content "src" attribute, to retrieve the full details of the vulnerability.

This section provides a non-normative example of a client retrieving an vulnerability as an Atom Entry. Having retrieved the Feed of interest, the client may then decide, based on the description and/or category information, that one of the entries in the Feed is of further interest. The client may retrieve this vulnerability Entry by performing an HTTP GET operation on the URL indicated by the "src" attribute of the atom:content element. Example HTTP GET request for an Entry:

The corresponding HTTP response would be an XML document containing the Atom Entry for the vulnerability record: Example HTTP GET response for an Entry:

f63aafa9-4082-48a3-9ce6-97a2d69d4a9b 2015-08-04T18:13:51.0Z 2015-08-05T18:13:51.0Z

A vulnerability issue identified by CVE-...

]]>

The example response above shows an XML document referenced by the "src" attribute of the atom:content element. The client may retrieve the document using this URL.

Changes in draft-ietf-mile-rolie-09 since draft-ietf-mile-rolie-08 revision: TLS requirements changed to clarify TLS versioning and recommendations Informative references and textual discussion added to Security Considerations around HTTP Authentication and content Signing/Encryption. IANA Expert review clarified. Editorial changes from AD review/WGLC. Changes in draft-ietf-mile-rolie-08 since draft-ietf-mile-rolie-07 revision: Reworked “usage of app:collection” and “usage of atom:feed” sections to clarify ROLIE vs non-ROLIE collections/feeds Removed requirement from Security Considerations that was a duplicate of text earlier in the document TLS requirement clarifications around mutal authentication Clarified requirements around support for the "/" resource Added IANA property registrations for content-id, content-published-date, and content-updated-date that can be used across all ROLIE extensions to increase consistency/interop Assorted editorial changes Changes in draft-ietf-mile-rolie-07 since draft-ietf-mile-rolie-06 revision: Condensed and re-focused Sections 1 and 4 to be more concise. Added /.well-known/ registration and requirement for service discovery. Added local category, property namespace, and additional property registrations Added privacy considerations section. Made a number of editorial changes as per WGLC review. Changes in draft-ietf-mile-rolie-06 since draft-ietf-mile-rolie-05 revision: Changed to standards track Added the rolie:property element Fixed references (Normative vs Informative) Set Service and Category document URL template requirements Fixed XML snippets in examples Changes in draft-ietf-mile-rolie-05 since draft-ietf-mile-rolie-04 revision: Added ROLIE specific terminology to section 2 Added AtomPub Category Document in section 5.2 Edited document, improving consistency in terminology usage and capitalization of key terms, as well as enhancing clarity. Removed unused format parameter type in section 8.3 Schema removed, the normative schema consists of the snippets in the requirements sections. Changes in draft-ietf-mile-rolie-04 since draft-ietf-mile-rolie-03 revision: Further specification and clarification of requirements IANA Considerations and extension system fleshed out and described. Examples and References updated. Schema created. Fixed both internal section and external document referencing. Removed XACML Guidance Appendix. This will be added to a future draft on ROLIE Authentication and Access Control. Changes made in draft-ietf-mile-rolie-03 since draft-ietf-mile-rolie-02 revision: Atom Syndication and Atom Pub requirements split and greatly expanded for increased justification and technical specification. Reintroduction and reformatting of some use case examples in order to provide some guidance on use. Established rough version of IANA table extension system along with explanations of said system. Re-organized document to put non-vital information in appendices. Changes made in draft-ietf-mile-rolie-02 since draft-field-mile-rolie-01 revision: All CSIRT and IODEF/RID material moved to companion CSIRT document Recast document into a more general use perspective. The implication of CSIRTs as the defacto end-user has been removed where ever possible. All of the original CSIRT based use cases remain completely supported by this document, it has been opened up to support many other use cases. Changed the content model to broaden support of representation Edited and rewrote much of sections 1,2 and 3 in order to accomplish a broader scope and greater readability Removed any requirements from the Background section and, if not already stated, placed them in the requirements section Re-formatted the requirements section to make it clearer that it contains the lions-share of the requirements of the specification Changes made in draft-ietf-mile-rolie-01 since draft-field-mile-rolie-02 revision: Added section specifying the use of RFC5005 for Archive and Paging of Feeds. Added section describing use of atom categories that correspond to IODEF expectation class and impact classes. See: normative-expectation-impact Dropped references to adoption of a MILE-specific HTTP media type parameter. Updated IANA Considerations section to clarify that no IANA actions are required.