Case studies

Work that has to go right the first time.

Many clients, especially in gaming and hospitality, don't allow their names to be published. These write-ups describe the work without naming the client.

Major Las Vegas casino operator · Ongoing engagement

ClearPass NAC rollout across thousands of Cisco switches

The challenge

A multi-property casino operator needed network access control on every wired port across thousands of Cisco IOS switches, without disrupting gaming floors, hotel operations or the many devices that had never authenticated before.

The approach

  • Designed a local ClearPass server at each property, with the data center as fallback, so a WAN outage never stops a property from authenticating.
  • Started every property on a 90-day monitor-and-accept policy to learn what was actually connected, then locked down to known devices.
  • Rolled out in stages: IOS code standardized by hardware type, global configuration next, then port configuration by interface range.
  • Checked every switch for trunks and non-standard ports first, and excluded them from enforcement rather than risk an outage.
  • Handed property technicians a simple path for new devices: add them in ClearPass, or open a ticket.

The result

Properties move to enforcement one at a time, with known devices on the network and a clear process for everything new.

Casino operator, innovation lab at a university research hub · Completed

An air-gapped demo lab alongside a production network

The challenge

A casino operator needed a lab at a university innovation center to demonstrate gaming and hospitality technology. The lab had to run alongside the company's production network while staying completely separate from it.

The approach

  • Designed and built the lab network across Aruba, Cisco, Arista and Palo Alto equipment.
  • Kept the lab air-gapped from production, so demo equipment and visiting vendors could never reach the company's live systems.
  • Built it so new gaming and hospitality technology could be brought in and shown without touching production.

The result

The operator got a multi-vendor lab for gaming and hospitality demos, isolated from the network that runs the business.

Las Vegas casino operator · Completed

Replacing a casino's datacenter network with minimal downtime

The challenge

A casino operator's datacenter ran on aging Cisco ACI infrastructure that needed to be replaced and brought up to current software. Gaming, hotel and back-office systems all depend on that datacenter, so long outages were not an option.

The approach

  • Replaced the full datacenter network: four spine switches, six sets of leaf switches, four service border leaf switches and four core routers, with the spines and core on Cisco 9500-series hardware.
  • Brought the fabric up to current software versions as part of the refresh.
  • Planned the work in stages, so each change was small, tested and reversible.
  • Ran each change in a maintenance window with a written MOP, test plan and backout plan.

The result

The datacenter runs on current, supported hardware and software, and the whole replacement was done with minimal downtime.

Las Vegas casino operator · Completed

Recovering a failed firewall deployment and standardizing the ruleset

The challenge

A gaming company's new Palo Alto firewalls, deployed by another integrator, weren't working as intended: rules weren't syncing from Panorama, configuration was being lost, and the ruleset had grown without a standard. The company called in a consultant it had trusted for years to fix it.

The approach

  • Assessed the deployment and the Panorama management setup to find why policy wasn't syncing and changes weren't sticking.
  • Rebuilt the firewalls to a clean, known configuration under change control, keeping production running throughout.
  • Brought the pair back under proper Panorama management, so policy is defined once and pushed consistently.
  • Designed and implemented a standardized ruleset: consistent naming, ordering and logging, with every rule tied to a purpose.

The result

The firewalls are stable and centrally managed, and the security team has a ruleset it can read, audit and maintain.

Credit union · Completed

Hardening the access layer with DHCP snooping and ARP inspection

The challenge

A credit union wanted to stop rogue DHCP servers and ARP spoofing on its branch networks by turning on DHCP snooping and Dynamic ARP Inspection. The catch: any device with a static IP address that wasn't accounted for would be cut off the moment enforcement started.

The approach

  • Built the list of statically addressed devices by comparing the firewall's ARP table, where the network's gateways live, against the DHCP server's leases, matched by MAC address.
  • Added the needed exceptions and reservations for those devices on the switches before turning on enforcement.
  • Staged the rollout through Aruba Central so trusted and untrusted ports were set deliberately, not by default.

The result

Snooping and ARP inspection went live without cutting off printers, cameras or other static devices, and the branches are protected against two common local-network attacks.

Biotech company preparing for an IPO · Ongoing engagement

From no documentation to an IPO-ready network

The challenge

A biotech company preparing for an IPO needed current-state network documentation for its readiness review and compliance program. There was none. The network itself also needed work: single-homed internet circuits, standalone access switches and remote access that needed a rethink.

The approach

  • Built the baseline documentation first: subnets and VLANs, public addressing, inbound services, internet circuits and failover, and diagrams.
  • Cut the FortiGate HA pair over to new Juniper core switches with link aggregation, in a planned change window.
  • Moved both internet circuits onto a redundant pair of switches with aggregated links to each firewall, so a firewall failover no longer drops a circuit.
  • Collapsed standalone access switches into stacks, one closet at a time.
  • Shut off SSL VPN entirely and assessed SASE against the existing FortiGate security stack, recommending each tool for what it does best.

The result

The core cutover and the first stack went in cleanly, the client was happy with the work, and the company now has documentation it can hand to auditors, with future-state documents to follow.

Steel fabricator in the defense supply chain · Delivered through a consulting partner

FortiGate security review mapped to NIST SP 800-171 and CMMC

The challenge

A manufacturer working toward CMMC needed its firewall reviewed against best practice and its findings tied to specific NIST SP 800-171 requirements, with remediation done against a hard deadline alongside the client's MSP and an outside assessment team.

The approach

  • Reviewed the FortiGate configuration line by line against best practice.
  • Mapped each finding to the 800-171 and CMMC requirements it affects, so the assessment team could trace every fix to a control.
  • Served as the subject-matter expert for the firewall items on the client's critical remediation tracker.
  • Coordinated changes with the client's MSP and the assessment team so nothing was done twice or missed.

The result

The client got a firewall review written in the language its assessors use, and a single owner for the firewall side of its remediation.

Global food manufacturer, North America and Europe · Ongoing engagement

Certificate-based wireless (EAP-TLS) across Fortinet and Meraki

The challenge

A global food manufacturer with sites in North America and Europe wanted to move its wireless to certificate-based authentication across two vendors, FortiGate/FortiAP and Meraki, without disrupting its existing RADIUS servers.

The approach

  • Designed EAP-TLS with certificates issued through Intune and a cloud PKI, so devices enroll without user involvement.
  • Built a separate test NPS pair rather than touching the production pair, with RADIUS returning VLANs so both vendors place users the same way.
  • Validated the design on lab hardware before rollout. The lab caught that older FortiAP firmware silently disabled WPA3-Enterprise, which was flagged as a pre-production fix for the European access points.
  • Kept a living tracking document shared with the client's regional and identity teams.

The result

A tested, vendor-neutral design, with a firmware problem found in the lab instead of in production.

Regional railroad · Completed; carrier cutover in planning

Rescuing a Cisco-to-Palo Alto firewall migration

The challenge

A railroad was replacing a Cisco router with a Palo Alto PA-445 firewall. NAT for traffic from field equipment to the railroad's operations servers worked only some of the time, and the team was close to pulling the Palo Alto out and going back to the old router. Earlier attempts to move the network's gateway had also failed without a clear reason.

The approach

  • Compared how the Cisco router and the Palo Alto each handle NAT. The Cisco reads translations from a table; the Palo Alto matches every session against zone-based policy. That explained why a rule appeared to work, but only by coincidence of routing.
  • Replaced a single bi-directional NAT rule with explicit one-way source and destination NAT rules, server by server, live with the client's team.
  • Wrote a living troubleshooting guide with side-by-side configurations, data-collection steps and a prioritized list of remaining items.
  • Mapped the rest of the traffic on the network, including radio tower and control point traffic, and found the routing, NAT and policy gaps that would have broken the next carrier migration.
  • Traced the earlier failed gateway migrations to asymmetric routing, which now shapes the plan for the upcoming carrier cutover.

The result

The new firewall stayed in place, the client was very happy with the result, and the next migration starts from a documented, understood network instead of guesswork.

Regional casino operator · Ongoing engagement

Modernizing corporate routing without a big-bang cutover

The challenge

A gaming company's corporate office and data center still ran on legacy GRE tunnels and EIGRP. The design worked, but it was hard to support and stood in the way of a planned office move and hardware refresh. Downtime on the corporate network was not an option.

The approach

  • Consolidated the firewalls' routing domains (VRFs) in planned windows, each with a written MOP, test plan and backout.
  • Brought up OSPF and BGP alongside the existing tunnels, leaving GRE and EIGRP in place as the preferred, proven path until cutover.
  • Diagnosed the side effects that appeared afterward, such as a management interface unreachable from the data center, down to missing routes and reverse-path checks, and fixed them.
  • Tracked down memory-exhaustion errors on a core switch to spanning-tree floods from a single flapping port.
  • Scoped the new office's core switching refresh with the client and built the requirements tracker for the bill of materials.

The result

The new routing design runs ready in parallel, so the final cutover is a controlled switch rather than a leap, with the old path one command away.

Regional casino operator, property sale · Completed

Sanitizing about 300 switches for a property handover

The challenge

When a gaming company sold a property, every network switch there, roughly 300 across several Cisco models, had to be stripped of the company's security and management configuration and handed to the new owner with working local access.

The approach

  • Wrote and hardened a Python script that removes authentication servers, SNMP, logging, NTP, access lists and other company-specific settings over SSH.
  • Changed the approach mid-project to point all authentication at local accounts instead of disabling AAA outright, which removed the risk of locking anyone out.
  • Added a parallel reachability checker to sort 300+ hosts into ready, unreachable and needs-attention before each run.
  • Wrote a manual fallback procedure and a console recovery checklist for the handful of switches that needed hands-on work.

The result

A job that would have taken weeks of switch-by-switch typing became a repeatable, logged process with a safe fallback.

Biotech company · Completed

Stopping a credential-stuffing attack on a firewall

The challenge

A firewall's logs showed a large-scale, automated login attack against its management interface: hundreds of thousands of attempts from a rotating botnet, using real corporate usernames.

The approach

  • Parsed and summarized the firewall's traffic and event logs to confirm the scope, the targets and the source pattern.
  • Locked down management access and hardened the firewall the same day.
  • Re-pulled the logs afterward to prove the attack had stopped, and checked that threat feeds and blocklists were still updating.
  • Flagged a separate finding along the way: the internet failover the client believed they had was not actually configured to work, with a plan to fix it.

The result

The attack stopped completely after the changes, and the client learned about a failover gap before it caused an outage.

Energy company in a regulated industry · Ongoing engagement

Planning a high-stakes ClearPass upgrade

The challenge

A company in a heavily regulated industry needed its ClearPass cluster, which handles network and device login for about 700 devices, upgraded two major versions, with urgency and with very little appetite for risk.

The approach

  • Documented the existing cluster and what each feature, certificate and service was actually used for.
  • Identified the hard blockers for the new version, such as outdated certificates and virtual hardware settings, before any change was scheduled.
  • Separated a pending authentication-method change from the version upgrade, so each could be done and verified on its own.
  • Wrote the MOP with layered rollback: the product's own rollback, configuration backups, and a synchronized snapshot of every node, confirmed with the vendor's support team.
  • Planned a full rehearsal on an isolated lab node, with steps to prove the lab can't touch production.

The result

The client has a documented environment and an upgrade plan with several independent ways back at every step.

Two-site company · Ongoing engagement

Proving an internet provider's fault with data

The challenge

The VPN between a company's two sites dropped about a dozen times a day, disconnecting shared drives. The internet provider kept closing tickets, and nobody could say for certain which side was at fault.

The approach

  • Exported weeks of gateway events and built a timeline of more than 600 outages, with duration, time of day and which gateway saw them.
  • Showed the drops were spread evenly around the clock, ruling out load, scheduled jobs and rekey timers.
  • Correlated the gateways' own health checks, including probes to the provider's directly connected equipment, to point at one circuit.
  • Built an evidence package and an escalation plan written to get past tier-one support, including answers to the provider's standard pushbacks.

The result

Instead of another ticket closed with 'no fault found', the client has a timestamped case the provider has to answer.

Pediatric medical practice, three clinics · Ongoing managed services

Managed IT for a multi-site medical practice

The challenge

A three-clinic pediatric practice with about 150 workstations depends on its network and its medical records system all day. When a cloud vendor pitched replacing much of the environment, the practice needed a clear answer on what it actually needed.

The approach

  • Runs and supports the practice's FortiGate, FortiSwitch and FortiAP network at every clinic, with SD-WAN and redundant internet at each site.
  • Maintains the servers on Proxmox, including the remote desktop servers staff use to reach their applications.
  • Reviewed the cloud vendor's proposal against the real environment and the records vendor's own move to the cloud, and showed where the pitch duplicated what the practice already had or was already getting.
  • Wrote a scope of services covering on-site support, workstations, printers, Wi-Fi, hardware and vendor management.

The result

The practice made its decision with the full picture, and kept a local partner who knows its network.

Small office, about 20 users · Completed

Recovering a failed domain controller

The challenge

A small office's domain controller failed, taking logins, file shares and group policy with it.

The approach

  • Repaired directory replication and cleaned up the failed controller's leftover records.
  • Rebuilt the domain controller as a virtual machine on Proxmox.
  • Fixed the firewall rules the domain needed and confirmed logins, shares and policies worked across the office.

The result

The office was back to normal the same day, on a rebuilt server that's easier to back up and restore.

Need references for a specific type of work? Ask on a scoping call.

Next step

Have a network that needs a second set of eyes?

Start with a 30-minute scoping call. You'll leave with a clear idea of what the work involves and a written quote.