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

Security compliance documentation #989

Open
5 tasks
ferrisoxide opened this issue Aug 11, 2024 · 0 comments
Open
5 tasks

Security compliance documentation #989

ferrisoxide opened this issue Aug 11, 2024 · 0 comments
Labels
security Pull requests that address a security vulnerability task

Comments

@ferrisoxide
Copy link
Collaborator

Describe the task

Prepare a document detailing the security context of the application, including security compliance provided by third party vendors (e.g. hosting vendors) as well as our own internal security protocols and practices.

The target audience for this are client's IT departments. The aim is to address any security concerns IT departments may have, as well as establish lines of communication for handling any potential future security issues.

Success Criteria

  • MUST cover compliance provided by all third-party vendors (hosting, monitoring, email, etc)
  • MUST detail security practices undertaken within Eventide
  • MUST refer to any security standards that are either met or form the basis of security protocols
  • MUST detail the process for reporting security issue to Eventide
  • MUST detail the process for Eventide to communicate any security issues to clients.

Additional Notes

We've prepared similar documents in the past. Try to find these first and see if we have already covered some of this.

@ferrisoxide ferrisoxide added the security Pull requests that address a security vulnerability label Aug 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
security Pull requests that address a security vulnerability task
Projects
Status: Backlog
Development

No branches or pull requests

1 participant