IBM Education United States

California State Polytechnic University, Pomona (Cal Poly Pomona)

Security and Compliance

Cal Poly Pomona needed to manage an enormous campus network, rising alert volumes, and multiple compliance obligations without overwhelming a small IT security team.

20-40 events tagged each day for investigation from alert pool
3,000 faculty and staff
84K devices being monitored on a 1,400-acre campus
around 100,000 users in peak periods

Reported impact

Business outcome

Cal Poly Pomona gained faster threat detection, simpler auditing and compliance support, and a much smaller pool of daily alerts for investigation, while also creating hands-on cybersecurity learning opportunities.

  • Compliance
  • Productivity Improvement
  • Risk Reduction

Solution

Cal Poly Pomona deployed IBM Security QRadar SIEM as a centralized security information and event management platform for a campus environment with more than 84,000 monitored devices. After choosing QRadar, IBM Security and university staff inventoried the architecture, documented network topology, and identified user roles with data access so alerts could be interpreted in context across police, healthcare, retail, and student systems. QRadar then centralized, normalized, and analyzed roughly 44 GB of logs and reports per day using machine learning, behavior analytics, and actionable alerting to surface suspicious activity rather than flooding staff with raw events. The platform also feeds an isolated SOC environment in the Mitchell Hill Data Center where students observe traffic and simulate issues. The result is a single monitoring layer that supports threat detection, incident response, auditing, compliance, and security education across the university.

Data flow

Logs from campus devices, wireless infrastructure, and regulated systems flow into QRadar SIEM, where events are centralized, normalized, and analyzed with behavior analytics before actionable offenses are surfaced to security staff and, in the training environment, to students running the SOC.

Solution architecture

1 components · 1 layer
  1. Uncategorized
    • IBM Security QRadar SIEM Centralizes, normalizes, and analyzes campus security telemetry so staff can focus on actionable threats and compliance needs.

Architecture clues

  • IBM Security and Cal Poly Pomona conducted a detailed inventory of the architecture and network topology during deployment.
  • Security staff added dashboard widgets to watch specific departments after incidents reoccurred.
  • The Mitchell Hill Data Center hosts an isolated student-managed SOC environment that mimics production.

Evidence from the source

"QRadar SIEM empowers Cal Poly Pomona to centralize, normalize and analyze incoming data from over 84,000 devices"
"We were getting so many device alerts that it could soon become overwhelming."
"With QRadar we quickly identified and reconfigured these systems in that same week."
"the solution routinely narrows potential alerts each day to between 20 and 40 actionable items"
"this generates roughly 44 GB of logs and reports each day"
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
    2 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

    California State Polytechnic University, Pomona (Cal Poly Pomona) customer story

    First-party
    https://www.ibm.com/case-studies/cal-poly-pomona
    Source type
    Vendor-published customer story
    Published
    May 14, 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.