Selected work
Before and after
These examples are from regulated and security-sensitive sectors, so the organisations are not named. They show work specialists who partner with L3NET have done. They were not all L3NET contracts. In each one, a senior engineer, architect or lead did the work. References from former contacts are available on request.
Semiconductor sector
Data centre and firewall overhaul
Before
A legacy data centre network. Firewall rule bases split across two vendors.
What was done
Low-level designs and migration plans were written for a move to Cisco ACI. The firewall rule bases were converted from both vendors to Palo Alto, and checked before cut-over. Custom F5 traffic rules were built for per-user access to development environments, and tested before production.
After
One firewall vendor instead of two, and per-user access to development environments.
Cisco · Palo Alto · F5
Proves Architecture, Firewalls
Telecommunications
Network and security operations for a telecom operator
Before
The data centre network was old and still had to move to a new fabric. The in-house team needed training on the new fabric, the firewalls and the load balancer. Documentation was missing.
What was done
Data centre services were moved onto the new fabric, joined up with the load balancer and the virtual server platform. Technical operations for the fabric and the firewalls were led for more than four years, as the main escalation point, looking for the root cause of problems, not only the symptom. Design blueprints and application flow maps were written, and the in-house team was trained on the data centre fabric, the firewalls and the load balancer.
After
Data centre services were moved to the new fabric. The design and the application flows were written down. The in-house team was trained to run the new platforms.
Cisco · Palo Alto · F5 · Check Point
Proves Data centre, Support and escalation
Energy
Perimeter security rebuild for a utility
Before
An ageing perimeter: separate firewalls, a web proxy, a legacy intrusion detection system and an older DLP product.
What was done
The perimeter was moved onto next-generation firewalls, with intrusion prevention and malware sandboxing. Web proxy services were moved onto the firewalls. DLP was upgraded and tuned for email, web upload and removable storage.
After
The separate web proxy and the legacy intrusion detection system were retired. The firewalls now do the proxying and the intrusion prevention.
Palo Alto · Fortinet
Proves Firewalls, Data protection and AI security
Defence
Multi-pod fabric operations in a high-security environment
Before
A growing multi-pod, multi-tenant data centre fabric, with monitoring that no longer fitted it.
What was done
The operations team was led. New pods and sites were designed and built, with new fabric monitoring. The documentation and the migration plans were reviewed.
After
New pods and sites were put into service, with monitoring that matched the fabric.
Cisco · Palo Alto
Proves Data centre
Online platformsIn progress
Edge and data centre consolidation
Before
The data centre core had reached end of life. The upgrade path was blocked: the new software was not compatible, and a known bug could crash the core during an upgrade. The load balancer did not pass on the client address, so the applications logged the load balancer's address instead. Traffic that skipped the CDN was still accepted. Old equipment for a service that had moved out still used rack space.
What was done
The upgrade and replacement options were set side by side, with the risk and the hardware for each. The cause of the lost client addresses was proved with packet captures, before any change was proposed. The fix was planned in two phases: log traffic that skips the CDN first, then block it. Trust client-address headers only when they come from the CDN. The clear-out of the old equipment was planned in two phases: first the equipment of the departed service, then the shared equipment.
After
The assessment is done. A proposal to move to a new switching platform, with risk-reduction steps first, is with the client. Engineering and day-to-day support continue. Traffic that skips the CDN is planned to be logged first, then blocked. The client-address header is to be trusted only from the CDN. The clear-out is planned and will free two racks.
Cisco · F5 · Akamai
Proves Data centre, Load balancing and CDN
Public sector
Endpoint and web DLP for a public agency
Before
An endpoint DLP product that was being replaced.
What was done
Endpoint DLP was moved to a new product, set up to find sensitive data on desktops. DLP for web and social-media traffic was designed and tuned. Test evidence was produced with the security team and the penetration testers.
After
DLP was in place on desktops and web traffic, with test evidence produced with the security team and the penetration testers.
Proves Data protection and AI security