Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the CrowdStrike edition of October 29, 2026

Government evaluationEmergingUndated source

Oldham County Schools: Endpoint Protection — CrowdStrike Falcon Complete (board attachment and quote)

Oldham County Schools (Kentucky) · K-12 education · Kentucky, USA

Publisher
Kentucky School Boards Association meeting portal
Original publication
Spring 2026 (quote dated 2026-04-01; term begins 2026-05-22)
Source retrieved
2026-10-30
Event date
2026-05-22
Read original source

What happened

After Kentucky's Office of Education Technology said it would stop providing district endpoint protection effective June 30, 2026, Oldham County Schools ran a structured evaluation from October 2025 and recommended CrowdStrike Falcon Complete MDR at $193,492 for 12 months via OMNIA Partners, over SentinelOne ($118,236.26) and Microsoft 365 ATP ($62,449.12), noting scopes were not equivalent. Chromebook XDR coverage and 24/7 MDR were decisive. The quote includes Charlotte AI line items at $1.33 per device for 2,500 staff devices and 16,000 ChromeOS devices.

Why it matters

Shows a state shared service ending and pushing districts to procure their own EDR/MDR, and that Charlotte AI is being bundled into K-12 endpoint purchases at a per-device price.

Evidence and measured results

District staff evaluation with stated criteria and three competitive quotes; itemized reseller quote. No measured security outcomes; comparisons explicitly non-equivalent. Why now: this is the stream's first run, and the June 30, 2026 Kentucky cutover makes district-level replacement evidence currently relevant even though the document predates this edition.

Limitations and uncertainty

Publication date of the board attachment is not stated; dates come from the quote. Not an outcome evaluation. Charlotte AI line items do not show whether it is enabled or used. Single district.

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
State-provided endpoint protection ended June 30, 2026, forcing the district to procure and administer its own solution.
Stakeholders
  • District technology director
  • Superintendent and board
  • Finance officer
  • Student data privacy lead
Discovery questions
  • Which services did the state previously handle that now fall to the district?
  • How were non-equivalent bids normalized?
  • Is Charlotte AI enabled on student ChromeOS devices, and under what policy?
Value hypothesis
MDR may offset limited district security staffing after the state exit; value relative to cheaper bids is unproven.
Potential engagement
Scope-normalized EDR/MDR comparison template for districts affected by the Kentucky OET change.
Unsupported claims
  • Superior detection versus SentinelOne or Microsoft
  • Measured benefit of Charlotte AI
  • Cost-effectiveness relative to lower bids

Pre-sales engineering

Role takeaway
Fit
Strong ChromeOS requirement matched to Falcon Insight for ChromeOS; Windows devices on Falcon Complete.
Architecture and integration
Replaces state-managed antivirus; must align with Kentucky's planned Active Directory decommissioning and identity federation.
Prerequisites
  • Accurate device inventory by OS
  • Google Admin console integration for ChromeOS
  • Incident contact roster for MDR
Constraints
  • Feature parity on ChromeOS may differ from Windows
  • Single-year term
  • District staff capacity
Security
Confirm what student-device telemetry is sent to cloud and AI features, and retention settings.
Proof of value
  • Measure enrolled versus inventoried devices by OS
  • Run a tabletop with the MDR escalation path
  • Document which Charlotte AI functions are active

Delivery

Role takeaway
Work
Sensor rollout across staff Windows and student ChromeOS fleets, MDR onboarding and policy baseline.
Dependencies
  • Reseller order and license activation
  • Google Workspace admin access
  • Board approval
Ownership
District Technology Department.
Skills and adoption
Staff need training on console use, MDR escalation and exception handling previously handled by the state.
Governance checkpoints
  • Privacy review of AI features on student devices
  • Pre-renewal performance review
  • Board report on coverage
Acceptance criteria
  • At least 98% of inventoried devices reporting (proposed)
  • Documented MDR escalation contacts
  • Written AI-feature enablement decision
Risks
  • ChromeOS coverage gaps
  • Budget pressure at renewal
  • Unclear AI data handling for minors

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?

Mixed Windows and ChromeOS fleet (16,000 ChromeOS devices) drives the requirement for Chromebook XDR; a managed service replaces state-managed antivirus.

Governance

Who approves, reviews and stays accountable for outcomes?

Decision shifted from state to district; evaluation criteria and cost trade-offs are documented for the board, a reusable template for peers.

Security and privacy

What data, permissions and controls need testing?

Charlotte AI licensed across student ChromeOS devices raises questions about what student-device telemetry generative AI features process; the document does not address this.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

MDR substitutes for scarce district security staff; no staffing numbers given.

Procurement

What should contracts, pricing and exit terms secure?

OMNIA Partners used for CrowdStrike and SentinelOne quotes and NASPO ValuePoint for Microsoft, showing cooperative vehicles shaping K-12 options.

Operating model

Which teams own the service once it runs?

Shift from a state shared service to district-owned operations with outsourced MDR.

Publication history

  1. 2026-10-29CrowdStrike · Issue 0110 resources
Read preserved resource versions (JSON)

Stable resource ID: oldham-county-schools-falcon-complete-2026