This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
wiki:policies:infosec [2022/11/07 18:23] peaceolaniran |
wiki:policies:infosec [2023/05/25 15:42] katcow |
||
---|---|---|---|
Line 9: | Line 9: | ||
* Kathryn Cowie, Operations Lead | * Kathryn Cowie, Operations Lead | ||
* Stephen Mead, Lead Engineer | * Stephen Mead, Lead Engineer | ||
- | * Peace Olaniran, Data Associate | ||
* An external cybersecurity consultant, who has already been vetted and interviewed by Nested Knowledge, will be hired as an independent contractor if the needs of our information security organization expand. | * An external cybersecurity consultant, who has already been vetted and interviewed by Nested Knowledge, will be hired as an independent contractor if the needs of our information security organization expand. | ||
Line 44: | Line 43: | ||
==== Data Protection Officer (DPO) ==== | ==== Data Protection Officer (DPO) ==== | ||
- | The DPO, responsible for approving data processing projects, will be Kevin Kallmes. | + | The DPO, responsible for approving data processing projects, will be Karl Holub |
==== Data Protection Impact Analysis Plan ==== | ==== Data Protection Impact Analysis Plan ==== | ||
Line 58: | Line 57: | ||
- **Scope of the processing: | - **Scope of the processing: | ||
- **Context of the processing: | - **Context of the processing: | ||
- | - *Purpose of the processing: | + | - **Purpose of the processing: |
- **Consultation Process** | - **Consultation Process** | ||
- describe when and how you will seek individuals’ views – or justify why it’s not appropriate to do so. Who else do you need to involve within your organization? | - describe when and how you will seek individuals’ views – or justify why it’s not appropriate to do so. Who else do you need to involve within your organization? | ||
Line 111: | Line 110: | ||
* Automated backup functions within software packages should be used where applicable. | * Automated backup functions within software packages should be used where applicable. | ||
* When a computer equipment is changed, consideration should be given to the backup media and data formats to ensure that they can still be restored. | * When a computer equipment is changed, consideration should be given to the backup media and data formats to ensure that they can still be restored. | ||
- | * The database backing the AutoLit application is backed up twice daily. The resulting image is copied to a separate data center for redundancy. | + | * The database backing the AutoLit application is backed up twice daily. The resulting image is copied to a separate data center for redundancy. Backups are retained for 60 days. |
+ | |||
+ | === Database Back Ups === | ||
+ | |||
+ | Backups are generated as database snapshots, and the snapshotting process is subject to email alerts from AWS. Database backups are fully exercised no more than every 3 months. A failure in restoring a backup results in highest priority escalation with the development team on our product management software. | ||
=== Restoration === | === Restoration === | ||
Line 117: | Line 120: | ||
* Authorization to restore data from backup media that would overwrite existing production data must be obtained from Data Owners. | * Authorization to restore data from backup media that would overwrite existing production data must be obtained from Data Owners. | ||
* Restoration of the current configuration must be within agreed recovery timescales | * Restoration of the current configuration must be within agreed recovery timescales | ||
- | * Restoration of the AutoLit database is tested with regularity | + | * Restoration of the AutoLit database is tested with quarterly |
+ | * Backups | ||
+ | * Evidence | ||
+ | |||
+ | **Testing** | ||
+ | |||
+ | Backup and restore procedures must be tested at least annually. Issues with backups identified should be documented and remediated. | ||
===== Revision History ===== | ===== Revision History ===== | ||
Line 123: | Line 132: | ||
^Author^Date of Revision/ | ^Author^Date of Revision/ | ||
|K. Cowie|11/ | |K. Cowie|11/ | ||
- | |K. Holub|11/17/2021|Review Completed| | + | |K. Holub|02/09/2023|Tracking restoration history| |
|K. Kallmes|11/ | |K. Kallmes|11/ | ||
|P. Olaniran|11/ | |P. Olaniran|11/ |