Browse Prior Art Database

Extensions to the IODEF-Document Class for Reporting Phishing (RFC5901)

IP.com Disclosure Number: IPCOM000197744D
Original Publication Date: 2010-Jul-01
Included in the Prior Art Database: 2010-Jul-21

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

P. Cain: AUTHOR [+2]

Abstract

Deception activities, such as receiving an email purportedly from a bank requesting you to confirm your account information, are an expanding attack type on the Internet. The terms "phishing" and "fraud" are used interchangeably in this document to characterize broadly-launched social engineering attacks in which an electronic identity is misrepresented in an attempt to trick individuals into revealing their personal credentials (e.g., passwords, account numbers, personal information, ATM PINs, etc.). A successful phishing attack on an individual allows the phisher (i.e., the attacker) to exploit the individual's credentials for financial or other gain. Phishing attacks have morphed from directed email messages from alleged financial institutions to more sophisticated lures that may also include malware.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 3% of the total text.

Internet Engineering Task Force (IETF)                           P. Cain Request for Comments: 5901                   The Cooper-Cain Group, Inc. Category: Standards Track                                      D. Jevans ISSN: 2070-1721                          The Anti-Phishing Working Group                                                                July 2010

      Extensions to the IODEF-Document Class for Reporting Phishing

Abstract

   This document extends the Incident Object Description Exchange Format    (IODEF) defined in RFC 5070 to support the reporting of phishing    events, which is a particular type of fraud.  These extensions are    flexible enough to support information gleaned from activities    throughout the entire electronic fraud cycle -- from receipt of the    phishing lure to the disablement of the collection site.  Both simple    reporting and complete forensic reporting are possible, as is    consolidating multiple incidents.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc5901.

Copyright Notice

   Copyright (c) 2010 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.

Cain & Jevans                Standards Track                    [Page 1]
 RFC 5901                IODEF Phishing Extensions              July 2010

 Table of Contents

   1. Introduction ....................................................3

      1.1. Why a Common Report Format Is Needed .......................3

      1.2. Processing of Exchanged Data Not Defined ...................4

      1.3. Relation to the INCH IO...