Frequently Asked Questions

What is SAMURAI Networks?

SAMURAI Networks is self-hosted, multi-vendor network security monitoring and management software: a single pane of glass that continuously syncs configuration and state from Cisco, Palo Alto, FortiGate, Juniper SRX, VMware and Active Directory, discovers endpoints, traces traffic paths, detects changes, and analyzes firewall policy. See the Introduction for the full overview and the Firewall Analyzer for the policy-analysis side.

The default login is admin / admin. Change it immediately after the first sign-in; the UI prompts you to do so.

Does SAMURAI Networks make changes to my devices?

No. It is agentless and read-only: every platform is connected with a read-only, least-privilege account over its native API or SSH, and SSH device commands are restricted to show. SAMURAI Networks polls and reads; it never writes configuration. See Device Onboarding for the per-vendor account requirements.

How is SAMURAI Networks licensed?

SAMURAI Networks is license-gated. Get a free trial license and upload it under Settings → License after signing in. The License page shows customer, validity, per-type device limits and current usage; see Deployment for how verification works.

Can I use my own MongoDB?

Yes. The image is external-first, embedded-fallback: set MONGODB_URL to use your external MongoDB, and if it is unset or unreachable the embedded mongod is used instead. Mount a volume at /app/mongo-data to persist the embedded database. See Deployment and Database Redundancy for the high-availability options.

Which vendors does SAMURAI Networks support?

Cisco ACI (APIC), Nexus Dashboard Orchestrator, FMC, FTD/ASA, ISE, and IOS / IOS-XE / NX-OS / IOS-XR routers and switches; Palo Alto, Fortinet FortiGate and Juniper SRX firewalls; Junos and VyOS routers; VMware vCenter; and Microsoft Active Directory. The Device Panels pages show what each platform exposes.

How are device credentials stored?

Device passwords, SMTP/LDAP secrets and tokens are encrypted at rest with AES-256-GCM. TLS verification is handled per connector.