Avoidsendingpasswords inemail or chatNeverreuse yourcredentialsNever create afile on yourcomputer tostore your logininformationDo not ignorethe securityof test anddevelopmentenvironmentsNever store SSHkeys andcertificates in thesame directoriesas their sourcecodeDo not store orshare secretinformationon publicsource coderepositories, suchas GitHub andBitbucketInject secretsvia anenvironmentvariable intoyour appDo not publishEPAM or EPAMclientsproprietary codeto publicrepositoriesAlways usecorporate toolssuch as MS Teamsto sharescreenshots andvideo portal toshare a videosTo share informationwith a customer, usecorporate FTPservers, which havebeen designedspecifically for thispurposeUse a passwordmanager thatsecurely stores andmanages thepasswords for youraccounts anddevicesAlways use pre-approved datatransfer channelswhen dealing withclient’s or EPAMproprietary dataNever commitsecrets (keys,password,certificates) toGit repositoriesNeversharepersonalpasswordsAlways usesecretsmanagement toolssuch as EPAMHashiCorp VaultDo not usebrowsers tostore anykind of logininformationAvoidsendingpasswords inemail or chatNeverreuse yourcredentialsNever create afile on yourcomputer tostore your logininformationDo not ignorethe securityof test anddevelopmentenvironmentsNever store SSHkeys andcertificates in thesame directoriesas their sourcecodeDo not store orshare secretinformationon publicsource coderepositories, suchas GitHub andBitbucketInject secretsvia anenvironmentvariable intoyour appDo not publishEPAM or EPAMclientsproprietary codeto publicrepositoriesAlways usecorporate toolssuch as MS Teamsto sharescreenshots andvideo portal toshare a videosTo share informationwith a customer, usecorporate FTPservers, which havebeen designedspecifically for thispurposeUse a passwordmanager thatsecurely stores andmanages thepasswords for youraccounts anddevicesAlways use pre-approved datatransfer channelswhen dealing withclient’s or EPAMproprietary dataNever commitsecrets (keys,password,certificates) toGit repositoriesNeversharepersonalpasswordsAlways usesecretsmanagement toolssuch as EPAMHashiCorp VaultDo not usebrowsers tostore anykind of logininformation

Securtiy bingo - Call List

(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
  1. Avoid sending passwords in email or chat
  2. Never reuse your credentials
  3. Never create a file on your computer to store your login information
  4. Do not ignore the security of test and development environments
  5. Never store SSH keys and certificates in the same directories as their source code
  6. Do not store or share secret informationon public source code repositories, such as GitHub and Bitbucket
  7. Inject secrets via an environment variable into your app
  8. Do not publish EPAM or EPAM clients proprietary code to public repositories
  9. Always use corporate tools such as MS Teams to share screenshots and video portal to share a videos
  10. To share information with a customer, use corporate FTP servers, which have been designed specifically for this purpose
  11. Use a password manager that securely stores and manages the passwords for your accounts and devices
  12. Always use pre-approved data transfer channels when dealing with client’s or EPAM proprietary data
  13. Never commit secrets (keys, password, certificates) to Git repositories
  14. Never share personal passwords
  15. Always use secrets management tools such as EPAM HashiCorp Vault
  16. Do not use browsers to store any kind of login information