IBM Commercial and Professional Services United Kingdom

boxxe

Security and Compliance

boxxe needed to detect and respond to faster-moving cyber threats across diverse customer environments without overloading its security analysts or relying on fragmented dashboards and manual reporting.

20 hours of manual monthly reporting eliminated
23% reduction in mean time to triage, from 13 minutes to 10 minutes
60% reduction in MTTR
65% reduction in MTTA, from 17 minutes to 6 minutes

Reported impact

Business outcome

boxxe reduced response times, cut manual reporting work, consolidated analyst tooling, and improved its ability to detect and mitigate sophisticated threats across customer environments.

  • Cost Reduction
  • Productivity Improvement
  • Risk Reduction

Solution

boxxe modernized its security-operations workflow with IBM Security QRadar SIEM on Cloud and IBM Security QRadar SOAR. QRadar's user behavior analytics applies machine learning to identify abnormal login behavior and other threats earlier than boxxe's prior manual rules, while SOAR and the unified analyst experience help analysts investigate, cross-reference, escalate, and threat-hunt from a smaller set of consolidated dashboards. The team deployed UBA in a multitenant architecture and activated more than 1,500 rules, allowing the platform to learn in the background and tune detection thresholds with minimal analyst input. QRadar's federated search also reaches into external platforms and returns filtered results into one pane of glass, which helped boxxe shrink 14 dashboards to three with a goal of one. That architecture gives the SOC broader visibility, faster detection, and lower operational overhead across managed customer environments.

Data flow

Security telemetry from customer systems is ingested into QRadar SIEM, where UBA and machine-learning analytics score risky behavior, federated search brings in context from other platforms, and QRadar SOAR helps analysts escalate and remediate threats from the same operating environment.

Solution architecture

2 components · 2 layers
  1. Serving
    • IBM Security QRadar SIEM Collects and analyzes security telemetry, applies UBA, and provides the federated investigation experience used by boxxe's SOC.
  2. Orchestration
    • IBM Security QRadar SOAR Coordinates response and automation workflows so the SOC can mitigate threats more quickly.

Architecture clues

  • Federated search is being used to consolidate 14 dashboards down to three and eventually one.
  • The deployment uses a multitenant architecture.
  • User behavior analytics detected one brute-force attack before the team's manual rule fired.

Evidence from the source

IBM Security QRadar SIEM on cloud, combined with IBM Security QRadar SOAR, offered the best advantages for today’s security challenges.
Mean time to resolution (MTTR): 60% reduction, from 35 minutes to 14 minutes
The team has deployed UBA in a multitenant architecture and activated more than 1,500 rules, and has gotten only one false positive.
Within five minutes, UBA detected abnormal logins and began increasing the activity’s risk score
eliminate about 20 hours per month of manual reporting
Transparency Evidence & methodology 100/100 reference value · 89% 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 value100/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
    4 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • 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
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference 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. IBM

    boxxe customer story

    First-party
    https://www.ibm.com/case-studies/boxxe
    Source type
    Vendor-published customer story
    Published
    Jun 7, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.