Our infrastructure and security team includes people who’ve played lead roles in designing, building, and operating highly secure Internet facing systems at companies ranging from startups to large public companies.
We have implemented a formal procedure for security events and have educated all our staff on our policies.
When security events are detected they are escalated to our emergency alias, teams are paged, notified and assembled to rapidly address the event.
After a security event is fixed we write up a post-mortem analysis.
The analysis is reviewed in person, distributed across the company and includes action items that will make the detection and prevention of a similar event easier in the future.
Sunlight will promptly notify you in writing upon verification of a security breach of the Sunlight services that affects your data. Notification will describe the breach and the status of Sunlight’s investigation.
We have functioning, frequently used automation in place so that we can safely and reliably rollout changes to both our application and operating platform within minutes.
We typically deploy code dozens of times a day, so we have high confidence that we can get a security fix out quickly when required.
All of our services run in the cloud. Sunlight does not run our own routers, load balancers, DNS servers, or physical servers.
All of our services and data are hosted in AWS facilities in Ireland and protected by AWS security, as described at http://aws.amazon.com/security/sharing-the-security-responsibility. Sunlight services have been built with disaster recovery in mind.
All of our infrastructure is spread across 3 AWS data centers (availability zones) and will continue to work should any one of those data centers fail unexpectedly. Amazon does not disclose the location of its data centers. As such, Sunlight builds on the physical security and environmental controls provided by AWS. See http://aws.amazon.com/security for details of AWS security infrastructure.
All of our servers are within our own virtual private cloud (VPC) with network access control lists (ACL’s) that prevent unauthorized requests getting to our internal network.
Sunlight uses a backup solution for datastores that contain customer data.
All customer data is stored in the European Economic Area ("EEA").
Customer data is stored in multi-tenant datastores and is automatically encrypted at rest, cloaking your data in another layer of protection.; we do not have individual datastores for each customer. However strict privacy controls exist in our application code that are designed to ensure data privacy and to prevent one customer from accessing another customer’s data (i.e., logical separation). We have many unit and integration tests in place to ensure these privacy controls work as expected. These tests are run every time our codebase is updated and even one single test failing will prevent new code being shipped to production.
Each Sunlight system used to process customer data is adequately configured and pathed using commercially-reasonable methods according to industry-recognized system-hardening standards.
All data sent to or from Sunlight is encrypted in transit using 256-bit encryption.
Our API and application endpoints are TLS/SSL only and score an "A+" rating on SSL Labs' tests. This means we only use strong cipher suites and have features such as HSTS and Perfect Forward Secrecy fully enabled.
Sunlight is served 100% over https. Sunlight runs a zero-trust corporate network.
There are no corporate resources or additional privileges from being on Sunlight network.
We have two-factor authentication (2FA) and strong password policies on GitHub, Google and AWS to ensure access to cloud services are protected.
Sunlight enables permission levels to be set for any employees with access to Sunlight.
Permissions and access can be set as an admin to be able to view group settings, billing, user data, integrations, budget management, analytics or the ability to view order details.
On an application level, we produce audit logs for all activity, ship logs to our service providers for analysis, and use S3/Glacier for archival purposes.
All access to Sunlight applications is logged and audited.
All actions taken on production consoles or in the Sunlight application are logged.
We use technologies to provide an audit trail over our infrastructure and the Sunlight application. Auditing allows us to do ad-hoc security analysis, track changes made to our setup and audit access to every layer of our stack.
Information about AWS security certifications and obtaining copies of security reports from AWS is available at http://aws.amazon.com/compliance/pci-data-privacy-protection-hipaa-soc-fedramp-faqs/
Sunlight Technologies Ltd complies with Cybersmart best practices and is accredited by IASME to hold Cyber Essential certification.
All payment instrument processing for purchase of the Sunlight services is performed by Stripe. For more information on Stripe’s security practices, please seehttps://stripe.com/docs/security/stripe.
Managing your own user accounts and roles from within the Sunlight services.
Protecting your own account and user credentials for all of your employees accessing the Sunlight services.
Compliance with the Terms and Conditions of your service agreement with Sunlight, including with respect to compliance with laws.
Promptly notifying Sunlight if a user credential has been compromised or if you suspect possible suspicious activities that could negatively impact security of the Sunlight services or your account.
You may not perform any security penetration tests or security assessment activities without the express advance written consent of Sunlight.