Skip to content

Fortress (Business Edge)

Fortress - Your Digital Stronghold

4GB RAM · $200 · Business-grade protection

Fortress is designed for permanent installation protecting home offices, small businesses, and enterprise edge networks with advanced network segmentation.

What Fortress Enables

CapabilityDescription
VLAN SegmentationIsolate IoT, cameras, guests, trusted
OpenFlow SDNProgrammable network control
Full IDS/IPSNAPSE engine
Local MLOn-device inference
Everything in GuardianL2-L7, dnsXai, mesh

Best For

  • Home offices
  • Small businesses
  • NIS2 compliance needs
  • Multi-VLAN networks
  • Security-conscious deployments

Hardware Requirements

ResourceMinimumRecommended
CPU4 coresIntel N100/N200 (8 threads)
RAM4GB8GB
Storage64GB SSD256GB NVMe
Network1GbpsIntel I226-V 2.5Gbps
  • Intel N100 Mini PC ($150-200)

    • 4 cores, 8 threads
    • Built-in 2.5GbE (Intel I226-V)
    • Low power consumption
  • Intel N200 Mini PC ($200-250)

    • Higher performance
    • Multiple NICs available

Approximate cost: ~$200-300

Installation

Terminal window
sudo ./install.sh --tier fortress --enable-aiochi

Installation Options

Terminal window
# Full installation
sudo ./install.sh --tier fortress --enable-aiochi
# With LTE failover
sudo ./install.sh --tier fortress --enable-aiochi --enable-lte
# With GPU support (if available)
sudo ./install.sh --tier fortress --enable-gpu

VLAN Segmentation

Fortress creates isolated network segments:

VLANIDPurposePolicy
IoT10Smart devicesInternet only, no LAN
Cameras20Security camerasNVR access only
Guest30VisitorsInternet only, isolated
Trusted40Work devicesFull access
Quarantine99CompromisedBlocked, logging

Traffic Flow

Guest Device Trusted Device
│ │
▼ ▼
┌───────────────────────────────────────────────────────┐
│ OpenVSwitch │
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
│ │ VLAN 30 │ │ VLAN 40 │ │ VLAN 10 │ │
│ │ Guest │ │ Trusted │ │ IoT │ │
│ └────┬────┘ └────┬────┘ └────┬────┘ │
│ │ │ │ │
│ ▼ ▼ ▼ │
│ ┌─────────────────────────────────────────────────┐ │
│ │ OpenFlow ACL Rules │ │
│ │ • Guest → Internet: ALLOW │ │
│ │ • Guest → Trusted: DROP │ │
│ │ • IoT → Internet: ALLOW │ │
│ │ • IoT → LAN: DROP │ │
│ │ • Trusted → All: ALLOW │ │
│ └─────────────────────────────────────────────────┘ │
└───────────────────────────────────────────────────────┘

Security Stack

Everything from Guardian plus:

ComponentPurpose
NAPSEAI-native IDS/NSM/IPS — unified packet analysis, protocol inspection, and signature matching
OpenVSwitchVLAN segmentation, OpenFlow ACLs
XDP/eBPFKernel-level DDoS mitigation
Local MLOn-device threat classification

Security Layer Depth

Layer 1: XDP/eBPF
├── DDoS mitigation
└── Rate limiting
Layer 2: NAPSE
├── AI-native IDS/NSM/IPS
├── Signature + ML detection
└── Protocol analysis
Layer 3: OpenVSwitch
├── VLAN isolation
└── ACL enforcement
Layer 4: dnsXai + ML
├── DNS protection
└── Threat classification
Layer 5: AEGIS
├── 8-agent AI orchestration
└── Autonomous response

OpenVSwitch Configuration

Bridge Setup

Terminal window
# View OVS configuration
ovs-vsctl show
# List ports
ovs-vsctl list-ports br0
# View flow rules
ovs-ofctl dump-flows br0

Example Flow Rules

# Allow established connections
cookie=0x1, priority=100, ip, ct_state=+est, actions=NORMAL
# Block IoT to trusted
cookie=0x2, priority=50, ip, in_port=1, dl_vlan=10, actions=DROP
# Allow trusted outbound
cookie=0x3, priority=50, ip, in_port=1, dl_vlan=40, actions=NORMAL
# Default: log and drop
cookie=0xff, priority=1, actions=controller

Dashboard

Fortress includes everything from Guardian plus:

Network Tab

  • VLAN status and traffic
  • Port statistics
  • Flow rule visualization
  • Bandwidth per segment

SDN Tab

  • OpenFlow rule management
  • Traffic engineering
  • ACL configuration
  • Flow statistics

Compliance Tab

  • NIS2 readiness
  • Audit log export
  • Policy enforcement
  • Incident timeline

Local ML Inference

Fortress runs ML models on-device:

# Threat classification
{
"model": "hookprobe-threat-classifier-v3",
"inference_time_ms": 2.3,
"classification": "command_and_control",
"confidence": 0.94,
"features_used": ["dns_entropy", "flow_pattern", "timing"]
}

Integration Options

LTE Failover

Terminal window
# Enable LTE backup
sudo ./install.sh --tier fortress --enable-lte
# Configure failover
nano /etc/hookprobe/lte-failover.conf

n8n Workflow Automation

Terminal window
# Enable workflow automation
sudo ./install.sh --tier fortress --enable-n8n

Use cases:

  • Automated incident response
  • Alert routing
  • Ticket creation
  • Slack/Teams notifications

Compliance Features

NIS2 Readiness

RequirementFortress Support
Network segmentationVLAN isolation
Access controlOpenFlow ACLs
Incident detectionIDS/IPS stack
LoggingFull audit trail
ReportingExport capability

Audit Logging

All actions are logged:

  • VLAN changes
  • ACL modifications
  • Threat detections
  • User authentications
  • Configuration changes

Management

Terminal window
# Status
hookprobe-ctl status
# VLAN management
hookprobe-ctl vlan list
hookprobe-ctl vlan add --id 50 --name "development"
# Flow rules
hookprobe-ctl flows list
hookprobe-ctl flows add --rule "block IoT to trusted"

Resource Usage

ResourceTypical Usage
RAM2.5-3.5GB
CPU20-40%
Disk I/OModerate
NetworkLine rate

Fortress vs Nexus

FeatureFortressNexus
RAM Required4GB16GB+
Cost$200$2000+
VLAN SegmentationYesNo
ML InferenceYesYes
ML TrainingNoYes
Fleet ManagementNoYes
ClickHouseNoYes

Upgrade Path

Ready for ML training and fleet management?

Terminal window
sudo ./install.sh --tier nexus --migrate

Next Steps

AI Intelligence (HIP)

Fortress runs the full HookProbe Intelligence Platform:

  • Hardware Detection: Supports all 13 NPU types via core/brain/hw_detect.py
  • Inference Bridge: Full ML classification + optional local LLM (TinyLlama-1.1B, 670MB)
  • HYDRA Full: All 11 microservices (anomaly detection, SENTINEL ensemble, temporal memory)
  • AEGIS Agents: 10 AI agents coordinating via PostgreSQL blackboard
  • Container Integration: core/brain/ included in HYDRA container image
# podman-compose.yml HIP configuration
hip_enabled: true
hip_local_llm: false # Enable for local LLM
hip_npu_backend: auto # auto | cpu | npu

See Brain & NPU Detection and AEGIS AI Defense for details.