<node id="51421">
  <nid>51421</nid>
  <type>news</type>
  <uid>
    <user id="27154"><![CDATA[27154]]></user>
  </uid>
  <created>1265751834</created>
  <changed>1475895889</changed>
  <title><![CDATA[GTISC and ARC Researchers Collaborate to Develop Next-Generation Spam Filters]]></title>
  <body><![CDATA[<p>Graduate student Anirudh Ramachandran's work on filtering spam using<br />
network-level properties will appear at the ACM Conference on Computer<br />
and Communications Security (CCS), ACM's top security conference, at<br />
the end of October.  Ramachandran and his advisor, Assistant Professor<br />
Nick Feamster, have been working with Professor Santosh Vempala to<br />
develop next-generation spam filtering techniques.</p>
<p>Spam is becoming increasingly virulent as it makes use of images and<br />
PDFs to evade content-based filters.  To make matters worse, spammers<br />
are sending spam from "fresh" machines every day, which makes it<br />
difficult to maintain static blacklists of known bad senders.  </p>
<p>To get a step ahead, the researchers have taken a different approach:<br />
<br />
rather than filtering spam based on content or an ephemeral identity of<br />
the sender (e.g., an IP address), the researchers have invented a new<br />
technique called "behavioral blacklisting".  Behavioral blacklisting<br />
aims to learn and "fingerprint" spammers' sending patterns---for<br />
example, the set of recipients a particular sender is targeting---and<br />
blacklist senders based on their sending behavior, rather than a fixed<br />
identity.</p>
<p>The researchers developed their first behavioral blacklisting technique<br />
by applying Professor Vempala's novel spectral clustering algorithms,<br />
which have also successfully been applied to other areas (e.g., Web<br />
search).</p>
<p><a href="http://www.cc.gatech.edu/~avr/publications/ccs07.pdf">You can read the paper here.</a></p>
<p></p>]]></body>
  <field_subtitle>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_subtitle>
  <field_dateline>
    <item>
      <value>2007-08-24T00:00:00-04:00</value>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_dateline>
  <field_summary_sentence>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[<p>Graduate student Anirudh Ramachandran's work on filtering spam using network-level properties will appear at the ACM Conference on Computer and Communications Security (CCS), ACM's top security conference, at the end of October.<br /></p>]]></value>
    </item>
  </field_summary>
  <field_media>
      </field_media>
  <field_contact_email>
    <item>
      <email><![CDATA[]]></email>
    </item>
  </field_contact_email>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_contact>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_contact>
  <field_sidebar>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_sidebar>
  <field_boilerplate>
    <item>
      <nid><![CDATA[]]></nid>
    </item>
  </field_boilerplate>
  <!--  TO DO: correct to not conflate categories and news room topics  -->
  <!--  Disquisition: it's funny how I write these TODOs and then never
         revisit them. It's as though the act of writing the thing down frees me
         from the responsibility to actually solve the problem. But what can I
         say? There are more problems than there's time to solve.  -->
  <links_related> </links_related>
  <files> </files>
  <og_groups>
          <item>47223</item>
      </og_groups>
  <og_groups_both>
      </og_groups_both>
  <field_categories>
      </field_categories>
  <core_research_areas>
      </core_research_areas>
  <field_news_room_topics>
      </field_news_room_topics>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>47223</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[College of Computing]]></item>
      </og_groups_both>
  <field_keywords>
      </field_keywords>
  <field_userdata><![CDATA[]]></field_userdata>
</node>
