Building a Rule
Click + Add Rule in the Compliance Rules editor to create a new rule. Each rule has a name, an IF row, a THEN row, a severity, and an enabled toggle.
Naming a rule
Section titled “Naming a rule”The name you give a rule is exactly what gets shown as the warning message on a node, in its Properties panel — so write it as the message you want a teammate to see, e.g. “Databases must have an IP address recorded,” not just “DB rule 1.”
The IF row
Section titled “The IF row”The IF row picks which nodes this rule applies to, using two dropdowns:
Node type — any icon type from the library (Server, Database, Firewall, Workstation, …), or Any node to match every node regardless of type.
Condition — optionally narrows further:
| Condition | Applies when… |
|---|---|
| (always) | No extra narrowing — applies to every node of the chosen type. |
| when crossing a network boundary | The node has at least one connection to a node in a different zone or segment (or a differently-contained neighbor). |
| when connected to internet | The node is directly connected to a node of type Internet. |
| when role is… | The node’s Role field (in its Properties panel) matches a value you type in. Matching ignores case. |
| when environment is… | The node’s Environment field matches — e.g. apply a rule only to Production systems. |
| when criticality is… | The node’s Criticality field matches — e.g. only to Critical systems. |
| when inside a zone | The node’s parent container is specifically a Zone (not a Network Segment). |
| when isolated (no connections) | The node has no connections at all. |
The THEN row
Section titled “The THEN row”The THEN row defines what must be true about a matching node’s connections:
| Relationship | Checks |
|---|---|
| must have in path | A node of the target type exists anywhere reachable from this node, following connections in any direction (not just direct neighbors). |
| must NOT have in path | Same reachability check, but the rule fails if a node of that type is found anywhere in the path. |
| must be directly connected to | A node of the target type is one connection away — a direct neighbor. |
| must NOT be directly connected to | No direct neighbor is of the target type. |
| must have at least N of | At least a chosen number of direct connections match the target type — or use Any node as the target to just require a minimum number of connections, regardless of type. |
| must have field set | A specific field on this node itself is non-empty — any of the fields in its Properties panel: Name, Hostname, IP address, Owner, Role, OS, Environment, Criticality, Location, Serial, and the rest. |
Severity and enabled
Section titled “Severity and enabled”- Warning (amber) or Error (red) — purely visual; both block nothing, they just change the badge and message color to signal how serious the finding is.
- Enabled — uncheck to keep a rule defined but temporarily turn it off, without deleting it.
A worked example
Section titled “A worked example”To require every server to sit behind a firewall somewhere in its connection path:
- Name: “Servers should be reachable through a firewall”
- IF: node type = Server, condition = (always)
- THEN: relationship = must have in path, target = Firewall
- Severity: Warning
Scope your rules carefully
Section titled “Scope your rules carefully”The single biggest thing to watch for: “Any node” in the IF row really does mean any node — including your switches, routers, and the firewall itself. A rule like “must be directly connected to a Firewall” scoped to Any node will also flag your core switch, your load balancer, and your VPN gateway, since none of them are directly touching a firewall either — even though none of them arguably should be.
In practice, scope rules to a specific node type (Server, Database, Mail, …) unless you genuinely mean every single node on the diagram. If a rule is producing warnings on nodes that don’t seem like real problems, that’s usually the fix — narrow the IF row’s type, not the THEN row.
Deleting a rule
Section titled “Deleting a rule”Click Delete at the bottom of the rule’s row in the editor. This can’t be undone from within the app — if you want it back, you’d need to re-create it (or reload an earlier saved copy of the diagram file).