Location Research Breakthrough Possible @S-Logix pro@slogix.in

Detecting ARP Spoofing Attacks Against OpenSSH Linux Servers Through ARP Table Integrity and Network Traffic Monitoring

Description

Enterprise Linux servers commonly provide remote administration services through OpenSSH. These servers communicate with administrators and other infrastructure systems over local networks.

A weakness in local network address resolution can allow an attacker to perform an ARP Spoofing attack, in which forged ARP messages associate the attacker's MAC address with the IP address of another system.

If successful, network traffic intended for the OpenSSH server or administrator workstation may be redirected through the attacker's system. This can enable traffic interception, session disruption, or man-in-the-middle conditions.

In this use case, an OpenSSH Linux server is deployed in an isolated enterprise-style laboratory environment using Ubuntu Linux. Kali Linux is used as the controlled security-testing system.

The ARP Spoofing attack is simulated against the controlled network using Ettercap. Wireshark is used to inspect ARP traffic, while arpwatch monitors changes in IP-to-MAC address relationships. Suricata provides network security monitoring and alerting.

The defensive mechanism focuses on detecting unexpected ARP mappings, identifying duplicate or changing MAC addresses, monitoring suspicious ARP traffic, and generating security alerts when ARP-based network manipulation is detected.

After implementing the controls, the ARP Spoofing assessment is repeated to verify that the attack is detected and that the OpenSSH server's network communication remains protected.

Existing Security Problem

Application: OpenSSH Linux Server

OpenSSH provides secure remote administration for Linux servers through encrypted SSH communication. Although SSH encrypts application-layer communication, the underlying network can still be targeted through ARP-based attacks.

ARP does not inherently provide authentication for IP-to-MAC address mappings. An attacker who has access to the same local network segment may send forged ARP messages to influence how systems associate IP addresses with MAC addresses.

Existing Problem:

The security problem occurs when ARP mappings change unexpectedly, a server IP becomes associated with an unknown MAC address, multiple systems claim the same IP address, the gateway MAC address changes unexpectedly, large numbers of unsolicited ARP replies are generated, or network traffic begins passing through an unauthorized intermediary. If these conditions are not monitored, an attacker may establish a man-in-the-middle position between an administrator workstation and an OpenSSH server.

The security problem is therefore:

Network Segment → ARP Mapping → Forged ARP Messages → Incorrect IP-to-MAC Mapping → Network Traffic Redirection → Potential Man-in-the-Middle Position

The proposed solution introduces ARP mapping monitoring, packet-level inspection, network intrusion detection, trusted ARP baselining, network segmentation, security-event monitoring, and security alerting to identify suspicious ARP behavior.

Attack

Specific Attack: ARP Spoofing

ARP Spoofing is a local-network attack in which an attacker sends forged ARP messages to associate their MAC address with the IP address of another network device. In this controlled assessment, the attacker system is placed on the same isolated virtual network as the OpenSSH server.

The assessment focuses on unexpected ARP replies, IP-to-MAC address changes, duplicate IP-to-MAC relationships, repeated unsolicited ARP responses, gateway MAC-address changes, and suspicious ARP traffic patterns.

Attack Behavior:
Kali Linux Attacker
ARP Spoofing Traffic
Forged ARP Responses
OpenSSH Server / Gateway
Incorrect IP-to-MAC Mapping
Network Traffic Redirection
ARP Monitoring + Packet Inspection
Security Alert
Attack Investigation

Security Concept

ARP Integrity Monitoring:

The security concept is based on continuously monitoring the relationship between IP addresses and MAC addresses on the protected network.

The security monitoring system maintains awareness of expected IP-to-MAC relationships and compares observed ARP behavior against the established network baseline. The assessment focuses on ARP mapping validation, ARP traffic inspection, MAC address changes, duplicate mappings, network security monitoring, and suspicious ARP activity.

The secure processing flow is:

ARP Traffic
IP/MAC Mapping Analysis
Baseline Comparison
Suspicious Change Detection
Security Alert

Defensive Mechanism

ARP Mapping Monitoring

arpwatch monitors IP-to-MAC address relationships and identifies unexpected changes.

Purpose

Detect suspicious changes to trusted network mappings.

Packet-Level ARP Inspection

Wireshark is used to inspect ARP packets and analyze source and destination information.

Purpose

Provide detailed visibility into ARP communication during investigation.

Network Intrusion Detection

Suricata monitors network traffic for suspicious patterns and generates security alerts.

Purpose

Provide centralized network-level detection capability.

Trusted ARP Baseline

Expected IP-to-MAC mappings for critical systems are documented before attack simulation.

Purpose

Establish a reference against which future changes can be evaluated.

Network Segmentation

The OpenSSH server and security-monitoring systems are placed within a controlled virtual network segment.

Purpose

Reduce unnecessary exposure and restrict the attack environment.

Security Event Monitoring

ARP-related alerts and network security events are collected for investigation.

Purpose

Support detection, analysis, and incident-response activities.

Security Tools

Target Application: OpenSSH

OpenSSH is the open-source secure remote administration service used on the Ubuntu Linux server in this project.

Purpose
  • Provide the protected SSH service.
  • Represent an enterprise Linux server endpoint.
  • Generate legitimate network communication.
  • Provide the target environment for ARP Spoofing assessment.
  • Validate legitimate SSH connectivity after remediation.

ARP Spoofing Simulation Tool: Ettercap

Ettercap is used from Kali Linux to perform the controlled ARP Spoofing simulation within the isolated laboratory network.

Purpose
  • Perform controlled ARP Spoofing.
  • Generate forged ARP traffic.
  • Simulate a man-in-the-middle condition.
  • Test ARP monitoring capabilities.
  • Validate attack detection.

Network Analysis Tool: Wireshark

Wireshark is used to capture and analyze network traffic involving the OpenSSH server.

Purpose
  • Capture laboratory network traffic.
  • Identify ARP packets.
  • Analyze ARP requests and responses.
  • Observe IP-to-MAC address relationships.
  • Investigate suspicious ARP activity.
  • Validate post-remediation network behavior.

ARP Monitoring Tool: arpwatch

arpwatch is used to monitor changes in IP-to-MAC address relationships on the protected network.

Purpose
  • Monitor ARP mappings.
  • Detect unexpected MAC-address changes.
  • Identify new IP-to-MAC associations.
  • Generate ARP-related monitoring events.
  • Support investigation of ARP Spoofing activity.

Network Intrusion Detection Tool: Suricata

Suricata is used to monitor network traffic and identify suspicious network activity.

Purpose
  • Monitor network traffic.
  • Detect suspicious communication patterns.
  • Generate security alerts.
  • Provide network-level security visibility.
  • Support ARP Spoofing investigation.
  • Validate detection after remediation.

Security Testing Platform: Kali Linux

Kali Linux is used as the authorized security-testing environment.

Purpose
  • Run Ettercap.
  • Run Wireshark.
  • Perform controlled ARP Spoofing testing.
  • Analyze captured network traffic.
  • Validate security controls.
  • Perform post-remediation testing.

Target Platform: Ubuntu Linux

Ubuntu Linux hosts the OpenSSH server and supporting security-monitoring components.

Purpose
  • Host OpenSSH.
  • Provide the protected Linux endpoint.
  • Run security-monitoring components.
  • Generate legitimate server activity.
  • Maintain the laboratory network configuration.
  • Support security validation.

Virtualization Platform: VirtualBox

VirtualBox provides the isolated cybersecurity laboratory environment.

Purpose
  • Host Ubuntu Linux.
  • Host Kali Linux.
  • Provide isolated virtual networking.
  • Separate the security-testing environment from production networks.
  • Maintain a reproducible Endpoint & Network Security environment.

Process

STEP 01

Prepare the Isolated Security Laboratory

  • Install VirtualBox.
  • Create an Ubuntu Linux virtual machine.
  • Create a Kali Linux virtual machine.
  • Configure an isolated virtual network.
  • Ensure the laboratory does not expose the attack to external networks.
  • Verify communication between the virtual machines.
Tools: VirtualBox + Ubuntu Linux + Kali Linux
STEP 02

Configure the OpenSSH Server

  • Start the Ubuntu Linux server.
  • Install and configure OpenSSH.
  • Assign the server an appropriate laboratory IP address.
  • Verify that the SSH service is running.
  • Confirm that the server is reachable from the authorized test workstation.
Tools: Ubuntu Linux + OpenSSH
STEP 03

Establish the Network Baseline

  • Record the IP address of the OpenSSH server.
  • Record its expected MAC address.
  • Identify the laboratory gateway.
  • Record the expected gateway MAC address.
  • Document the normal IP-to-MAC relationships.
Tools: Ubuntu Linux + Wireshark
STEP 04

Install ARP Monitoring

  • Install arpwatch on the monitoring system.
  • Configure monitoring for the laboratory network interface.
  • Start ARP monitoring.
  • Confirm that normal IP-to-MAC mappings are observed.
  • Verify that monitoring events are being recorded.
Tools: arpwatch + Ubuntu Linux
STEP 05

Configure Network Traffic Monitoring

  • Install Suricata in the monitoring environment.
  • Configure the monitored network interface.
  • Enable network security monitoring.
  • Verify that network traffic is being observed.
  • Confirm that security events can be reviewed.
Tools: Suricata + Ubuntu Linux
STEP 06

Capture Normal ARP Traffic

  • Start Wireshark.
  • Select the laboratory network interface.
  • Capture normal network traffic.
  • Filter the capture for ARP packets.
  • Identify normal ARP request and response behavior.
  • Save the baseline observations for comparison.
Tools: Wireshark
STEP 07

Establish Normal SSH Communication

  • Connect to the OpenSSH server using the authorized test account.
  • Verify successful SSH authentication.
  • Perform normal administrative test activity.
  • Observe the associated network traffic.
  • Confirm that the server communicates normally before attack simulation.
Tools: OpenSSH + Ubuntu Linux
STEP 08

Prepare the Controlled ARP Spoofing Test

  • Configure the Kali Linux system as the authorized security-testing host.
  • Identify the laboratory target and gateway.
  • Start Wireshark packet capture.
  • Start arpwatch monitoring.
  • Ensure the test is restricted to the isolated virtual network.
Tools: Kali Linux + Wireshark + arpwatch
STEP 09

Perform Controlled ARP Spoofing Simulation

  • Use Ettercap to perform an authorized ARP Spoofing simulation.
  • Generate forged ARP traffic within the laboratory network.
  • Do not target external systems.
  • Observe the resulting ARP traffic.
  • Stop the simulation if unexpected behavior occurs.
Tools: Ettercap + Kali Linux
STEP 10

Analyze ARP Traffic

  • Review the captured ARP packets.
  • Identify unexpected ARP replies.
  • Compare observed MAC addresses with the established baseline.
  • Identify changes in IP-to-MAC relationships.
  • Determine whether the traffic is consistent with ARP Spoofing.
Tools: Wireshark
STEP 11

Analyze ARP Mapping Changes

  • Review arpwatch events.
  • Identify MAC-address changes.
  • Compare the changed mappings with the trusted baseline.
  • Determine whether the OpenSSH server or gateway mapping changed.
  • Record the detected security event.
Tools: arpwatch
STEP 12

Validate Network Detection

  • Review Suricata network events.
  • Identify alerts associated with suspicious network behavior.
  • Correlate Suricata observations with Wireshark packets.
  • Compare the detection time across monitoring tools.
  • Determine whether the attack generated sufficient evidence for investigation.
Tools: Suricata + Wireshark
STEP 13

Establish the ARP Spoofing Finding

  • Correlate the Ettercap activity with ARP traffic.
  • Correlate ARP traffic with arpwatch mapping changes.
  • Correlate network activity with Suricata monitoring.
  • Confirm that the observed behavior represents ARP Spoofing.
  • Document the affected laboratory server and network segment.
Tools: Ettercap + Wireshark + arpwatch + Suricata
STEP 14

Implement ARP Monitoring Controls

  • Maintain trusted IP-to-MAC mappings for critical systems.
  • Configure arpwatch to monitor the protected network.
  • Review ARP mapping-change notifications.
  • Define an investigation procedure for unexpected mapping changes.
  • Ensure critical network devices are monitored continuously.
Tools: arpwatch + Ubuntu Linux
STEP 15

Strengthen Network Security Monitoring

  • Configure Suricata for continuous network monitoring.
  • Monitor suspicious network traffic.
  • Review generated security events.
  • Correlate network alerts with ARP mapping changes.
  • Establish an alerting workflow for suspicious ARP activity.
Tools: Suricata
STEP 16

Re-Test ARP Spoofing After Remediation

  • Repeat the controlled ARP Spoofing simulation.
  • Capture the resulting network traffic.
  • Review arpwatch events.
  • Review Suricata alerts.
  • Compare the results with the original assessment.
  • Verify that suspicious ARP activity is detected.
Tools: Ettercap + Wireshark + arpwatch + Suricata
STEP 17

Validate Legitimate SSH Communication

  • Stop the attack simulation.
  • Restore the expected network mappings.
  • Reconnect to the OpenSSH server.
  • Verify legitimate SSH communication.
  • Confirm that authorized users can continue accessing the server.
  • Verify that the security controls do not unnecessarily disrupt legitimate traffic.
Tools: OpenSSH + Ubuntu Linux
STEP 18

Perform Final Security Validation

  • Review all ARP monitoring events.
  • Review packet captures.
  • Review Suricata alerts.
  • Verify that unexpected IP-to-MAC changes are detectable.
  • Confirm that the ARP Spoofing attack is identified.
  • Confirm that legitimate OpenSSH communication continues to function.
  • Document the attack, detection evidence, defensive controls, and final results.
Tools: Wireshark + arpwatch + Suricata + OpenSSH

Outcome

  1. The OpenSSH Linux server is protected within an isolated enterprise-style network environment.
  2. A trusted baseline of IP-to-MAC address mappings is established for critical systems.
  3. A controlled ARP Spoofing attack is successfully simulated within the laboratory network.
  4. Suspicious ARP requests and responses are identified through packet-level traffic analysis.
  5. Unexpected IP-to-MAC address changes are detected using arpwatch.
  6. Suricata provides additional network-level visibility and security alerts for suspicious activity.
  7. ARP Spoofing evidence is correlated across Ettercap, Wireshark, arpwatch, and Suricata.
  8. The attack is detected and investigated without affecting external or production systems.
  9. Legitimate OpenSSH communication continues to function after the security controls are implemented.
  10. The use case demonstrates practical Endpoint & Network Security through ARP Spoofing detection, ARP integrity monitoring, network traffic analysis, intrusion detection, and post-remediation security validation.
Project 1 of 5
Next Project →