From the CrowdStrike edition of October 29, 2026
Placer County Board memo: CrowdStrike software subscription renewal via ePlus (NASPO ValuePoint)
County of Placer, California (General Services / Information Technology Department) · Local government (county IT, sheriff's office) · Placer County, California, USA
- Publisher
- County of Placer
- Original publication
- 2026-10-06
- Source retrieved
- 2026-10-30
- Event date
- 2026-09-16
What happened
Placer County staff asked the Board to approve $363,625 for CrowdStrike subscriptions and support for Sept 16, 2026 to Sept 14, 2027, plus an optional renewal year up to $399,988 (total $763,613). IT has used CrowdStrike antivirus and endpoint detection since 2023; the Sheriff's Office separately funds a $4,900 SIEM component. Licenses expired Sept 15, 2026, and CrowdStrike kept them operational pending approval. Purchase uses a California participating addendum to the Utah-led NASPO ValuePoint agreement via Carahsoft, exempt from competitive bid.
Why it matters
Direct county-level evidence of sustained CrowdStrike use across general IT and public safety, and of the cooperative-contract route counties use to renew without a new competitive solicitation.
Evidence and measured results
Primary government procurement memo with dollar amounts, term dates, contract vehicle and funding sources. It documents a purchasing decision, not a security-outcome evaluation; no detection, incident or AI-feature performance data is reported.
Limitations and uncertainty
Procurement record only; classed as government-evaluation because it is a staff recommendation to elected officials, not an effectiveness assessment. Does not say which modules are licensed or whether Charlotte AI is included. Board action outcome not confirmed on this page.
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
- Endpoint licenses expired Sept 15, 2026 before board approval; renewal depends on the board calendar and a cooperative master agreement expiring Jan 2027.
- Stakeholders
- County Director of General Services
- Purchasing Manager
- IT Department leadership
- Sheriff's Office administration
- Board of Supervisors
- Discovery questions
- How will the county renew if NASPO AR2472 is not extended past Jan 13, 2027?
- Is the sheriff's SIEM integrated with county EDR telemetry?
- Which Falcon modules are licensed today, and are any AI features in use?
- Value hypothesis
- Co-terming and calendaring renewals across county IT and the sheriff could reduce lapse risk and administrative effort; savings are unquantified.
- Potential engagement
- A short renewal and license-inventory review aligning county IT and sheriff security subscriptions to fiscal and board timelines.
- Unsupported claims
- Any security outcome improvement from CrowdStrike
- Cost savings versus alternatives
- Use or value of Charlotte AI at the county
Pre-sales engineering
Role takeaway
- Fit
- Existing EDR/antivirus customer since 2023 with a separate public-safety SIEM component.
- Architecture and integration
- Unknown whether the sheriff SIEM ingests county Falcon telemetry; needs discovery before any consolidation proposal.
- Prerequisites
- Module and endpoint inventory
- Sheriff SIEM data-flow map
- CJIS boundary review
- Constraints
- Cooperative vehicle term limits
- Separate departmental budgets
- Possible CJIS logging requirements
- Security
- Coverage continuity relied on a vendor extension during the lapse; confirm contractual coverage terms for future gaps.
- Proof of value
- Verify all county endpoints report to the console after renewal
- Confirm sheriff SIEM retention meets policy
- Document any AI features enabled and their approvals
Delivery
Role takeaway
- Work
- Renewal runbook, license inventory and SIEM data-flow documentation.
- Dependencies
- Board approval
- Reseller quote under the NASPO addendum
- Sheriff administration participation
- Ownership
- County IT Department, with Sheriff Administration for the SIEM component.
- Skills and adoption
- Minimal new skills; procurement and IT staff need a shared renewal calendar.
- Governance checkpoints
- Board agenda deadline 60+ days before expiry
- Master agreement term check
- Annual module inventory review
- Acceptance criteria
- Zero days of unlicensed endpoint coverage at next renewal
- Documented inventory of licensed modules
- Written data-flow for sheriff SIEM
- Risks
- Master agreement expiry before option year
- Informal vendor extensions not guaranteed
- Departmental budget misalignment
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?
Single-vendor endpoint/EDR estate with a separate public-safety SIEM line item suggests mixed tooling across county IT and the sheriff; integration between them is not described.
Governance
Who approves, reviews and stays accountable for outcomes?
Licenses lapsed before board approval and the vendor extended coverage informally, a renewal-timing risk; cooperative vehicles shorten procurement but depend on the master agreement's term (NASPO AR2472 effective through Jan 13, 2027).
Security and privacy
What data, permissions and controls need testing?
Continuity of endpoint protection depended on vendor goodwill during the lapse window; sheriff SIEM data implies criminal-justice logging considerations, though the memo does not discuss CJIS.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
No workforce detail; continued reliance on a county IT team is implied but not quantified.
Procurement
What should contracts, pricing and exit terms secure?
Shows NASPO ValuePoint participating addenda as a standard county renewal route and the optional-year structure (up to $399,988).
Operating model
Which teams own the service once it runs?
Split funding between IT and sheriff points to shared-service governance needs.
Publication history
- 2026-10-29CrowdStrike · Issue 0110 resources
Stable resource ID: placer-county-crowdstrike-renewal-2026