SIRP General Requirements Sample Clauses

SIRP General Requirements. Implementer’s SIRP will include Security Incident handling and response procedures, specific contacts in an event of a Security Incident, the contacts’ roles and responsibilities, and their plans to notify SCE or its affiliates, as the case may be, concerning the Security Incident. The SIRP must be based on and meet all requirements of the following: 16.2.2.1 U.S. federal and applicable state laws, statutes and regulations concerning the custody, care and integrity of data and information. In particular and without limitation, Implementer shall ensure that its SIRP and its business practices in performing work on behalf of SCE comply with California's Information Practices Act of 1977, California Civil Code §§ 1798.80 et seq., which addresses among other things the provision of notice to SCE or its affiliates, as the case may be, of any breach of the security of SCE Personal Information if it is reasonably believed to have been acquired by an unauthorized person. 16.2.2.2 SCE information management and information security policies and procedures as made available to Implementer from time to time (“SCE Policies and Procedures”), including without limitation ITS-445 “Standards for Information Security Response – Third Parties.”
Sample 1
AutoNDA by SimpleDocs
SIRP General Requirements. ISONAS’s SIRP will include Security Incident handling and response procedures, specific contacts in an event of a Security Incident, the contacts’ roles and responsibilities, and their plans to notify Client or its Affiliates, as the case may be, concerning the Security Incident. The SIRP must be based on and meet all requirements of the following: (i) U.S. federal and applicable state laws, statutes and regulations concerning the custody, care and integrity of data and information. ISONAS shall ensure that its SIRP and its business practices in performing work on behalf of Client comply with California's Information Practices Act of 1977, California Civil Code §§ 1798.80 et seq., which addresses the provision of notice to Client or its Affiliates, as the case may be, of any breach of the security of Client Personal and Client Proprietary Information if it is reasonably believed to have been acquired by an unauthorized person. (ii) Client information management and information security policies and procedures as made available to ISONAS upon ISONAS’s request (“Client Policies and Procedures”).
Sample 1

Related to SIRP General Requirements

  • General Requirements The Contractor hereby agrees:

  • General Requirement Any notice, election, demand, request, consent, approval, or other communication required or permitted to be given under this Contract shall be in writing signed by an officer or duly authorized representative of the party making same and shall be delivered personally or shall be sent by certified or statutory mail, postage prepaid, return receipt requested, shall be effective as of the date on which it is received or would have been received but for the refusal of the addressee to accept delivery, and shall be addressed as shown in the Contract. The persons and addresses to which notices should be given may be changed by notice given in accordance with this Article.

  • Operational Requirements 4 At-Sea Monitors are deployed, in accordance with coverage rates developed by 5 NMFS and as assigned through the Pre-Trip Notification System (PTNS), to 6 vessels. Due to availability of funding, changes in the fishery management, 7 such as emergency closures, court ordered closures, weather, and unforeseen 8 events must remain flexible. Additional funding for sea days may be added to 9 the contract within the scope and maximum allowable sea days. 10 The following items define the operational services to be provided by the 11 contractor under this contract.

  • Procedural Requirements All holders of record of shares of Preferred Stock shall be sent written notice of the Mandatory Conversion Time and the place designated for mandatory conversion of all such shares of Preferred Stock pursuant to this Section 6. Such notice need not be sent in advance of the occurrence of the Mandatory Conversion Time. Upon receipt of such notice, each holder of shares of Preferred Stock shall surrender his, her or its certificate or certificates for all such shares (or, if such holder alleges that such certificate has been lost, stolen or destroyed, a lost certificate affidavit and agreement reasonably acceptable to the Corporation to indemnify the Corporation against any claim that may be made against the Corporation on account of the alleged loss, theft or destruction of such certificate) to the Corporation at the place designated in such notice. If so required by the Corporation, certificates surrendered for conversion shall be endorsed or accompanied by written instrument or instruments of transfer, in form satisfactory to the Corporation, duly executed by the registered holder or by his, her or its attorney duly authorized in writing. All rights with respect to the Preferred Stock converted pursuant to Section 6.1, including the rights, if any, to receive notices and vote (other than as a holder of Common Stock), will terminate at the Mandatory Conversion Time (notwithstanding the failure of the holder or holders thereof to surrender the certificates at or prior to such time), except only the rights of the holders thereof, upon surrender of their certificate or certificates (or lost certificate affidavit and agreement) therefor, to receive the items provided for in the next sentence of this Subsection 6.2. As soon as practicable after the Mandatory Conversion Time and the surrender of the certificate or certificates (or lost certificate affidavit and agreement) for Preferred Stock, the Corporation shall issue and deliver to such holder, or to his, her or its nominees, a certificate or certificates for the number of full shares of Common Stock issuable on such conversion in accordance with the provisions hereof, together with cash as provided in Subsection 5.2 in lieu of any fraction of a share of Common Stock otherwise issuable upon such conversion and the payment of any declared but unpaid dividends on the shares of Preferred Stock converted. Such converted Preferred Stock shall be retired and cancelled and may not be reissued as shares of such series, and the Corporation may thereafter take such appropriate action (without the need for stockholder action) as may be necessary to reduce the authorized number of shares of Preferred Stock accordingly.

  • Additional Requirements As a condition precedent to the execution and Delivery, the registration of issuance, transfer, split-up, combination or surrender, of any ADS, the delivery of any distribution thereon, or the withdrawal of any Deposited Property, the Depositary or the Custodian may require (i) payment from the depositor of Shares or presenter of ADSs or of an ADR of a sum sufficient to reimburse it for any tax or other governmental charge and any stock transfer or registration fee with respect thereto (including any such tax or charge and fee with respect to Shares being deposited or withdrawn) and payment of any applicable fees and charges of the Depositary as provided in Section 5.9 and Exhibit B, (ii) the production of proof reasonably satisfactory to it as to the identity and genuineness of any signature or any other matter contemplated by Section 3.1, and (iii) compliance with (A) any laws or governmental regulations relating to the execution and Delivery of ADRs or ADSs or to the withdrawal of Deposited Securities and (B) such reasonable regulations as the Depositary and the Company may establish consistent with the provisions of the representative ADR, if applicable, the Deposit Agreement and applicable law.

  • Procedural and Operational Requirements By accepting and using the Financial Assistance awarded under this Agreement and for this Program Element, LPHA agrees to conduct the following activities in accordance with the indicated procedural and operational requirements: a. LPHA must operate its Communicable Disease program in accordance with the Requirements and Standards for the Control of Communicable Disease set forth in ORS Chapters 431, 432, 433 and 437 and OAR Chapter 333, Divisions 12, 17, 18, 19 and 24, as such statutes and rules may be amended from time to time. b. LPHA must use all reasonable means to investigate in a timely manner all reports of Reportable Diseases, infections, or conditions. To identify possible sources of infection and to carry out appropriate control measures, the LPHA Administrator shall investigate each report following procedures outlined in OHA’s Investigative Guidelines or other procedures approved by OHA. OHA may provide assistance in these investigations, in accordance with OAR 333-019-0000. Investigative guidelines are available at: xxxx://xxx.xxxxxx.xxx/oha/PH/DiseasesConditions/CommunicableDisease/ReportingCommuni cableDisease/ReportingGuidelines/Pages/index.aspx c. As part of its Communicable Disease control program, LPHA must, within its service area, investigate the Outbreaks of Communicable Diseases, institute appropriate Communicable Disease control measures, and submit required information in a timely manner regarding the Outbreak to OHA in Orpheus (or Opera for COVID-19 Cases and XXXXX for COVID-19 contacts) as prescribed in OHA CD Investigative Guidelines available at: d. LPHA must establish and maintain a single telephone number whereby physicians, hospitals, other health care providers, OHA and the public can report Communicable Diseases and Outbreaks to LPHA 24 hours a day, 365 days a year. LPHA may employ an answering service or 911 system, but the ten-digit number must be available to callers from outside the local emergency dispatch area, and LPHA must respond to and investigate reported Communicable Diseases and Outbreaks. e. LPHA must attend Communicable Disease 101 and Communicable Disease 303 training. f. LPHA must attend monthly Orpheus user group meetings or monthly Orpheus training webinars.

  • Special Requirements Additional terms and conditions of this Agreement, if any, which are made a part hereof are set forth in the “Special Requirements” attached hereto as Exhibit “B” and incorporated herein by this reference. In the event of a conflict between the provisions of Exhibit “B” and any other provisions of this Agreement, the provisions of Exhibit “B” shall govern.

  • Collateral Requirements All amounts deposited or invested with financial institutions in excess of any insurance limit shall be collateralized in accordance with the Public Funds Investment Act, 30 ILCS 235/. The Superintendent or designee shall keep the Board informed of collateral agreements.

  • Functional Requirements Applications must implement controls that protect against known vulnerabilities and threats, including Open Web Application Security Project (OWASP) Top 10 Risks and denial of service (DDOS) attacks.

  • Financial Requirements A report of monthly and cumulative financial requirements; and

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