You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SecureComm-Analyzer is an academic-grade cybersecurity framework that studies, evaluates, and demonstrates how modern network communication systems ensure confidentiality, integrity, and availability (the CIA triad) of data in transit.
🎓 Academic Context
Attribute
Detail
Student
Guggilla Yogamruth Reddy
Program
B.Tech Computer Science & Engineering
Institution
Woxsen University
Domain
Cybersecurity / Network Security
Academic Year
2025–2026
Project Category
Capstone / Final Year Project
🎯 Core Objectives
┌─────────────────────────────────────────────────────────────┐
│ PROJECT OBJECTIVES │
├─────────────────────────────────────────────────────────────┤
│ ① Analyze secure vs. insecure communication channels │
│ ② Demonstrate AES-256 / GnuPG encryption workflows │
│ ③ Deploy and test Snort IDS rule-based threat detection │
│ ④ Inspect network traffic with Wireshark (DPI) │
│ ⑤ Simulate phishing campaigns using GoPhish │
│ ⑥ Implement NIST SP 800-61 Incident Response │
│ ⑦ Measure and quantify security effectiveness │
│ ⑧ Build a live interactive security dashboard │
└─────────────────────────────────────────────────────────────┘
🚨 Problem Statement
Modern enterprises transmit petabytes of sensitive data daily across networks that are increasingly targeted by sophisticated adversaries. Without proper encryption, monitoring, and detection mechanisms, even legitimate communication channels become attack surfaces.
graph TB
subgraph USER["👤 User Plane"]
A[Web Browser] --> D
B[Email Client] --> D
C[API Consumer] --> D
end
subgraph NET["🌐 Network Layer"]
D[TCP/IP Stack] --> E
end
subgraph SEC["🔒 Security Layer ⭐"]
E[TLS 1.3 Handshake] --> F
F[AES-256-GCM Cipher] --> G
G[GnuPG Key Exchange]
end
subgraph MON["📡 Monitoring Layer"]
G --> H[Wireshark DPI]
H --> I[Packet Capture PCAP]
end
subgraph IDS["🚨 Detection Layer"]
I --> J[Snort IDS Engine]
J --> K{Threat Detected?}
K -->|Yes| L[🔴 Alert Generated]
K -->|No| M[✅ Traffic Allowed]
end
subgraph IR["🛡️ Response Layer"]
L --> N[Incident Playbook]
N --> O[Contain & Eradicate]
O --> P[Recovery & Report]
end
style SEC fill:#1a3a5c,stroke:#38bdf8,color:#fff
style IDS fill:#3a1a1a,stroke:#ef4444,color:#fff
style IR fill:#1a3a2a,stroke:#10b981,color:#fff
Loading
Encryption Data Flow
sequenceDiagram
participant Alice as 👤 Alice (Sender)
participant GPG as 🔑 GnuPG Engine
participant TLS as 🔒 TLS 1.3
participant NET as 🌐 Network
participant IDS as 🚨 Snort IDS
participant Bob as 👤 Bob (Receiver)
Alice->>GPG: Plaintext Message
GPG->>GPG: Generate AES-256-GCM Key
GPG->>GPG: Encrypt with Bob's Public Key
GPG->>TLS: Encrypted Ciphertext
TLS->>TLS: TLS Handshake (ECDHE)
TLS->>NET: Secure Packet Transmitted
NET->>IDS: Packet Inspected
IDS->>IDS: Rule Match Check
IDS-->>NET: ✅ Pass (No Threat)
NET->>Bob: Encrypted Payload
Bob->>GPG: Decrypt with Private Key
GPG->>Bob: ✅ Plaintext Recovered
Loading
Component Interaction Map
graph LR
subgraph Frontend
A[Dashboard HTML] --> B[Chart.js]
A --> C[Real-time JS]
end
subgraph Backend
D[Flask REST API] --> E[Security Services]
E --> F[Encryption Module]
E --> G[IDS Monitor]
E --> H[Traffic Analyzer]
end
subgraph Tools
I[Wireshark PCAP] --> H
J[Snort Engine] --> G
K[GnuPG Keys] --> F
L[GoPhish Server] --> M[Phishing DB]
end
C --> D
B --> D
flowchart TD
A[📦 Incoming Packet] --> B{Rule Engine}
B --> C{Priority 1\nMatch?}
B --> D{Priority 2\nMatch?}
B --> E{Priority 3\nMatch?}
C -->|YES| F[🔴 CRITICAL ALERT\nBlock & Log]
D -->|YES| G[🟡 WARNING\nLog & Monitor]
E -->|YES| H[🔵 INFO\nLog Only]
C -->|NO| D
D -->|NO| E
E -->|NO| I[✅ Allow Traffic]
F --> J[(Alert Log)]
G --> J
H --> J
J --> K[Dashboard Notification]
Loading
Sample Snort Rules Used:
# SYN Flood Detection
alert tcp any any ->$HOME_NET 80 (flags:S; \
threshold: type both, track by_src, count 100, seconds 10; \
msg:"[SECURECOMM] SYN Flood Detected"; sid:1000001;)
# SQL Injection Detection
alert http $EXTERNAL_NET any ->$HTTP_SERVERS$HTTP_PORTS \
(msg:"[SECURECOMM] SQL Injection Attempt"; \
http_uri; content:"OR 1=1"; nocase; sid:1000002;)
# Port Scan Detection
alert tcp any any ->$HOME_NET any \
(msg:"[SECURECOMM] Nmap Port Scan"; \
flags:S; threshold: type both, track by_src, \
count 30, seconds 5; sid:1000003;)
# Phishing DNS Query
alert dns any any -> any any \
(msg:"[SECURECOMM] Suspicious DNS - Phishing Domain"; \
dns.query; content:"secure-bank-login"; nocase; sid:1000004;)
4. 🎣 Social Engineering Simulation (GoPhish)
flowchart LR
A[🎯 Define Target Group] --> B[✉️ Craft Phishing Email]
B --> C[🌐 Create Landing Page]
C --> D[📤 Launch Campaign]
D --> E{User Interaction}
E -->|Clicked Link| F[📊 Record Click]
E -->|Submitted Creds| G[🔴 High Risk User]
E -->|Ignored| H[✅ Aware User]
F --> I[📈 Analytics Report]
G --> I
H --> I
I --> J[🎓 Awareness Training]
flowchart TD
A([🟢 Start: User Sends Message]) --> B[Compose Message]
B --> C{Is Channel\nEncrypted?}
C -->|No| D[⚠️ Apply TLS Session]
D --> E
C -->|Yes| E[Load Recipient Public Key]
E --> F[Generate AES-256 Session Key]
F --> G[Encrypt Payload with AES]
G --> H[Sign with Sender RSA Key]
H --> I[Compute SHA-256 Hash]
I --> J[Wrap in TLS Record]
J --> K[Transmit via Network]
K --> L{IDS Check}
L -->|Threat Detected| M[🔴 Block & Alert]
L -->|Clear| N[Deliver to Recipient]
N --> O[Verify SHA-256 Hash]
O --> P{Integrity OK?}
P -->|No| Q[🔴 Tampered — Discard]
P -->|Yes| R[Decrypt with Private Key]
R --> S([✅ Message Delivered Securely])
style A fill:#10b981,color:#fff
style S fill:#10b981,color:#fff
style M fill:#ef4444,color:#fff
style Q fill:#ef4444,color:#fff
Loading
Workflow 2: Threat Detection & Response
flowchart LR
A[Network Traffic] --> B[Wireshark Capture]
B --> C[Packet Queue]
C --> D{Snort\nRule Engine}
D -->|Priority 1 Match| E[🔴 CRITICAL]
D -->|Priority 2 Match| F[🟡 WARNING]
D -->|Priority 3 Match| G[🔵 INFO]
D -->|No Match| H[✅ Allow]
E --> I[Immediate Block]
I --> J[Alert Administrator]
J --> K[Log Incident]
K --> L{Active\nResponse?}
L -->|Yes| M[Execute Playbook]
L -->|No| N[Queue for Review]
M --> O[Contain Threat]
O --> P[Eradicate]
P --> Q[Recover System]
Q --> R[Post-Incident Report]
Encryption Latency by Algorithm:
─────────────────────────────────────────────────────────
AES-128-GCM ██ 0.9 ms
AES-256-GCM ████ 1.8 ms ← Used
RSA-2048 Enc ████████████ 5.2 ms
RSA-4096 Enc ████████████████████████ 42.0 ms ← Key exchange
3DES ████████████████ 16.4 ms
ChaCha20 ███ 1.2 ms
All measurements on: Intel Core i7, 16GB RAM, Linux
MIT License
Copyright (c) 2026 Guggilla Yogamruth Reddy
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software...
See LICENSE file for full terms.
🙏 Acknowledgements
Woxsen University — Academic guidance and research environment
NIST — Cybersecurity frameworks and incident response standards
OWASP Foundation — Web application security guidelines
Snort Community — Open-source IDS rule development
Wireshark Foundation — World-class packet analysis tooling
⭐ If this project helped you understand network security, please give it a star!
