Servstead, LLC

Security Incident Response Plan

How Servstead detects, responds to, and communicates security incidents affecting customer or financial data.

Version
1.0
Effective date
July 3, 2026
Policy owner
Servstead, LLC — Information Security Lead
Review cadence
At least annually, and after any material incident

Document owner: Servstead, LLC. Version 1.0. Effective date: July 3, 2026.

1. Purpose

This plan defines roles and procedures for responding to suspected or confirmed security incidents involving Servstead systems or data, including financial data received through Plaid.

2. Reporting

Employees, contractors, and customers report suspected incidents to servstead@gmail.com immediately.

Reports should include: date/time observed, systems affected, data types potentially involved, and steps already taken.

3. Severity classification

Low: failed login attempts, spam, non-exploitable bugs without data exposure.

Medium: vulnerability with limited exposure potential, unauthorized access attempt blocked by controls.

High: confirmed unauthorized access, data exfiltration, compromise of production credentials, or exposure of financial integration tokens.

4. Response phases

(1) Triage — Information Security Lead confirms the incident and assigns severity within four (4) business hours of report.

(2) Containment — revoke compromised credentials, disable affected integrations, block malicious IPs, or take affected components offline as needed.

(3) Eradication — remove unauthorized access, patch vulnerabilities, rotate secrets.

(4) Recovery — restore services from known-good state; verify integrity before re-enabling integrations.

(5) Post-incident review — document root cause, timeline, and preventive actions within fourteen (14) days.

5. Customer notification

Affected customers are notified without undue delay when a confirmed incident impacts their personal information or financial data, consistent with applicable law.

Notifications include a description of the incident, data types affected, and remediation steps.

6. Third-party coordination

When incidents involve subprocessors (Supabase, Stripe, Plaid, etc.), we coordinate with the vendor's security team and follow their guidance.

7. Record keeping

Incident summaries, timelines, and remediation actions are retained for at least three (3) years.

8. Related documents

Information Security Policy: https://servstead.com/policies/security

Privacy Policy: https://servstead.com/policies/privacy

9. Contact

Report incidents: servstead@gmail.com. Legal/privacy: servstead@gmail.com.