Inject secretsvia anenvironmentvariable intoyour appDo not publishEPAM or EPAMclientsproprietary codeto publicrepositoriesNeverreuse yourcredentialsTo share informationwith a customer, usecorporate FTPservers, which havebeen designedspecifically for thispurposeDo not store orshare secretinformationon publicsource coderepositories, suchas GitHub andBitbucketDo not ignorethe securityof test anddevelopmentenvironmentsDo not usebrowsers tostore anykind of logininformationAlways usesecretsmanagement toolssuch as EPAMHashiCorp VaultNever commitsecrets (keys,password,certificates) toGit repositoriesNeversharepersonalpasswordsNever store SSHkeys andcertificates in thesame directoriesas their sourcecodeAvoidsendingpasswords inemail or chatUse a passwordmanager thatsecurely stores andmanages thepasswords for youraccounts anddevicesAlways usecorporate toolssuch as MS Teamsto sharescreenshots andvideo portal toshare a videosAlways use pre-approved datatransfer channelswhen dealing withclient’s or EPAMproprietary dataNever create afile on yourcomputer tostore your logininformationInject secretsvia anenvironmentvariable intoyour appDo not publishEPAM or EPAMclientsproprietary codeto publicrepositoriesNeverreuse yourcredentialsTo share informationwith a customer, usecorporate FTPservers, which havebeen designedspecifically for thispurposeDo not store orshare secretinformationon publicsource coderepositories, suchas GitHub andBitbucketDo not ignorethe securityof test anddevelopmentenvironmentsDo not usebrowsers tostore anykind of logininformationAlways usesecretsmanagement toolssuch as EPAMHashiCorp VaultNever commitsecrets (keys,password,certificates) toGit repositoriesNeversharepersonalpasswordsNever store SSHkeys andcertificates in thesame directoriesas their sourcecodeAvoidsendingpasswords inemail or chatUse a passwordmanager thatsecurely stores andmanages thepasswords for youraccounts anddevicesAlways usecorporate toolssuch as MS Teamsto sharescreenshots andvideo portal toshare a videosAlways use pre-approved datatransfer channelswhen dealing withclient’s or EPAMproprietary dataNever create afile on yourcomputer tostore your 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. Inject secrets via an environment variable into your app
  2. Do not publish EPAM or EPAM clients proprietary code to public repositories
  3. Never reuse your credentials
  4. To share information with a customer, use corporate FTP servers, which have been designed specifically for this purpose
  5. Do not store or share secret informationon public source code repositories, such as GitHub and Bitbucket
  6. Do not ignore the security of test and development environments
  7. Do not use browsers to store any kind of login information
  8. Always use secrets management tools such as EPAM HashiCorp Vault
  9. Never commit secrets (keys, password, certificates) to Git repositories
  10. Never share personal passwords
  11. Never store SSH keys and certificates in the same directories as their source code
  12. Avoid sending passwords in email or chat
  13. Use a password manager that securely stores and manages the passwords for your accounts and devices
  14. Always use corporate tools such as MS Teams to share screenshots and video portal to share a videos
  15. Always use pre-approved data transfer channels when dealing with client’s or EPAM proprietary data
  16. Never create a file on your computer to store your login information