Pro-Tem, Inc.
ent_e3c181e4e399a0551342a45a
Disclosures
5
State AG · 5 jurisdictions
Incidents
1
filings grouped by incident
Max affected reported
31,149
as filed · State AG OR
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- Pro-Tem, Inc.
- Normalized
- pro tem— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- None on record
Disclosure history (5)newest first
- 🦬Montana State AGas victim2022-11-15
Pro-Tem, Inc. dba PTI Systems reported a data breach to the Montana Attorney General. The breach was reported on 2022-11-15. The breach occurred from 7/7/2022 to 7/16/2022. 70 Montana residents were affected.
- 🦞Maine State AGas victim2022-11-15
Pro-Tem, Inc. (PTI Systems) experienced an external system breach between July 7 and July 16, 2022, which was discovered on October 17, 2022. The incident compromised the names and Social Security numbers of 31,149 individuals, including 52 Maine residents. The company provided written notifications and offered one year of identity theft protection services through Experian.
- 🐻California State AGas victim2022-11-15
Pro-Tem, Inc. dba PTI Systems reported a data breach affecting 17 Rhode Island residents. Suspicious activity occurred July 7-16, 2022, involving unauthorized access to files containing names, SSNs, addresses, and DOBs. PTI Systems engaged forensic specialists, implemented EDR, upgraded hardware, and offered credit monitoring.
- 🦫Oregon State AGas victim2022-11-15
Pro-Tem, Inc. dba PTI Systems reported a data breach to the Oregon Attorney General. The breach was reported on 2022-11-15. The breach occurred during 7/7/2022 - 7/16/2022. The breach was discovered on 10/17/2022. 31,149 individuals were affected. Notice was sent on 11/15/2022.
- 🌲Washington State AGas victim2022-11-15
Pro-Tem, Inc. dba PTI Systems, a business sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2022-07-18 and filed notice on 2022-11-15. 677 Washington residents were affected. 120 days elapsed between awareness and notification. 11 days to identify the breach. 0 days to contain the breach.