ACCOUNT MONITORING / ATYPICAL USAGE, ACCOUNT MANAGEMENT |
Organizations can describe the specific conditions or circumstances under which information system accounts can be used, for example, by restricting usage to certain days of the week, time of day, or specific durations of time. INACTIVITY LOGOUT, ACCOUNT MANAGEMENT |
DISABLE ACCOUNTS FOR HIGH-RISK INDIVIDUALS.
Before joining FedTech, Elizabeth was a reporter for Gannett, covering health care policy and medicine. The purpose of the publication is to recommend security practices for designing, implementing, and operating email systems on public and private networks. CM-11
They share a local login account and then use a 2fa token to login. NIST Creates New Guidelines for Managing Privileged Accounts .
PCI DSS Requirements 8.1 and 8.5 refer to using unique accounts and not using shared accounts.
The Federal Computer Security Managers Forum is an informal group sponsored by the National Institute of Standards and Technology (NIST) to promote the sharing of system security information among US federal agencies. potential assessment methods and objects: Examine: [select from: Access control policy; procedures addressing account management; information system design documentation; information system configuration settings and associated documentation; system-generated list of shared/group accounts and associated role; information system audit records; other relevant documents or records].
Elizabeth Neus. ,
If you can limit those accounts to a privileged access workstation (PAW), you can put an individual user account in between the shared accounts. USA | Healthcare.gov
Hosted by ABCI
DYNAMIC PRIVILEGE MANAGEMENT, ACCOUNT MANAGEMENT |
NIST SP 800-53 also has sections on identification and use of shared accounts. | Science.gov
Reviews accounts for compliance with account management requirements [Assignment: organization-defined frequency]; and.
This is a potential security issue, you are being redirected to https://nvd.nist.gov, Security and Privacy Controls for Federal Information Systems and Organizations, Revision 4 Statements
Disclaimer | Scientific
This document was developed in furtherance of NIST's statutory responsibilities under the Federal Information Security Management Act (FISMA) of 2002, Public Law 107-347.
Harm includes potential adverse impacts to organizational operations and assets, individuals, other organizations, or the Nation.
This document was developed in furtherance of NIST's statutory responsibilities under the Federal Information Security Management Act (FISMA) of 2002, Public Law 107-347. 800-12, 800-30, 800-39, 800-100; NIST Interagency Report 7874. This type of privilege management includes, for example, automatic adjustments of privileges if users are operating out of their normal work times, or if information systems are under duress or in emergency maintenance situations. MA-5
Close coordination between authorizing officials, information system administrators, and human resource managers is essential in order for timely execution of this control enhancement.