1. What is dog?
2. Why dog?
3. Features
4. Components
5. Architecture
6. Security
7. Quick Install
8. Install
9. Use
10. Road Map

dog is a distributed firewall management system designed to manage hundreds+ of per-server firewalls. Currently iptables on Linux supported, but others could be added.

dog is your network guard dog.

'dog-fw' is the search friendly name for dog.

• Need consistent network access rules across hundreds+ of servers in multiple regions on multiple providers?
• Need defense-in-depth, beyond gateway firewalls?
• Need blocklists with thousands of addresses distributed across many servers updated constantly?
• Need to limit number of connections and/or bandwidth usage?
• Sick of error-prone manual updates of per-server iptables rules?

• Centrally manage hundreds+ of per-server iptables firewalls.
• Works across clouds, regions, and on-premise infrastructure.
• Adapts to dynamic address changes.
• Large blocklists/allowlists can be used and will be updated across all servers in seconds.
• Rules scale to tens of thousands of addresses (using ipsets).
• Alerts if servers fail to communicate or if their firewalls are modified outside of dog control.
• Reactive web interface.
• API for external integrations.
• Tested in production with hundreds of servers.
• Multiple dog_trainers can be federated together to allow sharing of addresses, while allowing each dog_trainer to have its own security rules.
• Integration with Flan Scan, a network vulnerability scanner.
• Agents support Linux 2.6+ iptables firewalls.
• Supports cloud public IP addresses (currently only EC2).
• Manages cloud security groups across multiple regions (EC2).
• Compatible with Docker, LXD localhost firewall rules.
• Terraform Provider: Can be managed as code with a Terraform provider.
• Ansible Plugins: Can be used as a dynamic inventory source and/or as a connector, replacing ssh.

• dog_trainer is a central server, used to configure and control dog agents.
  Multiple dog_trainers can be federated together to allow sharing of agents' addresses, while allowing each dog_trainer to have its own security rules.

• dog agents are deployed to all managed servers. dog agents control the server's iptables firewalls.

• dog_park is the browser user interface for dog_trainer.

• dog Agents communicate with dog_trainer over RabbitMQ queues.
• dog_trainer stores its configuration in a RethinkDB database.
• dog_park communicates with dog_trainer via a RESTful API, which can be used for further integrations.

• Provides defense-in-depth, so you are not completely dependent on gateway firewalls.
• dog agents authenticate to RabbitMQ with per-agent client certificates, and all communication is encrypted.
• RabbitMQ should be configured to only communicate over private networks.
• Additional federated RabbitMQs can be configured to allow communication over regional boundaries.
• dog_trainer stores hashes of the iptables and ipsets it sends to agents. Agents send their own generated hashes to dog_trainer via a scheduled check-in.
• dog_trainer will alert if agents fail to communicate over time or if the hashes the agents provide do not match what dog_trainer expects.
• dog's use of ipsets not only allows highly scalable, fast rulesets, it also keeps iptables size small enough to be auditable by a human.

A working dog environment on containers in a local VM

• dog_on_a_dock

• dog_trainer
• dog_park
• dog_agent

• user_manual

• Manage Cloud security groups
  • AWS EC2
  • Google Cloud
  • Microsoft Azure
• Support Cloud Instances
  • AWS EC2
  • Google Cloud
  • Microsoft Azure
• Agent support for
  • More Linux distros
    • Arch
  • Other *nix OSes
    • BSD
• Support for other firewall types
  • nftables (beyond the current iptables-legacy compatibility support)