Organizations use Secure Shell (SSH) to administer Linux servers, manage remote systems, and perform authorized command-line operations. Because SSH provides remote access to system resources, publicly exposed SSH services are frequently targeted by unauthorized login attempts, password guessing, and suspicious command interactions.
A conventional SSH honeypot can record login attempts, submitted usernames and passwords, session information, and commands entered by an interacting user. However, its interaction behavior depends on the honeypot's configuration and implementation. A conventional honeypot may not provide context-aware responses that adapt to the sequence of interactions within a session.
In this use case, Cowrie SSH Honeypot is deployed on an Ubuntu Linux virtual machine inside an isolated VirtualBox laboratory. Kali Linux is used as the controlled security-testing environment for generating authorized SSH login attempts and simulated command interactions.
A publicly available SSH honeypot dataset is used to study existing SSH interaction patterns and support the preparation and evaluation of representative test cases. The dataset is kept separate from the records generated during the laboratory experiments.
Llama 3.1, executed locally through Ollama, is integrated with Cowrie using a Python-based response-generation workflow. The integration supplies relevant session context to the language model and receives candidate responses for validation before they are returned through the honeypot interaction.
The implementation must connect the model to Cowrie's actual interaction-handling workflow. Installing Ollama and Llama 3.1 alone does not make Cowrie adaptive. Python integration code is required to manage the interaction context, request model responses, validate the output, and handle failures safely.
Cybersecurity tools such as Wireshark and Suricata can support network-level observation and monitoring of the controlled testing environment. Cowrie session logs remain the primary source for examining the simulated SSH interactions and evaluating the generated responses.
The final assessment determines whether the integrated honeypot can generate context-aware responses, record interaction evidence, handle invalid model outputs, and continue operating without executing model-generated commands on the underlying host.
The complete security-validation workflow is:
SSH Honeypot Deployment
→
Public Dataset Review
→
Controlled SSH Interaction
→
Cowrie Session Logging
→
Session Context Extraction
→
Python Integration
→
Llama 3.1 Response Generation
→
Response Validation
→
Adaptive Honeypot Interaction
→
Security Monitoring
→
Response Evaluation
→
Final Security Validation