From b9720533330f06467ab89151b47aade3ffa8f52d Mon Sep 17 00:00:00 2001 From: stpeter Date: Tue, 17 Apr 2012 09:51:43 -0600 Subject: [PATCH] 0.4 --- xep-0268.xml | 216 +++++++++++++++++++++++---------------------------- 1 file changed, 97 insertions(+), 119 deletions(-) diff --git a/xep-0268.xml b/xep-0268.xml index 98469862..0d68e6a2 100644 --- a/xep-0268.xml +++ b/xep-0268.xml @@ -6,11 +6,11 @@
- Incident Reporting - This specification defines methods for incident reporting among XMPP server deployments. + Incident Handling + This specification defines methods for incident reporting among XMPP server deployments using the IODEF format produced by the IETF's INCH Working Group. &LEGALNOTICE; 0268 - Deferred + Experimental Standards Track Standards Council @@ -40,12 +40,13 @@ mremond@process-one.net &stpeter; - - Matthew - Wild - mwild1@gmail.com - mwild1@jaim.at - + &mwild; + + 0.4 + 2012-04-17 + psa +

Changed the XML format from a custom schema to IODEF (RFC 5070); incremented namespace version from 1 to 2.

 + 0.3 2009-11-17 @@ -85,135 +86,119 @@
-

As XMPP technologies have been deployed more widely, the open XMPP network has become a more significant target for attacks. This specification defines ways for XMPP server deployments to share information with each other and therefore to handle such attacks in a more real-time fashion. In particular, it defines a format for sharing incident reports among XMPP server deployments. (For some related considerations, see &rfc2350;, &rfc3067;, and &rfc5070;.)

+

As XMPP technologies have been deployed more widely, the open XMPP network has become a more significant target for attacks. This specification defines ways for XMPP server deployments to share information with each other and therefore to handle such attacks in a more real-time fashion. In particular, it defines a way to use the IODEF format (defined in &rfc5070; and produced by the IETF's INCH Working Group) as the basis for sharing incident reports among XMPP server deployments. (For some related considerations, see &rfc2350; and &rfc3067;.)

 - -

An incident report consists of an XMPP &MESSAGE; stanza containing an <incident/> child element that includes an 'id' attribute whose value is a UUID as described in &rfc4122;. An example is shown below. A server deployment SHOULD send incident reports only to peer servers that it trusts, for example peers that are in its "server roster" as described in &xep0267;.

+ +

This document defines several interactions (similar to those in &rfc6045;) between XMPP server deployments with respect to incident handling. These interactions are transported using the XMPP &IQ; stanza as described below.

+
    +

  1. The <report/> element (contained in an &IQ; stanza of type "set" or, in response to an <inquiry/> element, of type "result") describes the nature of an incident and also flags the 'status' of the incident as "new", "updated", or "resolved"; it is sent from one server to another for informative purposes (sometimes in reply to the <inquiry/> element) but without requesting assistance (for which see the <request/> element).

    2. +

  2. The <inquiry/> element (contained in an &IQ; stanza of type "get") asks for information about an incident; it is expected that the reply will contain a <report/> element.

    3. +

  3. The <request/> element (contained in an &IQ; stanza of type "get") asks for assistance in resolving an incident.

    4. +

  4. The <response/> element (contained in an &IQ; stanza of type "result") provides assistance in resolving an incident.

    5. +
+ + + +

An incident report consists of an XMPP &IQ; stanza of type "set" or "result" containing an IODEF document. An example is shown below.

- - - - stpeter@jabber.org - operators@conference.jabber.org - + + + 4BF5D2CE-7C90-4860-BEF2-43A7D777D5FF + 2009-04-13T19:05:20Z + 2009-04-13T19:27:22Z + 2009-04-13T19:31:07Z + lots of MUC spammers from abuse.lit! + + + stpeter@jabber.org + + + + + stpeter@jabber.org + + + + + operators@muc.xmpp.org + + + + 133BCE2E-E669-4ECE-B0F8-766B9E65630D + + + + + + + + +
abuser@abuse.lit
+ 123 + + +
luser27@abuse.lit
+ 47 + + + + +
jdev@conference.jabber.org
+
jabber@conference.jabber.org
+ + + + muc presence long-messages - - - jdev@conference.jabber.org - jabber@conference.jabber.org - - - 133BCE2E-E669-4ECE-B0F8-766B9E65630D - - 2 - - - abuser@abuse.lit - loser@abuse.lit - - - lots of MUC spammers from abuse.lit! - - - - + + ]]> -

The defined children of the <description/> element are as follows:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Element NameDescription
<discuss/>The JID of the server admin who generated the incident report (<admin/>), as well as a &xep0045; room where the incident can be discussed (<muc/>).
<info/>Structured information about the incident. The defined values of the <category/> and <type/> elements shall be provided via a registry. It is envisioned that the <category/> values shall be "muc" for &xep0045; incidents, "pubsub" for &xep0060; incidents, "reg" for account registration (&xep0077;) incidents, and "stanzas" for general XMPP incidents.
<locs/>The place or places on the XMPP network where the incident has occurred (such as a multi-user chat room, a publish-subscribe service, or a general XMPP server), each contained in a separate <loc/> element.
<rels/>The IDs of one or more incidents to which this incident might be related, each contained in a separate <rel/> element.
<severity/>The seriousness of the problem, from 5 (least serious) to 1 (most serious).
<source/>The IPv4 or IPv6 address (optionally including port) and JabberID where the incident originated (multiple instance of each source type can be included).
<text/>A natural-language description of the event. This element SHOULD possess an 'xml:lang' attribute. Multiple <text/> elements MAY be included, each with a different 'xml:lang' value.
<time/>The time when the incident began and ended (include an empty <end/> element if the incident is still happening) and, optionally, was reported. The dates MUST conform to the DateTime profile specified in &xep0082;
+

If the report is contained in an &IQ; stanza of type "set" and the recipient of the report is able to process it, it MUST return an &IQ; stanza of type "result". Error handling will be defined in a future version of this specification.

 - -

If the reporting entity determines a solution to the problem or a receiving entity has a suggested solution to the problem, it SHOULD send out a revised incident report containing a <solution/> element (alternatively, the reporting entity can include a solution in its initial report). The solution element can include any of the elements defined for the <description/> element, such as the <ip/> element (since the XMPP server of a source JID might know the IP address and port of the connected entity).

- - - - ... - - - - - 192.0.2.1:53667 - - - iptables -A INPUT -s 192.0.2.1 -j DROP - - - - ]]> + +

To follow.

 - -

Unless explicitly configured to do so, a receiving server SHOULD NOT automatically modify its configuration based on receipt of an incident report, even from a trusted server, but instead SHOULD prompt the human administrators so that they can take appropriate action.

-

A receiving server MAY accept incident reports from peers that are not on its "trust list", but SHOULD treat such reports with caution and provide them to the human administrator(s) of the server.

-

A receiving server MAY forward reports that it receives to other servers it trusts.

+ +

To follow.

+ + + +

To follow.

+ + + +

The <jid/> element qualified by the 'urn:xmpp:incident:2' namespace is a "JID slot" as described in &rfc6122bis;.

 +

It is RECOMMENDED for a server deployment to exchange incident reports only with peer servers that it trusts, for example peers that are in its "server roster" as described in &xep0267;.

This technology is designed to help mitigate attacks on the XMPP network. However, incident reporting is itself vulnerable to the following attacks:

  • False reports could lead a server to deny service to legitimate users or peer servers (see also &xep0205;). To help mitigate such attacks, a server SHOULD treat with caution any incident reports that it might receive from untrusted entities.
  • If traffic between two servers is not protected using Transport Layer Security (TLS), a passive eavesdropper could gain access to incident reports and therefore adjust its behavior in response. To prevent such attacks, servers SHOULD use TLS.
+

Use of the XMPP channel is convenient for communication among XMPP servers; however, if a denial of service attack is severe enough then that channel itself might be unusable.

+

Unless explicitly configured to do so, a receiving server SHOULD NOT automatically modify its configuration based on receipt of an incident report, even from a trusted server, but instead SHOULD prompt the human administrators so that they can take appropriate action.

+

A receiving server MAY accept incident reports from peers that are not on its "trust list", but SHOULD treat such reports with caution and provide them to the human administrator(s) of the server.

+

A receiving server MAY forward reports that it receives to other servers it trusts.

 -

This document requires no interaction with &IANA;.

+

This document might require interaction with &IANA; to register various IODEF extension attributes.

This specification defines the following XML namespace:

    -
  • urn:xmpp:incident:0
    • +
  • urn:xmpp:incident:2

Upon advancement of this specification from a status of Experimental to a status of Draft, the ®ISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.

 @@ -228,18 +213,11 @@ - - - - - - - - + ]]>