Which scenario describes exposure of FTP/SFTP server credentials on a public code hosting platform?

• A. Exposed SFTP credentials in a public repository
• B. Exposed a password hash in log files
• C. Exposed FTP/SFTP server credentials on GitHub
• D. Exposed database credentials in a configuration file

Answer: (C)

Focusing on the risk of secrets being exposed through a public code hosting platform is key. When FTP/SFTP server login details are published in a repository on GitHub, they become publicly discoverable to anyone who visits the project. This is a direct leakage of credentials through a platform that is specifically designed to host and share code, making it the clearest example of exposing FTP/SFTP server credentials on a public code hosting service.

The other scenarios involve sensitive data but not the explicit context of a public code hosting platform. A password hash found in log files is still dangerous, but it isn’t credentials exposed on a code-hosting site. Exposing database credentials in a configuration file is a common mistake, but again it doesn’t demonstrate leakage specifically through a public code hosting platform.