Lazarus is an advanced API security platform designed to discover, monitor, and secure your API ecosystem. It specializes in identifying undocumented (Shadow), deprecated but active (Zombie), and unused (Stale) APIs while providing automated remediation, compliance reporting, and AI-powered insights.
Modern API ecosystems often grow uncontrollably, leaving behind:
- Undocumented endpoints (Shadow APIs)
- Deprecated but still active endpoints (Zombie APIs)
- Unused endpoints (Stale APIs)
Lazarus solves this problem by combining:
- Real-time traffic analysis
- Security posture evaluation
- Automated remediation workflows
- AI-powered explanations
Lazarus is built using a modern full-stack architecture:
-
FastAPI (Python)
- API catalog management
- Security analysis engine
- Decommissioning workflows
- AI integration
-
React + Vite + TailwindCSS
- Interactive dashboards
- API insights visualization
- AI chat interface
-
MongoDB
- Stores logs, honeypots, redirects
- Maintains audit trails
-
OpenRouter (Qwen LLM)
- Context-aware explanations
- Natural language querying of system data
-
Compares OpenAPI definitions vs live traffic
-
Automatically classifies APIs into:
- ✅ Active
- 🧟 Zombie
- 👤 Shadow
- ⏳ Stale
Each API is evaluated across:
- 🔐 Authentication (OAuth2, JWT, etc.)
- 🔒 Encryption (TLS checks)
- 🚦 Rate Limiting
- 📤 Data Exposure (PII leaks, secrets)
- 🧪 Input Validation
- 🚫 HTTP 410 Gone intercept responses
- 🔁 Smart traffic redirection (301/302)
- 📧 Automated stakeholder notifications
- 📜 Full compliance audit trail
Scan any external endpoint for:
- Missing security headers
- Weak CORS configurations
- Exposed server details
- Common sensitive paths (
/admin,/.env,/swagger)
Ask questions in plain English:
- “Which APIs lack rate limiting?”
- “Explain this risk to a non-technical manager.”
- “Summarize shadow API exposure.”
💡 AI responses are based on live internal system data
-
📄 Downloadable compliance reports
-
🧾 Full decommission lifecycle tracking:
- Traffic rerouting
- Gateway blocking
- DNS removal
- Token revocation
- Documentation cleanup
- Stakeholder notification
c:\UBI\
├── .env
├── server.py
├── mock_data.py
├── database.py
├── ai_engine.py
├── openrouter_engine.py
├── email_notifier.py
└── frontend/
├── index.html
├── tailwind.config.js
└── src/
├── components/
│ ├── DashboardHome.jsx
│ ├── ApiDetail.jsx
│ ├── ExternalScanner.jsx
│ ├── Reports.jsx
│ ├── AiChat.jsx
│ ├── Sidebar.jsx- Python 3.10+
- Node.js 16+
- MongoDB instance
Create a .env file:
OPENROUTER_API_KEY=your_api_key_here
OPENROUTER_MODEL=qwen/qwen3-235b-a22b:free
# MongoDB URI
MONGO_URI=your_mongodb_connection
# Email (optional)
SMTP_HOST=your_smtp_host
SMTP_PORT=your_port
SMTP_USER=your_email
SMTP_PASS=your_password# Activate virtual environment
source .venv/bin/activate
# OR (Windows)
.\.venv\Scripts\activate
# Install dependencies (if needed)
pip install -r requirements.txt
# Run server
uvicorn server:app --reloadcd frontend
# Install dependencies
npm install
# Start dev server
npm run dev- Review critical APIs (Shadow / Zombie)
- Inspect API details
- Use AI explanations for clarity
- Decommission unsafe APIs
- Redirect traffic safely
- Scan production/staging URLs
- Export reports for audits
- Regularly monitor Shadow APIs
- Immediately decommission unused endpoints
- Use honeypots for suspicious traffic
- Validate external exposure frequently
- Maintain compliance logs for audits
- Enterprise API governance
- Security compliance (PCI-DSS, SOC2)
- DevSecOps pipelines
- API lifecycle management
Lazarus — Protecting your API estate from the shadows.