Back to all case studies
Security EngineeringLive2025

Cyber Attack Monitoring Dashboard

Real-time threat intelligence and investigation toolkit for security analysts.

Full-Stack Developer & Security Researcher Evidence-led build notes

0

client API keys

Credentials stay behind server-side route proxies.

3

core lookup types

IP, domain, and CVE workflows share one investigation surface.

5+

security controls

Headers, validation, caching, safe links, and protected configuration.

01 / Visual evidence

Screenshots and workflow

Cyber Attack Monitoring Dashboard showing threat feed and risk scores

Threat feed workspace

Live indicators, risk scores, and investigation shortcuts in one analyst view.

sanitized view

Investigation surface

The same workflow keeps IP, domain, and CVE context close to the analyst.

02 / System design

Architecture diagram

System flow
PUBLIC VIEW
01

Analyst

  • Next.js UI
  • TanStack Query cache
  • Recharts visualizations
02

Application

  • Server-side API routes
  • Input validation
  • Security headers
03

Intelligence

  • AbuseIPDB
  • CIRCL CVE
  • VirusTotal / OTX / Shodan links

A server-mediated lookup flow keeps third-party credentials away from the browser while the client focuses on investigation and visualization.

Evidence

Sanitized report

Public verification snapshot from the production review. Values describe controls and scope, not private targets.

Client-side secretsNo API keys shippedPASS
Lookup surfacesIP · domain · CVEINFO
Security headersEnabled at deployment edgePASS
DeploymentVercel · liveINFO
SCOPE: public dashboard controls
RESULT: secrets remain server-side
NOTE: target identifiers and provider response bodies removed

03 / Verification

Testing methodology

01

Threat-model the browser boundary

Mapped every external lookup and marked credentials, user input, and provider responses as separate trust boundaries.

02

Exercise the lookup routes

Tested valid, malformed, empty, and provider-error inputs before wiring results into the UI.

03

Review deployment controls

Checked headers, client bundles, outbound links, responsive states, and loading/error behavior on the deployed build.

04 / Ownership

What I personally contributed

Clear ownership matters in security work. These are the decisions and deliverables I directly handled for this project.

  • Owned the product direction, threat model, and end-to-end implementation.
  • Designed the route-proxy boundary and integrated the threat-intelligence providers.
  • Built the analyst UI, charts, loading states, error states, and responsive behavior.
  • Configured deployment, security headers, analytics, and the public documentation.