# Alabama resident and risk assessment

Alabama Data Breach Notification Act | Worked example with fictional data

Step: Find the data, people and likely harm
Owner: Forensics + Privacy + system owners + service provider
When: Start promptly; update the working count as evidence improves

## Gather first
- System and data inventory
- Affected-file query
- Residence evidence
- Encryption and key status
- Access, download and misuse evidence
- Alabama Act §§8-38-2 and 8-38-4

## How to prepare it
1. Have the system owner produce a read-only count from the affected source. Deduplicate people, not rows. Keep Alabama residents separate from other states, and keep direct identifiers out of executive summaries.
2. Map the exposed fields to the statutory combinations. Record whether name or first initial plus last name appears with a covered identifier. For account credentials, verify whether they permit access to an account reasonably likely to contain or obtain sensitive information.
3. For each data set, document whether it was acquired or is reasonably believed acquired by an unauthorized person and why the evidence supports that view. Consider copying, possession, public posting, use, fraud reports and identity theft reports.
4. Record encryption status and key or security credential status together. A label such as encrypted is not enough if the key or credential may have been exposed. Assess substantial harm for the relevant people and record the evidence and reviewer.
5. Have Legal approve the final trigger and notice decision. Keep unknowns visible, assign owners and revisit the decision when the person count, data fields or access evidence changes.

## Example

### Fictional affected population
Training example only. A query identifies 1,140 distinct Alabama resident accounts in a payroll export. The count is a working total, not a real incident or a legal conclusion.

### Fictional field mapping
Name plus bank-account number and access code appears in the sample. Privacy records the source columns, masking applied in the workbook and how the system owner validated the query.

### Fictional acquisition evidence
Cloud audit records show an external download from an unrecognized session. The team records the session ID and time range, then asks forensics to verify whether the transferred file contained the mapped rows.

### Fictional harm and key review
The relevant account credential was in the export. Security confirms that the credential was not encrypted separately; Legal records the likely-harm analysis and the current gaps before the final decision.

## Review
Every resident count can be reproduced from a named source, and every notice or no-notice conclusion has a documented field mapping, acquisition analysis, harm rationale and reviewer.

## Handoff
Send Legal the resident-count methodology and evidence-backed decision memo. Limit access to row-level personal information.

Official reference: Alabama Data Breach Notification Act, §§8-38-2 and 8-38-4
https://www.alabamaag.gov/wp-content/uploads/2026/05/Act-2018-396.pdf

Use the current rules and any prescribed forms for your engagement.
