Deception-driven cybersecurity / 01

DETECT.
DIVERT.
UNDERSTAND.

Give suspicious activity somewhere else to go. DecoyGuard brings deception and behavioural analysis together to make threats easier to investigate.

Detect / Deceive / Analyze
INCOMING / TRAFFIC
DECOY / ENVIRONMENT
DecoyGuard shield
DG / DECEPTION SYSTEM● ◌ ● ◌ ●
SECURITY THROUGH DECEPTIONSCROLL TO EXPLORE ↓
01 / The framework

ABOUT DECOYGUARD

DecoyGuard is a two-layer security framework that brings together honeypot-based deception and log-based behavioral threat detection. It is designed to identify suspicious activity, observe unauthorized access attempts, and provide security teams with clearer visibility into potential threats.

02 / Our technology

A SMARTER
APPROACH TO SECURITY.

Three complementary capabilities. One coordinated approach to understanding malicious activity.

01 / DETECT
⌁

Behavioral Detection

Analyze system and web-server logs to identify suspicious patterns and anomalies.

02 / DECEIVE
⬡

Honeypot Environments

Use realistic decoy services to observe and record unauthorized interactions.

03 / ANALYZE
▥

Threat Intelligence

Track attacker activity, source information, and threat events to support investigation and reporting.

03 / How it works

SAME TRAFFIC.
DIFFERENT DESTINATION.

DecoyGuard assesses activity for suspicious patterns and supports deception-based handling, helping separate legitimate services from controlled decoy environments.

INCOMING WEB TRAFFIC
↓
Traffic assessment
Detection & routing
↗ LEGITIMATE SERVICEExpected requests
↘ DECOY ENVIRONMENTSuspicious interactions

Conceptual architecture illustration; actual handling depends on deployment configuration.

Our purpose / 03

THREE GOALS.
ONE MISSION.

From early detection to meaningful evidence, each layer has a purpose.

01

Deception-based detection

Simulate decoy environments that attract and detect unauthorized access attempts early.

02

Behavioural analysis

Monitor activities and analyse logs for suspicious patterns in real time.

03

Evidence & reporting

Present detected behavioural threats and generate reports for investigation.

04 / Controlled demonstrations

TEST ENVIRONMENTS

Explore two application scenarios used to evaluate deception and detection workflows.

Environment 01

OWASP Juice Shop

An intentionally vulnerable application used for authorized security testing and training.

View setup instructions ↗
Environment 02

Banking Demonstration

A simulated banking application for controlled testing with synthetic data.

View setup instructions ↗
05 / Get started

DEPLOY DECOYGUARD.

Set up DecoyGuard in an authorized local or lab environment. Follow the installation steps and connect your test applications through the configured gateway.

A verified public download URL has not yet been configured.

INSTALLATION OVERVIEW

✓ Python runtime and dependencies
✓ Docker Desktop for lab applications
✓ Playwright browser setup
✓ Local gateway configuration
✓ Authorized testing environment
06 / The people

MEET OUR TEAM

Portrait of Farazilawati Baizura Binti Mohd Pooad

Farazilawati Baizura
Binti Mohd Pooad

Supervisor

Portrait of Aiman Danish Bin Mohd Khairunnizam

Aiman Danish Bin
Mohd Khairunnizam

CBS24070471

Log-Based Threat Detection

Portrait of Muhammad Ryan Bin Hifzi

Muhammad Ryan Bin Hifzi

CBS24070151

Project Leader & System Integration

Portrait of Puteri Nia Natasya Binti Mohamad Syahril

Puteri Nia Natasya Binti
Mohamad Syahril

CBS24070728

Honeypot / Deception Layer, Dashboard

Portrait of Nur Sabrina Lutfiah Binti Nurmohamad

Nur Sabrina Lutfiah
Binti Nurmohamad

CBS24070261

Dashboard, Alerts & Documentation

Installation notes

Install Python and the dependencies supplied with the verified DecoyGuard release. Install Docker Desktop if using containerized lab applications, and install Playwright Chromium when required by the mirroring engine.

Configure the test-site gateway addresses locally, then start the application using the command provided by your release. Only test systems you own or are authorized to assess.

Exact commands and downloadable files should be checked against the final release package before publishing.