FAQ
Frequently Asked Questions

Everything you need to know about HoneyBee Platform — from technical architecture to deployment timelines.

Q. How is HoneyBee Defender different from traditional firewalls or EDR?+

Traditional firewalls focus on network perimeter control; EDR on file and behavioral detection. Defender operates at the process level — controlling server-to-server communication by PID. This closes the lateral movement gap both miss.

Q. How does Process Identity-Based Microsegmentation work?+

Beyond IP/Port filtering, Defender identifies processes by name, command-line, and hash value. Only authorized processes can communicate; unauthorized ones are detected and blocked instantly.

Q. Does it impact server performance?+

No. CPU usage 1–3%, memory under 20MB. Validated in production environments with thousands of servers without performance degradation.

Q. How does it handle firewall tampering?+

Defender performs real-time policy integrity verification. Any unauthorized modification is detected and automatically restored — zero security gap, zero operator intervention.

Q. Can it run alongside EDR, NAC, SIEM without conflicts?+

Yes. Defender operates on the OS firewall layer, architecturally independent from other tools. It complements EDR, NAC, and SIEM without policy conflicts.

Q. How does Zero Trust implementation work without service disruption?+

Defender runs in detection mode first to learn normal communication and build a whitelist. After operator validation, it transitions to blocking mode — Zero Trust at process level without service outages.