Common use of Secure Code Review Clause in Contracts

Secure Code Review. As a condition of Buyer’s acceptance of Goods; at least every two years from the date of Buyer’s acceptance of Goods; and within three months after every major version update to the Goods, Seller shall demonstrate to Buyer’s satisfaction either: (a) that the Goods contain no defects that exceed a Common Vulnerability Scoring System (“CVSS”) score of 6.0, as assessed by a third party assessment organization approved in writing by Buyer; or (b) that Seller’s secure development lifecycle is in substantial alignment with ISO 27034.

Secure Code Review. As a condition of Buyer’s acceptance of GoodsProducts; at least every two years from the date of Buyer’s acceptance of GoodsProducts; and within three months after every major version update to the GoodsProducts, Seller shall demonstrate to Buyer’s satisfaction either: (a) that the Goods Products contain no defects that exceed a Common Vulnerability Scoring System (“CVSS”) score of 6.0, as assessed by a third party assessment organization approved in writing by Buyer; or (b) that Seller’s secure development lifecycle is in substantial alignment with ISO 27034.

Secure Code Review. As a condition of BuyerXxxxx’s acceptance of Goods; at least every two years from the date of BuyerXxxxx’s acceptance of Goods; and within three months after every major version update to the Goods, Seller shall demonstrate to Buyer’s satisfaction either: : (a) that the Goods contain no defects that exceed a Common Vulnerability Scoring System (“CVSS”) score of 6.0, as assessed by a third party assessment organization approved in writing by Buyer; or (b) that Seller’s secure development lifecycle is in substantial alignment with ISO 27034.