---
title: "Alisal Union School District data incident"
description: "Alisal disclosed possible unauthorized file access, with conflicting incident dates in its letter and California registry record."
incident_type: "Cybersecurity incident"
status: "active"
last_modified: "2026-10-13"
canonical_url: "https://www.ally.security/incidents/alisal-union-school-district-data-incident-2026"
markdown_url: "https://www.ally.security/incidents/alisal-union-school-district-data-incident-2026.md"
stix_url: "https://www.ally.security/incidents/alisal-union-school-district-data-incident-2026/stix.json"
---

# Alisal Union School District data incident

A district network incident led to a personal-data review and individual notices; the precise access date remains unresolved.

Last modified Oct 13, 2026 · 2 sources

## Summary

- **Environment:** School-district computer network
- **Operational impact:** District says backups minimized disruption and supported restoration
- **Financial impact:** No incident cost established in the reviewed evidence

## What happened

[Alisal Union School District](https://www.alisal.org/) identified unusual activity around June 22, 2026. Its [October 7 letter](https://oag.ca.gov/system/files/Alisal%20Exhibit%20A.pdf) describes possible file access or downloading around June 19. [2](#source-2)

## Impact

The letter identifies names but leaves additional recipient-specific fields blank. It gives no affected-person total. [2](#source-2)

## Timeline

### August 27, 2026 — General notice

The district issued an initial community notice. [2](#source-2)

### October 1, 2026 — Data review completed

Review of potentially affected information concluded. [2](#source-2)

### October 7, 2026 — Individual notice dated

The retained consumer letter is dated October 7. [2](#source-2)

### October 13, 2026 — Briefing updated

This briefing was last reviewed and updated on October 13, 2026.

## Threat Group & Attack Vector

The reviewed evidence does not establish the initial access method. The [California registry](https://oag.ca.gov/ecrime/databreach/reports/sb24-630952) lists May 20 as the breach date, conflicting with the letter’s approximate June chronology. [1](#source-1) [2](#source-2)

### Actors

- No threat actor group has been identified in the reviewed public evidence.

### TTPs

- No specific MITRE ATT\&CK technique is currently mapped for this case.

## Response

Alisal said backups helped restore operations and minimize disruption. It offered 12 months of monitoring and identity-protection services. [2](#source-2)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/alisal-union-school-district-data-incident-2026/stix.json>)

## Sources

Primary source records used to research this incident.

<a id="source-1"></a>

### California breach record — Alisal Union School District

regulatory · California Department of Justice

<https://oag.ca.gov/ecrime/databreach/reports/sb24-630952>

<a id="source-2"></a>

### Alisal Union School District consumer notice

official · Alisal Union School District · Oct 7, 2026

<https://oag.ca.gov/system/files/Alisal%20Exhibit%20A.pdf>

<details>
<summary>Evidence ledger</summary>

Review the supporting structured claims.

1. **Resulted In · 100% confidence · current**  
   General notice: The district issued a general notice while its review continued.
2. **Occurred At · 100% confidence · current**  
   Data review completed: 2026-10-01
3. **Resulted In · 100% confidence · current**  
   Data review completed: The district completed its review of potentially affected personal information.
4. **Resulted In · 100% confidence · current**  
   Alisal Union School District data incident: The district reported unusual network activity on or around June 22, 2026 and possible unauthorized access to or downloading of files on or around June 19, 2026.
5. **Affected Organization · 100% confidence · current**  
   Alisal Union School District data incident: Alisal Union School District
6. **Occurred At · 100% confidence · current**  
   General notice: 2026-08-27
7. **Resulted In · 100% confidence · current**  
   Individual notice dated: The district’s consumer notice is dated October 7.
8. **Resulted In · 100% confidence · current**  
   Alisal Union School District data incident: The notice identifies names but leaves the recipient-specific additional data fields blank; it does not establish the full categories or affected-person count.
9. **Resulted In · 100% confidence · current**  
   Alisal Union School District data incident: General notice
10. **Resulted In · 100% confidence · current**  
   Alisal Union School District data incident: Individual notice dated
11. **Resulted In · 100% confidence · current**  
   Alisal Union School District data incident: Data review completed
12. **Resulted In · 100% confidence · disputed**  
   Alisal Union School District data incident: The California notification registry lists May 20, 2026 as the breach date; this conflicts with the district letter’s approximate June 19 file-access date and is unresolved.
13. **Resulted In · 100% confidence · current**  
   Alisal Union School District data incident: The district said viable backups minimized operational disruption and supported restoration; it offered 12 months of identity monitoring.
14. **Occurred At · 100% confidence · current**  
   Individual notice dated: 2026-10-07
15. **Resulted In · 100% confidence · disputed**  
   Alisal Union School District data incident: The district letter describes possible file access or downloading on or around June 19, 2026; this differs from the May 20 breach date in the California registry.

</details>