Hardening Sample Clauses
The Hardening clause defines the process and requirements for ensuring that a system, product, or software is made secure and resilient against vulnerabilities before it is delivered or deployed. Typically, this involves implementing security measures such as patching known vulnerabilities, disabling unnecessary services, and conducting security testing or audits. By specifying these obligations, the clause helps ensure that the delivered product meets agreed-upon security standards, thereby reducing the risk of exploitation and protecting both parties from potential security breaches.
POPULAR SAMPLE Copied 8 times
Hardening. The Cloud Environment shall be hardened using industry-standard practices to protect it from vulnerabilities, including by changing default passwords, removing unnecessary software, disabling or removing unnecessary services, and regular patching as described in this Security Policy.
Hardening. 1. Databricks employs industry standards to ▇▇▇▇▇▇ images and operating systems under its control that are deployed within the Platform Services, including deploying baseline images with hardened security configuration such as disabled remote root login, isolation of user code, and images are regularly updated and refreshed.
2. For Systems under Databricks control supporting the production data processing environment, Databricks tracks security configurations against industry standard baselines such as CIS and STIG.
Hardening. All unnecessary packages must be removed and/or disabled from the system. Additionally, all unused operating system services and unused networking ports must be disabled or blocked. Only secure maintenance access shall be permitted and all known insecure protocols shall be disabled.
Hardening. Contractor shall configure hardening of operational Equipment based upon manufacture recommendations and existing Site hardening documentation.