The periodic audit of Synapse activity is intended to surface potential threat scenarios concerning the privacy and security of data held in the Synapse. The approach to this audit is informed by an assessment of risks to priority data, such as the data sets associated with Synapse with Synapse projects marked with restricted access control lists. The risk assessment process considers access control at the point when access is granted, when access is used, and when access may become uncontrolled.
...
An audit report is generated during each audit to analyze the data and explain whether there have been any security breaches or privacy concerns. The Governance Regulatory Support Team should submit the audit report to WIRB annually in October during the Synapse continuing review, which occurs in October.
Audit Constraints
The Synapse audit approach was revised in 2020 to focus on specific threats identified through a risk assessment process. Automated queries were designed to report on the activity related to each threat.
The audit reports are limited by the time spans available to the automated queries. Some queries are based on changes to properties of objects and a query may not be able to compare an event with activity outside of its observation window. In these cases, the query will not surface a conflict between the event and a prior state. Additionally, the audit reports are constrained by what data is available in the Synapse data warehouse. Currently, account tier information (i.e. anonymous, registered, certified, validated) is not captured in the data warehouse, and therefore cannot be analyzed in the audit report. Additionally, changes to access requirement text is not captured and likewise cannot be reported.For more details, please reference the following pages:
| Child pages (Children Display) |
|---|
Audit Timeline
When | Who | What |
First two weeks of January and July | Synapse Security Engineer | Run Automation
Reference |
“Engineering Audit Resources” page for details | ||
Second two weeks of January and July | Synapse ACT | Sort Data & Triage Threats
|
Reference the |
“Audit Details for ACT” page for details | ||
Mid September | Synapse Security Engineer and Synapse ACT | Generate Audit report following this template
Reference the |
“Audit Report” |
page for details | ||
Late September | Director of Governance (Christine) | Review and Approve/Reject Audit Report
|
October | Synapse Security Engineer and Governance Regulatory Support Team | Security Engineer: Submit Audit Report to HITRUST Governance Regulatory Support Team: Submit Audit Report to WIRB during Synapse Continuing Review Reference the |
“Audit Report” |
Audit Report
Generating the Report:
The audit report should be generated annually in September, and the report requires approval by the Sage Bionetworks Director of Governance. The report should contain data from the past two audit cycles. For example, the October 2021 audit report should contain data from the Q1/Q2 2020 audit and the Q3/Q4 2020 audit periods.
Use this audit report template to generate the report. The same audit report can be submitted to WIRB and to HITRUST. The report should be finalized by the end of September so that it can be submitted to WIRB and HITRUST in October.
Submitting the Report:
One audit report will be generated for both the WIRB and HITRUST submissions.
WIRB Submission:
The Governance Regulatory Support team will submit the audit report during the Synapse Continuing Review, which occurs annually in October. For reference, Synapse submissions to WIRB are stored here.
HITRUST Submission:
The Synapse Security Engineer will submit the audit report to HITRUST annually in October.
Storing the Report:
...
page for details |