-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
23 additions
and
13 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,19 +1,29 @@ | ||
# B-Root Anomalies | ||
|
||
This folder contains labeling program for B-Root anomalies dataset. | ||
This folder contains labeling program for anomalies datasets that | ||
start with the prefix /B_Root_anomaly-/. The `tag` tool in this | ||
directory can be used to analyze each of the dataset's file according | ||
to each dataset's README.md file. | ||
|
||
## Creating the tool | ||
|
||
Run: | ||
``` | ||
make | ||
``` | ||
to create `tag` executable. There are | ||
several folders, containing information on how to use `tag` executable | ||
with the original data to produce record-level tags. | ||
The record-level labels look like: | ||
``` | ||
recordID label | ||
``` | ||
where recordID looks like: | ||
``` | ||
timestamp-sourceIP-sourceport-destIP-destport | ||
``` | ||
and label can be A (attack) or B (benign) | ||
to create `tag` executable. | ||
|
||
## Using the tool | ||
|
||
Each dataset contains a README.md file containing information on how | ||
to use `tag` executable with the original data to produce record-level | ||
tags. The record-level labels that `tag` generated are of the | ||
following format: | ||
|
||
recordID label | ||
|
||
where `recordID` is of the form: | ||
|
||
timestamp-sourceIP-sourceport-destIP-destport | ||
|
||
and `label` is either the letter A (attack) or the letter B (benign). |