Product Security. Flexera One is provided in accordance with the Product Security Documentation set out at xxxxx://xxx.xxxxxxx.xxx/sites/default/files/information-security-standards-flexera-one.pdf
Product Security. 3.1. Smarsh will leverage a “security by design” approach and will utilize a software development life cycle that follows best practices defined by NIST and the OWASP Software Assurance Maturity Model (SAMM).
3.2. Smarsh will proactively ensure the security of its applications and environment by leveraging a “software by design” approach. Smarsh will, in accordance with industry accepted benchmarks such as those published by the Center for Internet Security (or equivalent), security-xxxxxx all network devices and servers that will host or process Client Data and code or web applications that are under Smarsh control. Smarsh will perform both static and dynamic automated web application security code analysis on all code prior to deployment in a production environment and correct security flaws discovered by source code analyses prior to deployment. Smarsh will monitor the Services and Smarsh networks, servers, and applications for potential security vulnerabilities. Smarsh will promptly respond to any identified vulnerabilities and assess criticality to resolve, or implement compensating controls for, such identified vulnerabilities within a reasonable amount of time, taking into account the risks posed by each such vulnerability.
3.3. Smarsh will employ then-current industry-standard measures to test the Services for (a) ‘back door,’ ‘time bomb,’ ‘Trojan Horse,’ ‘worm,’ ‘drop dead device,’ ‘virus’, ‘spyware’ or ‘malware;’ or (b) any computer code or software routine that disables, damages, erases, disrupts or impairs the normal operation of the Services or any component thereof.
3.4. Smarsh QA and test networks and environments will be physically or logically separated from production networks and environments and will not be globally accessible to anyone on the internet. Administrative passwords across QA and test environments will be different than those used in production environments.
3.5. Smarsh will enforce a formal change management process which will include tracking and approving all product changes. Any such changes will be internally reviewed and tested within a staging environment before such changes are finalized and deployed.
3.6. Smarsh will not use Client Data for testing purposes.
Product Security. Maintain a product security program responsible for monitoring and assessing vulnerabilities and threats that may impact Red Hat services.
Product Security. 18.1 The Authority shall be responsible for destruction of all Conforming Product in its possession for which the shelf life has expired or, at Valneva’s request and at Valneva’s cost, shall return the same to Valneva. Valneva shall be responsible for destruction of all Products that are Non-Compliant. In complying with its respective destruction obligations, the applicable Party shall undertake such destruction within mutually acceptable timelines, and prior to the destruction the applicable Party possessing the applicable Product shall hold the same securely pending destruction. Each Party shall keep a record of any destruction it undertakes and shall promptly issue certificates of destruction to the other Party upon request. Such records shall be kept for a period of at least [***].
18.2 The Authority shall comply with all Applicable Laws relating to the traceability of pharmaceutical products applicable to the Products Delivered pursuant to this Agreement.
18.3 The Authority warrants and undertakes that it will not alter or modify any Product in any way (including Labelling and packaging but excluding any transportation packaging) after Delivery to the Delivery Locations.
18.4 After Delivery, all Products shall be: (i) stored securely by the Authority (or its Authorised Agents); and (ii) delivered, shipped and distributed by the Authority (or its Authorised Agents) in a secure manner appropriate to the transportation route and destination, in each case (i) and (ii) to guard against and deter theft, diversion, tampering or substitution (with, for example, counterfeits).
Product Security. STA will ensure that all FibroGen Materials, including API and Product, while under the control of STA, its Affiliates or authorized Subcontractors are under appropriately secure conditions with procedures in place to (a) detect diversion, counterfeit, theft, etc., and take protective measures therefrom; and (b) include mechanisms for full accounting and reconciliation of FibroGen Materials, including API and Product, in each case, as may be more fully set forth under the Quality Agreement. STA will promptly notify FibroGen should any breach or discrepancy thereof occur, and STA shall work cooperatively with FibroGen to resolve any such discrepancy.
Product Security. Following treatment, security of the treated batches to be exported to New Zealand shall be maintained in accordance with the procedure described in Section 3.4.5 and 3.4.6 of the section 3.4 of the “Quarantine Procedures for the Operation of Commercial Heat Treatment Chamber, Nadi Airport”.
Product Security. The post inspection security of commodities approved under the non-host “treatment” export pathway to be exported to New Zealand shall be maintained in accordance with the procedures described in the document entitled Procedures for the export of Pineapples from Fiji to New Zealand dated November 2001.
Product Security. 3.1. Smarsh will leverage a “security by design” approach and will utilize a software development life cycle that follows best practices defined by NIST and the OWASP software assurance maturity model.
3.2. Smarsh will proactively ensure the security of its applications and environment by leveraging a “software by design” approach. Smarsh will, in accordance with industry accepted benchmarks such as those published by the Center for Internet Security (or equivalent), security-xxxxxx all network devices and servers that will host or process Client Data and code or web applications that are under Smarsh control. Smarsh will perform both static and dynamic automated web application security code analysis. on all code prior to deployment in a production environment and correct security flaws discovered by source code analyses prior to deployment. Smarsh will monitor the Services and Smarsh networks, servers, and applications for potential security vulnerabilities. Smarsh will promptly respond to any identified vulnerabilities and assess criticality to resolve, or implement compensating controls for, such identified vulnerabilities within a reasonable amount of time, taking into account the risks posed by each such vulnerability.
3.3. Smarsh will employ then-current industry-standard measures to test the Services for (a) ‘back door,’ ‘time bomb,’ ‘Trojan Horse,’ ‘worm,’ ‘drop dead device,’ ‘virus’, ‘spyware’ or ‘malware;’ or (b) any computer code or software
Product Security. There are two distinct products in Alchemy Application. The frontend and backend WebApp provides access to authorized users. The front end is customer facing portal for customers to login and view information while the backend is a role based system for admin and other backend users to view and perform their roles such as underwriting and approval. Alchemy incorporates authentication protocols to prevent unauthorized access to the system. Authentication information is always transmitted encrypted using SSL. The authentication token consists of a unique login name and user defined password. Passwords are obfuscated from view as the user enters them. Users only have access to the system through the Alchemy Application, which restricts access based on account login and assigned role associations.
Product Security. 13.1 The Purchaser shall be responsible for destruction of all Conforming Product in its possession for which the shelf life has expired. AstraZeneca shall be responsible for destruction of all Defective Products. In complying with its respective destruction obligations, the applicable Party shall undertake such destruction within mutually acceptable timelines, and prior to the destruction the applicable Party possessing the applicable Product shall hold the same securely pending destruction. Each Party shall keep a record of any destruction it undertakes and shall promptly issue certificates of destruction to the other Party upon request. Such records shall be kept for a period of at least five (5) years.
13.2 The Purchaser shall comply with all Applicable Laws relating to the traceability of pharmaceutical products in accordance with AstraZeneca’s Specifications, standards, strategy and
