Hubfly spaceDocs
Console

Box · Guide

Box firewall

Control inbound and outbound traffic at the Box or NIC level, then inspect the effective policy and counters.

Defaults and layers

New Boxes start with an inbound allowlist and outbound allow-all. A Box policy supplies the baseline; each NIC may inherit or override the inbound and outbound mode.

  • An allowlist permits only traffic matched by allowed rules and platform-managed exposure exceptions. Allow-all opens that direction more broadly.
  • A NIC override affects that interface. Read the effective policy when diagnosing a connection because the saved Box policy alone may not show the final result.
  • The guest OS can run its own firewall too; Box policy cannot open a port blocked by the guest.

Edit rules without overwriting another change

Read the current policy, change its enabled state, direction modes, and rules, then submit the update. Both Box and NIC updates support a generation value.

  • Use the current generation when supplied so stale edits do not replace a newer policy.
  • Rules are ordered and have action, protocol, source or destination selectors, and ports as exposed by the API schema. Keep rules narrow and document why each one exists.
  • A port mapping adds a narrow inbound exception for its guest port. Remove unused mappings rather than relying only on a broad deny rule.

Verify enforcement

The effective-policy endpoint shows the merged rules applied to a Box or NIC. Counters show matched traffic and can be reset for a new measurement window.

  • Compare desired and observed generations when policy looks stale. A mismatch signals that enforcement may not have caught up or failed.
  • Reset counters only if you no longer need their previous values; reset is an operation, not a read.

Automating this workflow

See the matching Box API endpoints for exact request fields and response schemas. Host operations can continue after an API request returns.

Back to the Box guide · All Box API groups

Something unclear or out of date? Emailsupport@hubfly.spaceBack to top