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 Policy Updates #254

Open
1 of 15 tasks
reynoldsalec opened this issue Jan 4, 2021 · 0 comments
Open
1 of 15 tasks

Security Policy Updates #254

reynoldsalec opened this issue Jan 4, 2021 · 0 comments
Assignees

Comments

@reynoldsalec
Copy link
Member

reynoldsalec commented Jan 4, 2021

Lando

  • Policy of forcing partners to not give us "real" websites
  • Switch off of Qbox.
  • Audit of current data. Think about ways we can change data collection to get better data/reduce footprint.
  • Eliminate email storage on our systems (allow providers the opportunity to store)
  • Separation of partner data storage/make it easier to send them exclusive stream of data.
  • Making it clear that our dependencies (particularly those interfacing with integration partners like P.sh/Pantheon/etc.) have separate privacy policies. Make the liability distinct.
  • Security scanning of Docker images/using official Docker images.
  • Dependency scanning -> way to keep more up-to-speed.

Tandem

  • Limiting usage of public unprotected networks. Promote cell phone?
  • VPN
  • Rotating SSH keys/passwords.
  • Go through training checklist.
  • Review compliance with individual team members.
  • Initial project audit for sensitive data.
  • Response if someone's computer is compromised/off-boarding a user.
@reynoldsalec reynoldsalec self-assigned this Jan 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant