Exam AZ-400 topic 5 question 41 discussion

D is the answer. https://docs.github.com/en/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-alerts-for-partners When you make a repository public, or push changes to a public repository, GitHub always scans the code for secrets that match partner patterns. Public packages on the npm registry are also scanned. If secret scanning detects a potential secret, we notify the service provider who issued the secret. The service provider validates the string and then decides whether they should revoke the secret, issue a new secret, or contact you directly. Their action will depend on the associated risks to you or them. You cannot change the configuration of secret scanning for partner patterns on public repositories.

Detection and notification: When a commit containing a matching pattern is made, GitHub notifies the relevant service provider directly. This happens even before any other party is informed. Other stakeholders: While the committer, owner, and organization administrator might receive notifications about the commit, they won't be notified first about the specific secret detection.

Secret scanning partner

D. the secret scanning partner Scan for potential secrets. When the commit is made, the secret scanning partner is the first to be notified. Then takes appropriate actions, such as alerting the owner or taking security measures.

A pattern matching a regular expression might be a token, a password, a secret of some kind or some other sensitive data that could be a potential security issue. The answer is D - a secret scanning partner. This is basically a bot that scans your changes, detects the aforementioned issues and can notify you to take corrective actions.

ChatGPT answer: Based on the information provided, the correct answer would be D. the secret scanning partner. When a commit is made to a public GitHub repository and it contains a pattern that matches a regular expression, GitHub's secret scanning feature is triggered. The secret scanning partner associated with GitHub is notified first to perform an analysis and identify any potential secrets or sensitive information in the commit.

the provided answer is right. the link provided by Pamban and zellck is right, but please notice the next part. https://docs.github.com/en/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-alerts-for-partners Secret scanning alerts for users are available for free on all public repositories. When you enable secret scanning for a repository, GitHub scans the code for patterns that match secrets used by many service providers. When the scan is completed, GitHub sends an email alert to the enterprise and organization owners, even if no secrets were found.

https://docs.github.com/en/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-alerts-for-partners

I believe its C. I can't seem to find no reference online about notification chain order. But it makes sense from my experience that the owners\maintainers of the repository are the first one being notified.