User Community. The external stakeholders of AIS may include Federal Departments and Agencies, foreign CERTs, and private sector companies. In order to participate in AIS, private sector and foreign CERTs must sign a Terms of Use agreement. Federal Departments and Agencies must sign the Enhance Shared Situational Awareness (ESSA) Multi-lateral Information Sharing Agreement (MISA).
User Community. Users who are authorized by Members and IHS may use this interconnection . . .
User Community. Both parties shall: Ensure that all employees, contractors, and other authorized users with access to the CMS Network and the Non-CMS Organization as well as the data sent and received from either organization are not security risks and meet the personnel security / suitability requirements of the CMS Business Partners System Security Manual (2018)10 as a guide, which is specifically incorporated herein. The Non-CMS Organization shall: Enforce the following IS best practices: – Least Privilege – Only authorizing access to the minimal amount of resources required for a function; – Separation of Duties – A security method that manages conflict of interest, the appearance of conflict of interest, and fraud. It restricts the amount of power held by any one individual; and – Role-Based Security – Access controls to perform certain operations (“permissions”) are assigned to specific roles. 10 Located at: xxxx://xxx.xxx.xxx/Regulations-and- Guidance/Guidance/Manuals/downloads/117_systems_security.pdf.
User Community. The minimum requirements for employees to work in support of this interconnection, to include background investigations and security clearances, will be governed by the contract(s) governing the support services provided by the vendor. [Organization 2] will be responsible for ensuring that their employees meet the standards set forth in all applicable contracts and for continuously monitoring and tracking the status of all [Organization 2] employees relevant to this interconnection. [Define the community of users who will access, exchange, and/or receive data across the interconnection as described in section 2.1] Information Exchange Security
User Community. EGS and <<VENDOR SYSTEM>> shall provide and maintain security mechanisms adequate for preventing unauthorized access to proposal or award records and proposal reviews. Both parties are responsible for determining authorized users as they see fit through the management of their system logins and associated roles. Both parties are encouraged to regularly review the user logins for their organization to ensure appropriate authorization.
User Community. A User Community comprises a set of users who support a specific mission. User Communities vary in size from dozens to millions of individual users. An individual user is a person or automated device that has access to a computer or router which can support IP packet flows. User terminals are typically connected to local area networks (LAN) that exist within one of the User Community’s edge networks. The LAN typically has access to one or more communications lines that are part of a wide area network (WAN). In some cases an edge network might support hundreds of user ter- minals, in other cases an edge network might contain only one user terminal. User Communities support a wide range of missions. Some are tactical and involve mobile vehicles. Others are strategic and are based on fixed enclaves. Some use combinations of satellite, wireless and ter- restrial links. Different missions support different applications. Some applications are based on TCP which can support reliable communications by automatically retransmitting lost packets. Other applica- tions are based on real time UDP packet streams that require small packet delay and jitter. The designation of what comprises a User Community shall be left to the various agencies that will connect to the GIG. The connections shall be made at locations agreed upon between the User Commu- nity and the GIG NSPs. The connection between a User Community and a Network Service Domain is called the “user edge”.
User Community. The user communities (the trainees) are defined above (6.1).
User Community. The purpose of this interconnection agreement is to share environmental data between the COSMIC-PGD and INPE-COSMIC-PGD. All COSMIC-PGD personnel undergo background checks as part of the hiring process. Background checks for COSMIC-PGD personnel are conducted by UCAR. All COSMIC-PGD and INPE-COSMIC-PGD personnel are required to take and pass Information Technology (IT) Security Awareness Training. The COSMIC-PGD users are required to acknowledge the UCAR Rules of Behavior (RoB) prior to being granted access to the COSMIC-PGD system, and as a part of the annual UCAR IT security awareness training. All INPE-COSMIC-PGD users are required to take introductory lectures on the awareness of the use of computational resources, and sign a safety standards awareness document, in order to comply with INPE´s General Director Resolution (RE-DIR) 518 - Normative document for the acceptable use of computational resources.
User Community. All Department of Housing and Urban Development users with access to the data received from Organization B are U.S. citizens or with an authorized work permit with a valid and current background clearance from Department of Housing and Urban Development. All Organization B users with access to the data received from Department of Housing and Urban Development are U.S. citizens or with an authorized work permit with a valid and current background clearance from Organization B.
User Community. All CBP employees with access to the data are U. S. citizens with a valid and current CBP Background Investigation.
