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).
Product Security. Maintain a product security program responsible for monitoring and assessing vulnerabilities and threats that may impact Red Hat services.
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. 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 [***].
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. Catalent will ensure that all FibroGen-supplied Materials, including API and Product, while under the control of Catalent are under appropriately secure conditions with procedures in place to (a) protect the materials against diversion and theft, 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. Catalent will promptly notify FibroGen should any breach or discrepancy thereof occur, and Catalent will work cooperatively with FibroGen to resolve any such breach or discrepancy, within the scope of its responsibilities under the Quality Agreement. [ ].
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. Authentication 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. Following the 2nd Amendment Effective Date, the Parties shall establish a Joint Product Security Committee as a JSC Subcommittee, which committee shall have authority to (a) establish an annual budget relating to Product security matters throughout the Territory, (b) oversee Product security matters throughout the Territory and (c) perform such other activities as may be delegated to it by the JSC or the Parties. All out-of-pocket costs and expenses approved by the Joint Product Security Committee relating to Product security matters shall be shared equally by the Parties (50%/50%).
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.
