{"id":107040,"date":"2023-03-02T12:48:19","date_gmt":"2023-03-02T10:48:19","guid":{"rendered":"https:\/\/prohoster.info\/?p=107040"},"modified":"2023-03-03T15:16:29","modified_gmt":"2023-03-03T13:16:29","slug":"github-realizoval-proverku-utechki-konfidenczialnyh-dannyh-v-repozitoriyah","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/github-realizoval-proverku-utechki-konfidenczialnyh-dannyh-v-repozitoriyah","title":{"rendered":"GitHub has implemented a check for the leakage of confidential data in repositories","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
GitHub has announced the launch of a free service for monitoring accidental publication of sensitive data in repositories, such as encryption keys, database passwords, and API access tokens. Previously, this service was only available to beta testing program participants, but it is now being provided without restrictions to all public repositories. To enable the scanning of your repository, you should activate the 'Secret scanning' option in the settings under the 'Code security and analysis' section. <\/p>\n
More than 200 templates have been implemented for identifying various types of keys, tokens, certificates, and credentials. The search for leaks occurs not only in the code but also in issues, descriptions, and comments. To eliminate false positives, only reliably identifiable types of tokens are checked, covering more than 100 different services, including Amazon Web Services, Azure, Crates.io, DigitalOcean, Google Cloud, NPM, PyPI, RubyGems, and Yandex.Cloud. Additionally, alerts are supported for the detection of self-signed certificates and keys. <\/p>\n