Cybersecurity
BreachSecureNow
Diagnosed a production failure across 32 microservices in 2 days, then stayed on for years.
The challenge
A US cybersecurity company had a production bug their own team could not solve for a month. It spanned 32 microservices, it was costing them, and every day it stayed open it cost more. They needed someone who could parachute into an unfamiliar system under pressure and find the real root cause, fast.
How we got there
Walking into someone else's system, mid-crisis
There was no ramp-up period. The system was live, the bug had already cost a month of the internal team's time, and every additional day it stayed open cost the business more. The job was to get productive inside an unfamiliar, 32-service system immediately, with no room for a slow onboarding.
Finding the real root cause, not just the symptom
In a system spanning 32 microservices, the failure could plausibly have been blamed on any number of components. The two-day diagnosis meant tracing the actual fault to its source rather than patching where the symptom happened to surface, the difference between a fix that holds and one that resurfaces somewhere else a month later.
Why perimeter security carried extra weight here
BreachSecureNow's own business is protecting other companies from phishing and email-based attacks, delivering security awareness training and phishing simulations to thousands of businesses through their MSP partners. For a company in that position, a gap in their own perimeter isn't just a bug, it undermines the credibility of the product itself. That context shaped why the email spoofing detection work mattered as much as the initial fix.
From emergency fix to standing engineering partner
The two-day diagnosis was the entry point, not the engagement. What followed was ongoing perimeter security and reliability work that continued for years, the kind of arrangement that only happens when a client trusts someone enough, after watching them perform under pressure once, to keep them close to the system long-term.
What we built
Root-cause diagnosis under pressure
Embedded into a live production system spanning 32 microservices and traced a month-long failure to its true root cause in two days.
Email spoofing detection
Detection logic for spoofed email at the perimeter, a core part of protecting their customers.
Perimeter security engineering
Ongoing security and reliability work across the platform through a multi-year partnership.
ROI
Results
Outcome
The two-day diagnosis turned into a partnership that lasted years. Enigma became a trusted extension of the team for perimeter security and reliability, the kind of relationship that only forms when someone proves, under pressure, that they can be relied on.
Technologies
"We've worked with Enigma for over two years and they have consistently proven to be a trusted partner. Their team delivers high-quality work on time, exceeding our expectations. We highly recommend Enigma.
Al LowensteinCTO, BreachSecureNow
