Incident Response Plan

How we detect, contain, and report security incidents, including our 72-hour notification commitment to institutions.

This page is generated from our source document. Institutional reviewers may request a signed or dated copy at admin@bayadataai.com.

Baya Data and AI LLC — Bothell, Washington, United States UBI 605 362 236

Plan owner Founder and Chief Executive (acting Incident Commander)
Applies to All security and privacy incidents affecting Smart Learning System
Version 1.0
Effective September 22, 2026
Review cycle Annually, and after any Severity 1 or Severity 2 incident

1. PURPOSE

This plan defines how Baya Data and AI LLC ("Baya") detects, contains, investigates, and reports security and privacy incidents, including any unauthorised access to or disclosure of student education records protected by FERPA.

It is a companion to the Information Security Policy.

2. DEFINITIONS

Event — any observable occurrence in a system. Most events are not incidents.

Incident — an event that compromises, or credibly threatens to compromise, the confidentiality, integrity, or availability of institutional data or the service.

Breach — an incident confirmed to have resulted in unauthorised access to, or acquisition or disclosure of, personal information or student education records.

3. ROLES

Role Held by Responsibility
Incident Commander Founder Declares the incident and its severity, directs response, approves all external communication, decides on notification
Technical lead Founder, or a designated contractor Containment, eradication, recovery, evidence preservation
Institutional contact Founder Single point of contact for each affected institution
External counsel To be engaged as needed Legal analysis of notification obligations
Cyber insurer / breach response Per policy in force Notified for any Severity 1 or Severity 2 incident, before engaging outside forensics where the policy requires it

Where a single individual holds several roles, the sequence in this plan is followed in order rather than in parallel.

4. SEVERITY LEVELS

Level Definition Examples Target response
SEV 1 — Critical Confirmed or probable unauthorised access to student data; ransomware; loss of production data Database exfiltration, encrypted production systems, exposed credentials with evidence of use Begin response immediately; institutions notified within 72 hours of confirmation
SEV 2 — High Credible threat to institutional data without confirmed access; extended outage Exposed credential with no evidence of use, successful phishing of an admin account, production outage beyond 8 hours Begin response within 4 hours
SEV 3 — Moderate Security-relevant issue with no institutional data exposure Vulnerable dependency in production, misconfiguration found and closed, single failed intrusion attempt Begin response within 2 business days
SEV 4 — Low Informational or policy matter Blocked phishing email, routine scanning traffic Log and review

If severity is uncertain, the higher level is assumed until the assessment is complete.

5. RESPONSE PROCEDURE

Step 1 — Detect and record (immediately)

Open an incident record capturing the date and time of detection, how it was detected, the systems and data types involved, and the initial severity. All subsequent actions and times are appended to this record.

Step 2 — Declare and assign (immediately)

The Incident Commander confirms severity and assumes command. For SEV 1 and SEV 2, notify the cyber insurer in accordance with the policy in force. Notify insurers before engaging outside forensic assistance where the policy requires prior consent.

Step 3 — Contain (SEV 1: immediately; SEV 2: within 4 hours)

As applicable:

  • Revoke or rotate affected credentials, API keys, and tokens
  • Disable compromised accounts and terminate active sessions
  • Isolate affected systems or restrict network access
  • Suspend affected integrations or LTI deployments
  • Preserve logs, snapshots, and system images before remediation alters them

Containment takes priority over root-cause analysis.

Step 4 — Assess (within 24 hours of containment for SEV 1)

Determine:

  1. What data was involved, and whether it includes personal information or student education records
  2. Which institutions and how many individuals are affected
  3. Whether data was accessed or acquired, or only exposed
  4. The root cause and the window of exposure

Where evidence is inconclusive, Baya assumes access occurred for the purpose of notification.

Step 5 — Notify

Recipient Trigger Deadline
Affected institution Confirmed breach of its student data Within 72 hours of confirmation
Cyber insurer SEV 1 or SEV 2 Immediately on declaration
Washington State Attorney General Breach affecting 500+ Washington residents Within 30 days (RCW 19.255.010)
Affected individuals Where Baya, rather than the institution, is the notifying party Within 30 days
Law enforcement Criminal activity, at the Incident Commander's discretion and in consultation with counsel and insurer As advised

Notification to an institution includes: what happened, when, the data types and approximate number of records involved, the current status, the steps taken, and a named contact. Baya provides the institution with the information it needs to discharge its own FERPA and state-law notification duties, and does not notify that institution's students directly unless the institution requests it in writing.

An initial notification is sent within the deadline even if the investigation is incomplete, and is followed by updates.

Step 6 — Eradicate and recover

Remove the root cause, patch or reconfigure affected systems, restore from verified clean backups where needed, and confirm service integrity before returning to normal operation. Monitor affected systems closely for a defined period afterwards.

Step 7 — Post-incident review

Within 10 business days of closing a SEV 1 or SEV 2 incident, complete a written review covering the timeline, root cause, what worked, what did not, and corrective actions with owners and due dates. Provide a summary to affected institutions on request. Update this plan and the Information Security Policy as indicated.

6. EVIDENCE PRESERVATION

Logs, snapshots, and records relevant to an incident are preserved in a separate location with restricted access and retained for at least two (2) years, or longer if litigation or a regulatory inquiry is anticipated. Evidence is not deleted, and affected systems are not rebuilt, until preservation is confirmed.

7. COMMUNICATION

All external communication about an incident is approved by the Incident Commander. Personnel do not discuss incidents publicly or on social media. Enquiries from media or third parties are directed to the Incident Commander. Communications with counsel are kept separate and marked as privileged where applicable.

8. CONTACTS

Incident Commander Founder — admin@bayadataai.com
Security reports admin@bayadataai.com
Content and takedown notices admin@bayadataai.com, subject "Content Notice"
Cyber insurer To be completed on binding — carrier, policy number, 24-hour claims line
External counsel To be completed on engagement

9. TESTING

This plan is exercised at least annually by walking through a realistic scenario (for example, a compromised administrative credential) and confirming that containment steps, contact details, and backup restoration work as documented. The date and outcome of each exercise are recorded below.

10. EXERCISE AND REVIEW LOG

Date Type Outcome Actions
(pending first exercise)

VERSION HISTORY

Version Date Change
1.0 September 22, 2026 Initial issue.