BB2G — Born Between 2 Generals
BB2GSensitive Data Briefing
PDF
National Data Resilience · 50 states + D.C. · Updated Nov. 10, 2026

Know where every record lives. Prove you can get it back.

Americans filed 1.1 million identity theft reports with the FTC in 2024 and lost a record $15.9 billion to fraud in 2025. The breaches on this map alone exposed more than 98 million health, tax, student, customer and driver records. This briefing maps the exposure in every state and shows how BB2G tracks sensitive data, keeps it on servers the state controls, and restores it on a clock.

Born Between 2 Generals, LLC · National Data Resilience
1,135,291Identity theft reports to the FTC in 2024
$15.9BFraud losses reported to the FTC in 2025, a record
—
99M+Records exposed in the breaches on this map
Breach map · FTC Consumer Sentinel 2024

Where sensitive data is leaking

States are shaded by identity theft reports per 100,000 residents. Each glow is a documented breach of health, financial, student, government or driver records; red marks breaches of a million people or more, and blinking marks the last four months.

Hot spotBreach of 1M+ peoplePriority regionFTC Consumer Sentinel 2024 · Census 2025 · sourced breach record
The identity theft beltFlorida (528 reports per 100k), Georgia (517), D.C. (480), Nevada (466) and Texas (393) report the most identity theft per resident.
Health data is the targetHospitals and insurers dominate the record: Kaiser (13.4M), HCA (11M), Ascension (5.6M) and Yale New Haven (5.5M) in four years.
The priority regionNebraska, Iowa, South Dakota, Kansas and Wyoming residents reported $192 million in fraud losses in 2024, and Change Healthcare reached 575,000 Nebraskans.
Latest · July – Nov. 2026

What leaked this year

Recent breaches of sensitive public and health records, newest first.

Sensitive data · National Data Resilience + Audit Network

Follow every record from birth to destruction

Health, tax, student, foster, voter, driver and court records pass through agencies, vendors, subcontractors, cloud hosts, processors and data brokers. BB2G maps each hop and holds every one to a legal basis.

Originate

Where the record was created and under what law: HIPAA, FERPA, DPPA, IRS 1075, CJIS or state statute.

Authorize

Who may hold it and why. No legal basis, no copy.

Store

Encrypted on servers the jurisdiction controls, with keys it holds.

Access

Named accounts, hardware keys and least privilege. Every read is logged.

Transfer

WAYBILL records each time data leaves: fields, recipient, basis, retention.

Retain and destroy

A retention clock on every record, verified deletion and a certificate of destruction.

The sensitive-data toolset

WAYBILL

A custody slip for every outbound transfer of protected data, matched to a contract and a destruction date.

Lineage Atlas

A map of where each data set came from and every system, vendor and subcontractor that touched it.

Vendor and broker map

Agencies, vendors, subcontractors, cloud hosts, processors and data brokers, with their contracts.

Breach clock

Each state's notification deadline starts the moment a breach is confirmed, with drafts ready.

Minimum necessary

Share only the fields a task needs. No bulk files, no model training, no resale.

Evidence grades

Every finding linked to its source and timestamp, separate from allegations.

The server stack · Sovereign Hybrid Compute

Sensitive data stays on servers the state controls

Three planes, each with a hard boundary. Sensitive data never leaves the jurisdiction's own hardware; only signed, de-identified results move up.

Plane 1 · Sovereign

State and county servers

Air-gapped local servers inside the jurisdiction hold every sensitive record.

  • Per-tenant isolation for each state and county
  • Encryption keys held by the jurisdiction
  • Write-once evidence vault
  • No inbound internet path
Plane 2 · Workbench

ProBox local analysis

A local workbench runs analysis and AI on the loopback address with no outside connection.

  • Runs on 127.0.0.1, zero egress
  • Local AI models, no cloud prompts
  • FIDO2 hardware keys to sign in
  • Signed outputs only
Plane 3 · Cloud

Bounded cloud staging

Public dashboards and executive reports run in the cloud with no personal data at all.

  • Aggregates and public records only
  • Signed release receipts
  • Security headers and audit logs
  • Instant rollback
One-way, signed releases: data only moves up after it is de-identified, and every release gets a receipt
Hardening on every server

LATCHKEY

FIDO2 hardware keys for every administrator. No shared accounts, no SMS codes.

Split-key changes

Two separate hardware keys are required to change a security baseline or a backup target.

Zero-trust access

Attribute-based access, mutual TLS between services and rate-limited tokens.

Credential watch

Session tokens checked against breach dumps and code repositories; a match revokes them.

Customer-private compute

Each customer's servers, identities and keys stay separate from BB2G's own.

Workforce controls

Role-based training, assigned encrypted USB devices, offboarding and audit trails.

BACKSTOP · 3-2-1 recovery

A backup isn't real until it's restored on a clock

Ransomware wins when backups are online, untested or encrypted along with everything else. BACKSTOP keeps copies the attacker can't reach and proves they work.

3Copies of every critical data set
2Different media: a live cluster and an air-gapped array
1Encrypted copy off-site and offline

Write once

Backups land in write-once storage that no account, including an administrator, can alter or delete.

Hash every block

A Merkle hash tree fingerprints every backup so tampering shows instantly.

Isolate on breach

A confirmed breach triggers fresh mirrors and cuts the compromised network segment off.

Timed restore drill

Scheduled restores on synthetic data, timed against the recovery target.

Two-key reset

Returning to normal operations requires two hardware keys.

Receipt

Every drill and restore produces a signed receipt for auditors.

Fail closedIf a backup's fingerprint doesn't match, it is never restored. The system stops, holds the last good copy and pages a named person.
Why small error rates become breaches

A record crosses 20 hands. At 95% each, it's safe 36% of the time.

Every vendor, transfer, backup and access is a step where a record can be mishandled. Twenty steps at 95% each leaves a 64% chance something went wrong. Real data passes through far more than 20. Move the sliders.

With BB2G, each step has a check that catches 99% of errors and stops the record instead of letting it move on.

No checks
With BB2G checks
Chance the work is still clean after each step, no checks
A record's life · gold steps are BB2G checks
CollectedClassifiedLegal basis checkEncrypted at restIndexedShared with vendorWAYBILL loggedSubcontractorCloud processorAnalyticsReportBackupHash verifiedRestore drillAccess reviewRetention clockIncident watchBreach noticeVerified destructionCertificate
Knowing when to stopA check that finds a problem stops the record. Stopping is the feature: a paused record can be fixed; a leaked one can't be recalled.
National rankings · all 51 jurisdictions

How every state compares

Rank 1 has the most identity theft reports per 100,000 residents (FTC, 2024). Select a column to re-sort.

Breach record · 2016 – Nov. 2026

Sensitive data already exposed

Documented breaches of health, financial, student, government, court and voter records, newest first, each linked to its source.

Jurisdiction profiles · 50 states + D.C.

Every state, on one page

2024 FTC identity theft and fraud figures, and every documented breach of sensitive records in each jurisdiction.

Exposure pathway

Route to exposure, and where to break it

How sensitive records get out, and the controls that stop each route.

Entry routes

Phishing and stolen logins
Vendor and file-transfer software
Ransomware and extortion
Tracking code and exposed APIs
Insider misuse

Sensitive data

Health records
Social Security and tax data
Student and foster records
Voter and driver records
Court and benefits records

Harm

Identity theftFraud in victims' names
ExtortionPatients and families threatened
OutageServices offline for weeks
TrustPeople stop sharing with government
BreakpointsWAYBILLLineage AtlasSovereign serversLATCHKEY keysBACKSTOP 3-2-1Verified destruction
Engagement plan

From a data map to proven recovery

Read-only first. Nothing touches a live system until the state approves.

Phase 1 · 90 days

Map the data

  • Inventory sensitive data sets, owners and legal bases.
  • Vendor, subcontractor and broker map from contracts.
  • Read-only review; no live systems touched.
Phase 2 · 2027

Prove recovery

  • Sovereign server plane stood up for one agency.
  • First timed restore drill on synthetic data.
  • WAYBILL logging on every outbound transfer.
Phase 3 · 2027 – 2028

Scale

  • Every agency on BACKSTOP 3-2-1 with quarterly drills.
  • Retention clocks and verified destruction statewide.
  • Same receipts and audit trail in every state.

Decision requested

Authorize a read-only data inventory of one agency to set owners, legal bases, safeguards and a restore-time target.

Download the briefing
Sources

Trace every figure