A developer has just completed the configuration of an API that connects sensitive internal systems. Based on company policies, the security of the data is a high priority.
Which approach must be taken to secure API keys and passwords?
I'm pretty sure the answer is 'D' - change them periodically. Anything else is just asking for a data breach, and I don't know about you, but I prefer keeping my job.
Storing them in the source tree? Are they trying to make it easier for hackers? That's like leaving your front door wide open and wondering why someone walked in.
Hidden files? Really? That's like hiding your house key under the doormat. Anyone with a bit of know-how can find it. Not the best option for securing API keys and passwords.
Seriously? Embedding sensitive data directly in the code? That's just asking for trouble! Definitely not the way to go, no matter how tempting it might be.
Carmela
15 days agoFrancine
3 days agoMalinda
19 days agoAmira
3 days agoJose
25 days agoLanie
11 days agoRocco
1 months agoSkye
1 months agoRana
10 days agoEdna
12 days agoCassi
15 days agoElke
1 months agoMy
2 days agoTamekia
17 days agoCherelle
20 days agoLelia
2 months agoLaurel
2 months ago