Limitations of Privilege & Authorization Requirements Product access Sample Clauses

Limitations of Privilege & Authorization Requirements Product access. A subset of our employees have access to the products and to customer data via controlled interfaces. The intent of providing access to a subset of employees is to provide effective customer support, to troubleshoot potential problems, to detect and respond to security incidents and implement data security. Access is enabled through “just in timerequests for access; all such requests are logged. Employees are granted access by role, and reviews of high- risk privilege grants are initiated daily. Employee roles are reviewed at least once every six months.
AutoNDA by SimpleDocs

Related to Limitations of Privilege & Authorization Requirements Product access

  • Application Requirements This application shall contain, as a minimum, a sketch showing the location of proposed facilities; a description, sketch, manufacturer’s brochure, etc. of the proposed facilities; and a description of the operation proposed. (11-28-90) 101. -- 199. (RESERVED)‌ 200. OPERATIONAL AGREEMENT.‌‌

  • Documentation Requirements (a) An employee must apply for personal leave in writing in the form required by the CEO as soon as it is reasonably practicable for the employee to make the application.

  • Specific Order Processes and Requirements 1. Distributor will order Software from SAP using and filling out completely such forms and minimum order requirements as SAP may prescribe from time to time and must comply with any then-current order process for the specific Software product. Where applicable, Distributor agrees to use the electronic means provided by SAP for placing orders.

  • Compliance with Non-Discrimination Requirements During the performance of this Agreement, Company, for itself, its assignees, successors in interest, subcontractors and consultants agrees as follows:

  • Data Submission Requirements As part of its registration and sponsorship of Registered Names in the Registry TLD, Registrar shall submit to the Registry System complete data as required by technical specifications of the Registry System that are made available to Registrar from time to time. Registrar hereby grants Registry Operator a non-exclusive, royalty free, non-transferable, limited license to such data for propagation of and the provision of authorized access to the TLD zone files and as otherwise required for Registry Operator to meet its obligations to ICANN and/or for Registry Operator’s operation of the Registry TLD.

  • Information Requirements (a) The Company covenants that, if at any time before the end of the Effectiveness Period the Company is not subject to the reporting requirements of the Exchange Act, it will cooperate with any Holder of Registrable Securities and take such further reasonable action as any Holder of Registrable Securities may reasonably request in writing (including, without limitation, making such reasonable representations as any such Holder may reasonably request), all to the extent required from time to time to enable such Holder to sell Registrable Securities without registration under the Securities Act within the limitation of the exemptions provided by Rule 144 and Rule 144A under the Securities Act and customarily taken in connection with sales pursuant to such exemptions. Upon the written request of any Holder of Registrable Securities, the Company shall deliver to such Holder a written statement as to whether it has complied with such filing requirements, unless such a statement has been included in the Company's most recent report filed pursuant to Section 13 or Section 15(d) of Exchange Act. Notwithstanding the foregoing, nothing in this Section 7 shall be deemed to require the Company to register any of its securities (other than the Common Stock) under any section of the Exchange Act.

  • Compliance with Privacy Code The parties acknowledge that the Warrant Agent may, in the course of providing services hereunder, collect or receive financial and other personal information about such parties and/or their representatives, as individuals, or about other individuals related to the subject matter hereof, and use such information for the following purposes:

  • Compliance with Nondiscrimination Requirements During the performance of this contract, the Contractor, for itself, its assignees, and successors in interest (hereinafter referred to as the “Contractor”), agrees as follows:

  • Contracting Information Requirements Contractor represents and warrants that it will comply with the requirements of Section 552.372(a) of the Texas Government Code. Except as provided by Section 552.374(c) of the Texas Government Code, the requirements of Subchapter J (Additional Provisions Related to Contracting Information), Chapter 552 of the Government Code, may apply to the Contract and the Contractor agrees that the Contract can be terminated if the Contractor knowingly or intentionally fails to comply with a requirement of that subchapter.

  • Notification Requirements 1. If the Family Leave is foreseeable, the employee must provide the agency/department with thirty (30) calendar days notice of his or her intent to take Family Leave.

Time is Money Join Law Insider Premium to draft better contracts faster.