Technical and logical security Sample Clauses

Technical and logical security. 3.1 The Data Processor has implemented the following technical and logic security measures:
AutoNDA by SimpleDocs

Related to Technical and logical security

  • Physical and Environmental Security DST shall: (i) restrict entry to DST’s area(s) where Fund Confidential Information is stored, accessed, or processed solely to DST’s personnel or DST authorized third party service providers for such access; and (ii) implement commercially reasonable practices for infrastructure systems, including fire extinguishing, cooling, and power, emergency systems and employee safety.

  • Personnel Security 6.1 Staff recruitment in accordance with government requirements for pre- employment checks;

  • Technical Security Controls 35 a. Workstation/Laptop encryption. All workstations and laptops that store PHI COUNTY 36 discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of 37 COUNTY either directly or temporarily must be encrypted using a FIPS 140-2 certified algorithm which 1 is 128bit or higher, such as AES. The encryption solution must be full disk unless approved by the 2 COUNTY.

  • Technical Services Party B will provide technical services and training to Party A, taking advantage of Party B’s advanced network, website and multimedia technologies to improve Party A’s system integration. Such technical services shall include:

  • Physical Security Contractor shall ensure that Medi-Cal PII is used and stored in an area that is physically safe from access by unauthorized persons during working hours and non- working hours. Contractor agrees to safeguard Medi-Cal PII from loss, theft or inadvertent disclosure and, therefore, agrees to:

  • Technical Safeguards 1. USAC and the Department will process the data matched and any data created by the match under the immediate supervision and control of authorized personnel to protect the confidentiality of the data, so unauthorized persons cannot retrieve any data by computer, remote terminal, or other means.

  • Password Security You are responsible for maintaining adequate security and control of any and all User IDs, Passwords, hints, personal identification numbers (PINs), or any other codes that you use to access the Account. Do not discuss, compare, or share information about your account number or password unless you are willing to give them full use of your money. Any loss or compromise of the foregoing information and/or your personal information may result in unauthorized access to your Account by third-parties and the loss or theft of any funds held in your Account and any associated accounts, including your Account. Checks and electronic withdrawals are processed by automated methods, and anyone who obtains your account number or access device could use it to withdraw money from your account, with or without your permission. You are responsible for keeping your email address and telephone number up to date in order to receive any notices or alerts that we may send you. We assume no responsibility for any loss that you may sustain due to compromise of your account login credentials due to no fault of ours and/or your failure to follow or act on any notices or alerts that we may send to you. If you believe your Account information has been compromised, or that someone has transferred or may transfer money from your account without your permission, contact us immediately, through Synapse, at xxxx@xxxxxxxxx.xxx or call at +0(000) 000-0000. You agree to promptly review all Account and transaction records and other Communications that we make available to you and to promptly report any discrepancy to us.

  • Physical Security of Media Transfer Agent shall implement controls, consistent with applicable prevailing industry practices and standards, that are designed to deter the unauthorized viewing, copying, alteration or removal of any media containing Fund Data. Removable media on which Fund Data is stored by Transfer Agent (including thumb drives, CDs, and DVDs, and PDAS) will be encrypted based on Transfer Agent encryption policies.

  • Project Manager, County The County shall appoint a Project Manager to act as liaison between the County and the Subrecipient during the term of this Contract. The County’s Project Manager shall coordinate the activities of the County staff assigned to work with the Subrecipient. The County’s Project Manager, in consultation and agreement with the County, shall have the right to require the removal and replacement of the Subrecipient’s Project Manager and key personnel. The County’s Project Manager shall notify the Subrecipient in writing of such action. The Subrecipient shall accomplish the removal within three (3) business days after written notice from the County’s Project Manager. The County is not required to provide any additional information, reason or rationale in the event it requires the removal of Subrecipient’s Project Manager from providing further services under the Contract.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

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