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.

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 a Security Strategy #85

Closed
johnml1135 opened this issue Aug 14, 2023 · 3 comments
Closed

Make a Security Strategy #85

johnml1135 opened this issue Aug 14, 2023 · 3 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@johnml1135
Copy link
Collaborator

What are we securing? How is it being secured? We need to review and document our approach, assumptions, and measures taken to ensure security.

@johnml1135 johnml1135 self-assigned this Aug 14, 2023
@johnml1135 johnml1135 added the documentation Improvements or additions to documentation label Aug 14, 2023
@johnml1135 johnml1135 added this to the 1.2 Paratext Plugin MVP milestone Aug 14, 2023
@davidbaines
Copy link

I had a couple of questions about security:
Will we continue to use AWS S3 in production? I imagine that the security offered there is sufficient for our needs. How do we test that assumption?

Will each project have its own credentials?
Can we be confident that access to one project does not give any way of discovering other projects on the server?
Leaked credentials from one project (such as in an error report) would not affect the security of any other project.

@johnml1135
Copy link
Collaborator Author

@johnml1135
Copy link
Collaborator Author

Completed enough for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Status: ✅ Done
Development

No branches or pull requests

2 participants