Maltrail is one system malicious traffic detection, which uses publicly available lists containing malicious or generally suspicious "paths", along with static traces collected from various AV reports and custom user-defined lists, where the trace can be anything from name, URL, IP address or header value user and HTTP.
It also uses advanced heuristic mechanisms that can help detect unknown threats.
Architecture
In case of a positive match, it sends the details of the event to the (central) server where they are stored in the appropriate log directory (ie LOG_DIR described in the Configuration section).
If the sensor is running on the same computer as the server (default configuration), logs are stored directly in the local log directory. Otherwise, they are sent via UDP messages to the remote server (ie LOG_SERVER described in the Configuration section).
The primary role of the server is to store event details and provide support for the web reporting application. In the default configuration, the server and sensor will work on the same computer.
Thus, to avoid possible interruptions in the sensor activities, the front-end reporting part is based on the “Fat client” architecture (i.e. All data after processing done within the client's web browser instance).
The events (ie log entries) for the selected period (24 hours) are transferred to the client, where the web reporting application is solely responsible for the presentation part. The data is sent to the client in compressed parts, where it is processed sequentially. The final report is created in a condensed form, effectively allowing the presentation of the almost unlimited number of events.
Installation
sudo apt-get install python python-pcapy git
git clone https://github.com/stamparm/maltrail.git
Application snapshots
Information on using the program, you will find here.