Create README.md
Browse files
README.md
ADDED
|
@@ -0,0 +1,30 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
Raw network data was collected over a period of 5 days, Monday through Friday, and stored in PCAP files.
|
| 2 |
+
Monday was used to create most of the Benign data, while the Attack-Network implemented various types of attacks over the next 4 days,
|
| 3 |
+
such as Brute Force connections (FTP and SSH), several types of DoS attacks, as well as a Botnet attack, Infiltration attacks and subsequent Port-Scanning activity.
|
| 4 |
+
|
| 5 |
+
The PCAP data was processed using a tool developed by one of the authors of [1], called CICFlowMeter [3].
|
| 6 |
+
This tool produces flow traces: sequences of packets between specific source and destination IP, with corresponding values for source and destination ports.
|
| 7 |
+
TCP flows are usually terminated by connection teardowns, while UDP flows are terminated by a flow timeout.
|
| 8 |
+
For each of these flow traces many features were selected, measuring flow characteristics, such as packet size, number of packets, flow duration, etc.
|
| 9 |
+
For some of these variables, statistics such as their mean and standard deviations are provided as features as well.
|
| 10 |
+
While several features are categorical (such as IP addresses, Port numbers and TCP flag counts), most of the other features are numerical.
|
| 11 |
+
|
| 12 |
+
The result is the CICIDS-2017 dataset, with about 80 features and several attack families which can ultimately be divided in 16 categories:
|
| 13 |
+
one Benign category and 15 Attack categories. This original dataset is available at [4]. Subsequently, the authors of [2] spent a lot of effort
|
| 14 |
+
to correct some errors in the dataset, by fixing the CICFlowMeter software (especially regarding TCP flow terminations) and by
|
| 15 |
+
re-labeling some of the samples accordingly. They posted the corrected dataset on their website [5];
|
| 16 |
+
this also has links to their GitHub site, which provides Python code that can be used to efficiently import the data.
|
| 17 |
+
I used that as a starting point for my notebook, here on Kaggle.
|
| 18 |
+
|
| 19 |
+
For each of the 5 days a csv file with network flows was produced.
|
| 20 |
+
|
| 21 |
+
These are the files in the dataset, with some changes: I created decimal values for the IP-addresses, and I removed a couple of rows with inf vales.
|
| 22 |
+
|
| 23 |
+
|
| 24 |
+
[1] Sharafaldin I., Lashkari A.H., and Ghorbani A.A. Toward generating a new intrusion detection dataset and intrusion traffic characterization, Proceedings of the 4th International Conference on Information Systems Security and Privacy ICISSP - Volume 1, 108-116, 2018.
|
| 25 |
+
[2] Engelen G., Rimmer V., and Joosen W. Troubleshooting an intrusion detection dataset: the CICIDS2017 case study, 2021 IEEE Security and Privacy Workshops (SPW), 2021:7-12.
|
| 26 |
+
[3] https://www.unb.ca/cic/research/applications.html
|
| 27 |
+
[4] https://www.unb.ca/cic/datasets/ids-2017.html
|
| 28 |
+
[5] https://intrusion-detection.distrinet-research.be/CNS2022/index.html
|
| 29 |
+
|
| 30 |
+
|