Always usesecretsmanagement toolssuch as EPAMHashiCorp VaultNeverreuse yourcredentialsAvoidsendingpasswords inemail or chatDo not usebrowsers tostore anykind of logininformationTo share informationwith a customer, usecorporate FTPservers, which havebeen designedspecifically for thispurposeAlways use pre-approved datatransfer channelswhen dealing withclient’s or EPAMproprietary dataNever commitsecrets (keys,password,certificates) toGit repositoriesNever create afile on yourcomputer tostore your logininformationNeversharepersonalpasswordsAlways usecorporate toolssuch as MS Teamsto sharescreenshots andvideo portal toshare a videosUse a passwordmanager thatsecurely stores andmanages thepasswords for youraccounts anddevicesDo not store orshare secretinformationon publicsource coderepositories, suchas GitHub andBitbucketInject secretsvia anenvironmentvariable intoyour appDo not ignorethe securityof test anddevelopmentenvironmentsDo not publishEPAM or EPAMclientsproprietary codeto publicrepositoriesNever store SSHkeys andcertificates in thesame directoriesas their sourcecodeAlways usesecretsmanagement toolssuch as EPAMHashiCorp VaultNeverreuse yourcredentialsAvoidsendingpasswords inemail or chatDo not usebrowsers tostore anykind of logininformationTo share informationwith a customer, usecorporate FTPservers, which havebeen designedspecifically for thispurposeAlways use pre-approved datatransfer channelswhen dealing withclient’s or EPAMproprietary dataNever commitsecrets (keys,password,certificates) toGit repositoriesNever create afile on yourcomputer tostore your logininformationNeversharepersonalpasswordsAlways usecorporate toolssuch as MS Teamsto sharescreenshots andvideo portal toshare a videosUse a passwordmanager thatsecurely stores andmanages thepasswords for youraccounts anddevicesDo not store orshare secretinformationon publicsource coderepositories, suchas GitHub andBitbucketInject secretsvia anenvironmentvariable intoyour appDo not ignorethe securityof test anddevelopmentenvironmentsDo not publishEPAM or EPAMclientsproprietary codeto publicrepositoriesNever store SSHkeys andcertificates in thesame directoriesas their sourcecode

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