Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.
Workstation Encryption Supplier will require hard disk encryption of at least 256-bit Advanced Encryption Standard (AES) on all workstations and/or laptops used by Personnel where such Personnel are accessing or processing Accenture Data.
Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.
Encryption The Fund acknowledges and agrees that encryption may not be available for every communication through the System, or for all data. The Fund agrees that Custodian may deactivate any encryption features at any time, without notice or liability to the Fund, for the purpose of maintaining, repairing or troubleshooting the System or the Software.
Encrypt or Encryption As defined in the Health Insurance Portability and Accountability Act of 1996 (HIPAA) Security Rule at 45 CFR 164.304, means the use of an algorithmic process to transform Personally Identifiable Information into an unusable, unreadable, or indecipherable form in which there is a low probability of assigning meaning without use of a confidential process or key.
ODUF Physical File Characteristics 6.2.1 ODUF will be distributed to TWTC via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN. If AT&T determines the Secure FTP Mailbox is nearing capacity levels, AT&T may move the customer to CONNECT: Direct file delivery. 6.2.2 If the customer is moved, CONNECT: Direct data circuits (private line or dial-up) will be required between AT&T and TWTC for the purpose of data transmission. Where a dedicated line is required, TWTC will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with AT&T. TWTC will also be responsible for any charges associated with this line. Equipment required on the AT&T end to attach the line to the mainframe computer and to transmit messages successfully on an ongoing basis will be negotiated on an individual case basis. Any costs incurred for such equipment will be TWTC's responsibility. Where a dial-up facility is required, dial circuits will be installed in the AT&T data center by AT&T and the associated charges assessed to TWTC. Additionally, all message toll charges associated with the use of the dial circuit by TWTC will be the responsibility of TWTC. Associated equipment on the AT&T end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on TWTC end for the purpose of data transmission will be the responsibility of TWTC. 6.2.3 If TWTC utilizes FTP for data file transmission, purchase of the FTP software will be the responsibility of TWTC.
Unbundled Voice Loops (UVLs) 2.2.1 BellSouth shall make available the following UVLs:
Enhanced Optional Daily Usage File Upon written request from <<customer_name>>, BellSouth will provide the Enhanced Optional Daily Usage File (EODUF) service to <<customer_name>> pursuant to the terms and conditions set forth in this section. EODUF will only be sent to existing ODUF subscribers who request the EODUF option.
Repayment of Amounts Advanced for Network Upgrades Upon the Commercial Operation Date, the Interconnection Customer shall be entitled to a repayment, equal to the total amount paid to the Participating TO for the cost of Network Upgrades. Such amount shall include any tax gross-up or other tax-related payments associated with Network Upgrades not refunded to the Interconnection Customer, and shall be paid to the Interconnection Customer by the Participating TO on a dollar-for- dollar basis either through (1) direct payments made on a levelized basis over the five- year period commencing on the Commercial Operation Date; or (2) any alternative payment schedule that is mutually agreeable to the Interconnection Customer and Participating TO, provided that such amount is paid within five (5) years from the Commercial Operation Date. Notwithstanding the foregoing, if this Agreement terminates within five (5) years from the Commercial Operation Date, the Participating TO’s obligation to pay refunds to the Interconnection Customer shall cease as of the date of termination. Any repayment shall include interest calculated in accordance with the methodology set forth in FERC’s regulations at 18 C.F.R. §35.19a(a)(2)(iii) from the date of any payment for Network Upgrades through the date on which the Interconnection Customer receives a repayment of such payment. Interest shall continue to accrue on the repayment obligation so long as this Agreement is in effect. The Interconnection Customer may assign such repayment rights to any person. If the Small Generating Facility fails to achieve commercial operation, but it or another Generating Facility is later constructed and makes use of the Network Upgrades, the Participating TO shall at that time reimburse Interconnection Customer for the amounts advanced for the Network Upgrades. Before any such reimbursement can occur, the Interconnection Customer, or the entity that ultimately constructs the Generating Facility, if different, is responsible for identifying the entity to which reimbursement must be made.
Transmission encryption All data transmissions of County PHI or PI outside the secure internal network must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as AES. Encryption can be end to end at the network level, or the data files containing PHI can be encrypted. This requirement pertains to any type of PHI or PI in motion such as website access, file transfer, and E-Mail.