Specific Security Requirements Sample Clauses

Specific Security Requirements. 1. Seller warrants that it shall comply with all applicable laws and regulations regarding data security and privacy including, but not limited to, Xxxxx-Xxxxx-Xxxxxx Act, HIPAA, and the provisions of 201 CMR 17.00 of the Code of Massachusetts Regulations for the Protection of PII.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Specific Security Requirements. Any Criminal Justice Information Services and/or Health Information Portability and Accountability Act-specific security requirements are attached in a separate addendum, if applicable.
Sample 1Sample 2
Specific Security Requirements. StarCompliance shall not use Client Data except as permitted by the Agreement. StarCompliance has established appropriate administrative, technical, and physical safeguards to protect the confidentiality of, and to prevent the unauthorized use or access to, Client Data.
Sample 1Sample 2
Specific Security Requirements. In addition to the foregoing, Seller shall implement and adhere to the following specific Raytheon security requirements, receipt of which Seller hereby acknowledges: Seller shall monitor access and security logs using commercially acceptable practices and tools for unusual activity including the following: • Excessive unauthorized/failed logon attempts, • Use of admin accounts at unusual times, • Unusual activity at any time, • Missing activity date/time ranges within the logs, • Failed backups Seller should support integration with Raytheon’s Simplified Sign-On (SSO) infrastructure, enabling Raytheon users to login to the service with their Raytheon SSO credentials. Where user authentication via Raytheon SSO is not a current capability and is performed with reusable passwords, adherence to Raytheon Password Requirements is mandatory. At a minimum: • Passwords are not easily guessed. Password complexity checking is enabled with minimum password length of eight characters. • Initial passwords are changed by the user on first use. • Passwords are changed immediately if compromise is suspected and are expired every 90 days. • Passwords are not reused for a period of one year (e.g., history is 4 where supported). • Passwords are not shared with others. • Passwords are not displayed, stored, or transmitted in plain text or readable form. • Passwords are disabled after the fifth failed authentication attempt in succession. • Additions and changes to access levels of users must be approved by appropriate Raytheon management. • Accounts to be disabled will be communicated by Raytheon and must be enacted by supplier in a timely manner. • Automated authentication Processes such as logon scripts, are protected from unauthorized access and do not contain unencrypted passwords. • Support procedures for remotely “resetting” a forgotten, lost or compromised means of user identity authentication must at a minimum:
Sample 1Sample 2
Specific Security Requirements. The Contractor shall not use SBA Data except as permitted by the Agreement. The Contractor has established appropriate administrative, technical, and physical safeguards to protect the confidentiality of, and to prevent the unauthorized use or access to, SBA Data.
Sample 1
Specific Security Requirements. The parties shall not use or further disclose the data specified in this Contract except as permitted by this Contract or as required by federal law, including the Health Information Portability and Accountability Act (HIPAA) and the Health Information Technology Economic and Clinical Health (HITECH) Act, their associated regulations, 45 CFR §§ 160, 162 and 164, and applicable Florida law. Disclosure to the Office is expressly permitted under federal law for complying with state law, and Florida and the Office is an “authorized public official” rather than a "covered entity" under federal law. See 45 C.F.R. §§ 164.512 and .514. The parties have established appropriate administrative, technical, and physical safeguards to protect the confidentiality and to prevent unauthorized use or access to the data specified in this Contract. Further, the uses and disclosures shall be in accordance with applicable Florida law.
Sample 1
Specific Security Requirements 
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs

Related to Specific Security Requirements

  • Security Requirements 11.1 The Supplier shall comply, and shall procure the compliance of the Suppliers Personnel, with the Security Policy and the Security Plan and the Supplier shall ensure that the Security Plan produced by the Supplier fully complies with the Security Policy.

  • Policy Requirements All of the policies of insurance referred to in this Article XIII shall be written in form reasonably satisfactory to Landlord and any Facility Mortgagee and issued by insurance companies with a minimum policyholder rating of “A-” and a financial rating of “VII” in the most recent version of Best’s Key Rating Guide, or a minimum rating of “BBB” from Standard & Poor’s or equivalent. If Tenant obtains and maintains the general liability insurance described in Section 13.1(e) above on a “claims made” basis, Tenant shall provide continuous liability coverage for claims arising during the Term. In the event such “claims made” basis policy is canceled or not renewed for any reason whatsoever (or converted to an “occurrence” basis policy), Tenant shall either obtain (a) “tail” insurance coverage converting the policies to “occurrence” basis policies providing coverage for a period of at least three (3) years beyond the expiration of the Term, or (b) an extended reporting period of at least three (3) years beyond the expiration of the Term. Tenant shall pay all of the premiums therefor, and deliver certificates thereof to Landlord prior to their effective date (and with respect to any renewal policy, prior to the expiration of the existing policy), and in the event of the failure of Tenant either to effect such insurance in the names herein called for or to pay the premiums therefor, or to deliver such certificates thereof to Landlord, at the times required, Landlord shall be entitled, but shall have no obligation, to effect such insurance and pay the premiums therefor, in which event the cost thereof, together with interest thereon at the Overdue Rate, shall be repayable to Landlord upon demand therefor. Tenant shall obtain, to the extent available on commercially reasonable terms, the agreement of each insurer, by endorsement on the policy or policies issued by it, or by independent instrument furnished to Landlord, that it will give to Landlord thirty (30) days’ (or ten (10) days’ in the case of non-payment of premium) written notice before the policy or policies in question shall be altered, allowed to expire or cancelled. Notwithstanding any provision of this Article XIII to the contrary, Landlord acknowledges and agrees that the coverage required to be maintained by Tenant may be provided under one or more policies with various deductibles or self-insurance retentions by Tenant or its Affiliates, subject to Landlord’s approval not to be unreasonably withheld. Upon written request by Xxxxxxxx, Tenant shall provide Landlord copies of the property insurance policies when issued by the insurers providing such coverage.

  • Personal Property Requirements The Collateral Agent shall have received:

  • Quality Requirements Performance Indicator Heading Indicator (specific) Threshold Method of Measurement Frequency of monitoring Consequence of Breach QUALITY Patient Safety - Incidents I1 Number of incidents Adverse incidents include the following: clinical or non clinical adverse events that have potential to cause avoidable harm to a patient, including medical errors or adverse events related to medical devices or other equipment. Clinical or non- clinical accidents, accidental injuries to staff and members of the public, verbal, physical or psychological abuse or harassment, unusual or dangerous occurrences, damage to trust property, plant or equipment, fire or flood, security, theft or loss, near misses are identified as any event where under different circumstances significant injury or loss may have occurred Number of recorded incidents in the contract month Monthly Remedial Action Plan brought to Performance Meeting following breach; action under Module C Clause 32 if needed I2 Number of Sis Definition of SUI according to trust policy and national guidance Number of Serious Untoward Incidents reported in contract month Monthly Remedial Action Plan brought to Performance Meeting following breach; action under Module C Clause 32 if needed S1 Percentage of eligible staff received child safeguarding training at level 2 (as identified in LSCB training strategy) 95% Number received training/ Number of identified staff requiring training Monthly S2 Percentage of eligible staff received adult safeguarding awareness training at level 2 ( as identified in K&M Safeguarding Vulnerable Adults training strategy) 95% Number of staff trained/ Number of identified staff requiring training Monthly

  • Authority Requirements During the Compliance Period, the following provisions shall apply.

  • Delivery Requirements Contractor must ensure that delivery of goods and/or services will be made as required by this Master Contract, the Purchase Order used by Purchasers, or as otherwise mutually agreed in writing between the Purchaser and Contractor. The following apply to all deliveries:

  • Business Day Requirements In the event that any notice or other action or omission is required to be taken by a Party under this Agreement on a day that is not a Business Day then such notice or other action or omission shall be deemed to be required to be taken on the next occurring Business Day.

  • Securities Law Requirements If at any time the Board or Committee determines that issuing Stock pursuant to this Agreement would violate applicable securities laws, the Corporation will not be required to issue such Stock. The Board or Committee may declare any provision of this Agreement or action of its own null and void, if it determines the provision or action fails to comply with applicable securities laws. The Corporation may require Participant to make written representations it deems necessary or desirable to comply with applicable securities laws.

  • Securities Laws Requirements The Company shall not be obligated to transfer any Common Stock to the Participant free of the restrictive legend described in Section 4 hereof or of any other restrictive legend, if such transfer, in the opinion of counsel for the Company, would violate the Securities Act of 1933, as amended (the "Securities Act") (or any other federal or state statutes having similar requirements as may be in effect at that time).

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