You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spot.apache.org by br...@apache.org on 2017/09/14 22:19:58 UTC
[08/15] incubator-spot git commit: edits
edits
Project: http://git-wip-us.apache.org/repos/asf/incubator-spot/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-spot/commit/2d2744d8
Tree: http://git-wip-us.apache.org/repos/asf/incubator-spot/tree/2d2744d8
Diff: http://git-wip-us.apache.org/repos/asf/incubator-spot/diff/2d2744d8
Branch: refs/heads/master
Commit: 2d2744d8c9ef5f6a4b2953beb23186266c2594da
Parents: e481bc1
Author: Brandon Edwards <br...@intel.com>
Authored: Wed Sep 6 10:40:17 2017 -0700
Committer: Brandon Edwards <br...@intel.com>
Committed: Wed Sep 6 10:40:17 2017 -0700
----------------------------------------------------------------------
spot-ml/DATA_SAMPLE.md | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-spot/blob/2d2744d8/spot-ml/DATA_SAMPLE.md
----------------------------------------------------------------------
diff --git a/spot-ml/DATA_SAMPLE.md b/spot-ml/DATA_SAMPLE.md
index 0030138..979da8f 100644
--- a/spot-ml/DATA_SAMPLE.md
+++ b/spot-ml/DATA_SAMPLE.md
@@ -1,13 +1,13 @@
# DNS Labeled Data Set
-An IXIA BreakingPoint box was used to simulate both normal and attack (DNS tunnelling) DNS traffic. The resulting pcaps were obtained and fields relevant to Apache Spot (incubating) were injested. The attacks can be differentiated from the normal activity due to codes that were inserted into the Transaction ID field(upon ingestion the field is: ‘dns_id’) which identifies either the fact that the traffic was normal or identifies the specific dns tunneling activity being used. We provide the schema for the injested pcap data as well as the location and specifications of both the raw pcaps and ingested data within Amazon-S3. Information is also provided for how to interpret the Transaction ID codes.
+An IXIA BreakingPoint box was used to simulate both normal and attack (DNS tunnelling) DNS traffic. The resulting pcaps were obtained and fields relevant to Apache Spot (incubating) were injested. The attacks can be differentiated from the normal activity due to codes that were inserted into the Transaction ID field (upon ingestion: ‘dns_id’) which identifies either the fact that the traffic was normal or identifies the specific DNS tunneling activity being used. We provide the schema for the injested pcap data as well as the location and specifications of both the raw pcaps and ingested data within Amazon-S3. Information is also provided for how to interpret the Transaction ID codes.
## Schema For Ingested Data
-The schema for the ingested DNS data includes one field, 'dns_id', in addition to what is usually used for DNS data in Apache Spot (incubating). The schema is as follows:
+The schema for the ingested DNS data includes one field ('dns_id') in addition to what is usually used for DNS data in Apache Spot (incubating). The schema is as follows:
| Name | Type |
@@ -27,19 +27,19 @@ The schema for the ingested DNS data includes one field, 'dns_id', in addition t
## Transaction ID Interpretations
Each value of the transaction ID ('dns_id' in the ingested data) indicates that either the data row was taken from a packet capture of simulated normal DNS traffic, or from a packet capture of a particular type of simulated DNS tunnelling.
-Within BreakingPoint, Transaction IDs are represented as a decimal number. However, tshark dissects the transaction ID in its hexadecimal representation(the format contained within parenthesis in the table below).
+Within BreakingPoint, Transaction IDs are represented as a decimal number. However, tshark dissects the transaction ID in its hexadecimal representation (the format contained within parenthesis in the table below).
-Within Apache Spot(incubating) only responses from DNS servers are ingested since the response packet contains the query made by the client and the response from the server in the same packet.
+Within Apache Spot (incubating), only responses from DNS servers are ingested since the response packet contains the query made by the client and the response from the server in the same packet.
-| Super Flow Name | Transaction IDs | Description |
+| Super Flow Name | Transaction ID | Description |
|---------------------------|:------------------:|-------------|
-| Brandon_DNS_domain_Test | 1008 (0x000003f0) | [Normal] This super flow simulates normal DNS queries distributed over time and IP address within the network.|
+| Brandon_DNS_domain_Test | 1008 (0x000003f0) | [Normal] This super flow simulates normal DNS queries.|
| DNS_Tunnel_BE_1 | 1002 (0x000003ea) | [Attack] This super flow simulates a message being tunneled over DNS via the query name field (url's are random strings), with a ip address response (drawn from a file of randomly generated IPs) being sent via the DNS answer field. |
| DNS_Tunnel_BE_2 | 1003 (0x000003eb}) | [Attack] This super flow simulates a message being tunneled over DNS via the query name field (url's random strings), with a response being given as no such url found. |
-| TCP_DNS_Tunnel_BE_1 | 1001 (0x000003e9) | [Attack] This super Flow emulates tunneling random noise using TCP over DNS. The payload is generated by a Markov Dictionary and encoded in the DNS requests (responses) by using hex0x20Hack encoding. |
-| TCP_DNS_Tunnel_BE_2 | 1005 (0x000003ed) | [Attack] This super Flow emulates tunneling random noise using TCP over DNS. The payload is generated by a Markov Dictionary and encoded in the DNS requests (responses) by using Base16Alpha encoding. |
-| TCP_DNS_Tunnel_BE_3 | 1007 (0x000003ef) | [Attack] This super Flow emulates tunneling random noise using TCP over DNS. The payload is generated by a Markov Dictionary and encoded in the DNS requests (responses) by using Base63 encoding. |
+| TCP_DNS_Tunnel_BE_1 | 1001 (0x000003e9) | [Attack] This super Flow simulates tunneling random noise using TCP over DNS. The payload is generated by a Markov Dictionary and encoded in the DNS requests (responses) by using hex0x20Hack encoding. |
+| TCP_DNS_Tunnel_BE_2 | 1005 (0x000003ed) | [Attack] This super Flow simulates tunneling random noise using TCP over DNS. The payload is generated by a Markov Dictionary and encoded in the DNS requests (responses) by using Base16Alpha encoding. |
+| TCP_DNS_Tunnel_BE_3 | 1007 (0x000003ef) | [Attack] This super Flow simulates tunneling random noise using TCP over DNS. The payload is generated by a Markov Dictionary and encoded in the DNS requests (responses) by using Base63 encoding. |
## Data Sets