Zone: Delivery

How we deliver: evidence first, change second

Most stalled security projects stall for the same reasons: nobody has one trustworthy picture of what is running, nobody can say what a rule change will touch, and nobody wants to be the person who cannot undo it. Our delivery model is built around those three problems, and so is the tooling we use.

One record of the estate

Devices, rules, routes, addresses and the traffic between systems are read from the platforms themselves and kept in one place, with the source of every fact. Gaps stay visible as gaps.

A path before a rule

Before policy moves, we trace the path between two systems hop by hop and name the rule or route where traffic stops. The question "what will this touch?" gets an answer from data.

Changes you can undo

Every change is a written plan with its inverse recorded before it runs. Higher-risk steps need a second person to approve, and anything that cannot be undone is called out before it starts.

Zone: Tooling

The tooling behind an engagement

Where an engagement benefits from it, we work with Storm Eye Core, software made by Storm Eye Networks for exactly this kind of work. It is installed on infrastructure you control, it is not in the packet path, and it changes nothing except through a reviewed plan. What it does today, in its 0.7.0 release:

See and trace

  • Discovery and inventory — private ranges you choose, with suggestions for the integration that fits each host. Public address space is refused.
  • Integration packs — separately versioned connectors for firewalls, SASE, SD-WAN, cloud, NAC, identity, IPAM, CMDB, hypervisors and endpoint tools. Only the ones an engagement needs are installed.
  • The layer-2 map and path trace — devices, links, subnets and the systems on each switch port, drawn from the network's own ARP, MAC and routing tables; pick two systems and walk the path.
  • Flow visibility — which hosts talk to which, on what port, as the evidence behind a segmentation proposal.

Change and prove

  • Change plans with a second approver — risk tiers, change windows and freezes, and tickets in Jira or ServiceNow where you already use them.
  • Segmentation in waves — proposed from observed traffic, simulated before enforcement, checked after each wave and rolled back with approved inverses if a wave fails.
  • Vendor migration — policy lifted into a neutral form, mapped and rendered on the destination, with every field the destination cannot express named as a loss.
  • Assistants that draft, people decide — optional, with your own model; they explain and draft but cannot approve, and only see the data you allow.

What we will not claim: integrations are tested to different depths, and some have met recorded vendor API responses rather than live equipment. Before we rely on any of it for your platforms, we tell you which applies.

Zone: Next

In development for Core 0.7.1

Storm Eye Networks is building the following for the next release. It is not available yet, and details can change before it ships.

More packs

Thirteen new or extended platforms, from WatchGuard and Forcepoint to CrowdStrike, SentinelOne and network access control, each with reviewed, reversible writes.

Layer 2 everywhere

Every pack and agent that can supply ARP or MAC data feeding one map, with click-to-trace and services along the path.

Incident response

A tamper-evident incident timeline, frozen evidence, and containment through pre-approved, bounded runbooks.

Tenant cells

For managed services: each customer in a separate cell with its own database, keys and licence, behind one sign-in.

Licensing

A registered Free tier and paid tiers with signed leases. A lapse never deletes data or blocks a rollback.

Zone: Accounts

Customer accounts

When Storm Eye Core licensing goes live, customers can be invited to an account on this site to see their own licences: product, edition, seats, installs and expiry. Licence keys are never shown on the site. Accounts are by invitation only. Sign in.