Weft Start free trial

Use case · Segmentation

Segment your network, deny by default

Say what each group of devices is allowed to reach. Between your sites and devices, everything you did not permit is refused — including traffic from devices in no group at all.

The problem

Flat networks let anything reach anything, so one compromised laptop can reach the finance server. Firewall rules written against addresses break as soon as a laptop moves.

How Weft does it

  • Groups and contracts. Put subnets, sites and roaming clients into groups, then write contracts that permit one group to reach another.
  • Deny unless permitted. A device outside every group is not exempt; its traffic to your other sites and devices is refused. Removing a group restricts its members rather than freeing them.
  • Policy follows the device. A roaming laptop's address is bound to its own key, so a rule about it holds wherever it connects from. Turn on group tags on the Policy page and the group also travels in the VXLAN header between sites, so a rule can admit a device by its group as well as by its address.
  • On enforce, quarantine cuts existing sessions. Its rules come before the rule that lets existing connections through, so isolating a device stops what it is already doing, not only what it tries next. On log, quarantine only records the device's traffic; to cut off a laptop at once, remove it.
  • You choose when it starts refusing. A new organisation begins with policy off, so nothing breaks while you set up. Switch to log to see what would be refused without blocking anything, then to enforce.
  • You can see it working. The console shows how many packets each contract has allowed or denied, and every site checks that the policy it installed is still the policy in its kernel.