---
title: NEW_ENTRY_NAME
---

- [Overview](#overview)
- [Environment](#environment)
- [Activity](#activity)
- [Contained Data](#contained-data)
- [Papers](#papers)
- [Links](#links)
- [Data Examples](#data-examples)

| <!-- -->                 | <!-- --> |
|--------------------------|----------|
| **Network Data Source**  |          |
| **Network Data Labeled** |          |
| **Host Data Source**     |          |
| **Host Data Labeled**    |          |
|                          |          |
| **Overall Setting**      |          |
| **OS Types**             |          |
| **Number of Machines**   |          |
| **Total Runtime**        |          |
| **Year of Collection**   |          |
| **Attack Categories**    |          |
| **User Emulation**       |          |
|                          |          |
| **Packed Size**          |          |
| **Unpacked Size**        |          |
| **Download Link**        |          |

***

### Overview
A general description of the dataset, giving a brief overview over origin, intended usage and some properties of the dataset.

### Environment
A description of the environment the dataset originated from, including networks, operating systems, running services, etc.

### Activity
What kind of activity, benign and malicious, was performed during the period of data collection.

### Contained Data
What kind of data was collected and how it is present in the dataset, including any processing and labeling.

### Papers
- List of related papers, ideally as DOI links

### Links
- List of related links, such as homepages and download sources

### Data Examples
Snippet from the dataset, ideally one for each data type.
Note that multi-word annotations (like `json lines`) will not render properly on GitHub Pages.
Wrapping these snippets with `raw`/`endraw` is not strictly required, but prevents Liquid from parsing anything it shouldn't.

<!--  {% raw %} -->
```
data example
```
<!--  {% endraw %} -->