While reviewing a client’s older codebase, you detect a compromised library that encodes user credentials with known flaws. The client asks for a resolution to limit exposure. Which action best addresses this flaw?
Reintroduce older routines for easier upgrades to modern standards later
Expand the length of credentials and keep the existing library
Disable the encoding processes and rely on internal checks
Switch to modern cryptographic routines and retire the outdated library
Adopting a modern standard closes the root flaw in the compromised library. Simply increasing password length leaves the vulnerable component in place. Reintroducing older routines can revive known weaknesses. Disabling encoding entirely risks exposing sensitive data without robust protective measures.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What are 'modern cryptographic routines' and why are they important?
Open an interactive chat with Bash
Why doesn't expanding credential length fix the underlying vulnerability?
Open an interactive chat with Bash
What risks are involved with disabling encoding entirely?