The challenge
Strata GPO is a group purchasing organization. Its portal is where dealer members, vendors and Strata staff handle invoices, remittance, documents and reporting every day. Then an independent security assessment flagged critical weaknesses at the foundation of the platform.
Passwords lived in the portal's own database with no second factor. Internal services accepted requests without checking who was calling. Secrets were partly hardcoded, releases were partly manual, and nothing scanned code or inspected traffic. Strata needed it all fixed while thousands of people kept using the portal.
What we did
Rebuilt sign-in with MFA
We replaced the portal's own login with Microsoft Entra External ID and a second step by email or text-message code, so the portal no longer stores credentials.
Kept members' passwords
A user's first sign-in carried the existing password across, so most users kept the password they already had.
Made every service verify callers
The API and both supporting services now check a signed token on every request, apply shared role-based rules and reject unknown endpoints by default.
Moved every secret to a vault
All passwords and keys now live in Azure Key Vault, read through managed identities, with soft delete, purge protection and audit logging.
Guarded the front door
All traffic now passes through Azure Front Door with a web application firewall, released in monitoring mode first and tuned against real traffic before blocking.
Made releases safe by default
Automated database migrations, environment-pinned builds, and code, dependency and secret scanning on every change block whole classes of mistakes.
“Briebug has delivered features on time and within budget, and we've seen end-user satisfaction through positive word-of-mouth reviews.”
The impact
What changed for the business.
Audit findings closed
An audit report became a documented set of fixes Strata can show auditors, partners and customers.
Members kept working
The new sign-in launched in one overnight release, and there were 1,932 successful sign-ins on the first day.
No secrets in code
Zero passwords or keys remain in source code; each service reads its own secrets from a managed vault.
Clean code scanning
All three codebases are scanned on every change, and zero code-scanning findings were open at closure.
Mistakes blocked automatically
The release pipeline now blocks the same classes of mistake automatically, before they reach production.