Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

There is no processes for when a new security breach is discovered #173

Open
Lortemanden opened this issue Apr 3, 2020 · 0 comments
Open

There is no processes for when a new security breach is discovered #173

Lortemanden opened this issue Apr 3, 2020 · 0 comments
Labels
GDPR GDPR meta gruppe priority: low
Projects
RAW_Product Backlog

Comments

@Lortemanden
Copy link
Contributor

Lortemanden commented Apr 3, 2020 •
edited by soenderby

Is your feature request related to a problem? Please describe.
If the system is ever breached there is no process for how we handle it.

Describe the solution you'd like
Determine and document a process for how we handle a breach. Here should be how we stop the breach, call the authorities, determine what information has been leaked, inform the people whose information might have been leaked and how we prevent another breach.
@Lortemanden Lortemanden added priority: low GDPR GDPR meta gruppe labels Apr 3, 2020
@Lortemanden Lortemanden added this to Issues to do in 2020f 3. sprint via automation May 5, 2020
@Lortemanden Lortemanden added this to the 2020S3 milestone May 5, 2020
@Lortemanden Lortemanden removed this from Issues to do in 2020f 3. sprint May 5, 2020
@Lortemanden Lortemanden removed this from the 2020S3 milestone May 5, 2020
@soenderby soenderby changed the title There is no processes for when a new security breach is discorved There is no processes for when a new security breach is discovered Sep 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
GDPR GDPR meta gruppe priority: low
Projects
RAW_Product Backlog
Low
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Lortemanden