开云体育

Sigh. I'm getting pushback from someone on my board due to her concerns about GIO being "secure enough." (Never mind the details.)

Can someone give me language that a somewhat tech-savvy layperson can grasp to allay their fears??

Pete

Without knowing what "secure enough" means in this person's head, it's pretty hard to say anything.??
What are the threats and attack vectors that are of concern?
Physical access to the servers?? How are the admin usernames/passwords secured and backed up?? the list goes on and on.......
A good place to start is here -> /static/about
The Data Processing Agreement might allay their concerns.
Toby

Toby, that is exactly the problem. I need to allay the fears of someone who isn't quite sure what her fears are based on.

Received from Peter Cook at 11/29/2018 03:52 PM UTC:

Sigh. I'm getting pushback from someone on my board due to her concerns about GIO being "secure enough." (Never mind the details.)

Can someone give me language that a somewhat tech-savvy layperson can grasp to allay their fears?

Pete

What sort of "tech-savvy" language do you expect will satisfy someone who has no specific reason to suspect Gio is insecure... especially when we've been told to "never mind the details?" Absolutely nothing has been provided that anyone can respond to.

Jim H

Here's what I wrote. Problem solved.

• a published privacy policy - /static/privacy?
• a published cookie policy - /static/cookie_policy
• information about GDPR compliance - /static/compliance
• a published DPA - /pdfs/Data%20Processing%20Agreement.pdf
• and offers 2-factor authentication.

Sometimes it makes my job as a board president so much easier if I just find a reasonable way to soothe fears.?

Pete