Dataset Open Access

# AIT Log Data Set V1.1

Landauer Max; Skopik Florian; Wurzenberger Markus; Hotwagner Wolfgang; Rauber Andreas

### Citation Style Language JSON Export

{
"publisher": "Zenodo",
"DOI": "10.5281/zenodo.4264796",
"title": "AIT Log Data Set V1.1",
"issued": {
"date-parts": [
[
2020,
11,
9
]
]
},
"abstract": "<p><strong>AIT Log Data Sets</strong></p>\n\n<p>This repository contains synthetic log data suitable for evaluation of intrusion detection systems. The logs were collected from four independent testbeds that were built at the Austrian Institute of Technology (AIT) following the approach by Landauer et al. (2020) [1]. Please refer to the paper for more detailed information on automatic testbed generation and cite it if the data is used for academic publications. In brief, each testbed simulates user accesses to a webserver that runs Horde Webmail and OkayCMS. The duration of the simulation is six days. On the fifth day (2020-03-04) two attacks are launched against each web server.</p>\n\n<p>The archive AIT-LDS-v1_0.zip contains the directories &quot;data&quot; and &quot;labels&quot;.</p>\n\n<p>The data directory is structured as follows. Each directory mail.&lt;name&gt;.com contains the logs of one web server. Each directory user-&lt;ID&gt; contains the logs of one user host machine, where one or more users are simulated. Each file log&lt;UID&gt;.log in the user-&lt;ID&gt; directories contains the activity logs of one particular user.</p>\n\n<p>Setup details of the web servers:</p>\n\n<ul>\n\t<li>OS: Debian Stretch 9.11.6</li>\n\t<li>Services:\n\t<ul>\n\t\t<li>Apache2</li>\n\t\t<li>PHP7</li>\n\t\t<li>Exim 4.89</li>\n\t\t<li>Horde 5.2.22</li>\n\t\t<li>OkayCMS 2.3.4</li>\n\t\t<li>Suricata</li>\n\t\t<li>ClamAV</li>\n\t\t<li>MariaDB</li>\n\t</ul>\n\t</li>\n</ul>\n\n<p>Setup details of user machines:</p>\n\n<ul>\n\t<li>OS: Ubuntu Bionic</li>\n\t<li>Services:\n\t<ul>\n\t\t<li>Chromium</li>\n\t\t<li>Firefox</li>\n\t</ul>\n\t</li>\n</ul>\n\n<p>User host machines are assigned to web servers in the following way:</p>\n\n<ul>\n\t<li>mail.cup.com is accessed by users from host machines user-{0, 1, 2, 6}</li>\n\t<li>mail.spiral.com is accessed by users from host machines user-{3, 5, 8}</li>\n\t<li>mail.insect.com is accessed by users from host machines user-{4, 9}</li>\n\t<li>mail.onion.com is accessed by users from host machines user-{7, 10}</li>\n</ul>\n\n<p>The following attacks are launched against the web servers (different starting times for each web server, please check the labels for exact attack times):</p>\n\n<ul>\n\t<li>Attack 1: multi-step attack with sequential execution of the following attacks:\n\t<ul>\n\t\t<li>nmap scan</li>\n\t\t<li>nikto scan</li>\n\t\t<li>smtp-user-enum tool for account enumeration</li>\n\t\t<li>hydra brute force login</li>\n\t\t<li>webshell upload through Horde exploit (CVE-2019-9858)</li>\n\t\t<li>privilege escalation through Exim exploit (CVE-2019-10149)</li>\n\t</ul>\n\t</li>\n\t<li>Attack 2: webshell injection through malicious cookie (CVE-2019-16885)</li>\n</ul>\n\n<p>Attacks are launched from the following user host machines. In each of the corresponding directories user-&lt;ID&gt;, logs of the attack execution are found in the file attackLog.txt:</p>\n\n<ul>\n\t<li>user-6 attacks mail.cup.com</li>\n\t<li>user-5 attacks mail.spiral.com</li>\n\t<li>user-4 attacks mail.insect.com</li>\n\t<li>user-7 attacks mail.onion.com</li>\n</ul>\n\n<p>The log data collected from the web servers includes</p>\n\n<ul>\n\t<li>&nbsp;Apache access and error logs</li>\n\t<li>&nbsp;syscall logs collected with the Linux audit daemon</li>\n\t<li>&nbsp;suricata logs</li>\n\t<li>&nbsp;exim logs</li>\n\t<li>&nbsp;auth logs</li>\n\t<li>&nbsp;daemon logs</li>\n\t<li>&nbsp;mail logs</li>\n\t<li>&nbsp;syslogs</li>\n\t<li>&nbsp;user logs</li>\n</ul>\n\n<p>&nbsp;<br>\nNote that due to their large size, the audit/audit.log files of each server were compressed in a .zip-archive. In case that these logs are needed for analysis, they must first be unzipped.<br>\n&nbsp;<br>\nLabels are organized in the same directory structure as logs. Each file contains two labels for each log line separated by a comma, the first one based on the occurrence time, the second one based on similarity and ordering. Note that this does not guarantee correct labeling for all lines and that no manual corrections were conducted.</p>\n\n<p><em>Version history:</em></p>\n\n<ul>\n\t<li>AIT-LDS-v1_0.zip: Initial version of data set.</li>\n\t<li>AIT-LDS-v1_1.zip: Removed carriage return of line endings in audit.log files.</li>\n</ul>\n\n<p>[1] <a href=\"https://ieeexplore.ieee.org/document/9262078\">M. Landauer, F. Skopik, M. Wurzenberger, W. Hotwagner and A. Rauber, &quot;Have it Your Way: Generating Customized Log Datasets With a Model-Driven Simulation Testbed,&quot; in IEEE Transactions on Reliability, vol. 70, no. 1, pp. 402-415, March 2021, doi: 10.1109/TR.2020.3031317.</a></p>",
"author": [
{
"family": "Landauer Max"
},
{
"family": "Skopik Florian"
},
{
"family": "Wurzenberger Markus"
},
{
"family": "Hotwagner Wolfgang"
},
{
"family": "Rauber Andreas"
}
],
"note": "Additionally funded by the FFG projects INDICAETING (868306) and DECEPT (873980).",
"version": "v1_1",
"type": "dataset",
"id": "4264796"
}
1,858
4,542
views