log
stringlengths 195
2.49k
| label
int64 0
1
| class
stringclasses 12
values | response
stringclasses 12
values |
|---|---|---|---|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 7, flow_bytes_toserver: 500, flow_bytes_toclient: 11991, flow_age: 1, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9553554, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 11321 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 11321, app_proto: http, fileinfo_filename: /, fileinfo_gaps: True, fileinfo_state: TRUNCATED, fileinfo_stored: False, fileinfo_size: 11321, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 7, flow_bytes_toserver: 500, flow_bytes_toclient: 11991, flow_age: 3, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9554516, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 11321 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 11321, app_proto: http, fileinfo_filename: /, fileinfo_gaps: True, fileinfo_state: TRUNCATED, fileinfo_stored: False, fileinfo_size: 11321, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 7, flow_pkts_toclient: 6, flow_bytes_toserver: 440, flow_bytes_toclient: 11949, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9556613, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 9, flow_pkts_toclient: 7, flow_bytes_toserver: 560, flow_bytes_toclient: 12003, flow_age: 1, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 13, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9559870, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186, app_proto: http, fileinfo_filename: /, fileinfo_gaps: False, fileinfo_state: CLOSED, fileinfo_stored: False, fileinfo_size: 1186, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 9, flow_pkts_toclient: 6, flow_bytes_toserver: 560, flow_bytes_toclient: 11949, flow_age: 3, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 13, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9559808, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186, app_proto: http, fileinfo_filename: /, fileinfo_gaps: False, fileinfo_state: CLOSED, fileinfo_stored: False, fileinfo_size: 1186, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 6, flow_bytes_toserver: 500, flow_bytes_toclient: 11949, flow_age: 1, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9561725, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 7, flow_pkts_toclient: 6, flow_bytes_toserver: 440, flow_bytes_toclient: 11937, flow_age: 8, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9567224, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 11321 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 11321, app_proto: http, fileinfo_filename: /, fileinfo_gaps: True, fileinfo_state: TRUNCATED, fileinfo_stored: False, fileinfo_size: 11321, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 6, flow_bytes_toserver: 506, flow_bytes_toclient: 13312, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9566596, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 6, flow_bytes_toserver: 500, flow_bytes_toclient: 11949, flow_age: 1, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 13, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9569092, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186, app_proto: http, fileinfo_filename: /, fileinfo_gaps: False, fileinfo_state: CLOSED, fileinfo_stored: False, fileinfo_size: 1186, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 9, flow_pkts_toclient: 6, flow_bytes_toserver: 560, flow_bytes_toclient: 11949, flow_age: 1, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9570043, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 9, flow_pkts_toclient: 6, flow_bytes_toserver: 560, flow_bytes_toclient: 11949, flow_age: 1, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 13, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9570137, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186, app_proto: http, fileinfo_filename: /, fileinfo_gaps: False, fileinfo_state: CLOSED, fileinfo_stored: False, fileinfo_size: 1186, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 9, flow_pkts_toclient: 6, flow_bytes_toserver: 560, flow_bytes_toclient: 11949, flow_age: 1, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9570141, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 6, flow_bytes_toserver: 506, flow_bytes_toclient: 13312, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9571399, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 9, flow_pkts_toclient: 7, flow_bytes_toserver: 560, flow_bytes_toclient: 11997, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 13, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 8486 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 8486, app_proto: http, fileinfo_filename: /, fileinfo_gaps: True, fileinfo_state: TRUNCATED, fileinfo_stored: False, fileinfo_size: 8486, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 9, flow_pkts_toclient: 6, flow_bytes_toserver: 560, flow_bytes_toclient: 11949, flow_age: 1, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9572654, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 6, flow_bytes_toserver: 500, flow_bytes_toclient: 11949, flow_age: 1, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9572557, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 39, flow_pkts_toclient: 38, flow_bytes_toserver: 4540, flow_bytes_toclient: 49354, flow_age: 7, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1b, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9578065, event_type: http, proto: TCP, tx_id: 0, http_hostname: www.danawa.com, http_url: /, http_http_user_agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.1, http_status: 200, http_length: 46365 ; pcap_cnt: 9578065, event_type: http, proto: TCP, tx_id: 1, http_hostname: www.danawa.com, http_url: /main/js/mainLayer.js?v=1704181113, http_http_user_agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0, http_http_refer: http://www.danawa.com/, http_http_method: GET, http_protocol: HTTP/1.1, http_length: 0 ; event_type: fileinfo, proto: TCP, http_hostname: www.danawa.com, http_url: /, http_http_user_agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.1, http_status: 200, http_length: 46365, app_proto: http, fileinfo_filename: /, fileinfo_gaps: False, fileinfo_state: TRUNCATED, fileinfo_stored: False, fileinfo_size: 309319, fileinfo_tx_id: 0
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 160, flow_bytes_toclient: 192, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9577002, event_type: dns, proto: UDP, dns_type: query, dns_id: 52214, dns_rrname: tracking.adweb.co.kr, dns_rrtype: A, dns_tx_id: 0 ; pcap_cnt: 9577003, event_type: dns, proto: UDP, dns_type: query, dns_id: 52214, dns_rrname: tracking.adweb.co.kr, dns_rrtype: A, dns_tx_id: 1 ; pcap_cnt: 9577036, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 52214, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: tracking.adweb.co.kr, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: tracking.adweb.co.kr, dns_answers_0_rrtype: A, dns_answers_0_ttl: 11, dns_answers_0_rdata: 121.78.124.168, dns_grouped_A_0: 121.78.124.168 ; pcap_cnt: 9577037, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 52214, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: tracking.adweb.co.kr, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: tracking.adweb.co.kr, dns_answers_0_rrtype: A, dns_answers_0_ttl: 11, dns_answers_0_rdata: 121.78.124.168, dns_grouped_A_0: 121.78.124.168
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 6, flow_bytes_toserver: 500, flow_bytes_toclient: 11949, flow_age: 1, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 13, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9578350, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186, app_proto: http, fileinfo_filename: /, fileinfo_gaps: False, fileinfo_state: CLOSED, fileinfo_stored: False, fileinfo_size: 1186, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 7, flow_pkts_toclient: 6, flow_bytes_toserver: 440, flow_bytes_toclient: 11949, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 13, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9576530, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186, app_proto: http, fileinfo_filename: /, fileinfo_gaps: False, fileinfo_state: CLOSED, fileinfo_stored: False, fileinfo_size: 1186, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 148, flow_bytes_toclient: 342, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9578881, event_type: dns, proto: UDP, dns_type: query, dns_id: 47240, dns_rrname: img.danawa.com, dns_rrtype: AAAA, dns_tx_id: 0 ; pcap_cnt: 9578882, event_type: dns, proto: UDP, dns_type: query, dns_id: 47240, dns_rrname: img.danawa.com, dns_rrtype: AAAA, dns_tx_id: 1 ; pcap_cnt: 9578885, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 47240, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: img.danawa.com, dns_rrtype: AAAA, dns_rcode: NOERROR, dns_answers_0_rrname: img.danawa.com, dns_answers_0_rrtype: CNAME, dns_answers_0_ttl: 3183, dns_answers_0_rdata: img.danawa.com.cdngc.net, dns_grouped_CNAME_0: img.danawa.com.cdngc.net, dns_authorities_0_rrname: cdngc.net, dns_authorities_0_rrtype: SOA, dns_authorities_0_ttl: 58, dns_authorities_0_soa_mname: ns1.cdngc.net, dns_authorities_0_soa_rname: noc.pantherexpress.net, dns_authorities_0_soa_serial: 2017051600, dns_authorities_0_soa_refresh: 1200, dns_authorities_0_soa_retry: 120, dns_authorities_0_soa_expire: 86400, dns_authorities_0_soa_minimum: 60 ; pcap_cnt: 9578886, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 47240, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: img.danawa.com, dns_rrtype: AAAA, dns_rcode: NOERROR, dns_answers_0_rrname: img.danawa.com, dns_answers_0_rrtype: CNAME, dns_answers_0_ttl: 3183, dns_answers_0_rdata: img.danawa.com.cdngc.net, dns_grouped_CNAME_0: img.danawa.com.cdngc.net, dns_authorities_0_rrname: cdngc.net, dns_authorities_0_rrtype: SOA, dns_authorities_0_ttl: 58, dns_authorities_0_soa_mname: ns1.cdngc.net, dns_authorities_0_soa_rname: noc.pantherexpress.net, dns_authorities_0_soa_serial: 2017051600, dns_authorities_0_soa_refresh: 1200, dns_authorities_0_soa_retry: 120, dns_authorities_0_soa_expire: 86400, dns_authorities_0_soa_minimum: 60
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 148, flow_bytes_toclient: 342, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9578954, event_type: dns, proto: UDP, dns_type: query, dns_id: 21585, dns_rrname: img.danawa.com, dns_rrtype: AAAA, dns_tx_id: 0 ; pcap_cnt: 9578955, event_type: dns, proto: UDP, dns_type: query, dns_id: 21585, dns_rrname: img.danawa.com, dns_rrtype: AAAA, dns_tx_id: 1 ; pcap_cnt: 9578958, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 21585, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: img.danawa.com, dns_rrtype: AAAA, dns_rcode: NOERROR, dns_answers_0_rrname: img.danawa.com, dns_answers_0_rrtype: CNAME, dns_answers_0_ttl: 3183, dns_answers_0_rdata: img.danawa.com.cdngc.net, dns_grouped_CNAME_0: img.danawa.com.cdngc.net, dns_authorities_0_rrname: cdngc.net, dns_authorities_0_rrtype: SOA, dns_authorities_0_ttl: 58, dns_authorities_0_soa_mname: ns1.cdngc.net, dns_authorities_0_soa_rname: noc.pantherexpress.net, dns_authorities_0_soa_serial: 2017051600, dns_authorities_0_soa_refresh: 1200, dns_authorities_0_soa_retry: 120, dns_authorities_0_soa_expire: 86400, dns_authorities_0_soa_minimum: 60 ; pcap_cnt: 9578959, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 21585, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: img.danawa.com, dns_rrtype: AAAA, dns_rcode: NOERROR, dns_answers_0_rrname: img.danawa.com, dns_answers_0_rrtype: CNAME, dns_answers_0_ttl: 3183, dns_answers_0_rdata: img.danawa.com.cdngc.net, dns_grouped_CNAME_0: img.danawa.com.cdngc.net, dns_authorities_0_rrname: cdngc.net, dns_authorities_0_rrtype: SOA, dns_authorities_0_ttl: 58, dns_authorities_0_soa_mname: ns1.cdngc.net, dns_authorities_0_soa_rname: noc.pantherexpress.net, dns_authorities_0_soa_serial: 2017051600, dns_authorities_0_soa_refresh: 1200, dns_authorities_0_soa_retry: 120, dns_authorities_0_soa_expire: 86400, dns_authorities_0_soa_minimum: 60
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
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: 9578935, event_type: dns, proto: UDP, dns_type: query, dns_id: 26512, dns_rrname: img.danawa.com, dns_rrtype: A, dns_tx_id: 0 ; pcap_cnt: 9578936, event_type: dns, proto: UDP, dns_type: query, dns_id: 26512, dns_rrname: img.danawa.com, dns_rrtype: A, dns_tx_id: 1 ; pcap_cnt: 9578937, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 26512, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: img.danawa.com, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: img.danawa.com, dns_answers_0_rrtype: CNAME, dns_answers_0_ttl: 3183, dns_answers_0_rdata: img.danawa.com.cdngc.net, dns_answers_1_rrname: img.danawa.com.cdngc.net, dns_answers_1_rrtype: A, dns_answers_1_ttl: 18, dns_answers_1_rdata: 14.0.70.136, dns_answers_2_rrname: img.danawa.com.cdngc.net, dns_answers_2_rrtype: A, dns_answers_2_ttl: 18, dns_answers_2_rdata: 14.0.67.87, dns_grouped_CNAME_0: img.danawa.com.cdngc.net, dns_grouped_A_0: 14.0.70.136, dns_grouped_A_1: 14.0.67.87 ; pcap_cnt: 9578938, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 26512, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: img.danawa.com, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: img.danawa.com, dns_answers_0_rrtype: CNAME, dns_answers_0_ttl: 3183, dns_answers_0_rdata: img.danawa.com.cdngc.net, dns_answers_1_rrname: img.danawa.com.cdngc.net, dns_answers_1_rrtype: A, dns_answers_1_ttl: 18, dns_answers_1_rdata: 14.0.70.136, dns_answers_2_rrname: img.danawa.com.cdngc.net, dns_answers_2_rrtype: A, dns_answers_2_ttl: 18, dns_answers_2_rdata: 14.0.67.87, dns_grouped_CNAME_0: img.danawa.com.cdngc.net, dns_grouped_A_0: 14.0.70.136, dns_grouped_A_1: 14.0.67.87
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 9, flow_pkts_toclient: 6, flow_bytes_toserver: 566, flow_bytes_toclient: 13312, flow_age: 7, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9578455, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 11321 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 11321, app_proto: http, fileinfo_filename: /, fileinfo_gaps: True, fileinfo_state: TRUNCATED, fileinfo_stored: False, fileinfo_size: 11321, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 5, flow_bytes_toserver: 506, flow_bytes_toclient: 13258, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9578483, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 5, flow_pkts_toclient: 5, flow_bytes_toserver: 940, flow_bytes_toclient: 1268, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1b, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9581832, event_type: http, proto: TCP, tx_id: 0, http_hostname: ad.danawa.com, http_url: /RealMedia/ads/adstream_sx.ads/www.danawa.com/main_EVENT@x81, http_http_user_agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0, http_http_content_type: text/html, http_http_refer: http://www.danawa.com/, http_http_method: GET, http_protocol: HTTP/1.1, http_status: 200, http_length: 555 ; pcap_cnt: 9582427, event_type: fileinfo, proto: TCP, http_hostname: ad.danawa.com, http_url: /RealMedia/ads/adstream_sx.ads/www.danawa.com/main_EVENT@x81, http_http_user_agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0, http_http_content_type: text/html, http_http_refer: http://www.danawa.com/, http_http_method: GET, http_protocol: HTTP/1.1, http_status: 200, http_length: 555, app_proto: http, fileinfo_filename: /RealMedia/ads/adstream_sx.ads/www.danawa.com/main_EVENT@x81, fileinfo_gaps: False, fileinfo_state: CLOSED, fileinfo_stored: False, fileinfo_size: 555, fileinfo_tx_id: 0
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
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: 9582482, event_type: dns, proto: UDP, dns_type: query, dns_id: 40256, dns_rrname: insight.danawa.com, dns_rrtype: A, dns_tx_id: 0 ; pcap_cnt: 9582483, event_type: dns, proto: UDP, dns_type: query, dns_id: 40256, dns_rrname: insight.danawa.com, dns_rrtype: A, dns_tx_id: 1 ; pcap_cnt: 9582486, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 40256, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: insight.danawa.com, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: insight.danawa.com, dns_answers_0_rrtype: A, dns_answers_0_ttl: 5727, dns_answers_0_rdata: 119.205.194.17, dns_grouped_A_0: 119.205.194.17 ; pcap_cnt: 9582487, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 40256, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: insight.danawa.com, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: insight.danawa.com, dns_answers_0_rrtype: A, dns_answers_0_ttl: 5727, dns_answers_0_rdata: 119.205.194.17, dns_grouped_A_0: 119.205.194.17
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 7, flow_bytes_toserver: 500, flow_bytes_toclient: 11991, flow_age: 25, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9585492, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 11321 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 11321, app_proto: http, fileinfo_filename: /, fileinfo_gaps: True, fileinfo_state: TRUNCATED, fileinfo_stored: False, fileinfo_size: 11321, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 7, flow_bytes_toserver: 500, flow_bytes_toclient: 12003, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 13, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9585570, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186, app_proto: http, fileinfo_filename: /, fileinfo_gaps: False, fileinfo_state: CLOSED, fileinfo_stored: False, fileinfo_size: 1186, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 7, flow_pkts_toclient: 6, flow_bytes_toserver: 440, flow_bytes_toclient: 11949, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 13, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9585419, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186, app_proto: http, fileinfo_filename: /, fileinfo_gaps: False, fileinfo_state: CLOSED, fileinfo_stored: False, fileinfo_size: 1186, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 6, flow_bytes_toserver: 500, flow_bytes_toclient: 11949, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 13, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9584500, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186, app_proto: http, fileinfo_filename: /, fileinfo_gaps: False, fileinfo_state: CLOSED, fileinfo_stored: False, fileinfo_size: 1186, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 9, flow_pkts_toclient: 6, flow_bytes_toserver: 560, flow_bytes_toclient: 11949, flow_age: 1, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 13, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9587521, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186, app_proto: http, fileinfo_filename: /, fileinfo_gaps: False, fileinfo_state: CLOSED, fileinfo_stored: False, fileinfo_size: 1186, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 7, flow_bytes_toserver: 500, flow_bytes_toclient: 11991, flow_age: 9, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9589655, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 118593
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 6, flow_bytes_toserver: 500, flow_bytes_toclient: 11949, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 13, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9591106, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186, app_proto: http, fileinfo_filename: /, fileinfo_gaps: False, fileinfo_state: CLOSED, fileinfo_stored: False, fileinfo_size: 1186, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 7, flow_pkts_toclient: 7, flow_bytes_toserver: 440, flow_bytes_toclient: 12003, flow_age: 1, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 13, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9593208, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 8, flow_bytes_toserver: 506, flow_bytes_toclient: 13420, flow_age: 1, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9592987, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186, app_proto: http, fileinfo_filename: /, fileinfo_gaps: False, fileinfo_state: CLOSED, fileinfo_stored: False, fileinfo_size: 1186, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 7, flow_pkts_toclient: 6, flow_bytes_toserver: 440, flow_bytes_toclient: 11949, flow_age: 1, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9595000, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
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: 10, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9595642, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 36759
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
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: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 2826
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
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: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9597798, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 6, flow_pkts_toclient: 4, flow_bytes_toserver: 380, flow_bytes_toclient: 11829, flow_age: 13, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1e, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 12, tcp_syn: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 7, flow_pkts_toclient: 6, flow_bytes_toserver: 440, flow_bytes_toclient: 11949, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 13, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9599121, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186, app_proto: http, fileinfo_filename: /, fileinfo_gaps: False, fileinfo_state: CLOSED, fileinfo_stored: False, fileinfo_size: 1186, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 10, flow_pkts_toclient: 6, flow_bytes_toserver: 620, flow_bytes_toclient: 11949, flow_age: 2, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9601030, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 7, flow_bytes_toserver: 500, flow_bytes_toclient: 11991, flow_age: 12, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9600833, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 118593
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 7, flow_bytes_toserver: 500, flow_bytes_toclient: 11991, flow_age: 6, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9600866, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 118593
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 7, flow_pkts_toclient: 7, flow_bytes_toserver: 440, flow_bytes_toclient: 12003, flow_age: 1, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 13, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9606940, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186, app_proto: http, fileinfo_filename: /, fileinfo_gaps: False, fileinfo_state: CLOSED, fileinfo_stored: False, fileinfo_size: 1186, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 9, flow_pkts_toclient: 6, flow_bytes_toserver: 566, flow_bytes_toclient: 13312, flow_age: 8, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9607698, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 11321 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 11321, app_proto: http, fileinfo_filename: /, fileinfo_gaps: True, fileinfo_state: TRUNCATED, fileinfo_stored: False, fileinfo_size: 11321, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
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: 10, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9607638, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 11321 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 11321, app_proto: http, fileinfo_filename: /, fileinfo_gaps: True, fileinfo_state: TRUNCATED, fileinfo_stored: False, fileinfo_size: 11321, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 7, flow_pkts_toclient: 6, flow_bytes_toserver: 440, flow_bytes_toclient: 11949, flow_age: 2, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 13, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9608626, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186, app_proto: http, fileinfo_filename: /, fileinfo_gaps: False, fileinfo_state: CLOSED, fileinfo_stored: False, fileinfo_size: 1186, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 9, flow_pkts_toclient: 6, flow_bytes_toserver: 560, flow_bytes_toclient: 11949, flow_age: 1, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 13, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9608892, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186, app_proto: http, fileinfo_filename: /, fileinfo_gaps: False, fileinfo_state: CLOSED, fileinfo_stored: False, fileinfo_size: 1186, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 7, flow_pkts_toclient: 6, flow_bytes_toserver: 440, flow_bytes_toclient: 11949, flow_age: 1, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9608898, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 8, flow_pkts_toclient: 7, flow_bytes_toserver: 500, flow_bytes_toclient: 12003, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 13, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9612791, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186, app_proto: http, fileinfo_filename: /, fileinfo_gaps: False, fileinfo_state: CLOSED, fileinfo_stored: False, fileinfo_size: 1186, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 10, flow_pkts_toclient: 8, flow_bytes_toserver: 1093, flow_bytes_toclient: 4625, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1f, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: last_ack ; pcap_cnt: 9614347, event_type: tls, proto: TCP, tls_sni: securepubads.g.doubleclick.net, tls_version: UNDETERMINED
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 24, flow_pkts_toclient: 28, flow_bytes_toserver: 2217, flow_bytes_toclient: 32909, flow_age: 1, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1b, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9615682, event_type: tls, proto: TCP, tls_subject: C=US, ST=California, L=Mountain View, O=Google Inc, CN=tpc.googlesyndication.com, tls_issuerdn: C=US, O=Google Inc, CN=Google Internet Authority G2, tls_serial: 21:0B:1F:4F:0E:66:E8:4F, tls_fingerprint: df:a0:13:3c:b3:ee:b8:ff:f9:58:cd:51:e2:86:14:57:15:7e:2c:bf, tls_sni: tpc.googlesyndication.com, tls_version: TLS 1.2, tls_notbefore: 2017-06-28T09:57:49, tls_notafter: 2017-09-20T09:27:00
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 168, flow_bytes_toclient: 200, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9615630, event_type: dns, proto: UDP, dns_type: query, dns_id: 58322, dns_rrname: pagead.l.doubleclick.net, dns_rrtype: A, dns_tx_id: 0 ; pcap_cnt: 9615631, event_type: dns, proto: UDP, dns_type: query, dns_id: 58322, dns_rrname: pagead.l.doubleclick.net, dns_rrtype: A, dns_tx_id: 1 ; pcap_cnt: 9615632, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 58322, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: pagead.l.doubleclick.net, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: pagead.l.doubleclick.net, dns_answers_0_rrtype: A, dns_answers_0_ttl: 14, dns_answers_0_rdata: 172.217.3.98, dns_grouped_A_0: 172.217.3.98 ; pcap_cnt: 9615633, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 58322, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: pagead.l.doubleclick.net, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: pagead.l.doubleclick.net, dns_answers_0_rrtype: A, dns_answers_0_ttl: 14, dns_answers_0_rdata: 172.217.3.98, dns_grouped_A_0: 172.217.3.98
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 7, flow_pkts_toclient: 6, flow_bytes_toserver: 440, flow_bytes_toclient: 11937, flow_age: 4, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9618543, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 11321 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 11321, app_proto: http, fileinfo_filename: /, fileinfo_gaps: True, fileinfo_state: TRUNCATED, fileinfo_stored: False, fileinfo_size: 11321, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 1, flow_pkts_toclient: 1, flow_bytes_toserver: 86, flow_bytes_toclient: 173, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9619268, event_type: dns, proto: UDP, dns_type: query, dns_id: 62972, dns_rrname: soma.smaato.net, dns_rrtype: AAAA, dns_tx_id: 0 ; pcap_cnt: 9619327, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 62972, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: soma.smaato.net, dns_rrtype: AAAA, dns_rcode: NOERROR, dns_authorities_0_rrname: smaato.net, dns_authorities_0_rrtype: SOA, dns_authorities_0_ttl: 25, dns_authorities_0_soa_mname: ns-1745.awsdns-26.co.uk, dns_authorities_0_soa_rname: awsdns-hostmaster.amazon.com, dns_authorities_0_soa_serial: 1, dns_authorities_0_soa_refresh: 7200, dns_authorities_0_soa_retry: 900, dns_authorities_0_soa_expire: 1209600, dns_authorities_0_soa_minimum: 86400
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 16, flow_pkts_toclient: 18, flow_bytes_toserver: 1803, flow_bytes_toclient: 13629, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9620266, event_type: tls, proto: TCP, tls_session_resumed: True, tls_sni: swf.mixpo.com, tls_version: TLS 1.2
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 7, flow_pkts_toclient: 6, flow_bytes_toserver: 440, flow_bytes_toclient: 11937, flow_age: 2, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9623398, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 121209
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 5, flow_pkts_toclient: 5, flow_bytes_toserver: 320, flow_bytes_toclient: 11889, flow_age: 2, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 1369
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 4, flow_pkts_toclient: 2, flow_bytes_toserver: 260, flow_bytes_toclient: 126, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1e, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 12, tcp_syn: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 3, flow_pkts_toclient: 5, flow_bytes_toserver: 200, flow_bytes_toclient: 11883, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1e, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 12, tcp_syn: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 1186, app_proto: http, fileinfo_filename: /, fileinfo_gaps: False, fileinfo_state: CLOSED, fileinfo_stored: False, fileinfo_size: 1186, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 9, flow_pkts_toclient: 7, flow_bytes_toserver: 560, flow_bytes_toclient: 12003, flow_age: 2, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9626726, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_method: GET, http_protocol: HTTP/1.0, http_length: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
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: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1f, tcp_tcp_flags_ts: 1e, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9625320, event_type: http, proto: TCP, tx_id: 0, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 11321 ; event_type: fileinfo, proto: TCP, http_url: /, http_http_content_type: text/html, http_http_method: GET, http_protocol: HTTP/1.0, http_status: 200, http_length: 11321, app_proto: http, fileinfo_filename: /, fileinfo_gaps: True, fileinfo_state: TRUNCATED, fileinfo_stored: False, fileinfo_size: 11321, fileinfo_tx_id: 0
| 1 |
DDoS
|
Classification: 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. These connections are characterized by repeated TCP flags such as SYN, FIN, RST, PSH, and ACK, minimal data exchange, and frequent timeouts or resets. This pattern of behavior is consistent with DDoS activity, where the objective is to exhaust the target's resources and disrupt normal service.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 170, flow_bytes_toclient: 304, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9639234, event_type: dns, proto: UDP, dns_type: query, dns_id: 11223, dns_rrname: cdn.syndication.twimg.com, dns_rrtype: AAAA, dns_tx_id: 0 ; pcap_cnt: 9639235, event_type: dns, proto: UDP, dns_type: query, dns_id: 11223, dns_rrname: cdn.syndication.twimg.com, dns_rrtype: AAAA, dns_tx_id: 1 ; pcap_cnt: 9639244, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 11223, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: cdn.syndication.twimg.com, dns_rrtype: AAAA, dns_rcode: NOERROR, dns_answers_0_rrname: cdn.syndication.twimg.com, dns_answers_0_rrtype: CNAME, dns_answers_0_ttl: 15, dns_answers_0_rdata: cs139.wac.edgecastcdn.net, dns_answers_1_rrname: cs139.wac.edgecastcdn.net, dns_answers_1_rrtype: AAAA, dns_answers_1_ttl: 188, dns_answers_1_rdata: 2606:2800:0220:05c1:0024:0c42:0035:1942, dns_grouped_AAAA_0: 2606:2800:0220:05c1:0024:0c42:0035:1942, dns_grouped_CNAME_0: cs139.wac.edgecastcdn.net ; pcap_cnt: 9639245, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 11223, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: cdn.syndication.twimg.com, dns_rrtype: AAAA, dns_rcode: NOERROR, dns_answers_0_rrname: cdn.syndication.twimg.com, dns_answers_0_rrtype: CNAME, dns_answers_0_ttl: 15, dns_answers_0_rdata: cs139.wac.edgecastcdn.net, dns_answers_1_rrname: cs139.wac.edgecastcdn.net, dns_answers_1_rrtype: AAAA, dns_answers_1_ttl: 188, dns_answers_1_rdata: 2606:2800:0220:05c1:0024:0c42:0035:1942, dns_grouped_CNAME_0: cs139.wac.edgecastcdn.net, dns_grouped_AAAA_0: 2606:2800:0220:05c1:0024:0c42:0035:1942
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 167, flow_bytes_toclient: 301, flow_age: 85, flow_state: established, flow_reason: timeout ; pcap_cnt: 9640296, event_type: dns, proto: UDP, dns_type: query, dns_id: 63305, dns_rrname: cs.bab.la, dns_rrtype: AAAA, dns_tx_id: 0 ; pcap_cnt: 9640315, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 63305, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: cs.bab.la, dns_rrtype: AAAA, dns_rcode: NOERROR, dns_authorities_0_rrname: bab.la, dns_authorities_0_rrtype: SOA, dns_authorities_0_ttl: 1797, dns_authorities_0_soa_mname: tim.ns.cloudflare.com, dns_authorities_0_soa_rname: dns.cloudflare.com, dns_authorities_0_soa_serial: 2024168364, dns_authorities_0_soa_refresh: 10000, dns_authorities_0_soa_retry: 2400, dns_authorities_0_soa_expire: 604800, dns_authorities_0_soa_minimum: 3600 ; pcap_cnt: 9653576, event_type: dns, proto: UDP, dns_type: query, dns_id: 13501, dns_rrname: www.dianping.com, dns_rrtype: AAAA, dns_tx_id: 2 ; pcap_cnt: 9653578, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 13501, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: www.dianping.com, dns_rrtype: AAAA, dns_rcode: NOERROR, dns_authorities_0_rrname: dianping.com, dns_authorities_0_rrtype: SOA, dns_authorities_0_ttl: 373, dns_authorities_0_soa_mname: ns3.dnsv5.com, dns_authorities_0_soa_rname: enterprise3dnsadmin.dnspod.com, dns_authorities_0_soa_serial: 1499249497, dns_authorities_0_soa_refresh: 3600, dns_authorities_0_soa_retry: 180, dns_authorities_0_soa_expire: 1209600, dns_authorities_0_soa_minimum: 180
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 1, flow_pkts_toclient: 1, flow_bytes_toserver: 83, flow_bytes_toclient: 99, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9640717, event_type: dns, proto: UDP, dns_type: query, dns_id: 33538, dns_rrname: www.babla.vn, dns_rrtype: A, dns_tx_id: 0 ; pcap_cnt: 9640739, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 33538, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: www.babla.vn, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: www.babla.vn, dns_answers_0_rrtype: A, dns_answers_0_ttl: 299, dns_answers_0_rdata: 85.25.30.175, dns_grouped_A_0: 85.25.30.175
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 4, flow_pkts_toclient: 2, flow_bytes_toserver: 276, flow_bytes_toclient: 260, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9640689, event_type: dns, proto: UDP, dns_type: query, dns_id: 11138, dns_rrname: sv.bab.la, dns_rrtype: AAAA, dns_tx_id: 0 ; pcap_cnt: 9640690, event_type: dns, proto: UDP, dns_type: query, dns_id: 11138, dns_rrname: sv.bab.la, dns_rrtype: AAAA, dns_tx_id: 1 ; pcap_cnt: 9640708, event_type: dns, proto: UDP, dns_type: query, dns_id: 11138, dns_rrname: sv.bab.la, dns_rrtype: AAAA, dns_tx_id: 2 ; pcap_cnt: 9640709, event_type: dns, proto: UDP, dns_type: query, dns_id: 11138, dns_rrname: sv.bab.la, dns_rrtype: AAAA, dns_tx_id: 3 ; pcap_cnt: 9640713, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 11138, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: sv.bab.la, dns_rrtype: AAAA, dns_rcode: NOERROR, dns_authorities_0_rrname: bab.la, dns_authorities_0_rrtype: SOA, dns_authorities_0_ttl: 900, dns_authorities_0_soa_mname: tim.ns.cloudflare.com, dns_authorities_0_soa_rname: dns.cloudflare.com, dns_authorities_0_soa_serial: 2024168364, dns_authorities_0_soa_refresh: 10000, dns_authorities_0_soa_retry: 2400, dns_authorities_0_soa_expire: 604800, dns_authorities_0_soa_minimum: 3600 ; pcap_cnt: 9640714, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 11138, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: sv.bab.la, dns_rrtype: AAAA, dns_rcode: NOERROR, dns_authorities_0_rrname: bab.la, dns_authorities_0_rrtype: SOA, dns_authorities_0_ttl: 900, dns_authorities_0_soa_mname: tim.ns.cloudflare.com, dns_authorities_0_soa_rname: dns.cloudflare.com, dns_authorities_0_soa_serial: 2024168364, dns_authorities_0_soa_refresh: 10000, dns_authorities_0_soa_retry: 2400, dns_authorities_0_soa_expire: 604800, dns_authorities_0_soa_minimum: 3600
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 569, flow_pkts_toclient: 888, flow_bytes_toserver: 43291, flow_bytes_toclient: 1518890, flow_age: 181, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1b, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9660336, event_type: tls, proto: TCP, tls_subject: C=US, ST=California, L=Mountain View, O=Google Inc, CN=*.google.com, tls_issuerdn: C=US, O=Google Inc, CN=Google Internet Authority G2, tls_serial: 0C:C5:FF:9E:7F:90:1B:22, tls_fingerprint: 71:65:fd:90:6f:e3:b4:f0:80:72:2e:3d:c1:2e:0a:c7:fd:84:88:49, tls_sni: safebrowsing-cache.google.com, tls_version: TLS 1.2, tls_notbefore: 2017-06-28T09:26:00, tls_notafter: 2017-09-20T09:26:00
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 172, flow_bytes_toclient: 204, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9663549, event_type: dns, proto: UDP, dns_type: query, dns_id: 2389, dns_rrname: secure-gl.imrworldwide.com, dns_rrtype: A, dns_tx_id: 0 ; pcap_cnt: 9663550, event_type: dns, proto: UDP, dns_type: query, dns_id: 2389, dns_rrname: secure-gl.imrworldwide.com, dns_rrtype: A, dns_tx_id: 1 ; pcap_cnt: 9663551, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 2389, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: secure-gl.imrworldwide.com, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: secure-gl.imrworldwide.com, dns_answers_0_rrtype: A, dns_answers_0_ttl: 0, dns_answers_0_rdata: 138.108.7.20, dns_grouped_A_0: 138.108.7.20 ; pcap_cnt: 9663552, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 2389, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: secure-gl.imrworldwide.com, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: secure-gl.imrworldwide.com, dns_answers_0_rrtype: A, dns_answers_0_ttl: 0, dns_answers_0_rdata: 138.108.7.20, dns_grouped_A_0: 138.108.7.20
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 166, flow_bytes_toclient: 198, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9663542, event_type: dns, proto: UDP, dns_type: query, dns_id: 48254, dns_rrname: e10883.g.akamaiedge.net, dns_rrtype: A, dns_tx_id: 0 ; pcap_cnt: 9663543, event_type: dns, proto: UDP, dns_type: query, dns_id: 48254, dns_rrname: e10883.g.akamaiedge.net, dns_rrtype: A, dns_tx_id: 1 ; pcap_cnt: 9663544, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 48254, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: e10883.g.akamaiedge.net, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: e10883.g.akamaiedge.net, dns_answers_0_rrtype: A, dns_answers_0_ttl: 0, dns_answers_0_rdata: 23.195.254.62, dns_grouped_A_0: 23.195.254.62 ; pcap_cnt: 9663545, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 48254, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: e10883.g.akamaiedge.net, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: e10883.g.akamaiedge.net, dns_answers_0_rrtype: A, dns_answers_0_ttl: 0, dns_answers_0_rdata: 23.195.254.62, dns_grouped_A_0: 23.195.254.62
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 4, flow_pkts_toclient: 2, flow_bytes_toserver: 320, flow_bytes_toclient: 256, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9663254, event_type: dns, proto: UDP, dns_type: query, dns_id: 5010, dns_rrname: connect.facebook.net, dns_rrtype: A, dns_tx_id: 0 ; pcap_cnt: 9663255, event_type: dns, proto: UDP, dns_type: query, dns_id: 5010, dns_rrname: connect.facebook.net, dns_rrtype: A, dns_tx_id: 1 ; pcap_cnt: 9663294, event_type: dns, proto: UDP, dns_type: query, dns_id: 5010, dns_rrname: connect.facebook.net, dns_rrtype: A, dns_tx_id: 2 ; pcap_cnt: 9663295, event_type: dns, proto: UDP, dns_type: query, dns_id: 5010, dns_rrname: connect.facebook.net, dns_rrtype: A, dns_tx_id: 3 ; pcap_cnt: 9663297, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 5010, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: connect.facebook.net, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: connect.facebook.net, dns_answers_0_rrtype: CNAME, dns_answers_0_ttl: 937, dns_answers_0_rdata: scontent.xx.fbcdn.net, dns_answers_1_rrname: scontent.xx.fbcdn.net, dns_answers_1_rrtype: A, dns_answers_1_ttl: 27, dns_answers_1_rdata: 157.240.18.19, dns_grouped_A_0: 157.240.18.19, dns_grouped_CNAME_0: scontent.xx.fbcdn.net ; pcap_cnt: 9663298, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 5010, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: connect.facebook.net, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: connect.facebook.net, dns_answers_0_rrtype: CNAME, dns_answers_0_ttl: 937, dns_answers_0_rdata: scontent.xx.fbcdn.net, dns_answers_1_rrname: scontent.xx.fbcdn.net, dns_answers_1_rrtype: A, dns_answers_1_ttl: 27, dns_answers_1_rdata: 157.240.18.19, dns_grouped_A_0: 157.240.18.19, dns_grouped_CNAME_0: scontent.xx.fbcdn.net
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 1, flow_pkts_toclient: 1, flow_bytes_toserver: 81, flow_bytes_toclient: 171, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9664824, event_type: dns, proto: UDP, dns_type: query, dns_id: 2642, dns_rrname: c.bing.com, dns_rrtype: A, dns_tx_id: 0 ; pcap_cnt: 9664911, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 2642, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: c.bing.com, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: c.bing.com, dns_answers_0_rrtype: CNAME, dns_answers_0_ttl: 1883, dns_answers_0_rdata: c-bing-com.a-0001.a-msedge.net, dns_answers_1_rrname: c-bing-com.a-0001.a-msedge.net, dns_answers_1_rrtype: CNAME, dns_answers_1_ttl: 1, dns_answers_1_rdata: a-0001.a-msedge.net, dns_answers_2_rrname: a-0001.a-msedge.net, dns_answers_2_rrtype: A, dns_answers_2_ttl: 1, dns_answers_2_rdata: 13.107.21.200, dns_answers_3_rrname: a-0001.a-msedge.net, dns_answers_3_rrtype: A, dns_answers_3_ttl: 1, dns_answers_3_rdata: 204.79.197.200, dns_grouped_A_0: 13.107.21.200, dns_grouped_A_1: 204.79.197.200, dns_grouped_CNAME_0: c-bing-com.a-0001.a-msedge.net, dns_grouped_CNAME_1: a-0001.a-msedge.net
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 15, flow_pkts_toclient: 18, flow_bytes_toserver: 2062, flow_bytes_toclient: 8861, flow_age: 68, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1e, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 1e, tcp_syn: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9665155, event_type: tls, proto: TCP, tls_subject: CN=www.bing.com, tls_issuerdn: C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, OU=Microsoft IT, CN=Microsoft IT SSL SHA2, tls_serial: 5A:00:05:29:CF:2A:5A:63:96:D3:FD:74:EC:00:01:00:05:29:CF, tls_fingerprint: 59:d8:38:3a:7d:72:85:d0:1e:53:c6:39:89:20:2e:c9:cb:bf:4a:20, tls_sni: c.bing.com, tls_version: TLS 1.2, tls_notbefore: 2016-11-04T17:10:22, tls_notafter: 2018-05-04T17:10:22
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 14, flow_pkts_toclient: 14, flow_bytes_toserver: 2114, flow_bytes_toclient: 4994, flow_age: 1, flow_state: closed, flow_reason: timeout, metadata_flowbits_0: ETPRO.Lazarus1, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1b, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9665122, event_type: tls, proto: TCP, metadata_flowbits_0: ETPRO.Lazarus1, tls_session_resumed: True, tls_sni: www.facebook.com, tls_version: TLS 1.2
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 4, flow_pkts_toclient: 2, flow_bytes_toserver: 324, flow_bytes_toclient: 218, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9666887, event_type: dns, proto: UDP, dns_type: query, dns_id: 55662, dns_rrname: scontent.xx.fbcdn.net, dns_rrtype: AAAA, dns_tx_id: 0 ; pcap_cnt: 9666888, event_type: dns, proto: UDP, dns_type: query, dns_id: 55662, dns_rrname: scontent.xx.fbcdn.net, dns_rrtype: AAAA, dns_tx_id: 1 ; pcap_cnt: 9666917, event_type: dns, proto: UDP, dns_type: query, dns_id: 55662, dns_rrname: scontent.xx.fbcdn.net, dns_rrtype: AAAA, dns_tx_id: 2 ; pcap_cnt: 9666918, event_type: dns, proto: UDP, dns_type: query, dns_id: 55662, dns_rrname: scontent.xx.fbcdn.net, dns_rrtype: AAAA, dns_tx_id: 3 ; pcap_cnt: 9666920, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 55662, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: scontent.xx.fbcdn.net, dns_rrtype: AAAA, dns_rcode: NOERROR, dns_answers_0_rrname: scontent.xx.fbcdn.net, dns_answers_0_rrtype: AAAA, dns_answers_0_ttl: 1, dns_answers_0_rdata: 2a03:2880:f012:0008:face:b00c:0000:0001, dns_grouped_AAAA_0: 2a03:2880:f012:0008:face:b00c:0000:0001 ; pcap_cnt: 9666921, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 55662, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: scontent.xx.fbcdn.net, dns_rrtype: AAAA, dns_rcode: NOERROR, dns_answers_0_rrname: scontent.xx.fbcdn.net, dns_answers_0_rrtype: AAAA, dns_answers_0_ttl: 1, dns_answers_0_rdata: 2a03:2880:f012:0008:face:b00c:0000:0001, dns_grouped_AAAA_0: 2a03:2880:f012:0008:face:b00c:0000:0001
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 1, flow_pkts_toclient: 1, flow_bytes_toserver: 91, flow_bytes_toclient: 107, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9667173, event_type: dns, proto: UDP, dns_type: query, dns_id: 42694, dns_rrname: advertiser.wbtrk.net, dns_rrtype: A, dns_tx_id: 0 ; pcap_cnt: 9667190, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 42694, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: advertiser.wbtrk.net, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: advertiser.wbtrk.net, dns_answers_0_rrtype: A, dns_answers_0_ttl: 42, dns_answers_0_rdata: 185.54.150.115, dns_grouped_A_0: 185.54.150.115
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 12, flow_pkts_toclient: 12, flow_bytes_toserver: 1245, flow_bytes_toclient: 2366, flow_age: 66, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1b, tcp_tcp_flags_tc: 13, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; event_type: http, proto: TCP, tx_id: 0, http_hostname: s373.meetrics.net, http_url: /bb-mx/prime/mtrcs_601894.js?pjid=601894&cpid=OasDefault/OH011496_ORF_sb10_front&place=front.orf.at/front/L18&cb=427655885&size=sb, http_http_user_agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:54.0) Gecko/20100101 Firefox/54.0, http_http_refer: http://www.orf.at/, http_http_method: GET, http_protocol: HTTP/1.1, http_length: 0
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 160, flow_bytes_toclient: 276, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9678861, event_type: dns, proto: UDP, dns_type: query, dns_id: 56462, dns_rrname: bachmannpreis.orf.at, dns_rrtype: A, dns_tx_id: 0 ; pcap_cnt: 9678862, event_type: dns, proto: UDP, dns_type: query, dns_id: 56462, dns_rrname: bachmannpreis.orf.at, dns_rrtype: A, dns_tx_id: 1 ; pcap_cnt: 9678869, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 56462, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: bachmannpreis.orf.at, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: bachmannpreis.orf.at, dns_answers_0_rrtype: CNAME, dns_answers_0_ttl: 76843, dns_answers_0_rdata: oesterreich.orf.at, dns_answers_1_rrname: oesterreich.orf.at, dns_answers_1_rrtype: A, dns_answers_1_ttl: 75381, dns_answers_1_rdata: 194.232.104.166, dns_answers_2_rrname: oesterreich.orf.at, dns_answers_2_rrtype: A, dns_answers_2_ttl: 75381, dns_answers_2_rdata: 194.232.104.167, dns_grouped_CNAME_0: oesterreich.orf.at, dns_grouped_A_0: 194.232.104.166, dns_grouped_A_1: 194.232.104.167 ; pcap_cnt: 9678870, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 56462, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: bachmannpreis.orf.at, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: bachmannpreis.orf.at, dns_answers_0_rrtype: CNAME, dns_answers_0_ttl: 76843, dns_answers_0_rdata: oesterreich.orf.at, dns_answers_1_rrname: oesterreich.orf.at, dns_answers_1_rrtype: A, dns_answers_1_ttl: 75381, dns_answers_1_rdata: 194.232.104.166, dns_answers_2_rrname: oesterreich.orf.at, dns_answers_2_rrtype: A, dns_answers_2_ttl: 75381, dns_answers_2_rdata: 194.232.104.167, dns_grouped_CNAME_0: oesterreich.orf.at, dns_grouped_A_0: 194.232.104.166, dns_grouped_A_1: 194.232.104.167
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 1, flow_pkts_toclient: 1, flow_bytes_toserver: 83, flow_bytes_toclient: 147, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9685157, event_type: dns, proto: UDP, dns_type: query, dns_id: 45316, dns_rrname: cs.adingo.jp, dns_rrtype: A, dns_tx_id: 0 ; pcap_cnt: 9685246, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 45316, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: cs.adingo.jp, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: cs.adingo.jp, dns_answers_0_rrtype: A, dns_answers_0_ttl: 1, dns_answers_0_rdata: 54.64.118.111, dns_answers_1_rrname: cs.adingo.jp, dns_answers_1_rrtype: A, dns_answers_1_ttl: 1, dns_answers_1_rdata: 52.193.200.174, dns_answers_2_rrname: cs.adingo.jp, dns_answers_2_rrtype: A, dns_answers_2_ttl: 1, dns_answers_2_rdata: 54.199.193.123, dns_answers_3_rrname: cs.adingo.jp, dns_answers_3_rrtype: A, dns_answers_3_ttl: 1, dns_answers_3_rdata: 54.249.38.117, dns_grouped_A_0: 54.64.118.111, dns_grouped_A_1: 52.193.200.174, dns_grouped_A_2: 54.199.193.123, dns_grouped_A_3: 54.249.38.117
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 14, flow_pkts_toclient: 17, flow_bytes_toserver: 6644, flow_bytes_toclient: 6125, flow_age: 41, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1e, tcp_tcp_flags_ts: 1a, tcp_tcp_flags_tc: 1e, tcp_syn: True, tcp_rst: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9685879, event_type: tls, proto: TCP, tls_subject: C=FR, ST=Paris, L=Paris, O=Criteo SA, OU=Criteo SA, CN=*.criteo.com, tls_issuerdn: C=US, O=Symantec Corporation, OU=Symantec Trust Network, CN=Symantec Class 3 Secure Server CA - G4, tls_serial: 54:3E:06:30:BF:7B:07:E6:C1:16:B3:0C:2A:F9:1C:A2, tls_fingerprint: be:d2:c0:1e:c2:2f:54:3d:33:3e:eb:02:df:e5:8d:68:fe:e8:ef:c3, tls_sni: dis.criteo.com, tls_version: TLS 1.2, tls_notbefore: 2015-10-13T00:00:00, tls_notafter: 2018-01-26T23:59:59
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 30, flow_pkts_toclient: 35, flow_bytes_toserver: 5012, flow_bytes_toclient: 14253, flow_age: 121, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1b, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9692949, event_type: tls, proto: TCP, tls_sni: yjtag.yahoo.co.jp, tls_version: UNDETERMINED
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 1, flow_pkts_toclient: 1, flow_bytes_toserver: 106, flow_bytes_toclient: 159, flow_age: 1, flow_state: established, flow_reason: timeout ; pcap_cnt: 9695316, event_type: dns, proto: UDP, dns_type: query, dns_id: 14514, dns_rrname: ocsp-ds.ws.symantec.com.edgekey.net, dns_rrtype: A, dns_tx_id: 0 ; pcap_cnt: 9695391, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 14514, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: ocsp-ds.ws.symantec.com.edgekey.net, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: ocsp-ds.ws.symantec.com.edgekey.net, dns_answers_0_rrtype: CNAME, dns_answers_0_ttl: 1, dns_answers_0_rdata: e8218.dscb1.akamaiedge.net, dns_answers_1_rrname: e8218.dscb1.akamaiedge.net, dns_answers_1_rrtype: A, dns_answers_1_ttl: 1, dns_answers_1_rdata: 23.54.187.27, dns_grouped_CNAME_0: e8218.dscb1.akamaiedge.net, dns_grouped_A_0: 23.54.187.27
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 160, flow_bytes_toclient: 192, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9694726, event_type: dns, proto: UDP, dns_type: query, dns_id: 3208, dns_rrname: widget.as.criteo.com, dns_rrtype: A, dns_tx_id: 0 ; pcap_cnt: 9694727, event_type: dns, proto: UDP, dns_type: query, dns_id: 3208, dns_rrname: widget.as.criteo.com, dns_rrtype: A, dns_tx_id: 1 ; pcap_cnt: 9694728, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 3208, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: widget.as.criteo.com, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: widget.as.criteo.com, dns_answers_0_rrtype: A, dns_answers_0_ttl: 17, dns_answers_0_rdata: 182.161.73.86, dns_grouped_A_0: 182.161.73.86 ; pcap_cnt: 9694729, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 3208, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: widget.as.criteo.com, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: widget.as.criteo.com, dns_answers_0_rrtype: A, dns_answers_0_ttl: 17, dns_answers_0_rdata: 182.161.73.86, dns_grouped_A_0: 182.161.73.86
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 152, flow_bytes_toclient: 266, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9697014, event_type: dns, proto: UDP, dns_type: query, dns_id: 57405, dns_rrname: ocsp.godaddy.com, dns_rrtype: A, dns_tx_id: 0 ; pcap_cnt: 9697015, event_type: dns, proto: UDP, dns_type: query, dns_id: 57405, dns_rrname: ocsp.godaddy.com, dns_rrtype: A, dns_tx_id: 1 ; pcap_cnt: 9697024, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 57405, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: ocsp.godaddy.com, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: ocsp.godaddy.com, dns_answers_0_rrtype: CNAME, dns_answers_0_ttl: 393, dns_answers_0_rdata: ocsp.godaddy.com.akadns.net, dns_answers_1_rrname: ocsp.godaddy.com.akadns.net, dns_answers_1_rrtype: A, dns_answers_1_ttl: 1, dns_answers_1_rdata: 72.167.239.239, dns_grouped_A_0: 72.167.239.239, dns_grouped_CNAME_0: ocsp.godaddy.com.akadns.net ; pcap_cnt: 9697025, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 57405, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: ocsp.godaddy.com, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: ocsp.godaddy.com, dns_answers_0_rrtype: CNAME, dns_answers_0_ttl: 393, dns_answers_0_rdata: ocsp.godaddy.com.akadns.net, dns_answers_1_rrname: ocsp.godaddy.com.akadns.net, dns_answers_1_rrtype: A, dns_answers_1_ttl: 1, dns_answers_1_rdata: 72.167.239.239, dns_grouped_CNAME_0: ocsp.godaddy.com.akadns.net, dns_grouped_A_0: 72.167.239.239
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 152, flow_bytes_toclient: 216, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9703779, event_type: dns, proto: UDP, dns_type: query, dns_id: 63330, dns_rrname: daisy.ubuntu.com, dns_rrtype: A, dns_tx_id: 0 ; pcap_cnt: 9703780, event_type: dns, proto: UDP, dns_type: query, dns_id: 63330, dns_rrname: daisy.ubuntu.com, dns_rrtype: A, dns_tx_id: 1 ; pcap_cnt: 9703783, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 63330, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: daisy.ubuntu.com, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: daisy.ubuntu.com, dns_answers_0_rrtype: A, dns_answers_0_ttl: 61, dns_answers_0_rdata: 162.213.33.164, dns_answers_1_rrname: daisy.ubuntu.com, dns_answers_1_rrtype: A, dns_answers_1_ttl: 61, dns_answers_1_rdata: 162.213.33.133, dns_grouped_A_0: 162.213.33.164, dns_grouped_A_1: 162.213.33.133 ; pcap_cnt: 9703784, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 63330, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: daisy.ubuntu.com, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: daisy.ubuntu.com, dns_answers_0_rrtype: A, dns_answers_0_ttl: 61, dns_answers_0_rdata: 162.213.33.164, dns_answers_1_rrname: daisy.ubuntu.com, dns_answers_1_rrtype: A, dns_answers_1_ttl: 61, dns_answers_1_rdata: 162.213.33.133, dns_grouped_A_0: 162.213.33.164, dns_grouped_A_1: 162.213.33.133
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 130, flow_bytes_toclient: 130, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9704048, event_type: dns, proto: UDP, dns_type: query, dns_id: 59637, dns_rrname: macpc, dns_rrtype: A, dns_tx_id: 0 ; pcap_cnt: 9704049, event_type: dns, proto: UDP, dns_type: query, dns_id: 59637, dns_rrname: macpc, dns_rrtype: A, dns_tx_id: 1 ; pcap_cnt: 9704052, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 59637, dns_flags: 8182, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: macpc, dns_rrtype: A, dns_rcode: SERVFAIL ; pcap_cnt: 9704053, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 59637, dns_flags: 8182, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: macpc, dns_rrtype: A, dns_rcode: SERVFAIL
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 142, flow_bytes_toclient: 206, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9707869, event_type: dns, proto: UDP, dns_type: query, dns_id: 40646, dns_rrname: tr.quant.jp, dns_rrtype: A, dns_tx_id: 0 ; pcap_cnt: 9707870, event_type: dns, proto: UDP, dns_type: query, dns_id: 40646, dns_rrname: tr.quant.jp, dns_rrtype: A, dns_tx_id: 1 ; pcap_cnt: 9707876, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 40646, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: tr.quant.jp, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: tr.quant.jp, dns_answers_0_rrtype: A, dns_answers_0_ttl: 59, dns_answers_0_rdata: 13.113.123.157, dns_answers_1_rrname: tr.quant.jp, dns_answers_1_rrtype: A, dns_answers_1_ttl: 59, dns_answers_1_rdata: 52.197.131.84, dns_grouped_A_0: 13.113.123.157, dns_grouped_A_1: 52.197.131.84 ; pcap_cnt: 9707877, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 40646, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: tr.quant.jp, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: tr.quant.jp, dns_answers_0_rrtype: A, dns_answers_0_ttl: 59, dns_answers_0_rdata: 13.113.123.157, dns_answers_1_rrname: tr.quant.jp, dns_answers_1_rrtype: A, dns_answers_1_ttl: 59, dns_answers_1_rdata: 52.197.131.84, dns_grouped_A_0: 13.113.123.157, dns_grouped_A_1: 52.197.131.84
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 177, flow_bytes_toclient: 240, flow_age: 166, flow_state: established, flow_reason: timeout ; pcap_cnt: 9709348, event_type: dns, proto: UDP, dns_type: query, dns_id: 27515, dns_rrname: ssl.gstatic.com, dns_rrtype: A, dns_tx_id: 0 ; pcap_cnt: 9709383, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 27515, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: ssl.gstatic.com, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: ssl.gstatic.com, dns_answers_0_rrtype: A, dns_answers_0_ttl: 1, dns_answers_0_rdata: 172.217.10.67, dns_grouped_A_0: 172.217.10.67 ; pcap_cnt: 9730764, event_type: dns, proto: UDP, dns_type: query, dns_id: 27440, dns_rrname: dmg.digitaltarget.ru, dns_rrtype: AAAA, dns_tx_id: 2 ; pcap_cnt: 9730798, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 27440, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: dmg.digitaltarget.ru, dns_rrtype: AAAA, dns_rcode: NOERROR, dns_authorities_0_rrname: digitaltarget.ru, dns_authorities_0_rrtype: SOA, dns_authorities_0_ttl: 845, dns_authorities_0_soa_mname: ns1.digitaltarget.ru, dns_authorities_0_soa_rname: 13alex.digitaltarget.ru, dns_authorities_0_soa_serial: 2017042402, dns_authorities_0_soa_refresh: 3600, dns_authorities_0_soa_retry: 900, dns_authorities_0_soa_expire: 604800, dns_authorities_0_soa_minimum: 86400
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 176, flow_bytes_toclient: 288, flow_age: 159, flow_state: established, flow_reason: timeout ; pcap_cnt: 9709946, event_type: dns, proto: UDP, dns_type: query, dns_id: 53639, dns_rrname: license.theoplayer.com, dns_rrtype: AAAA, dns_tx_id: 0 ; pcap_cnt: 9709947, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 53639, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: license.theoplayer.com, dns_rrtype: AAAA, dns_rcode: NOERROR, dns_authorities_0_rrname: theoplayer.com, dns_authorities_0_rrtype: SOA, dns_authorities_0_ttl: 25, dns_authorities_0_soa_mname: ns1lmy.name.com, dns_authorities_0_soa_rname: support.name.com, dns_authorities_0_soa_serial: 1499299200, dns_authorities_0_soa_refresh: 10800, dns_authorities_0_soa_retry: 3600, dns_authorities_0_soa_expire: 604800, dns_authorities_0_soa_minimum: 3600 ; pcap_cnt: 9729480, event_type: dns, proto: UDP, dns_type: query, dns_id: 47302, dns_rrname: ads.adfox.ru, dns_rrtype: AAAA, dns_tx_id: 2 ; pcap_cnt: 9729500, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 47302, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: ads.adfox.ru, dns_rrtype: AAAA, dns_rcode: NOERROR, dns_authorities_0_rrname: adfox.ru, dns_authorities_0_rrtype: SOA, dns_authorities_0_ttl: 275, dns_authorities_0_soa_mname: ns1.yandex.ru, dns_authorities_0_soa_rname: sysadmin.yandex.ru, dns_authorities_0_soa_serial: 2017070744, dns_authorities_0_soa_refresh: 300, dns_authorities_0_soa_retry: 300, dns_authorities_0_soa_expire: 3600000, dns_authorities_0_soa_minimum: 300
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 333, flow_pkts_toclient: 503, flow_bytes_toserver: 34661, flow_bytes_toclient: 991876, flow_age: 76, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1b, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9711002, event_type: tls, proto: TCP, tls_session_resumed: True, tls_sni: www.poste.it, tls_version: TLS 1.2
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 10, flow_pkts_toclient: 7, flow_bytes_toserver: 1031, flow_bytes_toclient: 5669, flow_age: 5, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1b, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9710942, event_type: tls, proto: TCP, tls_session_resumed: True, tls_sni: d1q62gfb8siqnm.cloudfront.net, tls_version: TLS 1.2
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 170, flow_bytes_toclient: 226, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9719148, event_type: dns, proto: UDP, dns_type: query, dns_id: 7087, dns_rrname: googleadapis.l.google.com, dns_rrtype: AAAA, dns_tx_id: 0 ; pcap_cnt: 9719149, event_type: dns, proto: UDP, dns_type: query, dns_id: 7087, dns_rrname: googleadapis.l.google.com, dns_rrtype: AAAA, dns_tx_id: 1 ; pcap_cnt: 9719193, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 7087, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: googleadapis.l.google.com, dns_rrtype: AAAA, dns_rcode: NOERROR, dns_answers_0_rrname: googleadapis.l.google.com, dns_answers_0_rrtype: AAAA, dns_answers_0_ttl: 58, dns_answers_0_rdata: 2607:f8b0:4006:0814:0000:0000:0000:200a, dns_grouped_AAAA_0: 2607:f8b0:4006:0814:0000:0000:0000:200a ; pcap_cnt: 9719194, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 7087, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: googleadapis.l.google.com, dns_rrtype: AAAA, dns_rcode: NOERROR, dns_answers_0_rrname: googleadapis.l.google.com, dns_answers_0_rrtype: AAAA, dns_answers_0_ttl: 58, dns_answers_0_rdata: 2607:f8b0:4006:0814:0000:0000:0000:200a, dns_grouped_AAAA_0: 2607:f8b0:4006:0814:0000:0000:0000:200a
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 23, flow_pkts_toclient: 20, flow_bytes_toserver: 3952, flow_bytes_toclient: 8857, flow_age: 62, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1b, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9720282, event_type: tls, proto: TCP, tls_subject: CN=*.adroll.com, tls_issuerdn: C=US, O=GeoTrust Inc., CN=RapidSSL SHA256 CA, tls_serial: 66:34:66:B6:9A:A2:E7:6C:F7:75:87:C5:03:8C:1A:05, tls_fingerprint: b0:70:17:a6:e1:e4:1b:de:76:cb:f8:d6:63:f4:eb:64:66:e5:4f:83, tls_sni: d.adroll.com, tls_version: TLS 1.2, tls_notbefore: 2016-10-03T00:00:00, tls_notafter: 2019-11-22T23:59:59
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: TCP, app_proto: tls, flow_pkts_toserver: 9, flow_pkts_toclient: 7, flow_bytes_toserver: 881, flow_bytes_toclient: 4656, flow_age: 5, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1b, tcp_tcp_flags_tc: 1b, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9720255, event_type: tls, proto: TCP, tls_subject: C=US, ST=Massachusetts, L=Cambridge, O=HubSpot, Inc., CN=*.usemessages.com, tls_issuerdn: C=US, O=DigiCert Inc, OU=www.digicert.com, CN=DigiCert SHA2 High Assurance Server CA, tls_serial: 09:CD:7B:43:9D:37:0C:18:6A:D9:B2:10:86:F1:C6:66, tls_fingerprint: 31:f5:78:32:07:05:f2:14:8a:a3:3c:57:7e:3c:2e:6e:ff:f0:56:5d, tls_sni: api.usemessages.com, tls_version: TLS 1.2, tls_notbefore: 2015-12-15T00:00:00, tls_notafter: 2017-12-18T12:00:00
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 1, flow_pkts_toclient: 1, flow_bytes_toserver: 93, flow_bytes_toclient: 109, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9720501, event_type: dns, proto: UDP, dns_type: query, dns_id: 16466, dns_rrname: e8037.g.akamaiedge.net, dns_rrtype: A, dns_tx_id: 0 ; pcap_cnt: 9720526, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 16466, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: e8037.g.akamaiedge.net, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: e8037.g.akamaiedge.net, dns_answers_0_rrtype: A, dns_answers_0_ttl: 1, dns_answers_0_rdata: 23.194.141.179, dns_grouped_A_0: 23.194.141.179
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: TCP, app_proto: http, flow_pkts_toserver: 5, flow_pkts_toclient: 5, flow_bytes_toserver: 726, flow_bytes_toclient: 2560, flow_age: 0, flow_state: closed, flow_reason: timeout, tcp_tcp_flags: 1b, tcp_tcp_flags_ts: 1b, tcp_tcp_flags_tc: 13, tcp_syn: True, tcp_fin: True, tcp_psh: True, tcp_ack: True, tcp_state: closed ; pcap_cnt: 9721148, event_type: fileinfo, proto: TCP, http_hostname: ocsp.godaddy.com, http_url: /, http_http_user_agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0, http_http_method: POST, http_protocol: HTTP/1.1, http_length: 0, app_proto: http, fileinfo_filename: /, fileinfo_gaps: False, fileinfo_state: CLOSED, fileinfo_stored: False, fileinfo_size: 75, fileinfo_tx_id: 0 ; event_type: http, proto: TCP, tx_id: 0, http_hostname: ocsp.godaddy.com, http_url: /, http_http_user_agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0, http_http_method: POST, http_protocol: HTTP/1.1, http_length: 0
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 170, flow_bytes_toclient: 288, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9730223, event_type: dns, proto: UDP, dns_type: query, dns_id: 27807, dns_rrname: tpc.googlesyndication.com, dns_rrtype: A, dns_tx_id: 0 ; pcap_cnt: 9730224, event_type: dns, proto: UDP, dns_type: query, dns_id: 27807, dns_rrname: tpc.googlesyndication.com, dns_rrtype: A, dns_tx_id: 1 ; pcap_cnt: 9730228, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 27807, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: tpc.googlesyndication.com, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: tpc.googlesyndication.com, dns_answers_0_rrtype: CNAME, dns_answers_0_ttl: 6475, dns_answers_0_rdata: pagead-googlehosted.l.google.com, dns_answers_1_rrname: pagead-googlehosted.l.google.com, dns_answers_1_rrtype: A, dns_answers_1_ttl: 263, dns_answers_1_rdata: 172.217.9.225, dns_grouped_A_0: 172.217.9.225, dns_grouped_CNAME_0: pagead-googlehosted.l.google.com ; pcap_cnt: 9730229, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 27807, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: tpc.googlesyndication.com, dns_rrtype: A, dns_rcode: NOERROR, dns_answers_0_rrname: tpc.googlesyndication.com, dns_answers_0_rrtype: CNAME, dns_answers_0_ttl: 6475, dns_answers_0_rdata: pagead-googlehosted.l.google.com, dns_answers_1_rrname: pagead-googlehosted.l.google.com, dns_answers_1_rrtype: A, dns_answers_1_ttl: 263, dns_answers_1_rdata: 172.217.9.225, dns_grouped_A_0: 172.217.9.225, dns_grouped_CNAME_0: pagead-googlehosted.l.google.com
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 160, flow_bytes_toclient: 328, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9730594, event_type: dns, proto: UDP, dns_type: query, dns_id: 18665, dns_rrname: tags.phx.bluekai.com, dns_rrtype: AAAA, dns_tx_id: 0 ; pcap_cnt: 9730595, event_type: dns, proto: UDP, dns_type: query, dns_id: 18665, dns_rrname: tags.phx.bluekai.com, dns_rrtype: AAAA, dns_tx_id: 1 ; pcap_cnt: 9730610, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 18665, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: tags.phx.bluekai.com, dns_rrtype: AAAA, dns_rcode: NOERROR, dns_authorities_0_rrname: phx.bluekai.com, dns_authorities_0_rrtype: SOA, dns_authorities_0_ttl: 799, dns_authorities_0_soa_mname: ns-1632.awsdns-12.co.uk, dns_authorities_0_soa_rname: awsdns-hostmaster.amazon.com, dns_authorities_0_soa_serial: 1, dns_authorities_0_soa_refresh: 7200, dns_authorities_0_soa_retry: 900, dns_authorities_0_soa_expire: 1209600, dns_authorities_0_soa_minimum: 86400 ; pcap_cnt: 9730611, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 18665, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: tags.phx.bluekai.com, dns_rrtype: AAAA, dns_rcode: NOERROR, dns_authorities_0_rrname: phx.bluekai.com, dns_authorities_0_rrtype: SOA, dns_authorities_0_ttl: 799, dns_authorities_0_soa_mname: ns-1632.awsdns-12.co.uk, dns_authorities_0_soa_rname: awsdns-hostmaster.amazon.com, dns_authorities_0_soa_serial: 1, dns_authorities_0_soa_refresh: 7200, dns_authorities_0_soa_retry: 900, dns_authorities_0_soa_expire: 1209600, dns_authorities_0_soa_minimum: 86400
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
event_type: flow, proto: UDP, app_proto: dns, flow_pkts_toserver: 2, flow_pkts_toclient: 2, flow_bytes_toserver: 134, flow_bytes_toclient: 250, flow_age: 0, flow_state: established, flow_reason: timeout ; pcap_cnt: 9733634, event_type: dns, proto: UDP, dns_type: query, dns_id: 7216, dns_rrname: smi2.ru, dns_rrtype: AAAA, dns_tx_id: 0 ; pcap_cnt: 9733635, event_type: dns, proto: UDP, dns_type: query, dns_id: 7216, dns_rrname: smi2.ru, dns_rrtype: AAAA, dns_tx_id: 1 ; pcap_cnt: 9733644, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 7216, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: smi2.ru, dns_rrtype: AAAA, dns_rcode: NOERROR, dns_authorities_0_rrname: smi2.ru, dns_authorities_0_rrtype: SOA, dns_authorities_0_ttl: 87, dns_authorities_0_soa_mname: ns1.e-generator.ru, dns_authorities_0_soa_rname: admin.e-generator.ru, dns_authorities_0_soa_serial: 2017062609, dns_authorities_0_soa_refresh: 1800, dns_authorities_0_soa_retry: 900, dns_authorities_0_soa_expire: 604800, dns_authorities_0_soa_minimum: 600 ; pcap_cnt: 9733645, event_type: dns, proto: UDP, dns_version: 2, dns_type: answer, dns_id: 7216, dns_flags: 8180, dns_qr: True, dns_rd: True, dns_ra: True, dns_rrname: smi2.ru, dns_rrtype: AAAA, dns_rcode: NOERROR, dns_authorities_0_rrname: smi2.ru, dns_authorities_0_rrtype: SOA, dns_authorities_0_ttl: 87, dns_authorities_0_soa_mname: ns1.e-generator.ru, dns_authorities_0_soa_rname: admin.e-generator.ru, dns_authorities_0_soa_serial: 2017062609, dns_authorities_0_soa_refresh: 1800, dns_authorities_0_soa_retry: 900, dns_authorities_0_soa_expire: 604800, dns_authorities_0_soa_minimum: 600
| 0 |
BENIGN
|
Classification: 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, or abnormal data exchanges, are absent. The network interactions recorded in the logs conform to expected and legitimate usage patterns, suggesting routine and benign operations.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.