91. A cryptographic algorithm may need replacement in the future. What would make that change manageable?
HardApplication & data security
Case
Show model answer
Maintain an inventory of cryptographic uses, protocols, data lifetimes, key ownership and external dependencies. Identify where algorithms or formats are embedded so a change does not require discovering hidden assumptions during an emergency.
Use supported maintainable implementations and plan compatible migration, testing and rollback appropriate to the data and protocol. Replacing an algorithm name is insufficient if peers, stored records or key-management procedures cannot support the new arrangement.
What interviewers listen for
- Inventory uses and dependencies
- Plan protocol and stored-data migration
- Test compatible rollout and recovery