Cloud Security Policy
Sourcegraph uses solely Cloud-based infrastructure and is moving towards holding customer data (our highest risk assets) in multiple Cloud Service Providers (CSPs). This policy outlines controls to be followed across all CSPs according to the data classification held or processed by the assets. The policy follows industry best-practices such as Center for Internet Security (CIS) and Cloud Security Alliance (CSA), along with ensuring several SOC2 controls.
This document covers all Cloud assets owned and/or managed by Sourcergaph in any Cloud provider. The responsibilities and requirements are broken into the following areas:
- Disaster recovery
- Access controls
- Infrastructure-as-code and change management
- Secure baselines
- Data protection
- Logging, monitoring and incident response
All Cloud assets must have defined owners internally. The owner is responsible for ensuring that the asset is compliant with internal policies. An owner can be an individual (DRI) or a team. The creator of an asset is its owner unless clearly stated otherwise.
We will maintain a documented Disaster Recovery plan for Cloud assets containing Restricted data, or any assets under compliance that requires so. The Disaster Recovery plans are tested on an annual basis and tests properly documented.
Our Cloud IAM is designed to enforce the principles of least privilege and segregation of duties. Access to any non-public data must require MFA options. Access to Restricted and Private data must require approval. Wherever possible access logs should be collected and monitored.
Infrastructure-as-code and change management
All assets containing Private or Restricted data should be defined and config through Infrastructure-as-Code (IaC). All changes to the infrastructure must be approved. Wherever possible changes should be made through automation and manual operations limited.
Assets should be configured to an approved secure baseline, based on industry standards such as Cloud Security Alliance (CSA), Center for Internet Security (CIS) and the National Institute of Standards Technology (NIST).
Internet-facing assets must be behind a Load Balancer (or similar) or be designed for being exposed externally, such as storage buckets.
We enforce data encryption at-rest and in-transit for assets containing Restricted and Private data. Data should be properly segregated given its sensitivity and purpose.
Logging, monitoring and incident response
Assets containing Restricted or Private data should be logged. Logs should be monitored and designed to be alerted upon through detection mechanisms. Sourcegraph shall maintain trained Incident Response teams with documented playbooks and incident management practices. The Security Incident Response Policy defines who should report incidents and how.
Sourcegraph will measure and verify compliance to this policy through various methods, including but not limited to, business tool reports, and both internal and external audits.
Exceptions to this policy must be documented in the Risk Register and approved by the Policy Owner.
Violations and enforcement
Any known violations of this policy should be reported to firstname.lastname@example.org. Failure to follow this policy can result in disciplinary action, up to and including termination.
Policy Owner: Head of Security
|1.0||Andre Eleuterio||First version|