Privilege Management Sample Clauses

Privilege Management. Supplier shall restrict and control the allocation and use of privileges to information systems and services through a formal authorization process. Privileges shall be allocated to users on a need-to-use basis and on least privileges in line with the access control policy.
AutoNDA by SimpleDocs
Privilege Management. Airship personnel with access to the Airship customer account or technical management systems are required to authenticate themselves via logical access controls with multi-factor authentication in order to administer the Service. Any access to customer data by an Airship representative is logged and tracked in real time, with oversight from the security team. In addition, Airship has implemented these additional privilege management measures:
Privilege Management. Subscriber’s administrators must authenticate themselves via a central authentication system or via a single sign on system in order to administer the Services.
Privilege Management. Customer’s administrators and Customer End Users must authenticate themselves via a central authentication system or via a single sign on system in order to use the Services.
Privilege Management. Customer’s Administrators and End Users must authenticate themselves via a central authentication system or via a single sign on system in order to use the Services. Internal Data Access Processes and Policies – Access Policy. Google’s internal data access processes and policies are designed to prevent unauthorized persons and/or systems from gaining access to systems used to process Customer Data. Google designs its systems to (i) only allow authorized persons to access data they are authorized to access; and (ii) ensure that Customer Data cannot be read, copied, altered or removed without authorization during processing, use and after recording. The systems are designed to detect any inappropriate access. Google employs a centralized access management system to control personnel access to production servers, and only provides access to a limited number of authorized personnel. Google’s
Privilege Management. 4.3.3.1.1. The computer and communications system privileges of all users, systems, and programs must be restricted based on the need to know. 4.3.3.1.2. System administrators managing multi-user computer systems must have at least two user IDs, one that provides privileged access, and the other to perform her or his normal day-to-day work. 4.3.3.1.3. Current records reflecting all the system privileges the users have on all the computer systems must be maintained. 4.3.3.1.4. The system privileges granted to every user must be reevaluated by the user’s immediate manager every year to determine whether currently-enabled system privileges are needed to perform the user’s current job duties. 4.3.3.1.5. The number of privileged user IDs must be strictly limited to those individuals who absolutely must have such privileges for authorized purposes. 4.3.3.1.6. Attribution of system privileges must be approved by the IS/IT management. 4.3.3.1.7. Special system privileges, such as the ability to examine the files of other users or to change the security state of the system, must be restricted to those directly responsible for system management or security, and granted only to those who have attended an approved system administrator training class.

Related to Privilege Management

  • Service Management Effective support of in-scope services is a result of maintaining consistent service levels. The following sections provide relevant details on service availability, monitoring of in-scope services and related components.

  • Care Management The Contractor’s protocol for referring members to care management shall be reviewed by OMPP and shall be based on identification through the health needs screening or when the claims history suggests need for intervention. In addition to population-based disease management educational materials and reminders, these members should receive more intensive services. Members with newly diagnosed conditions, increasing health services or emergency services utilization, evidence of pharmacy non-compliance for chronic conditions and identification of special health care needs should be strongly considered for case management. Care management services include direct consumer contacts in order to assist members with scheduling, location of specialists and specialty services, transportation needs, 24-Hour Nurse Line, general preventive (e.g. mammography) and disease specific reminders (e.g. Xxx X0X), pharmacy refill reminders, tobacco cessation and education regarding use of primary care and emergency services. The Contractor shall make every effort to contact members in care management telephonically. Materials should also be delivered through postal and electronic direct-to-consumer contacts, as well as web-based education materials inclusive of clinical practice guidelines. Materials shall be developed at the fifth grade reading level. All members with the conditions of interest shall receive materials no less than quarterly. The Contractor shall document the number of persons with conditions of interest, outbound telephone calls, telephone contacts, category of intervention, intervention delivered, mailings and website hits. Care management shall be coordinated with the Right Choices Program for members qualifying for the Right Choices Program. However, the Right Choices Program is not a replacement for care management.

  • Information Management Information and Records

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

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

  • Patch Management All workstations, laptops and other systems that process and/or 20 store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or 21 transmits on behalf of COUNTY must have critical security patches applied, with system reboot if 22 necessary. There must be a documented patch management process which determines installation 23 timeframe based on risk assessment and vendor recommendations. At a maximum, all applicable 24 patches must be installed within thirty (30) calendar or business days of vendor release. Applications 25 and systems that cannot be patched due to operational reasons must have compensatory controls 26 implemented to minimize risk, where possible.

  • Network Management 60.1 CLEC and CenturyLink will exchange appropriate information (e.g., network information, maintenance contact numbers, escalation procedures, and information required to comply with requirements of law enforcement and national security agencies) for network management purposes. In addition, the Parties will apply sound network management principles to alleviate or to prevent traffic congestion and to minimize fraud associated with third number billed calls, calling card calls, and other services related to this Agreement. 60.2 The Parties will employ characteristics and methods of operation that will not interfere with or impair the Parties’ networks, or the network of any third parties or Affiliated companies, connected with or involved directly in the network or facilities of CenturyLink. 60.3 CLEC shall not interfere with or impair service over any circuits, facilities or equipment of CenturyLink, its Affiliated companies, or its connecting and concurring carriers. 60.4 If CLEC causes any impairment or interference, CenturyLink shall promptly notify CLEC of the nature and location of the problem and that, unless promptly rectified, a temporary discontinuance of the use of any circuit, facility or equipment may be required. The Parties agree to work together to attempt to promptly resolve the impairment or interference. If CLEC is unable to promptly remedy, then CenturyLink may, at its option, temporarily discontinue the use of the affected circuit, facility or equipment until the impairment is remedied. 60.5 Any violation of Applicable Law or regulation regarding the invasion of privacy of any communications carried over CenturyLink’s facilities, or that creates hazards to the employees of CenturyLink or to the public, is also considered an impairment of service. 60.6 CenturyLink shall give advanced notice to CLEC of all non-scheduled maintenance or other planned network activities to be performed by CenturyLink on any Network Element, including any hardware, equipment, software, or system, providing service functionality of which CLEC has advised CenturyLink may potentially impact CLEC End Users. 60.7 The Parties shall provide notice of network changes and upgrades in accordance with 47 C.F.R. §§51.325 through 51.335. CenturyLink may discontinue any Interconnection arrangement, Telecommunications Service, or Network Element provided or required hereunder due to network changes or upgrades after providing CLEC notice as required by this Section. CenturyLink agrees to cooperate with CLEC and/or the appropriate regulatory body in any transition resulting from such discontinuation of service and to minimize the impact to customers which may result from such discontinuance of service.

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

  • General Management In the discharge of its general duty to manage the successful performance of the Services, Vendor shall: 3.2.1.1. within thirty (30) calendar days of the Effective Date, identify to Citizens the primary and secondary management contacts responsible for the oversight and management of Services for Citizens; 3.2.1.2. ensure Vendor Staff tasked with management and oversight of the Services are available promptly to perform Services during Business Hours; 3.2.1.3. ensure each assigned Adjuster submits a time record directly to Vendor’s manager or point of contact. At any time during this Agreement, Citizens may require copies of time records from Vendor; 3.2.1.4. ensure that no Vendor Staff carries a weapon on their person while performing Services; 3.2.1.5. ensure that no Vendor Staff uses impairing drugs, chemicals, or alcohol while performing Services; 3.2.1.6. ensure that Vendor Staff avoid using their duties and obligations under this Agreement to engage in any conduct that could create either an actual or perceived conflict of interest, such as due to an ongoing business relationship with an entity other than Citizens that would enable Vendor Staff to receive an improper benefit or unfair competitive advantage; 3.2.1.7. ensure that the Services comply with the Best Claims Practices & Estimating Guidelines as applicable to each Service Category and any other policies or processes set forth by Citizens, including but not limited to: a. monitoring applicable file production on a weekly basis to determine compliance with Citizens’ production requirements; and, b. providing detailed reports to Citizens related to Vendor performance upon request.

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

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