https://github.com/eth0izzle/data-breach-notifications
A collection of data breach notifications
https://github.com/eth0izzle/data-breach-notifications
cyber-security data-breaches gdpr
Last synced: 4 months ago
JSON representation
A collection of data breach notifications
- Host: GitHub
- URL: https://github.com/eth0izzle/data-breach-notifications
- Owner: eth0izzle
- Created: 2020-06-15T20:48:38.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2020-06-15T21:40:43.000Z (over 5 years ago)
- Last Synced: 2025-03-12T05:25:25.677Z (10 months ago)
- Topics: cyber-security, data-breaches, gdpr
- Size: 1.12 MB
- Stars: 4
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Data Breach Notifications
This repository serves as a collection of data breach notifications. It is not meant to analyse the notifications themselves but merely serve as an archive.
## Contributing
You are very welcome to contribute to this project via a pull request. To ensure data remains in a consistent format and can be easily processed, it must be presented in the following format:
1. Create a new folder with the format `YYYY-mm-dd-organisation` where YYYY-mm-dd is the date of notification in ISO 8601 format and `organisation` is the lowercase name of the company affected. For example, `2020-05-21-easyjet`.
2. Each folder should contain a minimum of two files:
* **notification.txt**: a plain text file containing just the notification message itself. All surrounding images, metadata, etc. should be removed.
* **capture.[pdf|jpg]**: a screen capture of the notification e-mail including images. You should ensure you have stripped any personally identifiable information.
* _(optionally)_ **email.eml**: a copy of the notifiation e-mail in eml format, including headers. You should ensure you have stripped any personally identifiable information by find and replace your name with `REDACTED`, your e-mail with `redacted@redacted.com`, and any special links, i.e. login
* And feel free to add anything else of relevance to the breach, i.e. post-notification updates via the organisations website.