To protect intellectual property in development hosted on a public cloud, which practice is recommended?

To protect intellectual property in development hosted on a public cloud, which practice is recommended?

• A. Obfuscation
• B. Public repository
• C. Implement a multi-factor authentication process
• D. Data exfiltration monitoring

Answer: (C)

Focusing on strong identity verification across cloud access is essential when IP is hosted publicly. Multi-factor authentication adds a second verification step beyond passwords, such as a code from an authenticator app or a hardware security key. This prevents unauthorized access even if credentials are compromised, which is a common attack vector in cloud environments. With development assets like source code, build artifacts, and configurations stored in cloud services, keeping access tightly controlled is critical to protecting IP. MFA reduces the risk of breach at the entry point and supports a broader security posture that includes principle of least privilege and regular credential rotation. Obfuscation is not reliable because determined attackers can often reverse engineer or deobfuscate code, and it does not stop unauthorized access to cloud accounts or repositories. A public repository would expose IP directly, making protection impractical. Data exfiltration monitoring helps detect and respond to leaks after they occur but does not prevent access in the first place, nor stop exfiltration in real time in many cases. MFA directly reduces the chance of unauthorized access, addressing the primary risk to IP in a public cloud development setup.

Focusing on strong identity verification across cloud access is essential when IP is hosted publicly. Multi-factor authentication adds a second verification step beyond passwords, such as a code from an authenticator app or a hardware security key. This prevents unauthorized access even if credentials are compromised, which is a common attack vector in cloud environments. With development assets like source code, build artifacts, and configurations stored in cloud services, keeping access tightly controlled is critical to protecting IP. MFA reduces the risk of breach at the entry point and supports a broader security posture that includes principle of least privilege and regular credential rotation.

Obfuscation is not reliable because determined attackers can often reverse engineer or deobfuscate code, and it does not stop unauthorized access to cloud accounts or repositories. A public repository would expose IP directly, making protection impractical. Data exfiltration monitoring helps detect and respond to leaks after they occur but does not prevent access in the first place, nor stop exfiltration in real time in many cases. MFA directly reduces the chance of unauthorized access, addressing the primary risk to IP in a public cloud development setup.