<?xml version="1.0" standalone="no"?>
                    <!DOCTYPE div SYSTEM "/www/backend/www-xml-443/dtd/caidaML.dtd">
                    <!-- do NOT ERASE the DOCTYPE declaration! --><div>


<tr bgcolor="#f4f4f4">
  <td>
<font face="helvetica,arial" size="2">
<b>URL:</b>
</font>
</td>
  <td>
<font face="helvetica,arial" size="2">
<a href="http://laim.ncsa.uiuc.edu/downloads/slagell06.pdf">http://laim.ncsa.uiuc.edu/downloads/slagell06.pdf</a>
</font>
  </td>
</tr>


<tr bgcolor="#e9e9e9">
  <td>
<font face="helvetica,arial" size="2">
<b>ENTRY DATE:</b>
</font>
</td>
  <td>
<font face="helvetica,arial" size="2">
2008-06-16


</font>
  </td>
</tr>


<tr bgcolor="#f4f4f4">
  <td>
<font face="helvetica,arial" size="2">
<b>ABSTRACT:</b>
</font>
</td>
  <td>
<font face="helvetica,arial" size="2">
FLAIM (Framework for Log Anonymization and Information Management)
addresses two important needs not well addressed by current log
anonymizers. First, it is extremely modular and not tied to the specific
log being anonymized. Second, it supports multi-level anonymization,
allowing system administrators to make fine-grained trade-offs between
information loss and privacy/security concerns. In this paper, we
examine anonymization solutions to date and note the above limitations
in each. We further describe how FLAIM addresses these problems, and we
describe FLAIM's architecture and features in detail.




</font>
  </td>
</tr>
</div>

