Access Management. The Engineer shall coordinate and evaluate access management within the project limits in accordance with the latest State Access Management Manual or as directed by the State.
Access Management a. Where Flexera personnel are accessing Customer systems or data, Flexera is responsible for validating the identity of such personnel.
b. Flexera will ensure that when accessing Customer systems or data, Flexera personnel have the minimal required system access to carry out their duties and will not use shared accounts or password.
c. Flexera will ensure that access to the Customer systems or data is governed by this Schedule.
Access Management. Access to the SaaS Service from HTL is by Hornbill Personnel and Sub-processors is secured, managed and protected through stringent authentication, segregation and authorisation processes and mechanisms, overseen by the HTL ISMS manager. A formal registration and deregistration process is adhered to and privileges are allocated on a need-to-use and event-by-event basis. A log is maintained of all privileges authorised and allocated and this is audited regularly to ensure privileges; (i) have been revoked as specified in the original request, (ii) continue to be valid and appropriate for the intended purpose, (iii) have not been obtained without the appropriate authorisation. User access rights are reviewed upon change to maintain effective control over access to data information services.
Access Management. Where applicable, the appointed Consulting Engineer shall ensure the adequate management of access as per the provisions of TRH 26: South African Road Classification and Access Management Manual and in consultation with the Client.
1. Normal Fee Services
Access Management. (a) Use multi-factor authentication to control access to root account credentials and not use root account credentials beyond initial account configuration, except in using Services for which AWS Identity and Access Management (IAM) is not available.
(b) Require each user to have unique security credentials that are rotated at least quarterly.
(c) Use multifactor authentication or federated credentials for all authentications and grant users and groups only the minimum privileges necessary.
(d) Restrict permissions in Security Groups and Access Control Lists to only those users required for Customer’s use of the Services.
(e) Restrict permitted source and destination authorizations to only those required for Customer’s use of the Services.
(f) Apply resource-based policies to limit access to Services only to authorized parties.
Access Management. County will provide Public Body with access to the Licensed Products through County’s Service Center.
Access Management a. Where Revenera personnel are accessing Customer systems or data, Revenera is responsible for validating the identity of such personnel.
b. Revenera will ensure that when accessing Customer systems or data, Revenera personnel have the minimal required system access to carry out their duties and will not use shared accounts or password.
c. Revenera will ensure that access to the Customer systems or data is governed by this Schedule.
Access Management. Application/system must control access to and within the system at multiple levels (e.g. per user, per user role, per area, per section of the chart) through a consistent mechanism of identification and authentication of all users in accordance with the ‘Role Based Access Control’ (RBAC) standard. Application/system must support measures to define, attach, modify and remove access rights for all classes of users. Application/system must support measures to enable and restrict access to the whole and/or sections of the technology solution in accordance with prevailing consent and access rules. Application must have the ability to create unique user accounts. Application must support session timeouts or automatic logoff after 60 minutes of inactivity.
Access Management. Airship employs a centralized access management system to control personnel access to production servers for the Service to a limited number of authorized personnel. Central network-based authentication systems are designed to provide Airship with secure and flexible access mechanisms. These mechanisms are designed to grant only approved access rights to site hosts, logs, data and configuration information for the Service. Airship requires the use of unique user IDs, strong passwords, two factor authentication and access lists for Airship personnel to access the Service. Airship personnel are granted access rights to the Service based on: (i) the authorized personnel’s job responsibilities; (ii) job duty requirements necessary to perform authorized tasks based on least privilege; and (iii) a need to know basis. The granting or modification of access rights must be performed in accordance with Airship’s internal data access policies and training. Approvals are managed by workflow tools that maintain audit records of all changes. Log-ins to the Service are logged into the Security Information and Event Management system (SIEM).
Access Management. The ENGINEER shall perform Access Management to develop feasible engineering solutions that improve mobility and safety through the traffic flow enhancement, delay reduction, and crash reduction. Associated activities include but not limited to data collection to determine existing conditions, data analysis, and identification of short-, medium-, and long-term improvements to improve mobility, reduce crashes, and support existing and future development. Proposed solutions may include but are not limited to managing access to development (e.g., increasing driveway spacing, providing channelized medians), traffic operations by providing or retiming traffic signals, and modifying intersection geometries by adding or extending left/right turn dedicated lanes and bays where required. DocuSign Envelope ID: 72A77E6D-1011-4A73-AFB3-C43B2D5483E3 ▪ The ENGINEER shall develop, propose, and apply access management and improvement strategies.
