No Description
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

xep-0268.xml 22KB

  1. <?xml version='1.0' encoding='UTF-8'?>
  2. <!DOCTYPE xep SYSTEM 'xep.dtd' [
  3. <!ENTITY % ents SYSTEM 'xep.ent'>
  4. <!ENTITY ADDITION "&lt;AdditionalData/&gt;">
  5. <!ENTITY JID "&lt;jid/&gt;">
  6. %ents;
  7. ]>
  8. <?xml-stylesheet type='text/xsl' href='xep.xsl'?>
  9. <xep>
  10. <header>
  11. <title>Incident Handling</title>
  12. <abstract>This specification defines methods for incident reporting among XMPP server deployments using the IODEF format produced by the IETF's INCH Working Group.</abstract>
  14. <number>0268</number>
  15. <status>Deferred</status>
  16. <type>Standards Track</type>
  17. <sig>Standards</sig>
  18. <approver>Council</approver>
  19. <dependencies>
  20. <spec>XMPP Core</spec>
  21. </dependencies>
  22. <supersedes/>
  23. <supersededby/>
  24. <shortname>NOT_YET_ASSIGNED</shortname>
  25. <discuss>operators</discuss>
  26. <author>
  27. <firstname>Artur</firstname>
  28. <surname>Hefczyc</surname>
  29. <email></email>
  30. <jid></jid>
  31. </author>
  32. <author>
  33. <firstname>Florian</firstname>
  34. <surname>Jensen</surname>
  35. <email></email>
  36. <jid></jid>
  37. </author>
  38. <author>
  39. <firstname>Mickaël</firstname>
  40. <surname>Rémond</surname>
  41. <email></email>
  42. <jid></jid>
  43. </author>
  44. &stpeter;
  45. &mwild;
  46. <revision>
  47. <version>0.6</version>
  48. <date>2012-05-29</date>
  49. <initials>psa</initials>
  50. <remark><p>Aligned document with the IETF guidelines for defining extensions to IODEF; defined several more IODEF NodeRole categories; added schema for the JID element; noted that the JID element might be moved to a separate specification.</p></remark>
  51. </revision>
  52. <revision>
  53. <version>0.5</version>
  54. <date>2012-05-16</date>
  55. <initials>psa</initials>
  56. <remark><p>Simplified the processing model to send reports only in IQ-sets (not in IQ-results); filled out the sections on inquiries, requests, and responses; corrected the schema and examples.</p></remark>
  57. </revision>
  58. <revision>
  59. <version>0.4</version>
  60. <date>2012-04-17</date>
  61. <initials>psa</initials>
  62. <remark><p>Changed the XML format from a custom schema to IODEF (RFC 5070); incremented namespace version from 1 to 2.</p></remark>
  63. </revision>
  64. <revision>
  65. <version>0.3</version>
  66. <date>2009-11-17</date>
  67. <initials>psa</initials>
  68. <remark><p>Added security considerations; defined schema.</p></remark>
  69. </revision>
  70. <revision>
  71. <version>0.2</version>
  72. <date>2009-06-05</date>
  73. <initials>mw/psa</initials>
  74. <remark><p>Added more detailed information about the solution element; removed the suggestion element since the solution element can be used by both reporting entities and receiving entities; added notes about processing of incident reports by receiving entities.</p></remark>
  75. </revision>
  76. <revision>
  77. <version>0.1</version>
  78. <date>2009-04-30</date>
  79. <initials>psa</initials>
  80. <remark><p>Initial published version.</p></remark>
  81. </revision>
  82. <revision>
  83. <version>0.0.3</version>
  84. <date>2009-04-30</date>
  85. <initials>psa</initials>
  86. <remark><p>Per Council feedback, moved server rosters to a separate specification.</p></remark>
  87. </revision>
  88. <revision>
  89. <version>0.0.2</version>
  90. <date>2009-04-27</date>
  91. <initials>psa/fj</initials>
  92. <remark><p>Refactored XML format; added elements for sub-categories, locations, related incidents, solutions, and suggestions.</p></remark>
  93. </revision>
  94. <revision>
  95. <version>0.0.1</version>
  96. <date>2009-04-13</date>
  97. <initials>ah/fj/psa/mr/mw</initials>
  98. <remark><p>First draft.</p></remark>
  99. </revision>
  100. </header>
  101. <section1 topic='Introduction' anchor='intro'>
  102. <p>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;.)</p>
  103. </section1>
  104. <section1 topic='Interactions' anchor='interactions'>
  105. <p>This document defines several interactions (similar to those in RID, see &rfc6045;) between XMPP server deployments with respect to incident handling. These interactions are transported using the XMPP &IQ; stanza as described below, where each element (qualified by the 'urn:xmpp:incident:2' namespace) is used as a wrapper for IODEF data.</p>
  106. <ol>
  107. <li><p>The &lt;report/&gt; element (contained in an &IQ; stanza of type "set") 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 but without requesting assistance (for which see the &lt;request/&gt; element). This element is similar to a RID message type of "Report".</p></li>
  108. <li><p>The &lt;inquiry/&gt; element (contained in an &IQ; stanza of type "get") asks for information about an incident; it is expected that the reply will contain a &lt;report/&gt; element. This element is similar to a RID message type of "IncidentQuery".</p></li>
  109. <li><p>The &lt;request/&gt; element (contained in an &IQ; stanza of type "get") asks for assistance in resolving an incident, e.g., by requesting that the server take some action. This element is similar to a RID message type of "Investigation" or "TraceRequest".</p></li>
  110. <li><p>The &lt;response/&gt; element (contained in an &IQ; stanza of type "set") provides assistance in resolving an incident. This element is similar to a RID message type of "Result".</p></li>
  111. </ol>
  112. </section1>
  113. <section1 topic='Report Format and Processing' anchor='report'>
  114. <p>When one server wants to send information about an incident, it sends a incident report to another server. The report consists of an XMPP &IQ; stanza of type "set" containing a &lt;report/&gt; element that in turn contains an IODEF document. An example is shown below.</p>
  115. <example caption="A report of trouble"><![CDATA[
  116. <iq from='' id='vk2x91g47' to='' type='set'>
  117. <report xmlns='urn:xmpp:incident:2'>
  118. <Incident xmlns='urn:ietf:params:xml:ns:iodef-1.0'
  119. purpose='reporting'>
  120. <IncidentID name=''>4BF5D2CE-7C90-4860-BEF2-43A7D777D5FF</IncidentID>
  121. <StartTime>2009-04-13T19:05:20Z</StartTime>
  122. <EndTime>2009-04-13T19:27:22Z</EndTime>
  123. <ReportTime>2009-04-13T19:31:07Z</ReportTime>
  124. <Description xml:lang='en'>lots of MUC spammers from clueless.lit!</Description>
  125. <Contact role='admin' type='person'>
  126. <AdditionalData>
  127. <jid xmlns='urn:xmpp:incident:2'></jid>
  128. </AdditionalData>
  129. </Contact>
  130. <Contact role='admin' type='person'>
  131. <AdditionalData>
  132. <jid xmlns='urn:xmpp:jid:0'></jid>
  133. </AdditionalData>
  134. </Contact>
  135. <Contact role='ext-type' ext-type='chatroom'>
  136. <AdditionalData>
  137. <jid xmlns='urn:xmpp:jid:0'></jid>
  138. </AdditionalData>
  139. </Contact>
  140. <RelatedActivity>
  141. <IncidentID name=''>133BCE2E-E669-4ECE-B0F8-766B9E65630D</IncidentID>
  142. </RelatedActivity>
  143. <Assessment>
  144. <Impact lang='en' severity='medium' completion='succeeded' type='dos'/>
  145. </Assessment>
  146. <EventData>
  147. <Flow>
  148. <System category='source'>
  149. <Node>
  150. <Address category='ext-category' ext-category='xmpp'>abuser@clueless.lit</Address>
  151. <Counter type='ext-type' ext-type='xmpp-presence'>123</Counter>
  152. </Node>
  153. <Node>
  154. <Address category='ext-category' ext-category='xmpp'>luser27@clueless.lit</Address>
  155. <Counter type='ext-type' ext-type='xmpp-presence'>47</Counter>
  156. </Node>
  157. </System>
  158. <System category='target'>
  159. <Node>
  160. <Address category='ext-category' ext-category='xmpp'></Address>
  161. <Address category='ext-category' ext-category='xmpp'></Address>
  162. <NodeRole category='ext-category' ext-category='xmpp-muc'/>
  163. </Node>
  164. </System>
  165. </Flow>
  166. </EventData>
  167. </Incident>
  168. </report>
  169. </iq>
  170. ]]></example>
  171. <p>If the recipient is able to process the report, it MUST return an &IQ; stanza of type "result"; if not, it MUST return an &IQ; stanza of type "error" (error handling will be defined in a future version of this specification).</p>
  172. </section1>
  173. <section1 topic='Inquiry Format and Processing' anchor='inquiry'>
  174. <p>When one server wants to find out more information about an incident, it sends an inquiry to another server (not necessarily the server where the incident occurred).</p>
  175. <example caption="An inquiry about an incident"><![CDATA[
  176. <iq from='' id='br6a31m9' to='' type='get'>
  177. <inquiry xmlns='urn:xmpp:incident:2'>
  178. <Incident xmlns='urn:ietf:params:xml:ns:iodef-1.0'
  179. purpose='traceback'>
  180. <IncidentID name=''>4BF5D2CE-7C90-4860-BEF2-43A7D777D5FF</IncidentID>
  181. </Incident>
  182. </inquiry>
  183. </iq>
  184. ]]></example>
  185. <p>If the recipient is able to process the inquiry, it MUST return an &IQ; stanza of type "result" and then send a report about the incident using an &IQ; stanza of type "set" as defined above; if not, it MUST return an &IQ; stanza of type "error" (error handling will be defined in a future version of this specification).</p>
  186. </section1>
  187. <section1 topic='Request Format and Processing' anchor='request'>
  188. <p>When one server wants to ask for assistance in resolving an incident, it sends a request to another server (not necessarily the server where the incident occurred).</p>
  189. <p>Here, the server where the attack occurred requests that the server where the attack originated will disable the offending accounts (via the "block-host" value for the 'action' attribute of the IODEF &lt;Expectation/&gt; element).</p>
  190. <example caption="A request for assistance"><![CDATA[
  191. <iq from='' id='kq62vx31' to='clueless.lit' type='get'>
  192. <request xmlns='urn:xmpp:incident:2'>
  193. <Incident xmlns='urn:ietf:params:xml:ns:iodef-1.0'
  194. purpose='mitigation'>
  195. <IncidentID name=''>4BF5D2CE-7C90-4860-BEF2-43A7D777D5FF</IncidentID>
  196. <StartTime>2009-04-13T19:05:20Z</StartTime>
  197. <EndTime>2009-04-13T19:27:22Z</EndTime>
  198. <ReportTime>2009-04-13T19:31:07Z</ReportTime>
  199. <Description xml:lang='en'>lots of MUC spammers from clueless.lit!</Description>
  200. <Contact role='admin' type='person'>
  201. <AdditionalData>
  202. <jid xmlns='urn:xmpp:incident:2'></jid>
  203. </AdditionalData>
  204. </Contact>
  205. <Contact role='admin' type='person'>
  206. <AdditionalData>
  207. <jid xmlns='urn:xmpp:jid:0'></jid>
  208. </AdditionalData>
  209. </Contact>
  210. <Contact role='ext-type' ext-type='chatroom'>
  211. <AdditionalData>
  212. <jid xmlns='urn:xmpp:jid:0'></jid>
  213. </AdditionalData>
  214. </Contact>
  215. <RelatedActivity>
  216. <IncidentID name=''>133BCE2E-E669-4ECE-B0F8-766B9E65630D</IncidentID>
  217. </RelatedActivity>
  218. <Assessment>
  219. <Impact lang='en' severity='medium' completion='succeeded' type='dos'/>
  220. </Assessment>
  221. <EventData>
  222. <Flow>
  223. <System category='source'>
  224. <Node>
  225. <Address category='ext-category' ext-category='xmpp'>abuser@clueless.lit</Address>
  226. <Counter type='ext-type' ext-type='xmpp-presence'>123</Counter>
  227. </Node>
  228. <Node>
  229. <Address category='ext-category' ext-category='xmpp'>luser27@clueless.lit</Address>
  230. <Counter type='ext-type' ext-type='xmpp-presence'>47</Counter>
  231. </Node>
  232. </System>
  233. <System category='target'>
  234. <Node>
  235. <Address category='ext-category' ext-category='xmpp'></Address>
  236. <Address category='ext-category' ext-category='xmpp'></Address>
  237. <NodeRole category='ext-category' ext-category='xmpp-muc'/>
  238. </Node>
  239. </System>
  240. </Flow>
  241. <Expectation action='block-host'/>
  242. </EventData>
  243. </Incident>
  244. </request>
  245. </iq>
  246. ]]></example>
  247. <p>If the recipient is able to process the report, it MUST return an &IQ; stanza of type "result"; if not, it MUST return an &IQ; stanza of type "error" (error handling will be defined in a future version of this specification).</p>
  248. </section1>
  249. <section1 topic='Response Format and Processing' anchor='response'>
  250. <p>When one server provides assistance in resolving an incident, it sends a response to another server (not necessarily the server where the incident occurred).</p>
  251. <p>Here, the server where the attack originated informs the server where the attack occurred that it has disabled the offending accounts (via the IODEF &lt;HistoryItem/&gt; element).</p>
  252. <example caption="A response to a request for assistance"><![CDATA[
  253. <iq from='clueless.list' id='ic1fa53v' to='' type='set'>
  254. <response xmlns='urn:xmpp:incident:2'>
  255. <Incident xmlns='urn:ietf:params:xml:ns:iodef-1.0'
  256. purpose='mitigation'>
  257. <IncidentID name=''>4BF5D2CE-7C90-4860-BEF2-43A7D777D5FF</IncidentID>
  258. <StartTime>2009-04-13T19:05:20Z</StartTime>
  259. <EndTime>2009-04-13T19:27:22Z</EndTime>
  260. <ReportTime>2009-04-13T19:31:07Z</ReportTime>
  261. <Description xml:lang='en'>lots of MUC spammers from clueless.lit!</Description>
  262. <Contact role='admin' type='person'>
  263. <AdditionalData>
  264. <jid xmlns='urn:xmpp:incident:2'></jid>
  265. </AdditionalData>
  266. </Contact>
  267. <Contact role='admin' type='person'>
  268. <AdditionalData>
  269. <jid xmlns='urn:xmpp:jid:0'></jid>
  270. </AdditionalData>
  271. </Contact>
  272. <Contact role='ext-type' ext-type='chatroom'>
  273. <AdditionalData>
  274. <jid xmlns='urn:xmpp:jid:0'></jid>
  275. </AdditionalData>
  276. </Contact>
  277. <RelatedActivity>
  278. <IncidentID name=''>133BCE2E-E669-4ECE-B0F8-766B9E65630D</IncidentID>
  279. </RelatedActivity>
  280. <Assessment>
  281. <Impact lang='en' severity='medium' completion='succeeded' type='dos'/>
  282. </Assessment>
  283. <EventData>
  284. <Flow>
  285. <System category='source'>
  286. <Node>
  287. <Address category='ext-category' ext-category='xmpp'>abuser@clueless.lit</Address>
  288. <Counter type='ext-type' ext-type='xmpp-presence'>123</Counter>
  289. </Node>
  290. <Node>
  291. <Address category='ext-category' ext-category='xmpp'>luser27@clueless.lit</Address>
  292. <Counter type='ext-type' ext-type='xmpp-presence'>47</Counter>
  293. </Node>
  294. </System>
  295. <System category='target'>
  296. <Node>
  297. <Address category='ext-category' ext-category='xmpp'></Address>
  298. <Address category='ext-category' ext-category='xmpp'></Address>
  299. <NodeRole category='ext-category' ext-category='xmpp-muc'/>
  300. </Node>
  301. </System>
  302. </Flow>
  303. <Expectation action='block-host'/>
  304. </EventData>
  305. <History>
  306. <HistoryItem action='blockquote'>
  307. <DateTime>2009-04-13T19:47:11Z</DateTime>
  308. <Description>Account disabled</Description>
  309. </HistoryItem>
  310. </History>
  311. </Incident>
  312. </response>
  313. </iq>
  314. ]]></example>
  315. <p>If the recipient is able to process the report, it MUST return an &IQ; stanza of type "result"; if not, it MUST return an &IQ; stanza of type "error" (error handling will be defined in a future version of this specification).</p>
  316. </section1>
  317. <section1 topic='Definition of IODEF Extensions' anchor='iodef'>
  318. <p>This document defines the following IODEF extensions, described in accordance with the guidelines in &miletemplate;.</p>
  319. <section2 topic='Contact' anchor='iodef-contact'>
  320. <p>This specification defines an extended Contact role of "chatroom", i.e., a new enumerated value for the Contact@role attribute. This value specifies a text conference where discussion of the incident can take place, e.g., an IRC channel or an XMPP &xep0045; room. Since there are many different chatroom technologies, the address of the chatroom shall be specified as the child of an &ADDITION; element. For XMPP chatrooms, the address is the XML character data of a &JID; element qualified by the 'urn:xmpp:jid:0' namespace.</p>
  321. <p>Note: Definition of the &JID; element might be moved to a separate specification.</p>
  322. </section2>
  323. <section2 topic='Address' anchor='iodef-address'>
  324. <p>This specification defines an extended Address category of "xmpp", i.e., a new enumerated value for the Address@category attribute. This value specifies the JabberID of a network entity, in conformance with &rfc6122; or its successor.</p>
  325. </section2>
  326. <section2 topic='NodeRole' anchor='iodef-noderole'>
  327. <p>This specification defines several extended NodeRole categories, i.e., new enumerated values for the NodeRole@category attribute:</p>
  328. <ul>
  329. <li>"xmpp" -- the network role of an XMPP service or core router as defined by &rfc6120; and &rfc6121;</li>
  330. <li>"xmpp-bytestreams" -- the network role of an XMPP SOCKS5 byestreams service as defined by &xep0065;</li>
  331. <li>"xmpp-muc" -- the network role of an XMPP multi-user chat service as defined by <cite>XEP-0045</cite></li>
  332. <li>"xmpp-pubsub" -- the network role of an XMPP pubsub service as defined by &xep0060;</li>
  333. </ul>
  334. </section2>
  335. <section2 topic='AdditionalData' anchor='iodef-additionaldata'>
  336. <p>This specification defines an AdditionalData element of &JID; qualified by the 'urn:xmpp:jid:0' namespace. The XML character data of this element is a JabberID (i.e., an XMPP address) that conforms to RFC 6122 or its successor.</p>
  337. <p>Note: Definition of the &JID; element might be moved to a separate specification.</p>
  338. </section2>
  339. </section1>
  340. <section1 topic='Internationalization Considerations' anchor='i18n'>
  341. <p>The &JID; element qualified by the 'urn:xmpp:incident:2' namespace is a "JID slot" as described in &rfc6122bis;.</p>
  342. <p>Note: Definition of the &JID; element might be moved to a separate specification.</p>
  343. </section1>
  344. <section1 topic='Security Considerations' anchor='security'>
  345. <p>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;.</p>
  346. <p>This technology is designed to help mitigate attacks on the XMPP network. However, incident reporting is itself vulnerable to the following attacks:</p>
  347. <ul>
  348. <li>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.</li>
  349. <li>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.</li>
  350. </ul>
  351. <p>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.</p>
  352. <p>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.</p>
  353. <p>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.</p>
  354. <p>A receiving server MAY forward reports that it receives to other servers it trusts.</p>
  355. </section1>
  356. <section1 topic='IANA Considerations' anchor='iana'>
  357. <p>This document might require interaction with &IANA; to register various IODEF extensions, in accordance with <cite>draft-ietf-mile-template</cite>.</p>
  358. </section1>
  359. <section1 topic='XMPP Registrar Considerations' anchor='reg'>
  360. <section2 topic='Protocol Namespaces' anchor='registrar-ns'>
  361. <p>This specification defines the following XML namespace:</p>
  362. <ul>
  363. <li>urn:xmpp:incident:2</li>
  364. <li>urn:xmpp:jid:0</li>
  365. </ul>
  366. <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
  367. <p>Note: Registration of the 'urn:xmpp:jid:0' namespace might be moved to a separate specification.</p>
  368. </section2>
  369. <section2 topic='Protocol Versioning' anchor='registrar-versioning'>
  370. &NSVER;
  371. </section2>
  372. </section1>
  373. <section1 topic='XML Schemas' anchor='schemas'>
  374. <section2 topic='Incident Namespace' anchor='schemas-incident'>
  375. <code><![CDATA[
  376. <?xml version='1.0' encoding='UTF-8'?>
  377. <xs:schema
  378. xmlns:xs=''
  379. targetNamespace='urn:xmpp:incident:2'
  380. xmlns='urn:xmpp:incident:2'
  381. elementFormDefault='qualified'>
  382. <xs:import namespace='urn:ietf:params:xml:ns:iodef-1.0'/>
  383. <xs:element name='inquiry' type='IODEFContainerType'/>
  384. <xs:element name='report' type='IODEFContainerType'/>
  385. <xs:element name='request' type='IODEFContainerType'/>
  386. <xs:element name='response' type='IODEFContainerType'/>
  387. <xs:complexType name="IODEFContainerType">
  388. <xs:sequence xmlns:i='urn:ietf:params:xml:ns:iodef-1.0'>
  389. <xs:element ref='i:Incident' minOccurs='1' maxOccurs='1'/>
  390. </xs:sequence>
  391. </xs:complexType>
  392. </xs:schema>
  393. ]]></code>
  394. </section2>
  395. <section2 topic='JID Namespace' anchor='schemas-jid'>
  396. <p>Note: This schema and associated text might be moved to a separate specification.</p>
  397. <code><![CDATA[
  398. <?xml version='1.0' encoding='UTF-8'?>
  399. <xs:schema
  400. xmlns:xs=''
  401. targetNamespace='urn:xmpp:jid:0'
  402. xmlns='urn:xmpp:jid:0'
  403. elementFormDefault='qualified'>
  404. <xs:element name='jid' type='xs:string'/>
  405. </xs:schema>
  406. ]]></code>
  407. </section2>
  408. </section1>
  409. </xep>