Secured regional events portal across several environments
CASE STUDY / 06ANONYMISED ASSIGNMENT
Media · events listing

Regional events portal

An events portal partly fed by automated collection, served by a modern front end, a business API and satellite services across three environments.

DURATION1 year
ROLEDevelopment, security, deployment
SCOPE3 environments
STATUSIn production
THE CONTEXT WE FOUND

Understand the system
before transforming it.

The assignment became critical when a remote code execution vulnerability, rated 9.5 out of 10, was published on the image optimiser of the framework in use.

WHAT WAS DONE

From diagnosis.
To production.

The scope describes the decisions and the work actually carried out, without naming the organisation involved.

01

Close the critical vulnerability

Remote sources disabled, framework upgraded and the fix verified live on all three environments.

02

Prove the absence of regression

Code analysis before the change: the site only used native images, so closing the feature had no functional effect.

03

Detect server drift

Fingerprint comparison between servers and repository after a manual fix that had never been committed was found.

04

Change the deployment rule

An uncommitted fix is now considered non-existent, to prevent any silent reintroduction.

MEASURED RESULTS

Facts.
Not a logo.

9.5 / 10flaw closed on 3 environments
Server driftdetected before any regression
3 environmentsfixed and verified
TECHNOLOGIES IN PRODUCTION

The foundation actually used.

Next.jsSymfonyMicroservicesDockerrsyncTraefik

Clients, brands, domains, addresses and identifying details are not published. The figures come from the logs, databases, clusters, repositories and control reports provided for these assignments. Security incidents are described without any reproducible exploitation path.

A critical system to build or to take over?

Describe the context, the existing systems and the expected result. We will propose the right level of intervention.

Talk to RGAIX