Update README.md
Browse files
README.md
CHANGED
@@ -1,31 +1,49 @@
|
|
1 |
---
|
2 |
license: cc-by-4.0
|
3 |
-
|
4 |
configs:
|
5 |
- config_name: 1024-unrolled
|
6 |
data_files:
|
7 |
- split: train
|
8 |
-
path:
|
9 |
- split: valid
|
10 |
-
path:
|
11 |
- split: test
|
12 |
-
path:
|
13 |
-
|
14 |
- config_name: 2048-unrolled
|
15 |
data_files:
|
16 |
- split: train
|
17 |
-
path:
|
18 |
- split: valid
|
19 |
-
path:
|
20 |
- split: test
|
21 |
-
path:
|
22 |
-
|
23 |
- config_name: 4096-unrolled_n
|
24 |
data_files:
|
25 |
- split: train
|
26 |
-
path:
|
27 |
- split: valid
|
28 |
-
path:
|
29 |
- split: test
|
30 |
-
path:
|
|
|
|
|
|
|
|
|
|
|
31 |
---
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
---
|
2 |
license: cc-by-4.0
|
|
|
3 |
configs:
|
4 |
- config_name: 1024-unrolled
|
5 |
data_files:
|
6 |
- split: train
|
7 |
+
path: 1024-unrolled/*train*.tar
|
8 |
- split: valid
|
9 |
+
path: 1024-unrolled/*valid*.tar
|
10 |
- split: test
|
11 |
+
path: 1024-unrolled/*test*.tar
|
|
|
12 |
- config_name: 2048-unrolled
|
13 |
data_files:
|
14 |
- split: train
|
15 |
+
path: 2048-unrolled/*train*.tar
|
16 |
- split: valid
|
17 |
+
path: 2048-unrolled/*valid*.tar
|
18 |
- split: test
|
19 |
+
path: 2048-unrolled/*test*.tar
|
|
|
20 |
- config_name: 4096-unrolled_n
|
21 |
data_files:
|
22 |
- split: train
|
23 |
+
path: 4096-unrolled_n/*train*.tar
|
24 |
- split: valid
|
25 |
+
path: 4096-unrolled_n/*valid*.tar
|
26 |
- split: test
|
27 |
+
path: 4096-unrolled_n/*test*.tar
|
28 |
+
task_categories:
|
29 |
+
- image-classification
|
30 |
+
- image-segmentation
|
31 |
+
size_categories:
|
32 |
+
- 1K<n<10K
|
33 |
---
|
34 |
+
|
35 |
+
# COSOCO: Compromised Software Containers Image Dataset
|
36 |
+
|
37 |
+
COSOCO (Compromised Software Containers) is a synthetic dataset of 3364 images representing benign
|
38 |
+
and malware-compromised software containers. Each image in the dataset represents a dockerized
|
39 |
+
software container that has been converted to an image using common byte-to-pixel tools widely used
|
40 |
+
in malware analysis. Software container records are labelled (1) **benign** or (2) **compromised**:
|
41 |
+
A benign software container will have installed commonly used harmless packages and tools, whereas
|
42 |
+
a compromised software container, will have, among harmless benign tools and packages, its underlying
|
43 |
+
file system affected by some activated malware instance. Each compromised instance is accompanied by
|
44 |
+
a mask, i.e. a black and white image which marks the pixels that correspond to the files of the
|
45 |
+
underlying system that have been altered by a malware.
|
46 |
+
|
47 |
+
COSOCO aims to support the identification of compromised software containers via the task of image
|
48 |
+
classification task and the identification of compromised files and file system regions inside a
|
49 |
+
container via the image segmentation task.
|