Google Cloud Retail Portugal

MC

Security and Compliance

Beyond daily defense, MC needed to solve the ultimate reliability puzzle: the "3rd site"—a dedicated, cloud-based disaster recovery environment designed to act as a fail-safe outside their existing physical data centers.

Achieved a 2 TB/day data ingestion, providing the Security Operations Center with 12 months of total historical visibility
Achieved a one-hour Recovery Point Objective, ensuring near-zero data loss for 340 TB of critical transactional systems
Beyond daily defense, MC needed to solve the ultimate reliability puzzle: the "3rd site"—a dedicated, cloud-based disaster recovery environment designed to act as a fail-safe outside their existing physical data centers. Protecting their…
MC redefined their defensive posture by implementing Google Security Operations (SecOps) Enterprise Plus . This "Next-Generation SOC" transition allowed them to scale massively, ingesting 2 TB of data per day with 12 months of hot…

Reported impact

Business outcome

Restored 800+ critical VMs; in less than 20 hours, significantly beating the 24-hour business continuity target; Achieved a 2 TB/day data ingestion, providing the Security Operations Center with 12 months of total historical visibility; Empowered analysts with Google AI tools, shifting focus from "maintenance" to active security

  • Cost Reduction
  • Customer Experience
  • Productivity Improvement
  • Revenue Growth

Solution

Beyond daily defense, MC needed to solve the ultimate reliability puzzle: the "3rd site"—a dedicated, cloud-based disaster recovery environment designed to act as a fail-safe outside their existing physical data centers. MC used Google SecOps Enterprise Plus and a cloud-based disaster recovery environment to ensure a resilient, fail-safe SOC. MC redefined their defensive posture by implementing Google Security Operations (SecOps) Enterprise Plus . This "Next-Generation SOC" transition allowed them to scale massively, ingesting 2 TB of data per day with 12 months of hot retention, providing a… Key components include Gemini provides the reasoning or generation layer used for classification, orchestration, content generation, or analysis; Google SecOps Enterprise Plus adds governance, security, and control to the production AI and data environment; Compute Engine runs serverless or virtualized application services with elastic scale for production AI workloads; Google Security.

Solution architecture

6 components · 2 layers
  1. Compute
    • Gemini Provides the reasoning or generation layer used for classification, orchestration, content generation, or analysis.
    • Compute Engine Runs serverless or virtualized application services with elastic scale for production AI workloads.
  2. Governance
    • Google SecOps Enterprise Plus Adds governance, security, and control to the production AI and data environment.
    • Google Security Operations (SecOps) Adds governance, security, and control to the production AI and data environment.
    • Google SecOps Adds governance, security, and control to the production AI and data environment.
    • Google Threat Intelligence Adds governance, security, and control to the production AI and data environment.

Architecture clues

  • Beyond daily defense, MC needed to solve the ultimate reliability puzzle: the "3rd site"—a dedicated, cloud-based disaster recovery environment designed to act as a fail-safe outside their existing physical data…
  • Beyond threat detection, MC established a high performance "3rd site" on Google Cloud VMware Engine and Compute Engine . This cloud-native architecture serves as a digital vault, allowing MC to replicate their entire…
  • Google Cloud to challenge the status quo, seeking a partner with the key to automate recovery and scale security. This wasn't just a migration; it was a journey to ensure that even in the face of a total data center…
  • In a real-life scenario, a security analyst no longer spends hours writing complex queries or sifting through disparate logs. Instead, they use Natural Language AI prompts to ask Gemini for instant summaries of alerts…
  • MC redefined their defensive posture by implementing Google Security Operations (SecOps) Enterprise Plus . This "Next-Generation SOC" transition allowed them to scale massively, ingesting 2 TB of data per day with 12…

Evidence from the source

Achieved a 2 TB/day data ingestion, providing the Security Operations Center with 12 months of total historical visibility
Achieved a one-hour Recovery Point Objective, ensuring near-zero data loss for 340 TB of critical transactional systems
Beyond daily defense, MC needed to solve the ultimate reliability puzzle: the "3rd site"—a dedicated, cloud-based disaster recovery environment designed to act as a fail-safe outside their existing physical data…
Empowered analysts with Google AI tools, shifting focus from "maintenance" to active security
MC used Google SecOps Enterprise Plus and a cloud-based disaster recovery environment to ensure a resilient, fail-safe SOC.
in less than 20 hours, significantly beating the 24-hour business continuity target
Transparency Evidence & methodology 90/100 reference value · 77% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value90/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth15/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    5 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence77%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    6 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Google Cloud

    MC customer story

    First-party
    https://cloud.google.com/customers/mc-sonae
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived May 12, 2026 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Apr 24, 2026 · Google Cloud · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.

Related

Similar use cases

See all like this