Access control management Sample Clauses

Access control management. One of the requirements identified in the previous analysis is the need to provide a control mechanism for access to the data handled and shared along the threat intelligence process. Sensitivity of data in threat intelligence may differ depending on the nature or type of event, its severity, or the additional attributes and information provided. In order to control how widely the information is allowed to be shared, it’s therefore highly recommendable to include as part of the model an indicator of the level of sensitivity of the information. To achieve this, the Traffic Light Protocol [TLP] will be used, which is popular among the intelligence community. This protocol (Figure 11) provides a simple and intuitive schema for indicating when and how sensitive information can be shared, facilitating more frequent and effective collaboration. In the event model, as presented in the previous section, the field “Tag” will contain the value of the TLP desired by the creator of the event.
AutoNDA by SimpleDocs

Related to Access control management

  • Access Control Supplier will maintain an appropriate access control policy that is designed to restrict access to Accenture Data and Supplier assets to authorized Personnel. Supplier will require that all accounts have complex passwords that contain letters, numbers, and special characters, be changed at least every 90 days, and have a minimum length of 8 characters.

  • Network Access Control The VISION Web Site and the Distribution Support Services Web Site (the “DST Web Sites”) are protected through multiple levels of network controls. The first defense is a border router which exists at the boundary between the DST Web Sites and the Internet Service Provider. The border router provides basic protections including anti-spoofing controls. Next is a highly available pair of stateful firewalls that allow only HTTPS traffic destined to the DST Web Sites. The third network control is a highly available pair of load balancers that terminate the HTTPS connections and then forward the traffic on to one of several available web servers. In addition, a second highly available pair of stateful firewalls enforce network controls between the web servers and any back-end application servers. No Internet traffic is allowed directly to the back-end application servers. The DST Web Sites equipment is located and administered at DST’s Winchester data center. Changes to the systems residing on this computer are submitted through the DST change control process. All services and functions within the DST Web Sites are deactivated with the exception of services and functions which support the transfer of files. All ports on the DST Web Sites are disabled, except those ports required to transfer files. All “listeners,” other than listeners required for inbound connections from the load balancers, are deactivated. Directory structures are “hidden” from the user. Services which provide directory information are also deactivated.

  • 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.

  • Virus Management DST shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within DST environment.

  • Disease Management If you have a chronic condition such as asthma, coronary heart disease, diabetes, congestive heart failure, and/or chronic obstructive pulmonary disease, we’re here to help. Our tools and information can help you manage your condition and improve your health. You may also be eligible to receive help through our care coordination program. This voluntary program is available at no additional cost you. To learn more about disease management, please call (000) 000-0000 or 0-000-000-0000. Our entire contract with you consists of this agreement and our contract with your employer. Your ID card will identify you as a member when you receive the healthcare services covered under this agreement. By presenting your ID card to receive covered healthcare services, you are agreeing to abide by the rules and obligations of this agreement. Your eligibility for benefits is determined under the provisions of this agreement. Your right to appeal and take action is described in Appeals in Section 5. This agreement describes the benefits, exclusions, conditions and limitations provided under your plan. It shall be construed under and shall be governed by the applicable laws and regulations of the State of Rhode Island and federal law as amended from time to time. It replaces any agreement previously issued to you. If this agreement changes, an amendment or new agreement will be provided.

  • SITE MANAGEMENT We reserve the right, but not the obligation, to: (1) monitor the Site for violations of these Terms of Use; (2) take appropriate legal action against anyone who, in our sole discretion, violates the law or these Terms of Use, including without limitation, reporting such user to law enforcement authorities; (3) in our sole discretion and without limitation, refuse, restrict access to, limit the availability of, or disable (to the extent technologically feasible) any of your Contributions or any portion thereof; (4) in our sole discretion and without limitation, notice, or liability, to remove from the Site or otherwise disable all files and content that are excessive in size or are in any way burdensome to our systems; and (5) otherwise manage the Site in a manner designed to protect our rights and property and to facilitate the proper functioning of the Site.

  • Change Management BellSouth provides a collaborative process for change management of the electronic interfaces through the Change Control Process (CCP). Guidelines for this process are set forth in the CCP document as amended from time to time during this Agreement. The CCP document may be accessed via the Internet at xxxx://xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx.

  • Access Controls The system providing access to PHI COUNTY discloses to 20 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY 21 must use role based access controls for all user authentications, enforcing the principle of least privilege.

  • 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:

  • PERFORMANCE MANAGEMENT SYSTEM 6.1 The Performance Plan (Annexure A) to this Agreement sets out – 6.1.1 The standards and procedures for evaluating the Employee’s performance; and 6.1.2 The intervals for the evaluation of the Employee’s performance. 6.2 Despite the establishment of agreed intervals for evaluation, the Employer may in addition review the Employee’s performance at any stage while the contract of employment remains in force; 6.3 Personal growth and development needs identified during any performance review discussion must be documented in a Personal Development Plan as well as the actions agreed to and implementation must take place within set time frames; 6.4 The Employee’s performance will be measured in terms of contributions to the goals and strategies set out in the Employer’s Integrated Development Plan (IDP) as described in 6.6 – 6.12 below; 6.5 The Employee will submit quarterly performance reports (SDBIP) and a comprehensive annual performance report at least one week prior to the performance assessment meetings to the Evaluation Panel Chairperson for distribution to the panel members for preparation purposes; 6.6 Assessment of the achievement of results as outlined in the performance plan: 6.6.1 Each KPI or group of KPIs shall be assessed according to the extent to which the specified standards or performance targets have been met and with due regard to ad-hoc tasks that had to be performed under the KPI, and the score of the employer will be given to and explained to the Employee during the assessment interview. 6.6.2 A rating on the five-point scale shall be provided for each KPI or group of KPIs which will then be multiplied by the weighting to calculate the final score; 6.6.3 The Employee will submit his self-evaluation to the Employer prior to the formal assessment; 6.6.4 In the instance where the employee could not perform due to reasons outside the control of the employer and employee, the KPI will not be considered during the evaluation. The employee should provide sufficient evidence in such instances; and 6.6.5 An overall score will be calculated based on the total of the individual scores calculated above.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!