Firewalls / Security Groups Sample Clauses

Firewalls / Security Groups. Snowflake shall protect the Cloud Environment using industry standard firewall or security groups technology with deny-all default policies to prevent egress and ingress network traffic protocols other than those that are business-required.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Firewalls / Security Groups. Firewalls are implemented as network access control lists or security groups within the Cloud Service Provider's account. Databricks also configures local firewalls or security groups within the Customer Data Plane.
Sample 1
Firewalls / Security Groups. Apollo shall protect the Cloud Environment using industry standard firewall or security groups technology to proactively set up egress and periodically review egress network traffic protocols for anomalies. Ingress is only allowed on those particular protocols and ports that are business-critical. Apollo reviews network security rulesets whenever a change is made by Apollo within the network, but in no event less than once each year.
Sample 1
Firewalls / Security Groups eGain protects the Cloud Environment using industry standard firewall or security groups technology with deny-all default policies to prevent egress and ingress network traffic protocols other than those that are business-required. The Service is a multi-tiered zone environment, and firewalls are utilized at each tier boundary to control access from each adjacent tier including the use of Access Control Lists (ACLs). In addition, eGain uses WAF (Web Application Firewall) at cloud boundary and implements host-based firewalls on each device deployed in eGain Cloud.
Sample 1
Firewalls / Security Groups. Slope shall protect the Cloud Environment using industry standard firewall or security groups technology with deny-all default policies to prevent egress and ingress network traffic protocols other than those that are business-required.
Sample 1

Related to Firewalls / Security Groups

  • Contractor and Employee Security Precautions A. The security aspects of working at the Correctional Facility are critical. The following security precautions are part of the site conditions and are a part of this Contract. All persons coming on the site in any way connected with this Work shall be made aware of them, and it is the (General) Contractor’s responsibility to check and enforce them.

  • System Security and Data Safeguards When SAP is given access to Licensee’s systems and data, SAP shall comply with Licensee’s reasonable administrative, technical, and physical safeguards to protect such data and guard against unauthorized access. In connection with such access, Licensee shall be responsible for providing Consultants with user authorizations and passwords to access its systems and revoking such authorizations and terminating such access, as Licensee deems appropriate from time to time. Licensee shall not grant SAP access to Licensee systems or personal information (of Licensee or any third party) unless such access is essential for the performance of Services under the Agreement. The parties agree that no breach of this provision shall be deemed to have occurred in the event of SAP non-conformance with the aforementioned safeguard but where no personal information has been compromised.

  • Security System The site and the Work area may be protected by limited access security systems. An initial access code number will be issued to the Contractor by the County. Thereafter, all costs for changing the access code due to changes in personnel or required substitution of contracts shall be paid by the Contractor and may be deducted from payments due or to become due to the Contractor. Furthermore, any alarms originating from the Contractor’s operations shall also be paid by the Contractor and may be deducted from payments due or to become due to the Contractor.

  • Security Management The Contractor shall comply with the requirements of the DOD 5200.1-M and the DD Form 254. Security of the Contractor’s electronic media shall be in accordance with the above documents. Effective Program Security shall require the Contractor to address Information Security and Operations Security enabled by the Security Classification Guides. The Contractor’s facility must be able to handle and store material up to the Classification Level as referenced in Attachment J-01, DD Form 254.

  • Security Safeguards (1) Each party acknowledges that it is solely responsible for determining and communicating to the other the appropriate technological, physical, and organizational security measures required to protect Personal Data.

  • Security Cameras Security cameras have been installed throughout the Facility; however, they will not routinely be used in areas where there is an expectation of privacy, such as restrooms or patient care areas.

  • Network Security 10.1 Protection of Service and Property. Each Party shall exercise the same degree of care to prevent harm or damage to the other Party and any third parties, its employees, agents or End User Customers, or their property as it employs to protect its own personnel, End User Customers and property, etc.

  • Security Systems The Service may not be compatible with security systems. You may be required to maintain a telephone connection through your local exchange carrier in order to use any alarm monitoring functions for any security system installed in your home or business. You are responsible for contacting the alarm monitoring company to test the compatibility of any alarm monitoring or security system with the Service.

  • NIST Cybersecurity Framework The U.S. Department of Commerce National Institute for Standards and Technology Framework for Improving Critical Infrastructure Cybersecurity Version 1.1.

  • Security Badging Any Company employee, or any employee of its contractors or agents, that require unescorted access to the Security Identification Display Area (SIDA) to perform work under this Agreement will be badged with an Airport identification badge (hereinafter referred to as "Badge") provided by Authority’s ID Badging Department and will be subject to an FBI fingerprint-based criminal history records check (CHRC) and an annual Security Threat Assessment (STA). A new or renewed Badge will not be issued to an individual until the results of the CHRC and the STA are completed and indicate that the applicant has not been convicted of a disqualifying criminal offense. If the CHRC or STA discloses a disqualifying criminal offense, the individual’s new or renewed badge application will be rejected. The costs of the CHRC and the annual STA will be paid by Company. These costs are subject to change without notice, and Company will be responsible for paying any increase in the costs. All badged employees of Company and its contractors or agents will comply with Authority's regulations regarding the use and display of Badges. Company will be assessed a fine for each Badge that is lost, stolen, unaccounted for or not returned to Authority at the time of Badge expiration, employee termination, termination of the Agreement, or upon written request by Authority. This fine will be paid by Company within 15 days from the date of invoice. The fine is subject to change without notice, and Company will be responsible for paying any increase in the fine. If any Company employee is terminated or leaves Company’s employment, Authority must be notified immediately, and the Badge must be returned to Authority promptly.

Time is Money Join Law Insider Premium to draft better contracts faster.