# GLoP: Enabling Massively Parallel Incident Response Through GPU Log   Processing

**Authors:** Xavier Bellekens, Christos Tachtatzis, Robert Atkinson, Craig, Renfrew, Tony Kirkham

arXiv: 1704.02278 · 2017-04-10

## TL;DR

GLoP leverages GPU parallel processing to significantly enhance the speed and scalability of large-scale log analysis for cybersecurity incident response, outperforming traditional CPU methods.

## Contribution

The paper introduces GLoP, a GPU-based log processing library that enables massively parallel analysis, including deep packet inspection, for faster cybersecurity incident detection.

## Key findings

- Achieves 20Gbps throughput in log processing
- Demonstrates GPU-based processing outperforms CPU counterparts
- Supports single and multi-GPU configurations for scalable analysis

## Abstract

Large industrial systems that combine services and applications, have become targets for cyber criminals and are challenging from the security, monitoring and auditing perspectives. Security log analysis is a key step for uncovering anomalies, detecting intrusion, and enabling incident response. The constant increase of link speeds, threats and users, produce large volumes of log data and become increasingly difficult to analyse on a Central Processing Unit (CPU). This paper presents a massively parallel Graphics Processing Unit (GPU) LOg Processing (GLoP) library and can also be used for Deep Packet Inspection (DPI), using a prefix matching technique, harvesting the full power of off-the-shelf technologies. GLoP implements two different algorithm using different GPU memory and is compared against CPU counterpart implementations. The library can be used for processing nodes with single or multiple GPUs as well as GPU cloud farms. The results show throughput of 20Gbps and demonstrate that modern GPUs can be utilised to increase the operational speed of large scale log processing scenarios, saving precious time before and after an intrusion has occurred.

## Full text

_Full body text omitted from this summary view._ Fetch the complete paper as Markdown: https://tomesphere.com/paper/1704.02278/full.md

## Figures

8 figures with captions in the complete paper: https://tomesphere.com/paper/1704.02278/full.md

## References

27 references — full list in the complete paper: https://tomesphere.com/paper/1704.02278/full.md

---
Source: https://tomesphere.com/paper/1704.02278