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

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