AI for networks and firewall audits
The user sees a failed connection. You need to see the entire path.
Between the branch and the application sit links, rules and equipment from multiple vendors. Myrmex reads the environment to locate the problem and prepare a fix with context.
Illustrative connection path
A rule can interrupt the path to the application.
From the symptom to the device that explains the problem.
Before changing a rule, find out what the path is telling you.
Topology organizes the observed connections. Device diagnostics help distinguish an outage from access policy or a configuration effect.
Follow the traffic until you find the explanation.
See the topology, then the end-to-end diagnosis. The analysis separates what was observed from what still needs confirmation.
“Build the topology of the building and tell me what you couldn't prove.”
Topology
What this example shows41 proven links, 9 inferred, 6 stretches with no evidence.
Illustrative scenario. Demonstration data; results depend on the environment and configured policies.
From the connection to the exposed service.
Beyond the map, see which hosts expose a port and which service or package is behind it. This evidence supports exposure investigations on observed assets.
The intent is the same. Each device has its own rules.
The work needs to account for the vendor’s configuration and syntax. Myrmex prepares the action within each integration’s context, for review before applying it.
The team’s request
Proposed configuration
Chat › SSH terminal
What this example showsThree syntaxes, one intent; applied after a named approval.
The tunnel needs to work at both ends.
Parameters, window, execution and tests belong to the same change. The change-management screen keeps the steps and rollback alongside the decision.
Changes › GMUD-0241
What this example showsTunnel up and tested; identical parameters on both sides.
Ultimately, there is an operation that needs to keep running.
Diagnosis needs to respect the reality of the equipment and the people who depend on it. Target, authorization and validation accompany the change.
Configuration has consequences beyond the console.
Work continues after the connection returns.
Auditing, resource usage and performance help find conditions that could bring the problem back. The report records what the next team needs to know.
“Audit the 34 network devices at head office and tell me where a loop can form.”
Integrations › sw-core-01 · Findings
What this example shows27 findings on the asset; two loop paths with evidence.
Before putting it to work
How we protect your operationsDoes topology distinguish observation from inference?
The examples separate proven links, inferred reach and segments without evidence. This distinction helps choose the next diagnostic step without treating a hypothesis as fact.
How does the team track a change across different devices?
The VPN scenario brings together both sides’ parameters, the change steps and planned tests. Execution depends on the permissions and approvals applicable to each integration.
Bring a network path no one can explain.
We will demonstrate the diagnosis, proposed change and connection verification.