Eagle-Eye: Quantum-Inspired Cyber-Threat Detection for Teleportation-Based Quantum Digital Signatures (QDS)
SIH PS 26141 | Smart India Hackathon
Deterministic, explainable security framework for teleportation-based QDS with zero AI/ML reliance.
Overview
Eagle-Eye is a comprehensive verification and threat detection platform built for teleportation-based Quantum Digital Signatures. By combining:
- Bell-state entanglement distribution ($|\Phi^+\rangle$),
- Quantum teleportation with classical Pauli corrections ($I, X, Z, XZ$),
- Projective Pauli measurements across $X$, $Y$, and $Z$ bases,
- Cryptographic freshness guards (anti-replay, timestamp skew control, canonical binding),
- Rigorous quantum statistical hypothesis testing (Wilson score intervals, Total Variation Distance, Sequential Probability Ratio Tests),
- Tamper-evident SHA-256 hash-chained audit ledgers,
- Cryptographically signed and reversible self-healing policy updates, and
- An interactive security operator dashboard with live attack scenario demonstrations,
Eagle-Eye provides mathematical guarantees, deterministic verdicts (ACCEPT, REJECT, ESCALATE), and explainable reason codes for quantum and classical threat vectors.
Key Architectural Principles
- Zero AI/ML: No black-box neural networks or unexplainable heuristics. Every security decision is grounded in verifiable quantum information statistics.
- Deterministic & Explainable: Identical inputs and seeds yield identical decisions. Every rejected or escalated verification explains the exact failed check and measured statistic.
- Fail-Closed Design: Any identity ambiguity, freshness breach, policy corruption, or statistical anomaly immediately fails closed (
REJECT). - Controlled Self-Healing: Incident updates cannot auto-deploy. They must pass shadow regression testing, require digital cryptographic authorization, and remain 100% reversible via signed rollback checkpoints.
- Clear Simulation Scope: Distinguishes software quantum state simulation from physical photon-level hardware; models realistic channel noise without over-claiming hardware guarantees.
Directory Structure
eagle-eye/
├── pyproject.toml # Python build specification
├── requirements.txt # Locked dependency definitions
├── LICENSE # Apache-2.0 License
├── README.md # System documentation & quickstart
├── CONTRIBUTING.md # Branch policy & contribution standards
├── ASSUMPTIONS.md # Cryptographic & quantum channel assumptions
├── docs/ # Governance & verification documentation
│ ├── PRD_MAPPING.md # Matrix mapping FR-01..10 to test suites
│ ├── THREAT_MODEL.md # STRIDE threat model & controls
│ └── BENCHMARK.md # Benchmark protocol & target gates
├── src/ # Core Eagle-Eye framework
│ ├── schemas/ # Phase 1: Pydantic schemas
│ ├── protocol/ # Phase 2: Quantum state & teleportation engine
│ ├── guards/ # Phase 3: Freshness, identity & canonical binding
│ ├── statistics/ # Phase 4: QBER, distances, confidence bounds (no AI)
│ ├── attacks/ # Phase 5: Attack scenario generators
│ ├── decision/ # Phase 6: Verdict engine & audit log chain
│ ├── self_healing/ # Phase 7: Signed rule lifecycle & rollback
│ ├── dashboard/ # Phase 8: Live operator dashboard & web UI
│ └── benchmark/ # Phase 9: Evaluation engine & report generator
└── tests/ # Multi-layer test suite
├── unit/ # Unit tests (Bell state, Pauli, QBER, etc.)
├── contract/ # API and schema validation tests
├── integration/ # End-to-end verification pipeline tests
├── attacks/ # Attack simulation suite (4 core attacks)
├── security/ # Audit tampering & policy integrity tests
└── resilience/ # Self-healing, bad updates, and rollback tests
Quickstart
1. Installation
python -m venv .venv
.\.venv\Scripts\Activate.ps1
pip install -r requirements.txt
2. Running Test Suite
.\.venv\Scripts\pytest -v
3. Running Benchmarks
.\.venv\Scripts\python -m src.benchmark.benchmark_runner
4. Launching the Security Dashboard
.\.venv\Scripts\uvicorn src.dashboard.app:app --host 127.0.0.1 --port 8000 --reload
Metadata
Release files for eagle-eye-qds 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| eagle_eye_qds-0.1.0.tar.gz | 43.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| eagle_eye_qds-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 99.9 kB
Release files / eagle_eye_qds-0.1.0.tar.gz
| Download URL | eagle_eye_qds-0.1.0.tar.gz |
|---|---|
| Size | 43.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f4dd120c3fbc839b2ecbb17241469c86edeb210eefccd61d219f514719ff05d5
|
|
BLAKE2b-256 checksum How to use checksums |
7d0aba89273dc88ef4d57cbc3ce4ea9817763e6fa586817315198d4b2fa4dc14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.10
|
Release files / eagle_eye_qds-0.1.0-py3-none-any.whl
| Download URL | eagle_eye_qds-0.1.0-py3-none-any.whl |
|---|---|
| Size | 56.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
66ab09babe2072d63ac36c75ec05ffb475bb24acabab19b6c313999848ea029f
|
|
BLAKE2b-256 checksum How to use checksums |
545bc62121c62d154dc488e409f7ea362cae5e68b04d7ab00e2a90e6cd016aba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.10
|