Always use pre-approved datatransfer channelswhen dealing withclient’s or EPAMproprietary dataNever commitsecrets (keys,password,certificates) toGit repositoriesNever store SSHkeys andcertificates in thesame directoriesas their sourcecodeUse a passwordmanager thatsecurely stores andmanages thepasswords for youraccounts anddevicesAlways usesecretsmanagement toolssuch as EPAMHashiCorp VaultNever create afile on yourcomputer tostore your logininformationInject secretsvia anenvironmentvariable intoyour appDo not ignorethe securityof test anddevelopmentenvironmentsTo share informationwith a customer, usecorporate FTPservers, which havebeen designedspecifically for thispurposeNeversharepersonalpasswordsAvoidsendingpasswords inemail or chatDo not store orshare secretinformationon publicsource coderepositories, suchas GitHub andBitbucketAlways usecorporate toolssuch as MS Teamsto sharescreenshots andvideo portal toshare a videosDo not usebrowsers tostore anykind of logininformationDo not publishEPAM or EPAMclientsproprietary codeto publicrepositoriesNeverreuse yourcredentialsAlways use pre-approved datatransfer channelswhen dealing withclient’s or EPAMproprietary dataNever commitsecrets (keys,password,certificates) toGit repositoriesNever store SSHkeys andcertificates in thesame directoriesas their sourcecodeUse a passwordmanager thatsecurely stores andmanages thepasswords for youraccounts anddevicesAlways usesecretsmanagement toolssuch as EPAMHashiCorp VaultNever create afile on yourcomputer tostore your logininformationInject secretsvia anenvironmentvariable intoyour appDo not ignorethe securityof test anddevelopmentenvironmentsTo share informationwith a customer, usecorporate FTPservers, which havebeen designedspecifically for thispurposeNeversharepersonalpasswordsAvoidsendingpasswords inemail or chatDo not store orshare secretinformationon publicsource coderepositories, suchas GitHub andBitbucketAlways usecorporate toolssuch as MS Teamsto sharescreenshots andvideo portal toshare a videosDo not usebrowsers tostore anykind of logininformationDo not publishEPAM or EPAMclientsproprietary codeto publicrepositoriesNeverreuse yourcredentials

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