HackingGovernmentGovernmentStolen CredentialsSupply Chain (3P Vendor)Customer Data InvolvedIdentity (basic)Financial accountLowContained

City of Thousand Oaks

bd_240da938e40b2af8 · schema v1 · pii pii-v1

Severity

Low

Discovered

Feb 28, 2018

Filed

Jun 4, 2018

To disclose

14 weeks

Affected

Not disclosed

Confidence

65%

Full breach record for City of Thousand Oaks →2 incidents on file

The City of Thousand Oaks notified residents that an unauthorized individual may have accessed a vendor's computer processing credit card transactions. The incident occurred between November 21, 2017, and February 26, 2018, and was discovered on February 28, 2018. Affected data may include names, payment card numbers, and expiration dates. The City hired a forensic firm and is enhancing security protocols.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 99 days

discovery → filing · 14 weeks / 96 days

Nov 21, 2017

Begins

Feb 28, 2018

Discovered

Jun 4, 2018

Filed

vs. sector median

+3 wks slower

Tracked as a single-filing incident — the only disclosure on record for this event so far.ConfirmedView incident

Name: City of Thousand Oaks
norm: city of thousand oaks

Name: City of Thousand Oaks
norm: city of thousand oaks
Industry: Governmentllm

Discovered: Feb 28, 2018
Breach occurred: Nov 21, 2017 – Feb 26, 2018
Undetected for: 99 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: Identity (basic)Financial account
Attack vector: Third-Party / Supply Chain
MITRE ATT&CK: T1078 Valid Accounts
Threat actor: External
Third party: via City's vendor
Initial access: trusted_relationship

During the incident: Immediately began an investigation
Hired a third-party forensic firm to determine what happened and what information may have been affected
Changes made: Taking steps to enhance our existing security protocols
Re-educating our vendors regarding the importance of protecting personal information
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 14 weeks(96 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://oag.ca.gov/ecrime/databreach/reports/sb24-136764
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jun 4, 2018
Raw hash: 7da4d00b105d0c1e2b7d0ea2fac87657d4ccdee89545b54c5b5db3a80375a2e3

Reporting entityCity of Thousand Oaks

Victim entityCity of Thousand Oaks

Incidentdiscovered Feb 28, 2018

Stated responseImmediately began an investigation

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov