Internet DRAFT - draft-moriarty-mile-implementreport
draft-moriarty-mile-implementreport
MILE K. Moriarty, Ed.
Internet-Draft EMC Corporation
Intended status: Informational February 11, 2014
Expires: August 15, 2014
MILE Implementation Report
draft-moriarty-mile-implementreport-00
Abstract
This document is a collection of implementation reports from vendors,
consortiums, and researchers who have implemented one or more of the
standards published from the IETF INCident Handling (INCH) and
Management Incident Lightweight Exchange (MILE) working groups.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 15, 2014.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Moriarty Expires August 15, 2014 [Page 1]
Internet-Draft Abbreviated Title February 2014
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Consortiums and Information Sharing and Analysis Centers
(ISACs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Anti-Phishing Working Group . . . . . . . . . . . . . . . . 3
2.2. Advanced Cyber Defence Centre (ACDC) . . . . . . . . . . . 3
3. Open Source Implementations . . . . . . . . . . . . . . . . . . 4
3.1. EMC/RSA RID Agent . . . . . . . . . . . . . . . . . . . . . 4
3.2. NICT IODEF-SCI implementation . . . . . . . . . . . . . . . 4
4. Vendor Implementations . . . . . . . . . . . . . . . . . . . . 5
4.1. Deep Secure . . . . . . . . . . . . . . . . . . . . . . . . 5
4.2. IncMan Suite, DFLabs . . . . . . . . . . . . . . . . . . . 5
4.3. Surevine Proof of Concept . . . . . . . . . . . . . . . . . 7
5. Vendors with Planned Support . . . . . . . . . . . . . . . . . 7
5.1. Threat Central, HP . . . . . . . . . . . . . . . . . . . . 7
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8
8. Security Considerations . . . . . . . . . . . . . . . . . . . . 8
9. Informative References . . . . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8
Moriarty Expires August 15, 2014 [Page 2]
Internet-Draft Abbreviated Title February 2014
1. Introduction
This document is a collection of implementation reports from vendors
and researchers who have implemented one or more of the standards
published from the INCH and MILE working groups. The standards
include:
o Incident Object Description Exchange Format (IODEF) v1, RFC5070,
o Incident Object Description Exchange Format (IODEF) v2, RFC5070-
bis,
o Extensions to the IODEF-Document Class for Reporting Phishing,
RFC5901
o Sharing Transaction Fraud Data, RFC5941
o IODEF-extension for Structured Cybersecurity Information, RFCXXXX
o Real-time Inter-network Defense (RID), RFC6545
o Transport of Real-time Inter-network Defense (RID) Messages over
HTTP/TLS, RFC6546.
The implementation reports included in this document have been
provided by the team or product responsible for the implementations
of the mentioned RFCs. Additional submissions are welcome and should
be sent to the draft editor. A more complete list of
implementations, including open source efforts and vendor products,
can also be found at the following location:
http://siis.realmv6.org/implementations/
2. Consortiums and Information Sharing and Analysis Centers (ISACs)
2.1. Anti-Phishing Working Group
Description of how IODEF is used will be provided in a future
revision.
2.2. Advanced Cyber Defence Centre (ACDC)
Description of how IODEF is used will be provided in a future
revision. http://www.botfree.eu/
Moriarty Expires August 15, 2014 [Page 3]
Internet-Draft Abbreviated Title February 2014
3. Open Source Implementations
3.1. EMC/RSA RID Agent
The EMC/RSA RID agent is an open source implementation of the
Internet Engineering Task Force (IETF) standards for the exchange of
incident and indicator data. The code has been released under an MIT
license and development will continue with the open source community
at the Github site for RSA Intelligence Sharing:
https://github.com/RSAIntelShare/RID-Server.git
The code implements the RFC6545, Real-time Inter-network Defense
(RID) and RFC6546, Transport of RID over HTTP/TLS protocol. The code
supports the evolving RFC5070-bis Incident Object Description
Exchange Format (IODEF) data model from the work in the IETF working
group Managed Incident Lightweight Exchange (MILE).
3.2. NICT IODEF-SCI implementation
Japan's National Institute of Information and Communications
Technology (NICT) Network Security Research Institute implemented
open source tools for exchanging, accumulating, and locating IODEF-
SCI documents.
Three tools are available in GitHub. They assist the exchange of
IODEF-SCI documents between parties. IODEF-SCI is the IETF draft
that extends IODEF so that IODEF document can embed structured
cybersecurity information (SCI). For instance, it can embed MMDEF,
CEE, MAEC in XML and CVE identifiers.
The three tools are generator, exchanger, and parser. The generator
generates IODEF-SCI document or appends an XML to existing IODEF
document. The exchanger sends the IODEF document to its
correspondent node. The parser receives, parses, and stores the
IODEF-SCI document. It also equips the interface that enable users
to locate IODEF-SCI documents it has ever received. The code has
been released under an MIT license and development will continue
here.
Note that users can enjoy this software with their own
responsibility.
Available Online:
https://github.com/TakeshiTakahashi/IODEF-SCI
Moriarty Expires August 15, 2014 [Page 4]
Internet-Draft Abbreviated Title February 2014
4. Vendor Implementations
4.1. Deep Secure
Deep-Secure Guards are built to protect a trusted domain from:
o releasing sensitive data that does not meet the organisational
security policy
o applications receiving badly constructed or malicious data which
could exploit a vulnerability (known or unknown)
Deep-Secure Guards support HTTPS and XMPP (optimised server to server
protocol) transports. The Deep-Secure Guards support transfer of XML
based business content by creating a schema to translate the known
good content to and from the intermediate format. This means that
the Deep-Secure Guards can be used to protect:
o IODEF/RID using the HTTPS transport binding (RFC 6546)
o IODEF/RID using an XMPP binding
o ROLIE using HTTPS transport binding (draft-field-mile-rolie-02)
o STIX/TAXII using the HTTPS transport binding
Deep-Secure Guards also support the SMTP transport and perform deep
content inspection of content including XML attachments. The Mail
Guard supports S/MIME and Deep Secure are working on support for the
upcoming PLASMA standard which enables information centric policy
enforcement of data.
4.2. IncMan Suite, DFLabs
The Incident Object Description Exchange Format, documented in the
RFC 5070, defines a data representation that provides a framework for
sharing information commonly exchanged by Computer Security Incident
Response Teams (CSIRTs) about computer security incidents. IncMan
Suite implements the IODEF standard for exchanging details about
incidents, either for exporting and importing activities. This has
been introduced to enhance the capabilities of the various CSIRT, to
facilitate collaboration and sharing of useful experiences, conveying
awareness on specific cases.
The IODEF implementation is specified as an XML schema, therefore all
data are stored in an xml file: in this file all data of an incident
are organized in a hierarchical structure to describe the various
objects and their relationships.
Moriarty Expires August 15, 2014 [Page 5]
Internet-Draft Abbreviated Title February 2014
IncMan Suite relies on IODEF as a transport format, composed by
various classes for describing the entities which are part of the
incident description: for instance the various relevant timestamps
(detect time , start time, end time, report time), the techniques
used by the intruders to perpetrate the incident, the impact of the
incident, either technical and non-technical (time and monetary) and
obviously all systems involved in the incident.
4.2.1. Exporting Incidents
Each incident defined in IncMan Suite can be exported via a User
Interface feature and it will populate an xml document. Due to the
nature of the data processed, the IODEF extraction might be
considered privacy sensitive by the parties exchanging the
information or by those described by it. For this reason, specific
care needs to be taken in ensuring the distribution to an appropriate
audience or third party, either during the document exchange and
subsequent processing.
The xml document generated will include description and details of
the incident along with all the systems involved and the related
information. At this stage it can be distributed for import into a
remote system.
4.2.2. Importing Incidents
IncMan Suite provides a functionality to import incidents stored in
files and transported via IODEF-compliant xml documents. The
importing process comprises of two steps: firstly, the file is
inspected to validate if well formed, then all data are uploaded
inside the system.
If an incident is already existing in the system with the same
incident id, the new one being imported will be created under a new
id. This approach prevents from accidentally overwriting existing
info or merging inconsistent data.
IncMan Suite includes also a feature to upload incidents from emails.
The incident, described in xml format, can be stored directly into
the body of the email message or transported as an attachment of the
email. At regular intervals, customizable by the user, IncMan Suite
monitors for incoming emails, filtered by a configurable white-list
and black-list mechanism on the sender's email account, then a parser
processes the received email and a new incident is created
automatically, after having validated the email body or the
attachment to ensure it is a well formed format.
Moriarty Expires August 15, 2014 [Page 6]
Internet-Draft Abbreviated Title February 2014
4.3. Surevine Proof of Concept
XMPP is enhanced and extended through the XMPP Extension Protocols
(or XEPs). XEP-0268 (http://xmpp.org/extensions/xep-0268.html)
describes incident management (using IODEF) of the XMPP network
itself, effectively supporting self-healing the XMPP network. In
order to more generically cover incident management of a network and
over a network, XEP-0268 requires some updates. We are working on
these changes together with a new XEP that supports "social
networking" over XMPP, enhancing the publish-and-subscribe XEP (XEP-
0060). This now allows nodes to publish any type of content and
subscribe to and therefore receive the content. XEP-0268 will be
used to describe IODEF content. We now have an alpha version of the
server-side software and client-side software required to demonstrate
the "social networking" capability and are currently enhancing this
to support Cyber Incident management in real-time.
5. Vendors with Planned Support
5.1. Threat Central, HP
HP has developed HP Threat Central, a security intelligence platform
that enables automated, real-time collaboration between organizations
to combat today's increasingly sophisticated cyber attacks. One way
automated sharing of threat indicators is achieved is through close
integration with the HP ArcSight SIEM for automated upload and
consumption of information from the Threat Central Server. In
addition HP Threat Central supports open standards for sharing threat
information so that participants who do not use HP Security Products
can participate in the sharing ecosystem. General availability of
Threat Central will be in 2014. It is planned that future versions
also support IODEF for the automated upload and download of threat
information.
6. Acknowledgements
The MILE Implementation report has been compiled through the
submissions of implementers of INCH and MILE working group standards.
A special note of thanks to the following contributors:
John Atherton, Surevine
Humphrey Browning, Deep-Secure
Dario Forte, DFLabs
Moriarty Expires August 15, 2014 [Page 7]
Internet-Draft Abbreviated Title February 2014
Tomas Sander, HP
Ulrich Seldeslachts, ACDC
Takeshi Takahashi, National Institute of Information and
Communications Technology Network Security Research Institute
7. IANA Considerations
This memo includes no request to IANA.
8. Security Considerations
This draft provides a summary of implementation reports from
researchers and vendors who have implemented RFCs and drafts from the
MILE and INCH working groups. There are no security considerations
added in this draft because of the nature of the document.
9. Informative References
[RFC5070] Danyliw, R., Meijer, J., and Y. Demchenko, "The Incident
Object Description Exchange Format", RFC 5070,
December 2007.
[RFC5901] Cain, P. and D. Jevans, "Extensions to the IODEF-Document
Class for Reporting Phishing", RFC 5901, July 2010.
[RFC5941] M'Raihi, D., Boeyen, S., Grandcolas, M., and S. Bajaj,
"Sharing Transaction Fraud Data", RFC 5941, August 2010.
[RFC6545] Moriarty, K., "Real-time Inter-network Defense (RID)",
RFC 6545, April 2012.
[RFC6546] Trammell, B., "Transport of Real-time Inter-network
Defense (RID) Messages over HTTP/TLS", RFC 6546,
April 2012.
Moriarty Expires August 15, 2014 [Page 8]
Internet-Draft Abbreviated Title February 2014
Author's Address
Kathleen Moriarty (editor)
EMC Corporation
176 South Street
Hopkinton, MA
US
Email: Kathleen.Moriarty@emc.com
Moriarty Expires August 15, 2014 [Page 9]
