From the CrowdStrike edition of October 29, 2026
CrowdStrike | UC-Wide Agreement (University of California Systemwide Procurement)
University of California Office of the President, Systemwide Procurement · Higher education and academic health · California, USA
- Publisher
- UC Procurement
- Original publication
- 2026-07-18
- Source retrieved
- 2026-10-30
- Event date
- 2026-07-18
What happened
UC established a systemwide agreement with CrowdStrike as of July 18, 2026 for Falcon Complete MDR and related endpoint security, reporting a 61% cost reduction versus initial pricing available to all UC locations. Negotiated terms include UC Appendix DS (Level 4 protections), Appendix BAA and Appendix GDPR. UC says adapting CrowdStrike's standard model to public-sector requirements for cyber risk allocation, data security, privacy and incident notification was challenging and required Procurement, Legal, Cybersecurity, Privacy, Risk and CIO coordination.
Why it matters
A large public research university system shows how data-security, BAA, GDPR and incident-notification terms can be negotiated into a vendor's standard model at system scale.
Evidence and measured results
Institutional procurement announcement. The 61% figure is a negotiation outcome versus initial vendor pricing, not versus market or prior spend; no security outcome data. 'Effective' refers to the procurement outcome only.
Limitations and uncertainty
Self-reported by the buyer; 'initial pricing' baseline undefined; deployment scope per campus not stated; AI features not mentioned. Published July 2026, before this edition; included because the stream has no prior run and the terms precedent is current.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-29; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Standard vendor terms did not fit UC's public-sector risk allocation, privacy and incident-notification requirements.
- Stakeholders
- Systemwide procurement
- Campus CISOs
- Office of General Counsel
- Privacy office
- Risk management
- Health system IT
- Discovery questions
- Which campuses have moved to the new pricing?
- How are incident notification obligations defined in the negotiated appendices?
- Are health locations under separate tenants?
- Value hypothesis
- System-level negotiation can improve terms and pricing for campuses; magnitude depends on baseline.
- Potential engagement
- Terms-and-onboarding review for a campus or peer system modelled on the UC appendices.
- Unsupported claims
- Savings versus prior spend or competitors
- Security outcome improvements
- Any AI capability value
Pre-sales engineering
Role takeaway
- Fit
- Falcon Complete MDR and endpoint security across a federated multi-campus and health environment.
- Architecture and integration
- Central contract, decentralized deployment; integration with campus SIEMs not described.
- Prerequisites
- Per-location endpoint inventory
- Tenant design
- Health data segmentation plan
- Constraints
- BAA and Level 4 data obligations
- GDPR for international data
- Campus autonomy
- Security
- Appendix DS Level 4 protections signal high-sensitivity data handling requirements.
- Proof of value
- Confirm onboarding per campus
- Test incident notification path end to end
- Verify data residency settings
Delivery
Role takeaway
- Work
- Campus onboarding, policy baselines and notification runbooks under the systemwide agreement.
- Dependencies
- CalUsource contract #2026004932
- Campus funding
- Vendor regional representatives
- Ownership
- Campus IT security teams under UCOP systemwide procurement.
- Skills and adoption
- Legal, privacy and security staff need shared understanding of negotiated appendices.
- Governance checkpoints
- Privacy review for health locations
- Annual terms review
- Incident-notification drill
- Acceptance criteria
- Each location documents onboarding status (proposed)
- Notification contacts tested
- Pricing transition confirmed per location
- Risks
- Uneven campus adoption
- Health-system complexity
- Baseline ambiguity in savings reporting
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Centralized purchasing through UCOP with campus-level deployment; health locations have dedicated vendor contacts, implying separate clinical environments.
Governance
Who approves, reviews and stays accountable for outcomes?
Demonstrates cross-functional negotiation of risk allocation and incident notification terms; useful precedent for other systems.
Security and privacy
What data, permissions and controls need testing?
Level 4 data protections and a BAA indicate the service may touch protected health and highly sensitive data.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Not addressed beyond stakeholder collaboration.
Procurement
What should contracts, pricing and exit terms secure?
Centralized purchasing model through UCOP with pricing extended to all locations; precedent for system-level negotiation.
Operating model
Which teams own the service once it runs?
MDR outsourcing at system scale with campus-level operational roles.
Publication history
- 2026-10-29CrowdStrike · Issue 0110 resources
Stable resource ID: uc-systemwide-crowdstrike-agreement-2026