Cisco network and security engineering.
Firewalls, Catalyst switching and Meraki Wi-Fi for small businesses, schools and healthcare teams. Designed with segmentation from the start, built during agreed change windows and handed over with full documentation.
Cisco firewall engineering
New installs, replacements, fixes and clean-ups for Cisco ASA and Cisco Secure Firewall.
Build and upgrade
- New installs and replacements
- High-availability pairs
- Software upgrades and licensing clean-up
Policy
- Access policies written around how you work
- NAT
- Intrusion prevention (IPS) tuning
VPN
- Site-to-site VPN
- Remote-access VPN with Cisco Secure Client (AnyConnect)
Audits and migrations
- Unused, shadowed and overly broad rules
- ASA to Secure Firewall migration
- Test, cutover and rollback plans
Cisco Catalyst switching
The wired network every device depends on, designed for segmentation and stability.
VLAN design
- VLAN and IP address plans
- Inter-VLAN routing
- 802.1Q trunks
Stability
- Spanning tree design and clean-up
- EtherChannel link bundles
Access-layer security
- Port security
- DHCP snooping
- Unused ports shut down and documented
Upgrades
- Switch upgrades and replacements
- Port-by-port inventory and labeling plan
Cisco Meraki Wi‑Fi
Wireless that follows the same segmentation as your wired network, managed from the Meraki dashboard.
Setup
- Meraki access point installation and configuration
- Dashboard organization, networks and alerts
Segmentation
- Separate Wi-Fi networks for staff, guests and devices
- Each Wi-Fi network mapped to its own VLAN
- Guest isolation so visitors can't reach internal systems
Segmentation, planned zone by zone
Every design starts with a zone plan: who belongs in each zone and what it's allowed to reach. Firewall rules and switch configs are built from it.
| Zone | What's in it | Allowed to reach |
|---|---|---|
| Staff | Laptops, desktops, printers | Internet and the business systems staff need |
| Guest Wi-Fi | Visitors and personal phones | Internet only |
| Payments | Card terminals and point of sale | The payment processor only |
| Cameras and IoT | Cameras, door controllers, building systems | Their own recorder or controller; nothing comes in from outside |
| Servers | File, application and management servers | Only what each service needs, rule by rule |
What you get at the end
Every Cisco project ends with documentation your team, your auditor or your next engineer can use.
- As-built configurationsFinal, commented configs for every firewall, switch and access point we touch.
- Network diagramsPhysical and logical diagrams that match what's actually installed.
- VLAN and IP address planEvery zone, subnet and what's allowed to live there.
- Firewall rule matrixEach rule with its purpose, owner and business reason.
- Change and rollback planStep-by-step plan for each change window, with a way back.
- Test results and runbookWhat we tested, what passed, and how to handle common tasks.
Tell us about your network
Email a few lines about your setup and what you need. A rough description is fine; we'll ask follow-up questions.
threats@datatravelers.com- Firewall make and model, if you know it
- Roughly how many sites, users and devices
- Any deadline: an audit, a renewal or an end-of-support date