TRADE ALLY’S PASSWORD MANAGEMENT Sample Clauses

The TRADE ALLY’S PASSWORD MANAGEMENT clause establishes requirements and responsibilities for how a trade ally must handle and protect passwords related to their access to certain systems or data. Typically, this clause mandates that the trade ally use strong, unique passwords, update them regularly, and keep them confidential to prevent unauthorized access. By setting these standards, the clause helps safeguard sensitive information and reduces the risk of security breaches caused by poor password practices.
TRADE ALLY’S PASSWORD MANAGEMENT. 9.1 The Trade Ally will ensure that the Trade Ally’s Electronic Information Assets which access, process, store, or transmit Electronic Confidential Information employ strong password complexity rules. 9.2 The Trade Ally will require all its personnel to comply with the Trade Ally’s password requirements. 9.3 Passwords will be at least eight (8) characters long and composed of lower and upper-case letters, numbers and special characters (where special characters are technically feasible). 9.4 The Trade Ally will ensure automatic logoff or locking is implemented and enforced, requiring all users to re-input their password to regain access if they have been inactive for a pre-determined period of time, which, as a minimum, should be no longer than 15 minutes of inactivity.
View SourceView Similar (6)

Related to TRADE ALLY’S PASSWORD MANAGEMENT

  • Workload Management 11.1 The parties to this Agreement acknowledge that Employees and management have a responsibility to maintain a balanced workload and recognise the adverse effects that excessive workloads may have on Employee/s and the quality of resident/client care. 11.2 To ensure that Employee concerns involving excessive workloads are effectively dealt with by Management the following procedures should be applied: (a) Step 1: In the first instance, Employee/s should discuss the issue with their immediate supervisor and, where appropriate, explore solutions. (b) Step 2: If a solution cannot be identified and implemented, the matter should be referred to an appropriate senior manager for further discussion. (c) Step 3: If a solution still cannot be identified and implemented, the matter should be referred to the Facility Manager for further discussion. (d) Step 4: The outcome of the discussions at each level and any proposed solutions should be recorded in writing and fed back to the effected Employees. 11.3 Workload management must be an agenda item at staff meetings on at least a quarterly basis. Items in relation to workloads must be recorded in the minutes of the staff meeting, as well as actions to be taken to resolve the workloads issue/s. Resolution of workload issues should be based on the following criteria including but not limited to: (a) Clinical assessment of residents’ needs; (b) The demand of the environment such as facility layout; (c) Statutory obligation, (including, but not limited to, work health and safety legislation); (d) The requirements of nurse regulatory legislation; (e) Reasonable workloads (such as roster arrangements); (f) Accreditation standards; and (g) Budgetary considerations. 11.4 If the issue is still unresolved, the Employee/s may advance the matter through clause 9 Dispute Resolution Procedure. Arbitration of workload management issues may only occur by agreement of the Employer and the Employee representative, which may include the union/s.

  • Traffic Management 9.2.1 During the Operating Period, Developer shall be responsible for the general management of traffic on the Project. Developer shall manage traffic so as to preserve and protect safety of traffic on the Project and Related Transportation Facilities and, to the maximum extent practicable, to avoid disruption, interruption or other adverse effects on traffic flow, throughput or level of service on the Project and Related Transportation Facilities. Developer shall conduct traffic management in accordance with all applicable Technical Provisions, Technical Documents, Laws and Governmental Approvals, and in accordance with the Traffic Management Plan. 9.2.2 Developer shall prepare and submit to TxDOT and the Independent Engineer for TxDOT approval a Traffic Management Plan for managing traffic on the Project and Related Transportation Facilities after the commencement of traffic operations on any portion of the Project, addressing (a) orderly and safe movement and diversion of traffic on Related Transportation Facilities during Project construction, (b) orderly and safe movement of traffic on the Project and (c) orderly and safe diversion of traffic on the Project and Related Transportation Facilities necessary in connection with field maintenance and repair work or Renewal Work or in response to Incidents, Emergencies and lane closures. Developer shall prepare the Traffic Management Plan according to the schedule set forth in the Technical Provisions. The Traffic Management Plan shall comply with the Technical Provisions and Technical Documents concerning traffic management and traffic operations. Developer shall carry out all traffic management during the Term in accordance with the approved Traffic Management Plan. 9.2.3 Developer shall implement the Traffic Management Plan to promote safe and efficient operation of the Project and Related Transportation Facilities at all times during the course of any construction or operation of the Project and during the Utility Adjustment Work. 9.2.4 TxDOT shall have at all times, without obligation or liability to Developer, the right 9.2.4.1 Issue Directive Letters to Developer regarding traffic management 9.2.4.2 Provide on the Project, via message signs or other means consistent with Good Industry Practice, non-Discriminatory traveler and driver information, and other public information (e.g. amber alerts), provided that the means to disseminate such information does not materially interfere with the functioning of the ETCS.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Patch Management All workstations, laptops and other systems that process and/or store County PHI or PI must have critical security patches applied, with system reboot if necessary. There must be a documented patch management process which determines installation timeframe based on risk assessment and vendor recommendations. At a maximum, all applicable patches must be installed within 30 days of vendor release.

  • Information Management Information and Records