Here’s what you need to know about sensitive information at TTS.
What is considered sensitive?
Anything that would make our systems vulnerable or would impact the privacy of others if it fell into the wrong hands. To learn what information we consider sensitive, see our Open Source Policy practices guide. See also: the GSA Controlled Unclassified Information (CUI) Guide.
TTS offers a few different tools for protecting sensitive information. As you learned in your Security Awareness and Privacy training in GSA Online University (OLU), only share sensitive information with the people who absolutely need it and are authorized to see it.
To prevent committing sensitive data to your Git repository, install Caulking.
You can use GSA Google Drive to share sensitive files, spreadsheets, and documents. This includes personally identifiable information (PII) of either federal staff or the public, but it does not include classified information of any kind. If you’re handling PII, be absolutely sure you are only sharing Drive files with GSA staff and that those staff members have a direct need for the information.
You can use OMB MAX to share sensitive files (in appropriate “workspaces” within MAX). We typically use MAX for working with partners who don’t have access to — or who don’t feel comfortable putting the information in — Google Drive. Some workspaces in MAX are available to private organizations (for example, cloud service providers in the FedRAMP workspaces) and many other government agencies. Anyone with a
@gsa.gov email can self-register on Max.gov; register your HSPD-12/PIV card or set up 2-factor authentication via SMS. Max.gov document sharing uses Confluence so you may need to read Max.gov’s documentation on how to manage permissions and upload documents.
Be sure you know who you need to share with before posting. Only .gov/.mil/.fed.us users can self-register to Max.gov; other email domains can be individually granted access, but you’ll have to personally sponser them by making a request to MAXsupport@omb.eop.gov.
You can create an S3 service instance on cloud.gov and issue credentials for partners to access it. See interacting with your S3 bucket.
Follow the linked instructions to password-protect a:
Send the encrypted file and password to the recipient separately, with the latter ideally through something ephemeral like a phone call.
Git-based workflows and Continous Integration and Deployment (CI/CD)
Preventing the leak/exposure of secrets and sensitive information must always be our top priority. For TTS Engineers and Developers,
Sensitive Information also includes protecting the development and operations of TTS Systems. TTS strongly encourages Continous Integration and Deployment (CI/CD). However, when using a git-based workflow, it is most important to protect branches and enforce reviewer approval before any automation of code changes
CircleCI has a Build Pull Request from Forked repos setting and a Pass Secrets to Builds from Forked Pull request setting. Both are disabled by default, but any repo owner can enable them.
Other references for protecting Sensitive Information in CI/CD