Mobile and Cloud Technology Sample Clauses

Mobile and Cloud Technology. 7.1 Storing Experian data on mobile devices is prohibited. Any exceptions must be obtained from Experian in writing; additional security requirements will apply. 7.2 Mobile applications development must follow industry known secure software development standard practices such as OWASP and OWASP Mobile Security Project adhering to common controls and addressing top risks. 7.3 Mobile applications development processes must follow secure software assessment methodology which includes appropriate application security testing (for example: static, dynamic analysis, penetration testing) and ensuring vulnerabilities are remediated. 7.4 Mobility solution server/system should be hardened in accordance with industry and vendor best practices such as Center for Internet Security (CIS) benchmarks, NIS, NSA, DISA and/or other. 7.5 Mobile applications and data shall be hosted on devices through a secure container separate from any personal applications and data. See details below. Under no circumstances is Experian data to be exchanged between secured and non-secured applications on the mobile device. 7.6 In case of non-consumer access, that is, commercial/business-to-business (B2B) users accessing Experian data via mobile applications (internally developed or using a third party application), ensure that multi-factor authentication and/or adaptive/risk- based authentication mechanisms are utilized to authenticate users to application. 7.7 When using cloud providers to access, transmit, store, or process Experian data ensure that:   Appropriate due diligence is conducted to maintain compliance with applicable laws and regulations and contractual obligations Cloud providers must have gone through independent audits and are compliant with one or more of the following standards, or a current equivalent as approved/recognized by Experian: 8. General o ISO 27001 o PCI DSS o EI3PA o SSAE 16 – SOC 2 or SOC3 o FISMA o CAI / CCM assessment 8.1 ACRAnet may from time to time audit the security mechanisms Company maintains to safeguard access to Experian information, systems and electronic communications. Audits may include examination of systems security and associated administrative practices 8.2 In cases where the Company is accessing Experian information and systems via third party software, the Company agrees to make available to ACRAnet upon request, audit trail information and management reports generated by the vendor software, regarding Company individual authorized user...
Sample 1Sample 2Sample 3See All (16)
AutoNDA by SimpleDocs
Mobile and Cloud Technology. Client will not store Credit Bureau Data on mobile devices. Any exceptions will be obtained from the specifically effected Credit Bureau. Mobile applications development must follow industry known secure software development standard practices such as OWASP and OWASP Mobile Security Project adhering to common controls and addressing top risks. a. Mobile applications development processes must follow secure software assessment methodology which includes appropriate application security testing (for example: static, dynamic analysis, penetration testing) and ensuring vulnerabilities are remediated. b. Mobility solution server/system should be hardened in accordance with industry and vendor best practices such as Center for Internet Security (CIS) benchmarks, NIS, NSA, DISA and/or other. c. Mobile applications and data shall be hosted on devices through a secure container separate from any personal applications and data. See details below. Under no circumstances is Credit Bureau Data to be exchanged between secured and nonsecured applications on the mobile device. d. In case of non-consumer access, that is, commercial/business-to-business (B2B) users accessing Credit Bureau Data via mobile applications (internally developed or using a third-party application), ensure that multi-factor authentication and/or adaptive/ risk-based authentication mechanisms are utilized to authenticate users to application. e. When using cloud providers to access, transmit, store, or process Credit Bureau Data ensure that: 1. Appropriate due diligence is conducted to maintain compliance with applicable laws and regulations and contractual obligations 2. Cloud providers must have gone through independent audits and are compliant with one or more of the following standards, or a current equivalent as approved/recognized by the Credit Bureaus: (i) ISO 27001 (ii) PCI DSS (iii) EI3PA (iv) SSAE16 – SOC2 or SOC 3 (v) FISMA
Sample 1Sample 2See All (4)
Mobile and Cloud Technology. 7.1 Storing Experian data on mobile devices is prohibited. Any exceptions must be obtained from Experian in writing; additional security requirements will apply. 7.2 Mobile applications development must follow industry known secure software development standard practices such as OWASP and OWASP Mobile Security Project adhering to common controls and addressing top risks. 7.3 Mobile applications development processes must follow secure software assessment methodology which includes appropriate application security testing (for example: static, dynamic analysis, penetration testing) and ensuring vulnerabilities are remediated. 7.4 Mobility solution server/system should be hardened in accordance with industry and vendor best practices such as Center for Internet Security (CIS) benchmarks, NIS, NSA, DISA and/or other. 7.5 Mobile applications and data shall be hosted on devices through a secure container separate from any personal applications and data. See details below. Under no circumstances is Experian data to be exchanged between secured and non-secured applications on the mobile device. 7.6 In case of non-consumer access, that is, commercial/business-to-business (B2B) users accessing Experian data via mobile applications (internally developed or using a third party application), ensure that multi-factor authentication and/or adaptive/risk-based authentication mechanisms are utilized to authenticate users to application. 7.7 When using cloud providers to access, transmit, store, or process Experian data ensure that:
Sample 1
Mobile and Cloud Technology. 7.1 Storing RPS data on mobile devices is prohibited. Any exceptions must be obtained from RPS in writing; additional security requirements will apply. 7.2 Mobile applications development must follow industry known secure software development standard practices such as OWASP and OWASP Mobile Security Project adhering to common controls and addressing top risks. 7.3 Mobile applications development processes must follow secure software assessment methodology which includes appropriate application security testing (for example: static, dynamic analysis, penetration testing) and ensuring vulnerabilities are remediated. 7.4 When using cloud providers to access, transmit, store, or process RPS data ensure that: • Appropriate due diligence is conducted to maintain compliance with applicable laws and regulations and contractual obligations
Sample 1
Mobile and Cloud Technology a) Storing Enformion Products on mobile, cloud or portable devices and services is prohibited. Any exceptions must be obtained from Enformion in writing; additional security requirements will apply. b) Mobile applications development must follow industry known secure software development standard practices such as OWASP and OWASP Mobile Security Project adhering to common controls and addressing top risks. c) Mobile applications development processes must follow secure software assessment methodology which includes appropriate application security testing (for example: static, dynamic analysis, penetration testing) and ensuring vulnerabilities are remediated. d) Under no circumstances are Enformion Products to be exchanged between secured and non-secured applications on the mobile device. e) In case of non-consumer access, that is, commercial/business-to-business (B2B) users accessing Enformion Products via mobile applications (internally developed or using a third party application), ensure that multi-factor authentication mechanisms are utilized to authenticate users to application.
Sample 1

Related to Mobile and Cloud Technology

  • Licensed Technology (a) LICENSOR is not aware of any interference, infringement, misappropriation, or other conflict with any intellectual property rights of third parties, and LICENSOR has never received any charge, complaint, claim, demand, or notice alleging any such interference, infringement, misappropriation, or violation (including any claim that LICENSOR must license or refrain from using any intellectual property rights of any third party). To the knowledge of LICENSOR, no third party has interfered with, infringed upon, misappropriated, or otherwise come into conflict with any of the LICENSED TECHNOLOGY. (b) Exhibit A identifies each patent or registration which has been issued to LICENSOR with respect to any of the LICENSED TECHNOLOGY and identifies each pending patent application or application for registration which LICENSOR has made with respect to any of the LICENSED TECHNOLOGY. LICENSEE acknowledges that LICENSOR has previously made available to LICENSEE correct and complete copies of all such patents, registrations and applications (as amended to-date) in LICENSOR’s possession and has made available to LICENSEE correct and complete copies of all other written documentation in LICENSOR’s possession evidencing ownership and prosecution (if applicable) of each such item. (c) Exhibit A identifies each item of LICENSED TECHNOLOGY that is assigned to LICENSOR or that LICENSOR uses pursuant to license, sublicense, agreement, or permission. LICENSOR has made available to LICENSEE correct and complete copies of all such licenses, sublicenses, agreements, patent prosecution files and permissions (as amended to-date) in LICENSOR’s possession. With respect to each item of LICENSED TECHNOLOGY required to be identified in Exhibit A and to the knowledge of LICENSOR: (i) the license, sublicense, agreement, or permission covering the item is legal, valid, binding, enforceable, and in full force and effect; (ii) the license, sublicense, agreement, or permission will continue to be legal, valid, binding, enforceable, and in full force and effect on identical terms following the consummation of the transactions contemplated hereby; (iii) no Party to the license, sublicense, agreement, or permission is in breach or default, and no event has occurred which with notice or lapse of time would constitute a breach or default or permit termination, modification, or acceleration thereunder; (iv) no party to the license, sublicense, agreement, or permission has repudiated any provision thereof; (v) the underlying item of LICENSED TECHNOLOGY is not subject to any outstanding lien or encumbrance, injunction, judgment, order, decree, ruling, or charge; (vi) no action, suit, proceeding, hearing, investigation, charge, complaint, claim, or demand is pending or is threatened which challenges the legality, validity, or enforceability of the underlying item of LICENSED TECHNOLOGY; and (vii) except as provided in Exhibit A, LICENSOR has not granted any license or similar right to the LICENSED TECHNOLOGY within the GENERAL FIELD or PARTHENOGENESIS FIELD.

  • Background Technology List here prior contracts to assign Inventions that are now in existence between any other person or entity and you.

  • Third Party Technology The Company makes use of third party technology to collect information required for traffic measurement, research, and analytics. Use of third party technology entails data collection. We therefore would like to inform clients the Company enables third parties to place or read cookies located on the browsers of users entering the Company’s domain. Said third parties may also use web beacons to collect information through advertising located on the Company’s web site. Please note that you may change your browser settings to refuse or disable Local Shared Objects and similar technologies; however, by doing so you may be disabling some of the functionality of Company’s services.

  • Technology Discoveries, innovations, Know-How and inventions, whether patentable or not, including computer software, recognized under U.S. law as intellectual creations to which rights of ownership accrue, including, but not limited to, patents, trade secrets, maskworks and copyrights developed under this Agreement.

  • New Technology When new or updated technology is introduced into a workplace, it will be the responsibility of the employer to provide appropriate and, if necessary, ongoing training to the employees directly affected. Such training will include any health and safety implications or information that will enable employees to operate the equipment without discomfort and will help maintain their general well-being.

  • Antivirus software All workstations, laptops and other systems that process and/or store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY must have installed and actively use comprehensive anti-virus software solution with automatic updates scheduled at least daily.

  • Manufacturing Technology Transfer Upon AbbVie’s written request with respect to a given Collaboration CAR-T Product and Licensed Product, Caribou shall effect a full transfer to AbbVie or its designee (which designee may be an Affiliate or a Third Party Provider) of all Materials and Know-How Controlled by Caribou relating to the then-current process for the Manufacture of such Collaboration CAR-T Product and any corresponding Licensed Products (each, a “Manufacturing Process”). Caribou shall provide, shall cause its Affiliates to provide, and shall use Commercially Reasonable Efforts to assist AbbVie in causing all Third Party Providers to provide, all reasonable assistance requested by AbbVie to enable AbbVie (or its Affiliate or designated Third Party Provider, as applicable) to implement each Manufacturing Process at the facilities designated by AbbVie. If requested by AbbVie, such assistance shall include facilitating the entering into of agreements with applicable Third Party suppliers relating to such Collaboration CAR-T Product and any corresponding Licensed Products. Without limitation of the foregoing, in connection with the Manufacturing Process and related transfer: (a) Caribou shall, and shall cause its Affiliates to, make available to AbbVie (or its Affiliate or designated Third Party Provider, as applicable), and shall use Commercially Reasonable Efforts to assist AbbVie in causing all Third Party Providers to make available to AbbVie, from time to time as AbbVie may request, all Materials and Manufacturing-related Know-How Controlled by Caribou relating to each Manufacturing Process, including methods, reagents and processes and testing/characterization Know-How, and all documentation constituting material support, performance advice, shop practice, standard operating procedures, specifications as to Materials to be used, and control methods, that are necessary or reasonably useful to enable AbbVie (or its Affiliate or designated Third Party manufacturer, as applicable) to use and practice such Manufacturing Process; (b) Caribou shall cause all appropriate employees and representatives of Caribou and its Affiliates, and shall use Commercially Reasonable Efforts to assist AbbVie in causing all appropriate employees and representatives of Third Party Providers, to meet with employees or representatives of AbbVie (or its Affiliate or designated Third Party Provider, as applicable) at the applicable manufacturing facility at mutually convenient times to assist with the working up and use of each Manufacturing Process and with the training of the personnel of AbbVie (or its Affiliate or designated Third Party Provider, as applicable) to the extent necessary or reasonably useful to enable AbbVie (or its Affiliate or designated Third Party Provider, as applicable) to use and practice such Manufacturing Process; (c) Without limiting the generality of this Section 4.4.2, Caribou shall cause all appropriate analytical and quality control laboratory employees and representatives of Caribou and its Affiliates, and shall use Commercially Reasonable Efforts to assist AbbVie in causing all appropriate analytical and quality control laboratory employees and representatives of Third Party Providers, to meet with employees or representatives of AbbVie (or its Affiliate or designated Third Party Provider, as applicable) at the applicable manufacturing facility and make available all necessary equipment, at mutually convenient times, to support and execute the provision of all applicable analytical methods and the validation thereof (including all applicable Know-How, Information and Materials Controlled by Caribou, and sufficient supplies of all primary and other reference standards); (d) Caribou shall, and shall cause its Affiliates to, take such steps, and shall use Commercially Reasonable Efforts to assist AbbVie in causing Third Party Providers take such steps, as are necessary or reasonably useful to assist AbbVie (or its Affiliate or designated Third Party Provider, as applicable) in obtaining any necessary licenses, permits or approvals from Regulatory Authorities with respect to the Manufacture of the applicable Collaboration CAR-T Products and corresponding Licensed Products at the applicable facilities; and (e) Caribou shall, and shall cause its Affiliates to, provide, and shall use Commercially Reasonable Efforts to assist AbbVie in causing Third Party Providers to provide, such other assistance as AbbVie (or its Affiliate or designated Third Party Provider, as applicable) may reasonably request to enable AbbVie (or its Affiliate or designated Third Party Provider, as applicable) to use and practice each Manufacturing Process and otherwise to Manufacture the applicable Collaboration CAR-T Products and corresponding Licensed Products.

  • Research License Each Collaborator shall allow the other Collaborator to practice any of its Non- Subject Inventions for the purpose of performing the Cooperative Work. No license, express or implied, for commercial application(s) is granted to either Collaborator in Non-Subject Inventions by performing the Cooperative Work. For commercial application(s) of Non-Subject Inventions, a license must be obtained from the owner.

  • Joint Technology The Parties agree that, in order to effectuate the provisions of Section 4.4.2, subject to any exclusive licenses granted hereunder, (a) the non-use provisions of this Article 9 shall not apply to each Party’s use of Joint Technology, and (b) each Party may disclose the Joint Technology to Third Parties who are under terms of confidentiality no less strict than those contained in this Agreement.

  • Licensed Software Computer program(s) provided by Contractor in connection with the Deliverables, subject to Section 14 of this Contract.

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