Edge2Web Security Practices
We place strict controls over our employees’ access to the data you and your users make available via the Edge2Web services ("Customer Data"), and are committed to ensuring that Customer Data is not seen by anyone who should not have access to it. The operation of the Edge2Web services requires that some employees have access to the systems which store and process Customer Data. For example, in order to diagnose a problem you are having with the Edge2Web services, we may need to access your Customer Data. These employees are prohibited from using these permissions to view Customer Data unless it is necessary to do so. We have technical controls and audit policies in place to ensure that any access to Customer Data is logged.
All of our employees and contract personnel are bound to our policies regarding Customer Data and we treat these issues as matters of the highest importance within our company.
Security Features for Team Administrators
In addition to the work we do at the infrastructure level, we provide Team Administrators of paid versions of the Edge2Web services with additional tools to enable their own users to protect their Customer Data.
Access logs are available to administrators of paid teams. We log every time an account signs in, noting the type of device used and the IP address of the connection.
Single Sign On
Administrators of paid teams can integrate their Edge2Web services instance with a variety of single-sign-on providers. Teams on the ‘Standard’ plan can enable Google Apps for Domains as their authentication provider, and teams on the ‘Plus’ plan can enable SAML SSO using popular SSO service providers.
Data Encryption In Transit and At Rest
The Edge2Web services support the latest recommended secure cipher suites and protocols to encrypt all traffic in transit. Customer Data is encrypted at rest.
We monitor the changing cryptographic landscape closely and work promptly to upgrade the service to respond to new cryptographic weaknesses as they are discovered and implement best practices as they evolve. For encryption in transit, we do this while also balancing the need for compatibility for older clients.
In addition to system monitoring and logging, we have implemented two-factor authentication for all server access across our production environment. Firewalls are configured according to industry best practices and unnecessary ports are blocked by configuration with AWS Security Groups.
Edge2Web maintains a centralized logging environment in our production environment which contains information pertaining to security, monitoring, availability, access, and other metrics about the Edge2Web services. These logs are analyzed for security events.
Incident Management & Response
In the event of a security breach, Edge2Web will promptly notify you of any unauthorized access to your Customer Data. Edge2Web has incident management policies and procedures in place to handle such an event.
External Security Audits
We conduct regular audits of the Edge2Web services to verify that our security practices are sound and to monitor the Edge2Web services for new vulnerabilities discovered by the security research community. In addition to periodic and targeted audits of the Edge2Web services and features, we also employ the use of continuous automated scanning of our web platform.
Product Security Practices
New features, functionality, and design changes go through our security review process. In addition, our code is audited with automated static analysis software, tested, and manually peer-reviewed prior to being deployed to production. Our engineering leadership works closely with development personnel to resolve any additional security concerns that may arise during development.