-
Notifications
You must be signed in to change notification settings - Fork 10
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.
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
Make changes to comply with Harvard level 3 privacy rules for our NERC data #48
Comments
We don't think this information is actually a security risk. the architectural details are the point- one of the goals of this project is to expose the architectural details so that this may be understood and other sites may reproduce. |
"Level 3" is really restrictive - https://security.harvard.edu/data-classification-table |
Scott and Wayne to discuss tuesday having Scott/Wayne present to security team with context. |
sent email to scott and wayne asking for an update. |
While we do not believe that sharing this information publicly is an security risk we would like to better understand why Harvard feels it is. The value of the data is in the relationships so if the data is to be obscured the relationships should be maintained; we believe doing so is going to be pretty diffic |
With Scott and Wayne, they are out for next 3 weeks. I am moving to April Sprint. This is tracking for others work. |
Feedback from Scott - ignoring this for now. |
Next Steps
Harvard Data Security Level 3
Link to Harvard Data Security Level-3
Links shared with Havard Data Security:
Nathan Hall's response:
"Hi Justin,
Much of that would be considered Level 3 data (specifically non-security technical specifications/architecture schema). Repositories with this level of detail about Harvard systems should not be public. Obfuscated/generalized specifications or reference architecture could be shared in public repos.
Nathan"
The text was updated successfully, but these errors were encountered: