Library staff leave authenticated sessions open on shared public-service PCs between patrons. What session-management control should be required for sensitive apps?
Select an answer to reveal the explanation.
Short Explanation
An open staff login on a shared library PC is a baton anyone can grab. Time out idle and long sessions and make sensitive apps ask again who is at the keyboard. No locks, forever admin cookies, or “patrons will log out later” hand the session to the next stranger.
Full Explanation
Session management is part of authentication strategy: idle and maximum lifetimes plus re-authentication limit the window of hijacked or abandoned sessions, especially on shared terminals. Disabling locks and permanently caching privileged cookies extend unauthorized use risk. Allowing patrons to inherit staff sessions collapses identity assurance. Libraries and other civic shared-PC environments need stricter session controls than dedicated single-user desktops.