{"resourceId":"oldham-county-schools-falcon-complete-2026","versions":[{"version":"external-69c6a601aae446e4f4b9ee27ff0f99a0d49a594f162e85c6af5b7cc94b4db032","resource":{"id":"oldham-county-schools-falcon-complete-2026","title":"Oldham County Schools: Endpoint Protection — CrowdStrike Falcon Complete (board attachment and quote)","organization":"Oldham County Schools (Kentucky)","sector":"K-12 education","geography":"Kentucky, USA","publishedAt":"Spring 2026 (quote dated 2026-04-01; term begins 2026-05-22)","publicationDate":null,"eventDate":"2026-05-22","sourceName":"Kentucky School Boards Association meeting portal","sourceLabel":"Board meeting attachment (PDF)","sourceUrl":"https://portal.ksba.org/public/Meeting/Attachments/DisplayAttachment.aspx?AttachmentID=953741","evidenceClass":"government-evaluation","outcomeClass":"emerging","topics":["governance-procurement","data-security","operating-model","accessibility-workforce"],"finding":"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.","sledRelevance":"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":"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.","architectureImplications":"Mixed Windows and ChromeOS fleet (16,000 ChromeOS devices) drives the requirement for Chromebook XDR; a managed service replaces state-managed antivirus.","governanceImplications":"Decision shifted from state to district; evaluation criteria and cost trade-offs are documented for the board, a reusable template for peers.","securityPrivacyImplications":"Charlotte AI licensed across student ChromeOS devices raises questions about what student-device telemetry generative AI features process; the document does not address this.","caveats":"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.","streamIds":["crowdstrike"],"roles":{"sales":"State service withdrawal is the framing point: when Kentucky OET stopped managing district endpoint protection, Oldham County had to choose its own MDR and picked the highest-priced option for Chromebook coverage and 24/7 response. Interpretation: districts losing state shared services need help comparing non-equivalent bids, not a push to a product. A bounded engagement could build a comparable-scope evaluation matrix. The source cannot support claims that Falcon Complete outperforms SentinelOne or Microsoft, or that Charlotte AI adds measurable value.","engineering":"Device mix is the framing point: 16,000 ChromeOS devices made Chromebook XDR coverage the decisive technical criterion. Interpretation: pre-sales engineers should confirm what telemetry and response actions are actually available on ChromeOS versus Windows, and whether Charlotte AI licensing on student devices has any functional effect. Identity changes also matter as Kentucky moves districts off state Active Directory. The quote lists modules but not configuration, so validation must test coverage on the real fleet rather than the bill of materials.","delivery":"Transition ownership is the framing point: the district inherits administration the state previously handled, even with MDR. Interpretation: delivery should define who owns policy, exceptions, incident communication and renewal, and should verify Chromebook enrollment completeness before relying on coverage. Governance checkpoints should include a review of any AI features on student devices against district privacy policy. Acceptance criteria should be measurable proposals such as enrollment coverage percentage, not observed outcomes, because the source reports none."},"roleDetails":{"sales":{"customerProblem":"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"],"discoveryQuestions":["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?"],"valueHypothesis":"MDR may offset limited district security staffing after the state exit; value relative to cheaper bids is unproven.","potentialEngagement":"Scope-normalized EDR/MDR comparison template for districts affected by the Kentucky OET change.","unsupportedClaims":["Superior detection versus SentinelOne or Microsoft","Measured benefit of Charlotte AI","Cost-effectiveness relative to lower bids"]},"engineering":{"fit":"Strong ChromeOS requirement matched to Falcon Insight for ChromeOS; Windows devices on Falcon Complete.","architectureIntegration":"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.","proofOfValue":["Measure enrolled versus inventoried devices by OS","Run a tabletop with the MDR escalation path","Document which Charlotte AI functions are active"]},"delivery":{"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.","skillsAdoption":"Staff need training on console use, MDR escalation and exception handling previously handled by the state.","governanceCheckpoints":["Privacy review of AI features on student devices","Pre-renewal performance review","Board report on coverage"],"acceptanceCriteria":["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"]}},"retrievedAt":"2026-10-29T22:08:39-05:00","enrichedAt":"2026-10-29T22:18:51-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"MDR substitutes for scarce district security staff; no staffing numbers given.","procurementImplications":"OMNIA Partners used for CrowdStrike and SentinelOne quotes and NASPO ValuePoint for Microsoft, showing cooperative vehicles shaping K-12 options.","operatingModelImplications":"Shift from a state shared service to district-owned operations with outsourced MDR.","sourceVerification":{"openedUrl":"https://portal.ksba.org/public/Meeting/Attachments/DisplayAttachment.aspx?AttachmentID=953741","referenceExcerpt":"Effective June 30, 2026, OET will discontinue this service, requiring each district to independently procure and administer its own solution.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}