I am trying to add DB support to Audit. What kind of DB support is expected &amp; would be most useful. Should it be on the basis of <br>1.) Ranges of netlink messages , ie.<br><pre><b><i> * 000 - 1099 are for commanding the audit system
</i></b><br><b><i> * 1100 - 1199 user space trusted application messages</i></b><br><b><i> * 1200 - 1299 messages internal to the audit daemon</i></b><br><a name="L34" href="http://www.gelato.unsw.edu.au/lxr/source/include/linux/audit.h#L34">
</a><b><i> * 1300 - 1399 audit event messages</i></b><br><b><i> * 1400 - 1499 SE Linux use</i></b><br><a name="L36" href="http://www.gelato.unsw.edu.au/lxr/source/include/linux/audit.h#L36"></a><b><i> * 1500 - 1599 kernel LSPP events
</i></b><br><a name="L37" href="http://www.gelato.unsw.edu.au/lxr/source/include/linux/audit.h#L37"></a><b><i> * 1600 - 1699 kernel crypto events</i></b><br><a name="L38" href="http://www.gelato.unsw.edu.au/lxr/source/include/linux/audit.h#L38">
</a><b><i> * 1700 - 1799 kernel anomaly records</i></b><br><a name="L39" href="http://www.gelato.unsw.edu.au/lxr/source/include/linux/audit.h#L39"></a><b><i> * 1800 - 1999 future kernel use (maybe integrity labels and related events)
</i></b></pre><br>nd etc , or<br>2.) The tables should be based on each type of record coming in the logs(which would be a daunting task).<br>Is there any other way i can use the audit logs, and do some classification of the records in an efficient manner in the database as tables? What should be the classification factor for the tables in the DB?
<br><br>Please reply , <br>Thanking You,<br>Mukul Khullar.<br>