Ubuntu wireless validating authentication ranches osi updating classic america
Users (and any processes acting on behalf of users) need to be uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization, which outlines specific user actions that can be performed on the Ubuntu operating system without identification or authentication.
-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.
This requirement addresses concurrent sessions for information system accounts and does not address concurrent sessions by single users via multiple system accounts.
The maximum number of concurrent sessions should be defined based upon mission needs and the operational environment for each system.
Regardless of where the session lock is determined and implemented, once invoked, the session lock shall remain in place until the user re-authenticates.
No other activity aside from re-authentication shall unlock the system.