Which of the following can be used to determine whether access keys are stored in the source code or any other configuration files during development?

Which of the following can be used to determine whether access keys are stored in the source code or any other configuration files during development?
A . Static code review
B . Dynamic code review
C . Vulnerability scanning
D . Credential scanning

View Answer

Answer: D

Explanation:

Credential scanning is a technique that can be used to detect and prevent the exposure of access keys and other sensitive information in the source code or any other configuration files during development. Credential scanning tools can scan the code repositories, files, and commits for any hardcoded credentials, such as access keys, passwords, tokens, certificates, and connection strings. They can also alert the developers or security teams of any potential leaks and suggest remediation actions, such as rotating or revoking the compromised keys, removing the credentials from the code, or using secure storage mechanisms like vaults or environment variables. Credential scanning can be integrated into the development pipeline as part of the continuous integration and continuous delivery (CI/CD) process, or performed periodically as a security audit. Credential scanning can help reduce the risk of credential leakage, which can lead to unauthorized access, data breaches, or account compromise.

Reference: Protecting Source Code in the Cloud with DSPM

Best practices for managing service account keys

Protect your code repository