When signing up for a new service ask yourself which team members you need to share access with. There are three types of account access for these services:
Individual accounts (created manually for you, such as Slack, Google): keep your credentials to yourself by storing them in your 'Personal' vault.
Shared accounts (services that don't allow individual accounts or where it is too expensive): store your credentials in an appropriate company 1Password vault so that your colleagues can sign in using your credentials.
OAuth accounts (authentication through GitLab or Google, such as for checkmk monitoring and grafana). For all credentials that are not stored in a shared vault on 1Password there should be one secure note in the 'Shared' vault. This can be services that have individual accounts or OAuth access. Locate the 'secure note' in the team's 'Shared' vault with the name of the service you are trying to access. The note should list whom can give you access in case it has individual accounts, or it may link to the onboarding checklist. You should be added to most of these services during onboarding.
If 2FA should be on for the new user account, make sure to store recovery codes in the login, and consider using auto-generated TOTP if useful.
If you need to give more people access to credentials move them to a vault that they can access. Never duplicate credentials! If needed put them in the 'shared' vault that the whole company can access or make a suggestion to create a new vault in the "1password Shared Folders" Google Sheet. Do not share passwords on a per person basis by sharing them via 1password, this makes it hard to reason about the sharing and doesn't change when the responsibilities change.
When asked security questions (what is your favorite pet, etc.) do not answer truthfully since that is easy to research. Make up an answer and write both the question and answer in 1password.
Do not share credentials via email, issue comments, chat etc. This includes email addresses to login and API keys. Use 1Password vaults for this. You will be invited to applicable vaults after joining the company.
If you want to see your vaults or ask to be added to a new one please leave a comment in the "1password Shared Folders" Google Doc.
Refer to the items with NAME_OF_SITE credentials in VAULT_NAME. For example: "for access please see the AOL credentials in the Luddite vault".
Do not store credentials in a vault if everyone has their own user account for the service.
Do not let your password manager store the master password. It is okay to store the login.
Enable two-factor authentication (2FA) with 1Password auto-generated TOTP for your Google, Slack, GitLab.com, and dev.gitlab.org accounts. The nice thing about 1Password is that it migrates when you have a new phone, unlike Google Authenticator.
You can also consider using a Yubikey with GitLab.
Encrypt your computer's home folder. For Mac users: Use FileVault to encrypt the entire disk.
Set up a screen saver with password lock on your laptop. The timeout can depend on how you use your laptop.
Never leave your unlocked computer unattended. Activate the screensaver, lock the desktop, or close the lid.
Report suspect situations to an officer of the company.
Never dismiss a security report as invalid. Keep asking questions until the researcher comes to the same conclusion or stops responding.
Do not forward company emails (@gitlab.com) to a non-company email address.
Do not click on links in emails you did not request yourself (requested password reset is OK, anything else is suspect). Clicking itself is a problem even when you don't enter a password, because a visit can already be used to execute a 0-day attack. We simulate phishing attacks by having an external service send emails to our company email addresses to ensure everyone is aware of the threat.
The CEO will not send you an email to wire cash. Feel free to verify any unusual requests with a video call.
During offboarding, your 1Password account is deleted. If you want to store your personal passwords please store them in your 'Primary' vault, not the vault named 'Your Vault'.
Do not install software with many known security vulnerabilities (as listed in the handbook). When in doubt, do not install until after checking with the team by discussing in an issue, and then document the verdict in the handbook.
1Password is a password manager. Ideally you memorize one strong password - hence the name - and let 1Password generate and manage strong, unique passwords for every site for which you have a login.
Following this guide, it will be helpful to understand a few terms we'll be using throughout.
App: A native 1Password application (OSX, iOS, Windows, Android).
Extension: A web browser extension/plugin that communicates with the App to provide access to your passwords securely without leaving the browser.
Vault: What 1Password calls any grouping of secure data, such as logins or secure notes. Sometimes called a "keychain".
Prior to adding Teams support, 1Password was designed for use by a single person. It uses a native app and stores your data in a local folder on your computer. You can optionally sync this folder to Dropbox to make it available on your phone's 1Password app, or on another computer.
1Password for Teams
1Password for Teams is a new feature, currently still in beta. It stores all Vaults on the 1Password servers and allows for sharing between multiple people on the same team.
Everyone at GitLab should already be signed up for our Teams account. This gives you access to the web interface, allowing you to view the Vaults we've configured and given you access to.
In addition to the shared vaults such as Everyone, Support, Marketing, each member of the team has a vault called Your Vault which only you can see, and allows you to store personal credentials within our team's account.
To really get the full benefit of 1Password, you'll need to hook our Teams account up to one of the native apps, which can be tricky.
Adding the GitLab Team to a 1Password app
This guide will cover setting up the OSX app. It's their lead platform and is the most up-to-date. These instructions may or may not work for the Windows version.
At the prompt, choose "I'm a new user". Note: This is one source of confusion. "I created my Teams account, I'm not new!" Just go with it.
Enter a master password, confirmation, and hint. This can (and should) be different from the password you used for our Teams account. This password gates access to your local, private Vault on your computer and/or phone.
Skip over the remaining dialogs (syncing, newsletter, etc.)
You should now have an empty vault called Primary.
Because the Teams feature is currently in beta, we need to update the app to a beta version:
Go to Preferences
Go to Updates
Check Include beta builds
Click Check Now
Install the update and relaunch
After relaunch, go to Preferences again
Go to Teams
Click the + icon
Now you'll need the Emergency Kit PDF that 1Password told you to save when you registered your Teams account.
If you saved it as a digital PDF file:
Open the PDF file
Click Scan QR Code
Drag the scanner window over the QR code on the PDF sheet
If you printed the PDF:
Click Sign In Manually
For Team URL enter gitlab.1password.com
For Account Key enter the Account Key from your Emergency Kit
For Email Address enter your @gitlab.com email
For Master Password enter the password to your Teams account (not the password you created above when you chose "I'm a new user")
After the Team is added, you should see some notifications about vaults being added to 1Password. By default you'll have Everyone and Your Vault, and may have access to others.
The latest iOS app supports Teams without requiring a beta version and is much more straightforward to set up, so I won't cover it here.
Click the Vault Selector in the upper-left corner of the window:
Keep in mind that Primary is your local, private vault and is not synced unless you enable syncing it to something like your personal Dropbox account.
Your Vault is your remote, private vault that is synced to the GitLab 1Password for Teams account, and can not be viewed by anyone else on the team, including admins.
Everyone is a vault that everyone on the GitLab Teams account has access to both read and write.
Go to Browser extensions and install the extension for whatever browser you're using. You should not need a beta version here.
With the extension installed, you should be able to go to a site that has credentials stored in our Team vault and log in:
If you don't see the site listed in the results window, make sure you're using the correct vault:
When 1Password detects a login form submission, it may ask if you want to save the login with a dialog like this:
If you do want to save it, make sure the appropriate Vault is selected first.
This is an example of how Robert, one of our developers, uses 1Password:
Once you fully commit to using 1Password to manage all of your security information, it really does make life easier.
I memorize one strong password and let the app generate everything else. Every site I use has a unique password that I can't compromise because I don't even know it, and a hacked site can't compromise it because the password is never re-used on another site.
I store my shipping and credit card info in 1Password and use the browser extension to quickly fill out shipping and billing information on shopping sites.
I store my passport data, along with a digital scan, in 1Password; drivers license info and scan; insurance info; software license keys; any important information that needs to be secure but still easily accessible when I need it, from anywhere. I sync my personal vault to my personal Dropbox so it's available on my phone, tablet, laptop, and desktop.
Even my 1Password for Teams account information is stored in my personal Primary vault, with the Emergency Kit PDF as a secure attachment:
I have no idea what the password is. I've never actually typed it. And that's the idea.