Trust · Security

Security as infrastructure

Marseille UPG runs payment-grade infrastructure on which our customers’ revenue depends. Our security programme is engineered, audited and monitored continuously — not a static document.

Last red-team
Feb 2026
Last pen test
Jan 2026
PCI scope
Level 1 service provider
SOC
24 / 7 / 365
Defence-in-depth architecture

Mutually authenticated, segmented services. Every internal call is signed, audited and rate-limited.

Cryptography by default

TLS 1.3 in transit, AES-256 at rest, FIPS-validated HSM-backed key custody for signing material.

Data minimisation

PAN data is tokenised or vaulted; the platform stores no cardholder data outside scope.

Strong identity

Hardware-key SSO and MFA for all admin paths. Per-tenant RBAC and ABAC for customer surfaces.

Continuous monitoring

24/7 SOC, behavioural detection, signed audit logs and immutable forensic retention.

Adversarial testing

Quarterly external penetration tests and continuous internal red-team exercises.

Authorised uptime SLO
99.995%
Detection median
< 30s
Containment median
< 15m
Cardholder-data incidents
0
01

Architecture

The platform runs across hardened multi-tenant service meshes in three independent regions (EU, US, APAC). Each region is self-sufficient: a regional outage does not propagate to others. All inter-service traffic is mutually authenticated using mTLS and signed at the application layer.

  • Network segmentation by trust zone: edge, control plane, processing plane, vault, observability.
  • Cardholder data flows are isolated to a hardened PCI environment with dedicated identities and key material.
  • Multi-region active/active for stateless paths; durable, replicated storage with regional pinning for stateful paths.
  • Configuration as code with two-person review and signed deployments; production access requires JIT approval.
02

Data protection

  • Tokenisation: PAN values are exchanged for tenant-scoped tokens; raw PAN never traverses the application plane.
  • Encryption at rest with AES-256 using customer-segregated keys; rotation enforced quarterly.
  • Encryption in transit with TLS 1.3 minimum, modern cipher suites only, HSTS, and certificate transparency monitoring.
  • Key custody on FIPS 140-2 Level 3 HSMs; signing keys dual-controlled and rotated on schedule and on event.
  • Backups encrypted, integrity-checked, periodically restored end-to-end, and geo-replicated within region.
03

Access control

  • Mandatory SSO with hardware-key MFA (FIDO2) for all employees and contractors.
  • Just-in-time, ticket-bound elevation; no standing production access for engineers.
  • Per-tenant RBAC and ABAC in the dashboard, with API-key scopes, IP allowlisting and short-lived tokens.
  • Quarterly access reviews; automated revocation on role change, leave or termination.
04

Operations & monitoring

  • 24/7 Security Operations Centre with follow-the-sun coverage across EU, US and APAC.
  • Centralised, signed audit log with immutable cold storage for forensic and regulatory retention.
  • Behavioural detection across identity, network, runtime and configuration planes.
  • Synthetic transaction monitoring across critical flows with paging on regression.
05

Incident response

Our incident response programme is documented, rehearsed quarterly, and integrated with customer notification channels. Severity 1 incidents are paged to executive leadership within 15 minutes and customers are notified per contractual commitments.

  • Runbooks for top-tier scenarios: credential compromise, vendor outage, data exposure, fraud spike.
  • Forensic retention with chain of custody and read-only review surfaces.
  • Post-incident reviews published in a customer-facing format on the status page within 5 business days.
06

Application security & SDLC

  • Threat modelling required for new services and major changes; reviewed by a security architect.
  • Static analysis, software composition analysis and secrets scanning enforced in CI; PRs blocked on high-severity findings.
  • Mandatory peer review for all changes; production deployments are signed and reproducible.
  • Dependency provenance via SLSA-aligned build attestations; SBOM published per release.
07

Third-party risk

Every sub-processor is reviewed for security, privacy and resilience before onboarding, and continuously thereafter. Material vendors are tier-classified, contractually bound to flow-down requirements, and published in the DPA.