To ensure proper and effective use of cryptography to protect the confidentiality, authenticity and/or integrity of information. This policy establishes requirements for the use and protection of cryptographic keys throughout their entire lifecycle.
All information systems developed and/or controlled by Sourcegraph which store or transmit confidential data.
Sourcegraph shall evaluate the risks inherent in processing and storing data, and shall implement cryptographic controls to mitigate those risks where deemed appropriate. Where encryption is in use, strong cryptography with associated key management processes and procedures shall be implemented and documented. All encryption shall be performed in accordance with industry standards, including NIST SP 800-57. For all personal data, Sourcegraph shall consider the state of the art, the costs of implementation and the nature, scope, context, and purposes of processing as well as the risk of varying likelihood and severity to the rights and freedoms of natural persons, and implement appropriate technical and organizational measures surrounding the pseudonymization and encryption of data to ensure a level of security appropriate to the risk. For all web traffic sent over the public Internet containing confidential information, the TLS v1.2 protocol or better must be utilized.
Access to keys and secrets shall be tightly controlled in accordance with the Access Control Policy.
The following table includes the recommended usage for cryptographic keys:
|Domain||Key Type||Algorithm||Key Length||Max Expiration|
|Web Certificate||Digital Signature||SHA256||256 bit||2 years|
|Web Cipher||Encryption||AES_128_GCM *||128 bit||N/A|
|Confidential||Encryption||AES256||256 bit||1 Year|
|Laptop HDD||Encryption||XTS-AES-128 **||256 bit||N/A|
* This is provided via the TLS 1.3 stack using the TLS_AES_128_GCM_SHA256 Cipher Suite.
** Please see Computer Standards for more information.
Requests for an exception to this policy must be submitted to Security for approval.
Violations & Enforcement
Any known violations of this policy should be reported to the #security slack channel. Violations of this policy can result in immediate withdrawal or suspension of system and network privileges and/or disciplinary action in accordance with company procedures up to and including termination of employment.
Policy Owner: Head of Security
|1.0||27-Jan-2022||First version||David Sandy||Diego Comas|
|1.1||30-May-2023||2023 review - no updates||André Eleuterio||Diego Comas|