Database
FlowSH: Detecting Web Attacks by Correlating Anomalous Network Flows and Endpoint Logs
arXiv cs.CR0 views
arXiv:2611.23669v1 Announce Type: new Abstract: Web applications compose the core of internet services, rendering them prominent targets for audacious attackers. Among web attacks, SQL injection (SQLi) remains a persistent, damaging web applications connected to databases. The widespread adoption of HTTPS has been a critical advancement for online security, ensuring the confidentiality and integrity of communications by encrypting network payloads. However, it also renders traditional Network Intrusion Detection Systems (NIDS) less effective, as these typically rely on packet inspection of plaintext traffic. To access encrypted payloads, some NIDS resort to TLS-interception proxies, which leads to data leaks and security risks. This paper presents FlowSH, a system for detecting web attacks that is agnostic to whether the traffic is encrypted (HTTPS) or not (HTTP). Rather than decrypting packets in transit, FlowSH correlates flow-level metadata (NetFlows) with endpoint logs, which inherently contain decrypted payloads after reaching the web server. The system combines unsupervised machine learning to flag anomalous NetFlows and similarity search over server-side logs using Locality Sensitive Hashing (LSH) to confirm attacks. We implemented and evaluated FlowSH in a testbed with multiple web scanners and demonstrated its detection effectiveness, detecting 70% of SQLi attacks missed by ModSecurity, a leading web application firewall.
Source:https://arxiv.org/abs/2611.23669PreviousProtecting Web Applications using a Multimodal AI-based System for Classifying Web Injection AttacksNextJEV vs. LLMs: A Comparative Analysis for Phishing Email Detection
Related posts
Respaldo NoSQL en Firestore: cifrar, verificar y recuperar documentos
0dev.to

The BIGINT Problem Explained
0dev.to
Stop Learning Programming Like You're Collecting Certificates. Start Building Things.
0dev.to Beginners

I spent a week with Claude Code trying to squeeze more out of my memory tool's LongMemEval score. Almost nothing worked. Is it my code or the benchmark?
0dev.to Rust
Nightly Reconciliation for Node.js Email and Webhook Failures: Idempotent Queue Recovery
0dev.to Go

MySQL to Redshift Without DMS: A Binlog CDC Tutorial Through AWS Glue
0dev.to Database