Flow ID stringlengths 33 43 | event_types stringlengths 8 788 | log_text stringlengths 272 41.3k | alerted bool 2
classes | Label stringclasses 14
values | truth bool 2
classes | Day stringclasses 5
values | num_tokens int64 119 18.7k | row int64 554 1.34M | classification stringclasses 2
values | justification stringclasses 14
values | response stringclasses 14
values |
|---|---|---|---|---|---|---|---|---|---|---|---|
172.16.0.1-41922-192.168.10.50-6003-6 | ['flow'] | src_ip: 172.16.0.1, src_port: 41922, dest_ip: 192.168.10.50, dest_port: 6003, event_type: flow, proto: TCP, flow_pkts_toserver: 1, flow_pkts_toclient: 1, flow_bytes_toserver: 74, flow_bytes_toclient: 60, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 16, tcp_tcp_flags_ts: 02, tcp_tcp_flags_tc: 14... | false | Portscan | true | Friday | 180 | 1,021,250 | Attack | The network event indicates a Portscan. Portscans involve scanning multiple ports on a target machine to identify open ports and services. Typically, the logs show multiple short-lived connection attempts from the same source IP to different destination ports. These connections are characterized by SYN, RST, and ACK fl... | classification: Attack
justification: The network event indicates a Portscan. Portscans involve scanning multiple ports on a target machine to identify open ports and services. Typically, the logs show multiple short-lived connection attempts from the same source IP to different destination ports. These connections are... |
172.16.0.1-57536-192.168.10.50-21-6 | ['flow', 'ftp', 'ftp', 'ftp', 'ftp', 'ftp', 'ftp', 'ftp', 'ftp'] | src_ip: 172.16.0.1, src_port: 57536, dest_ip: 192.168.10.50, dest_port: 21, event_type: flow, proto: TCP, app_proto: ftp, flow_pkts_toserver: 11, flow_pkts_toclient: 17, flow_bytes_toserver: 848, flow_bytes_toclient: 1306, flow_age: 9, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1b, t... | false | FTP-Patator | true | Tuesday | 947 | 253,635 | Attack | The network event indicates a FTP-Patator. FTP-Patator attacks involve brute force attempts to gain access to an FTP server. Typically, the logs show multiple login attempts from the same source IP to the FTP server, often with varied credentials. This pattern of behavior is consistent with brute force attacks aiming t... | classification: Attack
justification: The network event indicates a FTP-Patator. FTP-Patator attacks involve brute force attempts to gain access to an FTP server. Typically, the logs show multiple login attempts from the same source IP to the FTP server, often with varied credentials. This pattern of behavior is consis... |
192.168.10.17-49327-172.217.6.195-443-6 | ['flow', 'tls'] | src_ip: 192.168.10.17, src_port: 49327, dest_ip: 172.217.6.195, dest_port: 443, event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 34, flow_pkts_toclient: 31, flow_bytes_toserver: 3431, flow_bytes_toclient: 21141, flow_age: 117, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_t... | false | BENIGN | false | Thursday | 253 | 774,628 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
192.168.10.5-54211-172.217.12.142-443-6 | ['flow', 'tls'] | src_ip: 192.168.10.5, src_port: 54211, dest_ip: 172.217.12.142, dest_port: 443, event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 19, flow_pkts_toclient: 15, flow_bytes_toserver: 1793, flow_bytes_toclient: 4956, flow_age: 181, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts... | false | BENIGN | false | Friday | 419 | 1,284,063 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
172.16.0.1-51118-192.168.10.50-22-6 | ['flow', 'ssh'] | src_ip: 172.16.0.1, src_port: 51118, dest_ip: 192.168.10.50, dest_port: 22, event_type: flow, proto: TCP, app_proto: ssh, flow_pkts_toserver: 23, flow_pkts_toclient: 34, flow_bytes_toserver: 3534, flow_bytes_toclient: 4997, flow_age: 12, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1b,... | false | SSH-Patator | true | Tuesday | 810 | 250,368 | Attack | The network event indicates a SSH-Patator. SSH-Patator attacks involve brute force attempts to gain access to an SSH server. Typically, the logs show multiple login attempts from the same source IP to the SSH server, often with varied credentials. This pattern of behavior is consistent with brute force attacks aiming t... | classification: Attack
justification: The network event indicates a SSH-Patator. SSH-Patator attacks involve brute force attempts to gain access to an SSH server. Typically, the logs show multiple login attempts from the same source IP to the SSH server, often with varied credentials. This pattern of behavior is consis... |
192.168.10.9-5394-23.60.139.27-80-6 | ['flow', 'http', 'fileinfo', 'fileinfo', 'http', 'fileinfo', 'fileinfo', 'fileinfo', 'http'] | src_ip: 192.168.10.9, src_port: 5394, dest_ip: 23.60.139.27, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 12, flow_pkts_toclient: 11, flow_bytes_toserver: 1998, flow_bytes_toclient: 6535, flow_age: 29, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1b... | false | BENIGN | false | Tuesday | 1,535 | 446,769 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
172.16.0.1-38172-192.168.10.50-80-6 | ['flow', 'http', 'fileinfo'] | src_ip: 172.16.0.1, src_port: 38172, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 7, flow_pkts_toclient: 6, flow_bytes_toserver: 440, flow_bytes_toclient: 11943, flow_age: 6, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, t... | false | DDoS | true | Friday | 391 | 997,030 | Attack | The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. These connections are characterized by rep... | classification: Attack
justification: The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. Thes... |
192.168.10.25-52676-172.217.6.194-443-6 | ['flow', 'tls'] | src_ip: 192.168.10.25, src_port: 52676, dest_ip: 172.217.6.194, dest_port: 443, event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 15, flow_pkts_toclient: 10, flow_bytes_toserver: 1677, flow_bytes_toclient: 6362, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: ... | false | BENIGN | false | Friday | 258 | 1,266,819 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
172.16.0.1-46532-192.168.10.50-80-6 | ['flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'http', 'fileinfo', 'http', 'fileinfo', 'http', 'http', 'http', 'fileinfo', 'http', 'http', 'http', 'http', 'http', 'http', 'fileinfo'] | src_ip: 172.16.0.1, src_port: 46532, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 6, flow_pkts_toclient: 6, flow_bytes_toserver: 752, flow_bytes_toclient: 11999, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1e, tcp_tcp_flags_ts: 1e, t... | false | DoS Hulk | true | Wednesday | 4,433 | 465,856 | Attack | The network event indicates a DoS Hulk. DoS Hulk attacks involve sending a high frequency of HTTP requests to overwhelm the target server. Typically, the logs show multiple connection attempts from the same source IP to the same destination IP, with each connection being short-lived and frequently timed out. These conn... | classification: Attack
justification: The network event indicates a DoS Hulk. DoS Hulk attacks involve sending a high frequency of HTTP requests to overwhelm the target server. Typically, the logs show multiple connection attempts from the same source IP to the same destination IP, with each connection being short-live... |
192.168.10.17-54176-31.13.66.36-443-6 | ['flow', 'tls'] | src_ip: 192.168.10.17, src_port: 54176, dest_ip: 31.13.66.36, dest_port: 443, event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 30, flow_pkts_toclient: 23, flow_bytes_toserver: 3277, flow_bytes_toclient: 17030, flow_age: 181, flow_state: closed, flow_reason: timeout, metadata_flowbits_0: ETPRO.Lazarus1,... | false | BENIGN | false | Wednesday | 293 | 566,405 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
192.168.10.8-51004-192.168.10.3-53-17 | ['flow', 'flow', 'flow', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns'] | src_ip: 192.168.10.8, src_port: 51004, dest_ip: 192.168.10.3, dest_port: 53, event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 164, flow_bytes_toclient: 286, flow_age: 0, flow_state: established, flow_reason: timeout ; event_type: flow, proto: UDP, app_prot... | false | BENIGN | false | Monday | 2,504 | 211,319 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
172.16.0.1-24085-192.168.10.50-80-6 | ['flow', 'http'] | src_ip: 172.16.0.1, src_port: 24085, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 7, flow_pkts_toclient: 5, flow_bytes_toserver: 440, flow_bytes_toclient: 11889, flow_age: 2, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, t... | false | DDoS | true | Friday | 251 | 951,949 | Attack | The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. These connections are characterized by rep... | classification: Attack
justification: The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. Thes... |
172.16.0.1-50252-192.168.10.50-80-6 | ['flow', 'flow', 'flow', 'flow', 'http', 'http', 'fileinfo', 'http', 'fileinfo', 'http'] | src_ip: 172.16.0.1, src_port: 50252, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 7, flow_pkts_toclient: 5, flow_bytes_toserver: 440, flow_bytes_toclient: 11883, flow_age: 4, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1e, tcp_tcp_flags_ts: 1e, t... | false | DDoS | true | Friday | 1,157 | 1,067,196 | Attack | The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. These connections are characterized by rep... | classification: Attack
justification: The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. Thes... |
192.168.10.9-4302-205.174.165.73-8080-6 | ['flow', 'http'] | src_ip: 192.168.10.9, src_port: 4302, dest_ip: 205.174.165.73, dest_port: 8080, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 5, flow_pkts_toclient: 4, flow_bytes_toserver: 494, flow_bytes_toclient: 368, flow_age: 0, flow_state: closed, flow_reason: timeout, metadata_flowbits_0: http.dottedquadhost... | true | Botnet | true | Friday | 362 | 1,321,486 | Attack | The network event indicates a Botnet. Botnet activities involve coordinated attacks from multiple compromised machines. Typically, the logs show traffic patterns indicative of control and command communication between the compromised machines and the command server. High volumes of data transfer, frequent anomalies, an... | classification: Attack
justification: The network event indicates a Botnet. Botnet activities involve coordinated attacks from multiple compromised machines. Typically, the logs show traffic patterns indicative of control and command communication between the compromised machines and the command server. High volumes of... |
172.16.0.1-51390-192.168.10.50-5002-6 | ['flow'] | src_ip: 172.16.0.1, src_port: 51390, dest_ip: 192.168.10.50, dest_port: 5002, event_type: flow, proto: TCP, flow_pkts_toserver: 1, flow_pkts_toclient: 1, flow_bytes_toserver: 74, flow_bytes_toclient: 60, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 16, tcp_tcp_flags_ts: 02, tcp_tcp_flags_tc: 14... | false | Portscan | true | Friday | 180 | 1,071,590 | Attack | The network event indicates a Portscan. Portscans involve scanning multiple ports on a target machine to identify open ports and services. Typically, the logs show multiple short-lived connection attempts from the same source IP to different destination ports. These connections are characterized by SYN, RST, and ACK fl... | classification: Attack
justification: The network event indicates a Portscan. Portscans involve scanning multiple ports on a target machine to identify open ports and services. Typically, the logs show multiple short-lived connection attempts from the same source IP to different destination ports. These connections are... |
172.16.0.1-56276-192.168.10.50-80-6 | ['flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'http', 'http', 'http', 'http'] | src_ip: 172.16.0.1, src_port: 56276, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 9, flow_pkts_toclient: 5, flow_bytes_toserver: 560, flow_bytes_toclient: 11895, flow_age: 1, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, t... | false | DDoS | true | Friday | 1,074 | 1,104,154 | Attack | The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. These connections are characterized by rep... | classification: Attack
justification: The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. Thes... |
192.168.10.8-60817-192.168.10.17-5566-6 | ['flow'] | src_ip: 192.168.10.8, src_port: 60817, dest_ip: 192.168.10.17, dest_port: 5566, event_type: flow, proto: TCP, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 120, flow_bytes_toclient: 120, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 16, tcp_tcp_flags_ts: 02, tcp_tcp_flags_tc... | false | Infiltration | true | Thursday | 180 | 905,911 | Attack | The network event indicates an 'Infiltration' attack. The event shows multiple connection attempts from the same source IP to the same destination IP. These connections are characterized by various TCP flags, such as SYN, FIN, RST, PSH, and ACK, suggesting sophisticated behavior to evade detection and maintain persiste... | classification: Attack
justification: The network event indicates an 'Infiltration' attack. The event shows multiple connection attempts from the same source IP to the same destination IP. These connections are characterized by various TCP flags, such as SYN, FIN, RST, PSH, and ACK, suggesting sophisticated behavior to... |
192.168.10.8-35516-192.168.10.25-89-6 | ['flow'] | src_ip: 192.168.10.8, src_port: 35516, dest_ip: 192.168.10.25, dest_port: 89, event_type: flow, proto: TCP, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 120, flow_bytes_toclient: 120, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 16, tcp_tcp_flags_ts: 02, tcp_tcp_flags_tc: ... | false | Infiltration | true | Thursday | 178 | 851,985 | Attack | The network event indicates an 'Infiltration' attack. The event shows multiple connection attempts from the same source IP to the same destination IP. These connections are characterized by various TCP flags, such as SYN, FIN, RST, PSH, and ACK, suggesting sophisticated behavior to evade detection and maintain persiste... | classification: Attack
justification: The network event indicates an 'Infiltration' attack. The event shows multiple connection attempts from the same source IP to the same destination IP. These connections are characterized by various TCP flags, such as SYN, FIN, RST, PSH, and ACK, suggesting sophisticated behavior to... |
172.16.0.1-41610-192.168.10.50-80-6 | ['flow', 'http', 'fileinfo'] | src_ip: 172.16.0.1, src_port: 41610, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 5, flow_bytes_toserver: 500, flow_bytes_toclient: 11883, flow_age: 12, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1e, tcp_tcp_flags_ts: 1e, ... | false | DDoS | true | Friday | 385 | 1,019,086 | Attack | The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. These connections are characterized by rep... | classification: Attack
justification: The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. Thes... |
192.168.10.19-56563-23.206.162.83-80-6 | ['flow'] | src_ip: 192.168.10.19, src_port: 56563, dest_ip: 23.206.162.83, dest_port: 80, event_type: flow, proto: TCP, flow_pkts_toserver: 5, flow_pkts_toclient: 3, flow_bytes_toserver: 338, flow_bytes_toclient: 214, flow_age: 6, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 13, tcp_tcp_flags_ts: 13, tcp_tcp_flags_tc:... | false | BENIGN | false | Thursday | 178 | 800,240 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
172.16.0.1-14611-192.168.10.50-80-6 | ['flow', 'http', 'fileinfo'] | src_ip: 172.16.0.1, src_port: 14611, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 7, flow_pkts_toclient: 6, flow_bytes_toserver: 440, flow_bytes_toclient: 11943, flow_age: 14, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, ... | false | DDoS | true | Friday | 390 | 942,593 | Attack | The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. These connections are characterized by rep... | classification: Attack
justification: The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. Thes... |
192.168.10.8-60467-192.168.10.9-2710-6 | ['flow'] | src_ip: 192.168.10.8, src_port: 60467, dest_ip: 192.168.10.9, dest_port: 2710, event_type: flow, proto: TCP, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 120, flow_bytes_toclient: 120, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 16, tcp_tcp_flags_ts: 02, tcp_tcp_flags_tc:... | false | Infiltration | true | Thursday | 180 | 904,332 | Attack | The network event indicates an 'Infiltration' attack. The event shows multiple connection attempts from the same source IP to the same destination IP. These connections are characterized by various TCP flags, such as SYN, FIN, RST, PSH, and ACK, suggesting sophisticated behavior to evade detection and maintain persiste... | classification: Attack
justification: The network event indicates an 'Infiltration' attack. The event shows multiple connection attempts from the same source IP to the same destination IP. These connections are characterized by various TCP flags, such as SYN, FIN, RST, PSH, and ACK, suggesting sophisticated behavior to... |
172.16.0.1-53026-192.168.10.50-80-6 | ['flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'anomaly', 'http', 'http', 'http', 'http', 'fileinfo', 'http', 'http', 'http', 'http', 'http', 'fileinfo', 'http', 'http', 'fileinfo', 'http', 'http'] | src_ip: 172.16.0.1, src_port: 53026, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 7, flow_pkts_toclient: 6, flow_bytes_toserver: 814, flow_bytes_toclient: 11999, flow_age: 1, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1e, tcp_tcp_flags_ts: 1e, t... | false | DoS Hulk | true | Wednesday | 4,560 | 469,107 | Attack | The network event indicates a DoS Hulk. DoS Hulk attacks involve sending a high frequency of HTTP requests to overwhelm the target server. Typically, the logs show multiple connection attempts from the same source IP to the same destination IP, with each connection being short-lived and frequently timed out. These conn... | classification: Attack
justification: The network event indicates a DoS Hulk. DoS Hulk attacks involve sending a high frequency of HTTP requests to overwhelm the target server. Typically, the logs show multiple connection attempts from the same source IP to the same destination IP, with each connection being short-live... |
192.168.10.16-21909-192.168.10.3-53-17 | ['flow', 'dns', 'dns', 'dns', 'dns'] | src_ip: 192.168.10.16, src_port: 21909, dest_ip: 192.168.10.3, dest_port: 53, event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 148, flow_bytes_toclient: 288, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 8480704, event_type: dns, p... | false | BENIGN | false | Thursday | 994 | 745,785 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
172.16.0.1-54550-192.168.10.50-80-6 | ['flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'anomaly', 'http', 'http', 'http', 'fileinfo', 'http', 'http', 'http', 'fileinfo', 'http', 'fileinfo', 'http', 'http', 'http', 'http', 'fileinfo', 'http', 'fileinfo', 'http', 'fileinfo', 'http', 'fileinfo'] | src_ip: 172.16.0.1, src_port: 54550, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 14, flow_pkts_toclient: 3, flow_bytes_toserver: 3473, flow_bytes_toclient: 208, flow_age: 103, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1e, tcp_tcp_flags_ts: 1a,... | false | DoS Slowloris | true | Wednesday | 6,054 | 469,869 | Attack | The network event indicates a DoS Slowloris. DoS Slowloris attacks involve sending partial HTTP requests to the target server, keeping connections open as long as possible. Typically, the logs show multiple long-lived connections with minimal data exchange, aiming to exhaust the target server's resources by maintaining... | classification: Attack
justification: The network event indicates a DoS Slowloris. DoS Slowloris attacks involve sending partial HTTP requests to the target server, keeping connections open as long as possible. Typically, the logs show multiple long-lived connections with minimal data exchange, aiming to exhaust the ta... |
192.168.10.19-5210-192.168.10.3-53-17 | ['flow', 'dns', 'dns', 'dns', 'dns'] | src_ip: 192.168.10.19, src_port: 5210, dest_ip: 192.168.10.3, dest_port: 53, event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 154, flow_bytes_toclient: 318, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 6899045, event_type: dns, pr... | false | BENIGN | false | Tuesday | 811 | 351,696 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
172.16.0.1-18451-192.168.10.50-80-6 | ['flow', 'http', 'fileinfo'] | src_ip: 172.16.0.1, src_port: 18451, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 6, flow_bytes_toserver: 500, flow_bytes_toclient: 11943, flow_age: 12, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, ... | false | DDoS | true | Friday | 390 | 946,389 | Attack | The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. These connections are characterized by rep... | classification: Attack
justification: The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. Thes... |
172.16.0.1-55182-192.168.10.50-80-6 | ['flow', 'flow', 'flow', 'flow', 'flow', 'http', 'fileinfo', 'http', 'fileinfo', 'http', 'http', 'http'] | src_ip: 172.16.0.1, src_port: 55182, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 4, flow_bytes_toserver: 500, flow_bytes_toclient: 11829, flow_age: 6, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1e, tcp_tcp_flags_ts: 1e, t... | false | DDoS | true | Friday | 1,371 | 1,097,012 | Attack | The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. These connections are characterized by rep... | classification: Attack
justification: The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. Thes... |
192.168.10.9-4923-43.255.254.20-443-6 | ['flow', 'tls'] | src_ip: 192.168.10.9, src_port: 4923, dest_ip: 43.255.254.20, dest_port: 443, event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 38, flow_pkts_toclient: 45, flow_bytes_toserver: 6048, flow_bytes_toclient: 41504, flow_age: 120, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts:... | false | BENIGN | false | Monday | 427 | 231,198 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
172.16.0.1-35609-192.168.10.50-8291-6 | ['flow'] | src_ip: 172.16.0.1, src_port: 35609, dest_ip: 192.168.10.50, dest_port: 8291, event_type: flow, proto: TCP, flow_pkts_toserver: 1, flow_pkts_toclient: 1, flow_bytes_toserver: 60, flow_bytes_toclient: 60, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 16, tcp_tcp_flags_ts: 02, tcp_tcp_flags_tc: 14... | false | Portscan | true | Friday | 181 | 980,239 | Attack | The network event indicates a Portscan. Portscans involve scanning multiple ports on a target machine to identify open ports and services. Typically, the logs show multiple short-lived connection attempts from the same source IP to different destination ports. These connections are characterized by SYN, RST, and ACK fl... | classification: Attack
justification: The network event indicates a Portscan. Portscans involve scanning multiple ports on a target machine to identify open ports and services. Typically, the logs show multiple short-lived connection attempts from the same source IP to different destination ports. These connections are... |
192.168.10.25-49630-172.217.10.66-443-6 | ['flow', 'tls'] | src_ip: 192.168.10.25, src_port: 49630, dest_ip: 172.217.10.66, dest_port: 443, event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 11, flow_pkts_toclient: 6, flow_bytes_toserver: 1580, flow_bytes_toclient: 1603, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1... | false | BENIGN | false | Monday | 251 | 115,992 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
192.168.10.15-58401-52.17.121.244-443-6 | ['flow', 'tls'] | src_ip: 192.168.10.15, src_port: 58401, dest_ip: 52.17.121.244, dest_port: 443, event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 11, flow_pkts_toclient: 11, flow_bytes_toserver: 1831, flow_bytes_toclient: 7846, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: ... | false | BENIGN | false | Thursday | 473 | 736,172 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
172.16.0.1-39492-192.168.10.50-8093-6 | ['flow'] | src_ip: 172.16.0.1, src_port: 39492, dest_ip: 192.168.10.50, dest_port: 8093, event_type: flow, proto: TCP, flow_pkts_toserver: 1, flow_pkts_toclient: 1, flow_bytes_toserver: 60, flow_bytes_toclient: 60, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 16, tcp_tcp_flags_ts: 02, tcp_tcp_flags_tc: 14... | false | Portscan | true | Friday | 181 | 1,006,933 | Attack | The network event indicates a Portscan. Portscans involve scanning multiple ports on a target machine to identify open ports and services. Typically, the logs show multiple short-lived connection attempts from the same source IP to different destination ports. These connections are characterized by SYN, RST, and ACK fl... | classification: Attack
justification: The network event indicates a Portscan. Portscans involve scanning multiple ports on a target machine to identify open ports and services. Typically, the logs show multiple short-lived connection attempts from the same source IP to different destination ports. These connections are... |
192.168.10.8-62906-192.168.10.15-1328-6 | ['flow'] | src_ip: 192.168.10.8, src_port: 62906, dest_ip: 192.168.10.15, dest_port: 1328, event_type: flow, proto: TCP, flow_pkts_toserver: 2, flow_pkts_toclient: 0, flow_bytes_toserver: 120, flow_bytes_toclient: 0, flow_age: 0, flow_state: new, flow_reason: timeout, tcp_tcp_flags: 02, tcp_tcp_flags_ts: 02, tcp_tcp_flags_tc: 00,... | false | Infiltration | true | Thursday | 166 | 912,520 | Attack | The network event indicates an 'Infiltration' attack. The event shows multiple connection attempts from the same source IP to the same destination IP. These connections are characterized by various TCP flags, such as SYN, FIN, RST, PSH, and ACK, suggesting sophisticated behavior to evade detection and maintain persiste... | classification: Attack
justification: The network event indicates an 'Infiltration' attack. The event shows multiple connection attempts from the same source IP to the same destination IP. These connections are characterized by various TCP flags, such as SYN, FIN, RST, PSH, and ACK, suggesting sophisticated behavior to... |
192.168.10.12-30142-192.168.10.3-53-17 | ['flow', 'dns', 'dns', 'dns', 'dns'] | src_ip: 192.168.10.12, src_port: 30142, dest_ip: 192.168.10.3, dest_port: 53, event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 166, flow_bytes_toclient: 366, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 6742013, event_type: dns, p... | false | BENIGN | false | Wednesday | 1,128 | 477,635 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
172.16.0.1-49598-192.168.10.50-42510-6 | ['flow'] | src_ip: 172.16.0.1, src_port: 49598, dest_ip: 192.168.10.50, dest_port: 42510, event_type: flow, proto: TCP, flow_pkts_toserver: 1, flow_pkts_toclient: 1, flow_bytes_toserver: 74, flow_bytes_toclient: 60, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 16, tcp_tcp_flags_ts: 02, tcp_tcp_flags_tc: 1... | false | Portscan | true | Friday | 180 | 1,064,678 | Attack | The network event indicates a Portscan. Portscans involve scanning multiple ports on a target machine to identify open ports and services. Typically, the logs show multiple short-lived connection attempts from the same source IP to different destination ports. These connections are characterized by SYN, RST, and ACK fl... | classification: Attack
justification: The network event indicates a Portscan. Portscans involve scanning multiple ports on a target machine to identify open ports and services. Typically, the logs show multiple short-lived connection attempts from the same source IP to different destination ports. These connections are... |
192.168.10.51-9345-192.168.10.3-53-17 | ['flow', 'flow', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns'] | src_ip: 192.168.10.51, src_port: 9345, dest_ip: 192.168.10.3, dest_port: 53, event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 156, flow_bytes_toclient: 220, flow_age: 0, flow_state: established, flow_reason: timeout ; event_type: flow, proto: UDP, app_prot... | false | BENIGN | false | Wednesday | 1,678 | 638,941 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
192.168.10.12-51120-91.236.51.44-443-6 | ['flow', 'tls'] | src_ip: 192.168.10.12, src_port: 51120, dest_ip: 91.236.51.44, dest_port: 443, event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 13, flow_pkts_toclient: 9, flow_bytes_toserver: 1387, flow_bytes_toclient: 5388, flow_age: 2, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1f... | false | BENIGN | false | Wednesday | 266 | 490,161 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
192.168.10.8-63810-192.168.10.15-7001-6 | ['flow'] | src_ip: 192.168.10.8, src_port: 63810, dest_ip: 192.168.10.15, dest_port: 7001, event_type: flow, proto: TCP, flow_pkts_toserver: 2, flow_pkts_toclient: 0, flow_bytes_toserver: 120, flow_bytes_toclient: 0, flow_age: 0, flow_state: new, flow_reason: timeout, tcp_tcp_flags: 02, tcp_tcp_flags_ts: 02, tcp_tcp_flags_tc: 00,... | false | Infiltration | true | Thursday | 166 | 917,741 | Attack | The network event indicates an 'Infiltration' attack. The event shows multiple connection attempts from the same source IP to the same destination IP. These connections are characterized by various TCP flags, such as SYN, FIN, RST, PSH, and ACK, suggesting sophisticated behavior to evade detection and maintain persiste... | classification: Attack
justification: The network event indicates an 'Infiltration' attack. The event shows multiple connection attempts from the same source IP to the same destination IP. These connections are characterized by various TCP flags, such as SYN, FIN, RST, PSH, and ACK, suggesting sophisticated behavior to... |
172.16.0.1-55806-192.168.10.50-21-6 | ['flow', 'ftp', 'ftp', 'ftp', 'ftp', 'ftp', 'ftp', 'ftp', 'ftp'] | src_ip: 172.16.0.1, src_port: 55806, dest_ip: 192.168.10.50, dest_port: 21, event_type: flow, proto: TCP, app_proto: ftp, flow_pkts_toserver: 11, flow_pkts_toclient: 17, flow_bytes_toserver: 854, flow_bytes_toclient: 1306, flow_age: 9, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1b, t... | false | FTP-Patator | true | Tuesday | 945 | 252,779 | Attack | The network event indicates a FTP-Patator. FTP-Patator attacks involve brute force attempts to gain access to an FTP server. Typically, the logs show multiple login attempts from the same source IP to the FTP server, often with varied credentials. This pattern of behavior is consistent with brute force attacks aiming t... | classification: Attack
justification: The network event indicates a FTP-Patator. FTP-Patator attacks involve brute force attempts to gain access to an FTP server. Typically, the logs show multiple login attempts from the same source IP to the FTP server, often with varied credentials. This pattern of behavior is consis... |
172.16.0.1-62823-192.168.10.50-80-6 | ['flow', 'flow', 'flow', 'flow', 'http', 'http', 'fileinfo', 'http', 'fileinfo', 'http'] | src_ip: 172.16.0.1, src_port: 62823, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 6, flow_bytes_toserver: 500, flow_bytes_toclient: 11943, flow_age: 2, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, t... | false | DDoS | true | Friday | 1,154 | 1,136,939 | Attack | The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. These connections are characterized by rep... | classification: Attack
justification: The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. Thes... |
192.168.10.19-50637-192.168.10.3-53-17 | ['flow', 'dns', 'dns', 'dns', 'dns'] | src_ip: 192.168.10.19, src_port: 50637, dest_ip: 192.168.10.3, dest_port: 53, event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 144, flow_bytes_toclient: 200, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 6599962, event_type: dns, p... | false | BENIGN | false | Thursday | 715 | 797,302 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
192.168.10.12-28016-192.168.10.3-53-17 | ['flow', 'dns', 'dns', 'dns', 'dns'] | src_ip: 192.168.10.12, src_port: 28016, dest_ip: 192.168.10.3, dest_port: 53, event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 168, flow_bytes_toclient: 288, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9952086, event_type: dns, p... | false | BENIGN | false | Wednesday | 828 | 477,186 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
192.168.10.19-37566-192.168.10.3-53-17 | ['flow', 'dns', 'dns', 'dns', 'dns'] | src_ip: 192.168.10.19, src_port: 37566, dest_ip: 192.168.10.3, dest_port: 53, event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 138, flow_bytes_toclient: 302, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 10342175, event_type: dns, ... | false | BENIGN | false | Tuesday | 803 | 347,461 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
192.168.10.8-64263-192.168.10.3-53-17 | ['flow', 'dns', 'dns', 'dns', 'dns'] | src_ip: 192.168.10.8, src_port: 64263, dest_ip: 192.168.10.3, dest_port: 53, event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 174, flow_bytes_toclient: 344, flow_age: 1, flow_state: established, flow_reason: timeout ; pcap_cnt: 5914173, event_type: dns, pr... | false | BENIGN | false | Monday | 1,146 | 225,853 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
192.168.10.8-56531-23.208.101.109-80-6 | ['flow', 'http'] | src_ip: 192.168.10.8, src_port: 56531, dest_ip: 23.208.101.109, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 17, flow_pkts_toclient: 15, flow_bytes_toserver: 2231, flow_bytes_toclient: 1412, flow_age: 116, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts... | false | BENIGN | false | Wednesday | 474 | 651,991 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
192.168.10.8-50746-192.168.10.19-5822-6 | ['flow'] | src_ip: 192.168.10.8, src_port: 50746, dest_ip: 192.168.10.19, dest_port: 5822, event_type: flow, proto: TCP, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 120, flow_bytes_toclient: 120, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 16, tcp_tcp_flags_ts: 02, tcp_tcp_flags_tc... | false | Infiltration | true | Thursday | 180 | 876,351 | Attack | The network event indicates an 'Infiltration' attack. The event shows multiple connection attempts from the same source IP to the same destination IP. These connections are characterized by various TCP flags, such as SYN, FIN, RST, PSH, and ACK, suggesting sophisticated behavior to evade detection and maintain persiste... | classification: Attack
justification: The network event indicates an 'Infiltration' attack. The event shows multiple connection attempts from the same source IP to the same destination IP. These connections are characterized by various TCP flags, such as SYN, FIN, RST, PSH, and ACK, suggesting sophisticated behavior to... |
192.168.10.14-64559-192.168.10.3-53-17 | ['flow', 'flow', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns'] | src_ip: 192.168.10.14, src_port: 64559, dest_ip: 192.168.10.3, dest_port: 53, event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 4, flow_pkts_toclient: 2, flow_bytes_toserver: 292, flow_bytes_toclient: 284, flow_age: 0, flow_state: established, flow_reason: timeout ; event_type: flow, proto: UDP, app_pro... | false | BENIGN | false | Thursday | 2,512 | 720,362 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
192.168.10.9-52143-192.168.10.3-53-17 | ['flow', 'flow', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns'] | src_ip: 192.168.10.9, src_port: 52143, dest_ip: 192.168.10.3, dest_port: 53, event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 144, flow_bytes_toclient: 444, flow_age: 0, flow_state: established, flow_reason: timeout ; event_type: flow, proto: UDP, app_prot... | false | BENIGN | false | Wednesday | 1,975 | 676,153 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
192.168.10.19-13390-192.168.10.3-53-17 | ['flow', 'flow', 'flow', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns'] | src_ip: 192.168.10.19, src_port: 13390, dest_ip: 192.168.10.3, dest_port: 53, event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 144, flow_bytes_toclient: 428, flow_age: 0, flow_state: established, flow_reason: timeout ; event_type: flow, proto: UDP, app_pro... | false | BENIGN | false | Thursday | 2,700 | 783,285 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
172.16.0.1-58533-192.168.10.50-80-6 | ['flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'http', 'fileinfo', 'http', 'http', 'fileinfo', 'http'] | src_ip: 172.16.0.1, src_port: 58533, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 9, flow_pkts_toclient: 5, flow_bytes_toserver: 566, flow_bytes_toclient: 13258, flow_age: 11, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, ... | false | DDoS | true | Friday | 1,364 | 1,117,760 | Attack | The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. These connections are characterized by rep... | classification: Attack
justification: The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. Thes... |
192.168.10.17-39102-192.168.10.3-53-17 | ['flow', 'flow', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns'] | src_ip: 192.168.10.17, src_port: 39102, dest_ip: 192.168.10.3, dest_port: 53, event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 166, flow_bytes_toclient: 394, flow_age: 0, flow_state: established, flow_reason: timeout ; event_type: flow, proto: UDP, app_pro... | false | BENIGN | false | Thursday | 2,175 | 769,231 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
172.16.0.1-60122-192.168.10.50-80-6 | ['flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'http', 'http', 'fileinfo', 'http', 'fileinfo', 'http', 'fileinfo', 'http', 'fileinfo', 'http', 'fileinfo', 'http', 'http', 'http', 'http', 'http', 'http', 'http', 'fileinfo'] | src_ip: 172.16.0.1, src_port: 60122, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 14, flow_pkts_toclient: 3, flow_bytes_toserver: 3473, flow_bytes_toclient: 208, flow_age: 102, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1e, tcp_tcp_flags_ts: 1a,... | false | DoS Slowloris | true | Wednesday | 5,627 | 472,655 | Attack | The network event indicates a DoS Slowloris. DoS Slowloris attacks involve sending partial HTTP requests to the target server, keeping connections open as long as possible. Typically, the logs show multiple long-lived connections with minimal data exchange, aiming to exhaust the target server's resources by maintaining... | classification: Attack
justification: The network event indicates a DoS Slowloris. DoS Slowloris attacks involve sending partial HTTP requests to the target server, keeping connections open as long as possible. Typically, the logs show multiple long-lived connections with minimal data exchange, aiming to exhaust the ta... |
192.168.10.8-35283-192.168.10.14-1840-6 | ['flow'] | src_ip: 192.168.10.8, src_port: 35283, dest_ip: 192.168.10.14, dest_port: 1840, event_type: flow, proto: TCP, flow_pkts_toserver: 2, flow_pkts_toclient: 0, flow_bytes_toserver: 120, flow_bytes_toclient: 0, flow_age: 0, flow_state: new, flow_reason: timeout, tcp_tcp_flags: 02, tcp_tcp_flags_ts: 02, tcp_tcp_flags_tc: 00,... | false | Infiltration | true | Thursday | 165 | 848,893 | Attack | The network event indicates an 'Infiltration' attack. The event shows multiple connection attempts from the same source IP to the same destination IP. These connections are characterized by various TCP flags, such as SYN, FIN, RST, PSH, and ACK, suggesting sophisticated behavior to evade detection and maintain persiste... | classification: Attack
justification: The network event indicates an 'Infiltration' attack. The event shows multiple connection attempts from the same source IP to the same destination IP. These connections are characterized by various TCP flags, such as SYN, FIN, RST, PSH, and ACK, suggesting sophisticated behavior to... |
192.168.10.5-58243-23.60.139.27-80-6 | ['flow'] | src_ip: 192.168.10.5, src_port: 58243, dest_ip: 23.60.139.27, dest_port: 80, event_type: flow, proto: TCP, flow_pkts_toserver: 4, flow_pkts_toclient: 2, flow_bytes_toserver: 246, flow_bytes_toclient: 126, flow_age: 6, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 13, tcp_tcp_flags_ts: 13, tcp_tcp_flags_tc: 1... | false | BENIGN | false | Tuesday | 178 | 391,884 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
172.16.0.1-21265-192.168.10.50-80-6 | ['flow', 'http'] | src_ip: 172.16.0.1, src_port: 21265, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 6, flow_bytes_toserver: 500, flow_bytes_toclient: 11937, flow_age: 2, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1e, tcp_tcp_flags_ts: 1e, t... | false | DDoS | true | Friday | 244 | 949,168 | Attack | The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. These connections are characterized by rep... | classification: Attack
justification: The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. Thes... |
192.168.10.51-37704-202.241.208.2-80-6 | ['flow', 'http'] | src_ip: 192.168.10.51, src_port: 37704, dest_ip: 202.241.208.2, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 7, flow_pkts_toclient: 7, flow_bytes_toserver: 2461, flow_bytes_toclient: 1290, flow_age: 15, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1... | false | BENIGN | false | Monday | 1,677 | 196,328 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
192.168.10.5-53744-205.174.165.73-8080-6 | ['flow', 'http'] | src_ip: 192.168.10.5, src_port: 53744, dest_ip: 205.174.165.73, dest_port: 8080, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 5, flow_pkts_toclient: 4, flow_bytes_toserver: 496, flow_bytes_toclient: 368, flow_age: 0, flow_state: closed, flow_reason: timeout, metadata_flowbits_0: http.dottedquadhos... | true | Botnet | true | Friday | 365 | 1,283,114 | Attack | The network event indicates a Botnet. Botnet activities involve coordinated attacks from multiple compromised machines. Typically, the logs show traffic patterns indicative of control and command communication between the compromised machines and the command server. High volumes of data transfer, frequent anomalies, an... | classification: Attack
justification: The network event indicates a Botnet. Botnet activities involve coordinated attacks from multiple compromised machines. Typically, the logs show traffic patterns indicative of control and command communication between the compromised machines and the command server. High volumes of... |
192.168.10.5-62505-192.168.10.3-53-17 | ['flow', 'dns', 'dns', 'dns', 'dns'] | src_ip: 192.168.10.5, src_port: 62505, dest_ip: 192.168.10.3, dest_port: 53, event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 156, flow_bytes_toclient: 188, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 12547486, event_type: dns, p... | false | BENIGN | false | Wednesday | 646 | 617,563 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
192.168.10.9-8822-199.233.57.19-443-6 | ['flow', 'tls'] | src_ip: 192.168.10.9, src_port: 8822, dest_ip: 199.233.57.19, dest_port: 443, event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 11, flow_pkts_toclient: 9, flow_bytes_toserver: 1334, flow_bytes_toclient: 6434, flow_age: 5, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1b,... | false | BENIGN | false | Friday | 454 | 1,336,128 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
192.168.10.51-10155-192.168.10.3-53-17 | ['flow', 'dns', 'dns', 'dns', 'dns'] | src_ip: 192.168.10.51, src_port: 10155, dest_ip: 192.168.10.3, dest_port: 53, event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 148, flow_bytes_toclient: 616, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 11390528, event_type: dns, ... | false | BENIGN | false | Tuesday | 2,616 | 404,737 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
172.16.0.1-14290-192.168.10.50-80-6 | ['flow', 'http'] | src_ip: 172.16.0.1, src_port: 14290, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 4, flow_bytes_toserver: 500, flow_bytes_toclient: 11829, flow_age: 13, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1e, tcp_tcp_flags_ts: 1e, ... | false | DDoS | true | Friday | 243 | 942,278 | Attack | The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. These connections are characterized by rep... | classification: Attack
justification: The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. Thes... |
172.16.0.1-51248-192.168.10.50-22-6 | ['flow', 'ssh'] | src_ip: 172.16.0.1, src_port: 51248, dest_ip: 192.168.10.50, dest_port: 22, event_type: flow, proto: TCP, app_proto: ssh, flow_pkts_toserver: 23, flow_pkts_toclient: 33, flow_bytes_toserver: 3534, flow_bytes_toclient: 4931, flow_age: 12, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1b,... | false | SSH-Patator | true | Tuesday | 807 | 250,433 | Attack | The network event indicates a SSH-Patator. SSH-Patator attacks involve brute force attempts to gain access to an SSH server. Typically, the logs show multiple login attempts from the same source IP to the SSH server, often with varied credentials. This pattern of behavior is consistent with brute force attacks aiming t... | classification: Attack
justification: The network event indicates a SSH-Patator. SSH-Patator attacks involve brute force attempts to gain access to an SSH server. Typically, the logs show multiple login attempts from the same source IP to the SSH server, often with varied credentials. This pattern of behavior is consis... |
192.168.10.25-51693-173.223.152.83-443-6 | ['flow', 'tls'] | src_ip: 192.168.10.25, src_port: 51693, dest_ip: 173.223.152.83, dest_port: 443, event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 12, flow_pkts_toclient: 7, flow_bytes_toserver: 1399, flow_bytes_toclient: 1210, flow_age: 1, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: ... | false | BENIGN | false | Tuesday | 263 | 358,573 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
192.168.10.15-52299-192.168.10.50-22-6 | ['flow', 'ssh'] | src_ip: 192.168.10.15, src_port: 52299, dest_ip: 192.168.10.50, dest_port: 22, event_type: flow, proto: TCP, app_proto: ssh, flow_pkts_toserver: 42, flow_pkts_toclient: 46, flow_bytes_toserver: 4956, flow_bytes_toclient: 9570, flow_age: 1, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1... | false | BENIGN | false | Tuesday | 747 | 294,704 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
172.16.0.1-49186-192.168.10.50-6001-6 | ['flow'] | src_ip: 172.16.0.1, src_port: 49186, dest_ip: 192.168.10.50, dest_port: 6001, event_type: flow, proto: TCP, flow_pkts_toserver: 1, flow_pkts_toclient: 1, flow_bytes_toserver: 74, flow_bytes_toclient: 60, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 16, tcp_tcp_flags_ts: 02, tcp_tcp_flags_tc: 14... | false | Portscan | true | Friday | 180 | 1,063,077 | Attack | The network event indicates a Portscan. Portscans involve scanning multiple ports on a target machine to identify open ports and services. Typically, the logs show multiple short-lived connection attempts from the same source IP to different destination ports. These connections are characterized by SYN, RST, and ACK fl... | classification: Attack
justification: The network event indicates a Portscan. Portscans involve scanning multiple ports on a target machine to identify open ports and services. Typically, the logs show multiple short-lived connection attempts from the same source IP to different destination ports. These connections are... |
172.16.0.1-60120-192.168.10.50-80-6 | ['flow', 'flow', 'flow', 'flow', 'flow', 'http', 'http', 'http', 'fileinfo', 'http'] | src_ip: 172.16.0.1, src_port: 60120, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 9, flow_pkts_toclient: 5, flow_bytes_toserver: 560, flow_bytes_toclient: 11895, flow_age: 2, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, t... | false | DDoS | true | Friday | 1,114 | 1,127,717 | Attack | The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. These connections are characterized by rep... | classification: Attack
justification: The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. Thes... |
192.168.10.16-37326-74.119.118.67-80-6 | ['flow'] | src_ip: 192.168.10.16, src_port: 37326, dest_ip: 74.119.118.67, dest_port: 80, event_type: flow, proto: TCP, flow_pkts_toserver: 4, flow_pkts_toclient: 3, flow_bytes_toserver: 272, flow_bytes_toclient: 206, flow_age: 6, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 13, tcp_tcp_flags_ts: 13, tcp_tcp_flags_tc:... | false | BENIGN | false | Tuesday | 178 | 315,759 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
192.168.10.15-56036-104.244.43.80-443-6 | ['flow', 'tls'] | src_ip: 192.168.10.15, src_port: 56036, dest_ip: 104.244.43.80, dest_port: 443, event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 10, flow_pkts_toclient: 10, flow_bytes_toserver: 1526, flow_bytes_toclient: 5283, flow_age: 11, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts:... | false | BENIGN | false | Wednesday | 457 | 526,297 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
192.168.10.15-55889-192.168.10.3-53-17 | ['flow', 'dns', 'dns', 'dns', 'dns'] | src_ip: 192.168.10.15, src_port: 55889, dest_ip: 192.168.10.3, dest_port: 53, event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 162, flow_bytes_toclient: 306, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 112567, event_type: dns, pr... | false | BENIGN | false | Thursday | 815 | 732,710 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
192.168.10.15-58241-192.168.10.3-53-17 | ['flow', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns'] | src_ip: 192.168.10.15, src_port: 58241, dest_ip: 192.168.10.3, dest_port: 53, event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 4, flow_pkts_toclient: 2, flow_bytes_toserver: 304, flow_bytes_toclient: 334, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 6728610, event_type: dns, p... | false | BENIGN | false | Wednesday | 1,170 | 529,517 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
172.16.0.1-48630-192.168.10.50-22-6 | ['flow', 'ssh'] | src_ip: 172.16.0.1, src_port: 48630, dest_ip: 192.168.10.50, dest_port: 22, event_type: flow, proto: TCP, app_proto: ssh, flow_pkts_toserver: 22, flow_pkts_toclient: 33, flow_bytes_toserver: 3468, flow_bytes_toclient: 4931, flow_age: 11, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1b,... | false | SSH-Patator | true | Tuesday | 809 | 249,133 | Attack | The network event indicates a SSH-Patator. SSH-Patator attacks involve brute force attempts to gain access to an SSH server. Typically, the logs show multiple login attempts from the same source IP to the SSH server, often with varied credentials. This pattern of behavior is consistent with brute force attacks aiming t... | classification: Attack
justification: The network event indicates a SSH-Patator. SSH-Patator attacks involve brute force attempts to gain access to an SSH server. Typically, the logs show multiple login attempts from the same source IP to the SSH server, often with varied credentials. This pattern of behavior is consis... |
172.16.0.1-49934-192.168.10.50-22-6 | ['flow', 'ssh'] | src_ip: 172.16.0.1, src_port: 49934, dest_ip: 192.168.10.50, dest_port: 22, event_type: flow, proto: TCP, app_proto: ssh, flow_pkts_toserver: 22, flow_pkts_toclient: 33, flow_bytes_toserver: 3484, flow_bytes_toclient: 4931, flow_age: 13, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1b,... | false | SSH-Patator | true | Tuesday | 809 | 249,781 | Attack | The network event indicates a SSH-Patator. SSH-Patator attacks involve brute force attempts to gain access to an SSH server. Typically, the logs show multiple login attempts from the same source IP to the SSH server, often with varied credentials. This pattern of behavior is consistent with brute force attacks aiming t... | classification: Attack
justification: The network event indicates a SSH-Patator. SSH-Patator attacks involve brute force attempts to gain access to an SSH server. Typically, the logs show multiple login attempts from the same source IP to the SSH server, often with varied credentials. This pattern of behavior is consis... |
172.16.0.1-45986-192.168.10.50-80-6 | ['flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'anomaly', 'anomaly', 'anomaly', 'http', 'fileinfo', 'http', 'http', 'fileinfo', 'http', 'fileinfo', 'http', 'http', 'fileinfo', 'http', 'http', 'http', 'fileinfo', 'http', 'fileinfo', 'http', 'fileinfo', 'http', 'http', 'fileinfo'... | src_ip: 172.16.0.1, src_port: 45986, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 8, flow_bytes_toserver: 883, flow_bytes_toclient: 12131, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1f, t... | false | DoS Hulk | true | Wednesday | 5,718 | 465,583 | Attack | The network event indicates a DoS Hulk. DoS Hulk attacks involve sending a high frequency of HTTP requests to overwhelm the target server. Typically, the logs show multiple connection attempts from the same source IP to the same destination IP, with each connection being short-lived and frequently timed out. These conn... | classification: Attack
justification: The network event indicates a DoS Hulk. DoS Hulk attacks involve sending a high frequency of HTTP requests to overwhelm the target server. Typically, the logs show multiple connection attempts from the same source IP to the same destination IP, with each connection being short-live... |
192.168.10.25-57662-23.20.149.182-443-6 | ['flow'] | src_ip: 192.168.10.25, src_port: 57662, dest_ip: 23.20.149.182, dest_port: 443, event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 17, flow_pkts_toclient: 11, flow_bytes_toserver: 3318, flow_bytes_toclient: 3834, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: ... | false | BENIGN | false | Tuesday | 206 | 365,705 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
172.16.0.1-39809-192.168.10.50-2160-6 | ['flow'] | src_ip: 172.16.0.1, src_port: 39809, dest_ip: 192.168.10.50, dest_port: 2160, event_type: flow, proto: TCP, flow_pkts_toserver: 1, flow_pkts_toclient: 1, flow_bytes_toserver: 60, flow_bytes_toclient: 60, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 16, tcp_tcp_flags_ts: 02, tcp_tcp_flags_tc: 14... | false | Portscan | true | Friday | 180 | 1,009,599 | Attack | The network event indicates a Portscan. Portscans involve scanning multiple ports on a target machine to identify open ports and services. Typically, the logs show multiple short-lived connection attempts from the same source IP to different destination ports. These connections are characterized by SYN, RST, and ACK fl... | classification: Attack
justification: The network event indicates a Portscan. Portscans involve scanning multiple ports on a target machine to identify open ports and services. Typically, the logs show multiple short-lived connection attempts from the same source IP to different destination ports. These connections are... |
172.16.0.1-22513-192.168.10.50-80-6 | ['flow', 'http'] | src_ip: 172.16.0.1, src_port: 22513, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 7, flow_pkts_toclient: 4, flow_bytes_toserver: 440, flow_bytes_toclient: 11829, flow_age: 4, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1e, tcp_tcp_flags_ts: 1e, t... | false | DDoS | true | Friday | 243 | 950,397 | Attack | The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. These connections are characterized by rep... | classification: Attack
justification: The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. Thes... |
192.168.10.17-33353-72.30.3.43-443-6 | ['flow', 'tls'] | src_ip: 192.168.10.17, src_port: 33353, dest_ip: 72.30.3.43, dest_port: 443, event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 7, flow_pkts_toclient: 5, flow_bytes_toserver: 969, flow_bytes_toclient: 3691, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1f, tc... | false | BENIGN | false | Tuesday | 251 | 330,948 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
172.16.0.1-42274-192.168.10.50-80-6 | ['flow', 'http', 'fileinfo'] | src_ip: 172.16.0.1, src_port: 42274, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 9, flow_pkts_toclient: 7, flow_bytes_toserver: 566, flow_bytes_toclient: 13366, flow_age: 11, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, ... | false | DDoS | true | Friday | 404 | 1,023,608 | Attack | The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. These connections are characterized by rep... | classification: Attack
justification: The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. Thes... |
172.16.0.1-42849-192.168.10.50-416-6 | ['flow'] | src_ip: 172.16.0.1, src_port: 42849, dest_ip: 192.168.10.50, dest_port: 416, event_type: flow, proto: TCP, flow_pkts_toserver: 1, flow_pkts_toclient: 1, flow_bytes_toserver: 60, flow_bytes_toclient: 60, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 16, tcp_tcp_flags_ts: 02, tcp_tcp_flags_tc: 14,... | false | Portscan | true | Friday | 180 | 1,029,380 | Attack | The network event indicates a Portscan. Portscans involve scanning multiple ports on a target machine to identify open ports and services. Typically, the logs show multiple short-lived connection attempts from the same source IP to different destination ports. These connections are characterized by SYN, RST, and ACK fl... | classification: Attack
justification: The network event indicates a Portscan. Portscans involve scanning multiple ports on a target machine to identify open ports and services. Typically, the logs show multiple short-lived connection attempts from the same source IP to different destination ports. These connections are... |
192.168.10.8-63036-192.168.10.51-3268-6 | ['flow'] | src_ip: 192.168.10.8, src_port: 63036, dest_ip: 192.168.10.51, dest_port: 3268, event_type: flow, proto: TCP, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 120, flow_bytes_toclient: 120, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 16, tcp_tcp_flags_ts: 02, tcp_tcp_flags_tc... | false | Infiltration | true | Thursday | 179 | 913,856 | Attack | The network event indicates an 'Infiltration' attack. The event shows multiple connection attempts from the same source IP to the same destination IP. These connections are characterized by various TCP flags, such as SYN, FIN, RST, PSH, and ACK, suggesting sophisticated behavior to evade detection and maintain persiste... | classification: Attack
justification: The network event indicates an 'Infiltration' attack. The event shows multiple connection attempts from the same source IP to the same destination IP. These connections are characterized by various TCP flags, such as SYN, FIN, RST, PSH, and ACK, suggesting sophisticated behavior to... |
192.168.10.14-53254-23.203.71.179-80-6 | ['flow'] | src_ip: 192.168.10.14, src_port: 53254, dest_ip: 23.203.71.179, dest_port: 80, event_type: flow, proto: TCP, flow_pkts_toserver: 4, flow_pkts_toclient: 2, flow_bytes_toserver: 246, flow_bytes_toclient: 126, flow_age: 5, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 13, tcp_tcp_flags_ts: 13, tcp_tcp_flags_tc:... | false | BENIGN | false | Wednesday | 178 | 504,109 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
172.16.0.1-57412-192.168.10.50-21-6 | ['flow', 'ftp', 'ftp', 'ftp', 'ftp', 'ftp', 'ftp', 'ftp', 'ftp'] | src_ip: 172.16.0.1, src_port: 57412, dest_ip: 192.168.10.50, dest_port: 21, event_type: flow, proto: TCP, app_proto: ftp, flow_pkts_toserver: 11, flow_pkts_toclient: 17, flow_bytes_toserver: 851, flow_bytes_toclient: 1306, flow_age: 9, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1b, t... | false | FTP-Patator | true | Tuesday | 948 | 253,573 | Attack | The network event indicates a FTP-Patator. FTP-Patator attacks involve brute force attempts to gain access to an FTP server. Typically, the logs show multiple login attempts from the same source IP to the FTP server, often with varied credentials. This pattern of behavior is consistent with brute force attacks aiming t... | classification: Attack
justification: The network event indicates a FTP-Patator. FTP-Patator attacks involve brute force attempts to gain access to an FTP server. Typically, the logs show multiple login attempts from the same source IP to the FTP server, often with varied credentials. This pattern of behavior is consis... |
192.168.10.8-2985-205.174.165.73-8080-6 | ['flow', 'http'] | src_ip: 192.168.10.8, src_port: 2985, dest_ip: 205.174.165.73, dest_port: 8080, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 5, flow_pkts_toclient: 4, flow_bytes_toserver: 498, flow_bytes_toclient: 368, flow_age: 0, flow_state: established, flow_reason: timeout, metadata_flowbits_0: http.dottedqua... | true | Botnet | true | Friday | 367 | 1,302,233 | Attack | The network event indicates a Botnet. Botnet activities involve coordinated attacks from multiple compromised machines. Typically, the logs show traffic patterns indicative of control and command communication between the compromised machines and the command server. High volumes of data transfer, frequent anomalies, an... | classification: Attack
justification: The network event indicates a Botnet. Botnet activities involve coordinated attacks from multiple compromised machines. Typically, the logs show traffic patterns indicative of control and command communication between the compromised machines and the command server. High volumes of... |
172.16.0.1-58296-192.168.10.50-80-6 | ['flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'anomaly', 'anomaly', 'anomaly', 'anomaly', 'http', 'http', 'http', 'fileinfo', 'http', 'http', 'fileinfo', 'http', 'fileinfo', 'http', 'http', 'http', 'fileinfo', 'http', 'http', 'fileinfo', 'http',... | src_ip: 172.16.0.1, src_port: 58296, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 15, flow_pkts_toclient: 3, flow_bytes_toserver: 3547, flow_bytes_toclient: 208, flow_age: 104, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1e, tcp_tcp_flags_ts: 1a,... | false | DoS Slowloris | true | Wednesday | 6,035 | 471,742 | Attack | The network event indicates a DoS Slowloris. DoS Slowloris attacks involve sending partial HTTP requests to the target server, keeping connections open as long as possible. Typically, the logs show multiple long-lived connections with minimal data exchange, aiming to exhaust the target server's resources by maintaining... | classification: Attack
justification: The network event indicates a DoS Slowloris. DoS Slowloris attacks involve sending partial HTTP requests to the target server, keeping connections open as long as possible. Typically, the logs show multiple long-lived connections with minimal data exchange, aiming to exhaust the ta... |
192.168.10.8-64823-192.168.10.5-512-6 | ['flow'] | src_ip: 192.168.10.8, src_port: 64823, dest_ip: 192.168.10.5, dest_port: 512, event_type: flow, proto: TCP, flow_pkts_toserver: 2, flow_pkts_toclient: 0, flow_bytes_toserver: 120, flow_bytes_toclient: 0, flow_age: 0, flow_state: new, flow_reason: timeout, tcp_tcp_flags: 02, tcp_tcp_flags_ts: 02, tcp_tcp_flags_tc: 00, t... | false | Infiltration | true | Thursday | 165 | 920,107 | Attack | The network event indicates an 'Infiltration' attack. The event shows multiple connection attempts from the same source IP to the same destination IP. These connections are characterized by various TCP flags, such as SYN, FIN, RST, PSH, and ACK, suggesting sophisticated behavior to evade detection and maintain persiste... | classification: Attack
justification: The network event indicates an 'Infiltration' attack. The event shows multiple connection attempts from the same source IP to the same destination IP. These connections are characterized by various TCP flags, such as SYN, FIN, RST, PSH, and ACK, suggesting sophisticated behavior to... |
192.168.10.17-37650-192.168.10.3-53-17 | ['flow', 'dns', 'dns', 'dns', 'dns'] | src_ip: 192.168.10.17, src_port: 37650, dest_ip: 192.168.10.3, dest_port: 53, event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 178, flow_bytes_toclient: 290, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 12814203, event_type: dns, ... | false | BENIGN | false | Wednesday | 832 | 558,780 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
192.168.10.5-54152-139.162.49.205-443-6 | ['flow', 'tls'] | src_ip: 192.168.10.5, src_port: 54152, dest_ip: 139.162.49.205, dest_port: 443, event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 10, flow_pkts_toclient: 10, flow_bytes_toserver: 1237, flow_bytes_toclient: 5647, flow_age: 11, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts:... | false | BENIGN | false | Monday | 467 | 168,248 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
192.168.10.9-1503-87.250.251.119-443-6 | ['flow', 'tls'] | src_ip: 192.168.10.9, src_port: 1503, dest_ip: 87.250.251.119, dest_port: 443, event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 38, flow_pkts_toclient: 36, flow_bytes_toserver: 7248, flow_bytes_toclient: 40505, flow_age: 88, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts:... | false | BENIGN | false | Monday | 242 | 227,546 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
192.168.10.5-60224-192.168.10.3-53-17 | ['flow', 'flow', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns', 'dns'] | src_ip: 192.168.10.5, src_port: 60224, dest_ip: 192.168.10.3, dest_port: 53, event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 160, flow_bytes_toclient: 628, flow_age: 0, flow_state: established, flow_reason: timeout ; event_type: flow, proto: UDP, app_prot... | false | BENIGN | false | Monday | 4,057 | 178,847 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
172.16.0.1-36330-192.168.10.50-2144-6 | ['flow'] | src_ip: 172.16.0.1, src_port: 36330, dest_ip: 192.168.10.50, dest_port: 2144, event_type: flow, proto: TCP, flow_pkts_toserver: 1, flow_pkts_toclient: 1, flow_bytes_toserver: 74, flow_bytes_toclient: 60, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 16, tcp_tcp_flags_ts: 02, tcp_tcp_flags_tc: 14... | false | Portscan | true | Friday | 180 | 986,001 | Attack | The network event indicates a Portscan. Portscans involve scanning multiple ports on a target machine to identify open ports and services. Typically, the logs show multiple short-lived connection attempts from the same source IP to different destination ports. These connections are characterized by SYN, RST, and ACK fl... | classification: Attack
justification: The network event indicates a Portscan. Portscans involve scanning multiple ports on a target machine to identify open ports and services. Typically, the logs show multiple short-lived connection attempts from the same source IP to different destination ports. These connections are... |
192.168.10.8-45500-192.168.10.9-7004-6 | ['flow'] | src_ip: 192.168.10.8, src_port: 45500, dest_ip: 192.168.10.9, dest_port: 7004, event_type: flow, proto: TCP, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 120, flow_bytes_toclient: 120, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 16, tcp_tcp_flags_ts: 02, tcp_tcp_flags_tc:... | false | Infiltration | true | Thursday | 179 | 864,676 | Attack | The network event indicates an 'Infiltration' attack. The event shows multiple connection attempts from the same source IP to the same destination IP. These connections are characterized by various TCP flags, such as SYN, FIN, RST, PSH, and ACK, suggesting sophisticated behavior to evade detection and maintain persiste... | classification: Attack
justification: The network event indicates an 'Infiltration' attack. The event shows multiple connection attempts from the same source IP to the same destination IP. These connections are characterized by various TCP flags, such as SYN, FIN, RST, PSH, and ACK, suggesting sophisticated behavior to... |
172.16.0.1-43596-192.168.10.50-80-6 | ['flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'flow', 'anomaly', 'http', 'http', 'http', 'fileinfo', 'http', 'http', 'fileinfo', 'http', 'fileinfo', 'http', 'fileinfo', 'http', 'fileinfo', 'http', 'http', 'http', 'http', 'fileinfo', 'http'] | src_ip: 172.16.0.1, src_port: 43596, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 7, flow_pkts_toclient: 7, flow_bytes_toserver: 803, flow_bytes_toclient: 12065, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1f, t... | false | DoS Hulk | true | Wednesday | 5,640 | 464,380 | Attack | The network event indicates a DoS Hulk. DoS Hulk attacks involve sending a high frequency of HTTP requests to overwhelm the target server. Typically, the logs show multiple connection attempts from the same source IP to the same destination IP, with each connection being short-lived and frequently timed out. These conn... | classification: Attack
justification: The network event indicates a DoS Hulk. DoS Hulk attacks involve sending a high frequency of HTTP requests to overwhelm the target server. Typically, the logs show multiple connection attempts from the same source IP to the same destination IP, with each connection being short-live... |
192.168.10.12-41384-23.203.87.43-443-6 | ['flow', 'tls'] | src_ip: 192.168.10.12, src_port: 41384, dest_ip: 23.203.87.43, dest_port: 443, event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 24, flow_pkts_toclient: 20, flow_bytes_toserver: 2349, flow_bytes_toclient: 5620, flow_age: 116, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts:... | false | BENIGN | false | Friday | 479 | 1,156,918 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
172.16.0.1-15369-192.168.10.50-80-6 | ['flow', 'http', 'fileinfo'] | src_ip: 172.16.0.1, src_port: 15369, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 7, flow_bytes_toserver: 506, flow_bytes_toclient: 13366, flow_age: 9, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, t... | false | DDoS | true | Friday | 403 | 943,341 | Attack | The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. These connections are characterized by rep... | classification: Attack
justification: The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. Thes... |
192.168.10.8-51296-192.168.10.51-5500-6 | ['flow'] | src_ip: 192.168.10.8, src_port: 51296, dest_ip: 192.168.10.51, dest_port: 5500, event_type: flow, proto: TCP, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 120, flow_bytes_toclient: 120, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 16, tcp_tcp_flags_ts: 02, tcp_tcp_flags_tc... | false | Infiltration | true | Thursday | 180 | 879,054 | Attack | The network event indicates an 'Infiltration' attack. The event shows multiple connection attempts from the same source IP to the same destination IP. These connections are characterized by various TCP flags, such as SYN, FIN, RST, PSH, and ACK, suggesting sophisticated behavior to evade detection and maintain persiste... | classification: Attack
justification: The network event indicates an 'Infiltration' attack. The event shows multiple connection attempts from the same source IP to the same destination IP. These connections are characterized by various TCP flags, such as SYN, FIN, RST, PSH, and ACK, suggesting sophisticated behavior to... |
172.16.0.1-42358-192.168.10.50-80-6 | ['flow', 'http'] | src_ip: 172.16.0.1, src_port: 42358, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 7, flow_pkts_toclient: 4, flow_bytes_toserver: 440, flow_bytes_toclient: 11829, flow_age: 8, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1e, tcp_tcp_flags_ts: 1e, t... | false | DDoS | true | Friday | 244 | 1,023,975 | Attack | The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. These connections are characterized by rep... | classification: Attack
justification: The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. Thes... |
172.16.0.1-38338-192.168.10.50-1105-6 | ['flow'] | src_ip: 172.16.0.1, src_port: 38338, dest_ip: 192.168.10.50, dest_port: 1105, event_type: flow, proto: TCP, flow_pkts_toserver: 1, flow_pkts_toclient: 1, flow_bytes_toserver: 74, flow_bytes_toclient: 60, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 16, tcp_tcp_flags_ts: 02, tcp_tcp_flags_tc: 14... | false | Portscan | true | Friday | 180 | 997,698 | Attack | The network event indicates a Portscan. Portscans involve scanning multiple ports on a target machine to identify open ports and services. Typically, the logs show multiple short-lived connection attempts from the same source IP to different destination ports. These connections are characterized by SYN, RST, and ACK fl... | classification: Attack
justification: The network event indicates a Portscan. Portscans involve scanning multiple ports on a target machine to identify open ports and services. Typically, the logs show multiple short-lived connection attempts from the same source IP to different destination ports. These connections are... |
192.168.10.19-64083-192.168.10.3-53-17 | ['flow', 'dns', 'dns', 'dns', 'dns'] | src_ip: 192.168.10.19, src_port: 64083, dest_ip: 192.168.10.3, dest_port: 53, event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 168, flow_bytes_toclient: 226, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 6567508, event_type: dns, p... | false | BENIGN | false | Friday | 702 | 1,261,840 | Normal | The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic patterns, suspicious connection attempts,... | classification: Normal
justification: The network event described in the Suricata logs indicates normal behavior. This classification implies that the observed network activity does not exhibit any characteristics associated with malicious intent or attack patterns. Typical signs of attacks, such as unusual traffic pat... |
172.16.0.1-35114-192.168.10.50-80-6 | ['flow', 'http', 'fileinfo'] | src_ip: 172.16.0.1, src_port: 35114, dest_ip: 192.168.10.50, dest_port: 80, event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 5, flow_bytes_toserver: 500, flow_bytes_toclient: 11883, flow_age: 12, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1e, tcp_tcp_flags_ts: 1e, ... | false | DDoS | true | Friday | 384 | 977,412 | Attack | The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. These connections are characterized by rep... | classification: Attack
justification: The network event indicates a DDoS. DDoS attacks involve overwhelming the target system with a high frequency of requests. Typically, the logs show multiple short-lived connection attempts from various source IPs to the same destination IP, often on a common port like port 80. Thes... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.