Never create afile on yourcomputer tostore your logininformationNever store SSHkeys andcertificates in thesame directoriesas their sourcecodeNeverreuse yourcredentialsDo not publishEPAM or EPAMclientsproprietary codeto publicrepositoriesAlways use pre-approved datatransfer channelswhen dealing withclient’s or EPAMproprietary dataAlways usesecretsmanagement toolssuch as EPAMHashiCorp VaultNeversharepersonalpasswordsInject secretsvia anenvironmentvariable intoyour appNever commitsecrets (keys,password,certificates) toGit repositoriesDo not usebrowsers tostore anykind of logininformationTo share informationwith a customer, usecorporate FTPservers, which havebeen designedspecifically for thispurposeUse a passwordmanager thatsecurely stores andmanages thepasswords for youraccounts anddevicesAvoidsendingpasswords inemail or chatDo not ignorethe securityof test anddevelopmentenvironmentsDo not store orshare secretinformationon publicsource coderepositories, suchas GitHub andBitbucketAlways usecorporate toolssuch as MS Teamsto sharescreenshots andvideo portal toshare a videosNever create afile on yourcomputer tostore your logininformationNever store SSHkeys andcertificates in thesame directoriesas their sourcecodeNeverreuse yourcredentialsDo not publishEPAM or EPAMclientsproprietary codeto publicrepositoriesAlways use pre-approved datatransfer channelswhen dealing withclient’s or EPAMproprietary dataAlways usesecretsmanagement toolssuch as EPAMHashiCorp VaultNeversharepersonalpasswordsInject secretsvia anenvironmentvariable intoyour appNever commitsecrets (keys,password,certificates) toGit repositoriesDo not usebrowsers tostore anykind of logininformationTo share informationwith a customer, usecorporate FTPservers, which havebeen designedspecifically for thispurposeUse a passwordmanager thatsecurely stores andmanages thepasswords for youraccounts anddevicesAvoidsendingpasswords inemail or chatDo not ignorethe securityof test anddevelopmentenvironmentsDo not store orshare secretinformationon publicsource coderepositories, suchas GitHub andBitbucketAlways usecorporate toolssuch as MS Teamsto sharescreenshots andvideo portal toshare a videos

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