Demo listing. This page uses illustrative seed metadata to demonstrate the Atlas. Claims shown here are not verified product facts.
BotLens
Network-side deep-autoencoder sentinel that learns each IoT device’s benign traffic snapshots and flags Mirai/BASHLITE-class attack…
A network-side deep-autoencoder sentinel that learns each IoT device’s benign traffic snapshots and flags Mirai/BASHLITE-class attack execution in under a second, so enterprises can cut bots off before outbound DDoS ramps.
Last verified 15 Sept 2026 · Updated 23 Sept 2026 · Metadata v4
Problem
Large enterprises and campuses with heterogeneous Wi-Fi IoT (including BYO wearables and facilities devices) that need centralized detection of *attack launch*, not only early infection scanning.
Outcome
A deployment-ready foundation that teams can configure into production.
Who uses it
- Operations Analyst
- Solution Architect
Key capabilities
Core workflow
AI-assistedIncludedPrimary operating workflow for this foundation.
Document intelligence
AI-assistedIncludedExtract and ground decisions from operating documents.
Typical workflow
Primary operating flow
Trigger: An operator starts the primary use case
Task
Stage 1: Capture inputs
Operator
AI-assisted
Stage 2: Assist with draft
System
Human checkpoint
Stage 3: Human approval
Approver
Task Automated AI-assisted Human checkpoint Decision
About this foundation
Per-device deep autoencoder NIDS for IoT botnets. NetRoster whitelists device *type* from behavior; ShadeScan inspects *binaries* on-device; QuorumSense merges on-device models; BotLens productizes N-BaIoT — 115-dimensional behavioral snapshots and deep autoencoders that reconstruct normality and fail loud on Mirai/BASHLITE attack traffic, with empirical sub-second isolation potential versus DDoS attacks that often last 20–90+ seconds.
Related applications
- AetherGrain
Hub-side RF physical-unclonable authenticator that recognizes transmitters from manufacturing “grain” in their radio chains — without…
- • Addresses the same problem: Manual Workflow, Fragmented Systems
- • Shared capabilities: Workflow Automation, Document Intelligence
- AgentWeave
Configuration studio for embodied IoT agent fleets that captures variability in sensors/actuators/behaviors, learns from evaluative…
- • Addresses the same problem: Manual Workflow, Fragmented Systems
- • Shared capabilities: Workflow Automation, Document Intelligence
- AlertStride
Streaming fall-detection service for retirement homes and rehab clinics that scores wearable accelerometer feeds in real time and notifies…
- • Addresses the same problem: Manual Workflow, Fragmented Systems
- • Shared capabilities: Workflow Automation, Document Intelligence
- ApronLink
Delivers beacon-accurate, personalized airport journeys—wayfinding, flight alerts, offers, parking pay—so hubs absorb demand spikes…
- • Addresses the same problem: Manual Workflow, Fragmented Systems
- • Shared capabilities: Workflow Automation, Document Intelligence
- AskShield
Human-in-the-loop active learning IDS for wireless IoT that queries analysts only for the most informative unlabeled flows, so teams reach…
- • Addresses the same problem: Manual Workflow, Fragmented Systems
- • Shared capabilities: Workflow Automation, Document Intelligence
- BitNest
Deployment toolchain that packs large CNNs into local quantization regions so resource-constrained IoT controllers run vision and speech…
- • Addresses the same problem: Manual Workflow, Fragmented Systems
- • Shared capabilities: Workflow Automation, Document Intelligence
Primary operating flow
Trigger: An operator starts the primary use case
Task
Stage 1: Capture inputs
Operator
AI-assisted
Stage 2: Assist with draft
System
Human checkpoint
Stage 3: Human approval
Approver
Actors
Operator, Approver
Outputs
- Completed work item
Evidence generated
- Audit trail
Exceptions
- Incomplete inputs returned to operator
Task Automated AI-assisted Human checkpoint Decision
Included ships in the foundation · Configurable is switched or tuned per customer · Extension is customer-specific build scope · Planned is on the roadmap and not available today.
Core workflow
AI-assistedIncludedPrimary operating workflow for this foundation.
Document intelligence
AI-assistedIncludedExtract and ground decisions from operating documents.
- Architecture class
- Domain-driven design, OpenAPI-first
- Bounded contexts
- 5
- API-first
- Yes — OpenAPI contracts are authoritative
- Identity
- Enterprise OIDC / SAML via the fazeZERO identity blueprint; tenant-aware role-based access.
- Multi-tenancy
- Tenant-aware
- Service boundaries
- Bounded contexts behind one API server.
- Integration approach
- Ports-and-adapters: every external system sits behind an adapter; OpenAPI contracts for inbound APIs.
- Eventing
- Integration events via transactional outbox.
- Storage abstraction
- Repository interfaces; DynamoDB or relational adapters.
- Deployment pattern
- Containerized API + web application; infrastructure as code per cloud profile.
- Architecture version
- 1.0
Approved domain names
- identity
- catalog
- workflows
- Web Application
- API Server
- Application Services
- Domain / Generated Core
- Adapters
- Customer Systems
Generator source, templates and factory orchestration are proprietary and are not part of this listing.
Reference Adapter: shipped and tested · Previously Integrated: delivered before · Standard API Pattern: integrates via a documented pattern · Customer-Specific: built in your implementation.
APIs
| Integration | Status | Direction | Method |
|---|---|---|---|
| Customer systems of record | Standard API Pattern | bidirectional | REST API |
Deployment
- Deployment models
- Customer Cloud, Private Cloud
- Cloud profiles
- Azure Profile, Cloud-Neutral
- Containerized
- Yes
- Regions
- GLOBAL
Cloud profiles describe approved deployment patterns. They are not formal marketplace certifications.
Data handling
- Stores customer data
- Configurable
- Data leaves customer environment
- Configurable
- Uses external AI provider
- Configurable
- Sends logs externally
- No
- PII expected
- Determined during customer configuration
- Data-residency support
- Yes
- Subprocessors required
- Determined during customer configuration
Identity & access
- Authentication
- OIDC, Entra ID, SAML
- Authorization
- Role-Based, Tenant-Aware
- Source availability
- Proprietary
Support
- Implementation
- Delivered by fazeZERO or a certified partner during the Solution Definition and AI Production Sprints.
- Production support
- Production support available under a separate support agreement.
- Contact
- support@fazezero.com
Badges
fazeZERO Verified
Listing metadata and published technical claims have been reviewed by fazeZERO.
Issued 23 Sept 2026
Evidence shows that this listing represents real engineering. Internal metrics are only published when fazeZERO has approved them for publication.
Build
Automated tests
Deployment validation
- Last verification
- 15 Sept 2026
- Release
- 1.0.0
- Architecture version
- 1.0
- Listing metadata version
- 4
- Last published
- 23 Sept 2026