Google Cloud Commercial and Professional Services UK

SEP2

Security and Compliance

SEP2 needed to eliminate the alert-analysis bottleneck in its security operations center, where analysts were spending up to 20 minutes gathering context for a single event and risking backlogs during threat spikes.

20x faster to triage new security alerts
6x faster to write threat detection rules with Gemini
This entire data-gathering process takes the agents just one minute
spent up to 20 minutes manually checking firewalls, endpoints, and threat feeds for a single event

Reported impact

Business outcome

SEP2 now writes threat-detection rules six times faster, triages new security alerts 20 times faster, avoids analyst burnout during high-volume periods, and is building toward proactive continuous threat hunting and automated containment.

  • Compliance
  • Productivity Improvement
  • Risk Reduction
  • Speed to Market

Solution

SEP2 built an ecosystem of custom security agents on Gemini platform and Google Security Operations to automate the repetitive parts of threat triage while keeping human analysts focused on higher-value investigations. The company defines specialized agent personas such as triage agents and threat-intelligence agents that pull data from firewalls, endpoints, and external feeds, then use Gemini reasoning to summarize findings and support faster remediation. These workflows also help engineers create new threat-detection rules far faster by turning natural-language inputs into programmatic logic. SEP2 designed the environment with customer-data isolation and UK residency requirements in mind, using Google Cloud controls so client data is kept separate and never used to train public models. The roadmap extends toward continuous threat-hunting agents and a self-healing SOC where verified threats can trigger automated containment in seconds.

Data flow

When a new alert fires, SEP2's triage and threat-intelligence agents gather evidence from firewalls, endpoints, and external feeds, reason over the combined context with Gemini, and present a standardized summary to human analysts who can approve remediation or continue deeper investigation.

Solution architecture

4 components · 3 layers
  1. Compute
    • Gemini Provides the reasoning engine for custom security agents and faster rule creation.
    • Google AI Supplies the broader AI services SEP2 uses to expand security automation.
  2. Serving
    • Google Security Operations Anchors SEP2's security workflows and live remediation environment.
  3. Orchestration
    • Gemini platform Hosts the agentic security ecosystem and orchestrates multi-step threat workflows.

Architecture clues

  • SEP2 organizes the platform around specialized agent personas such as triage and threat-intelligence agents.
  • The company is integrating Google Security Operations with Gemini platform for agentic remediation.
  • The environment is configured so all customer data remains isolated and localized for UK residency needs.
  • The long-term design target is a self-healing SOC with automated containment.

Evidence from the source

20x faster to triage new security alerts
6x faster to write threat detection rules with Gemini
Because the company services enterprise clients with strict security needs, they use Google Cloud configuration parameters to ensure that all customer data remains isolated.
The long-term goal is a self-healing security operations center where verified threats trigger automated containment actions
This entire data-gathering process takes the agents just one minute
Transparency Evidence & methodology 95/100 reference value · 82% confidence · 2 sources

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 value95/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/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
    3 metrics describe measurable impact.
  • Deployment scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence82%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency9/10
    2 source references document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/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

    SEP2 customer story

    First-party
    https://cloud.google.com/customers/sep2
    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
  2. LinkedIn

    SEP2 Limited | LinkedIn

    Independent secondary
    https://www.linkedin.com/company/sep2-limited/

    LinkedIn's Organization JSON-LD lists addressLocality "Leeds", addressCountry "GB", and numberOfEmployees value 102.

    Source type
    Structured company profile
    Supports
    • Company size

Date evidence

  • Sitemap last modified Oct 9, 2026 · Google Cloud · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
  • Unverified extracted date Oct 9, 2026 · Google Cloud · Unknown Legacy extracted date without source-page confirmation.
    Open date source
Not separately sourced Industry, Region. Treat these normalized attributes as lower-confidence until a dedicated source is added.