Protective Protocols Clause Samples

The Protective Protocols clause establishes specific procedures and safeguards to ensure the safety and security of parties, assets, or information involved in an agreement. Typically, this clause outlines the steps each party must take to prevent harm, such as implementing cybersecurity measures, following health and safety guidelines, or maintaining confidentiality standards. Its core practical function is to minimize risks and liabilities by clearly defining the responsibilities and actions required to protect all relevant interests under the contract.
Protective Protocols. Either Party may use protective network traffic management controls such as 7-digit and 10-digit code gaps on traffic toward each other’s network, when required to protect the public switched network from congestion due to facility failures, switch congestion or failure or focused overload. CLEC and Sprint will immediately notify each other of any protective control action planned or executed.
View SourceView Similar (118)
Protective Protocols. Either Party may use protective network traffic management controls such as 7-digit and 10-digit code gaps on traffic toward each others network, when required to protect the public switched network from congestion due to facility failures, switch congestion or failure or focused overload. The Parties will immediately notify each other of any protective control action planned or executed.
View SourceView Similar (48)
Protective Protocols. All traffic between users and the application occurs over HTTPS with TLS 1.2. • Connections between application and database are encrypted using TLS. • Application servers, database servers exist in a private virtual network. • Network Security groups are used to restrict access to application/database servers. • IAM policies are used to limit employee access to cloud computing resources. • OS Security patches are installed in a timely manner. • AWS GuardDuty is used to detect anomalous cloud account activity. • Data is encrypted in transit and at rest at a minimum of 128-bit AES. • Maintain a Data Incidence Response Plan which aligns with the NIST Cybersecurity Framework v1.1. • Adopted practices and procedures which align with applicable NIST principles and industry- standard practices. • Annual training for employees and contracted personnel, covering: - FERPA law overview - COPPA law overview - Cybersecurity and best practices - State-specific requirements (as applicable) - Data security incident plans (for relevant employees) - How to handle requests for data access/erasure (for relevant employees) - How to verify identity for requests relating to customer data (for relevant employees) Upon expiration of an agreement or termination of use, data may be securely destroyed or transferred, per and upon request from the EA or customer, barring any legal obligations. The following process will be followed when responding to a suspected incident:
View Source
Protective Protocols. Either Party may use protective network traffic management controls such as 3, 7, and 10 digit network controls on traffic toward each other’s network, when required to protect the public switched network from congestion due to facility failures, Switch congestion or failure, or focused overload. MCIm and Verizon shall promptly notify each other of any significant protective control action executed.
View Source
Protective Protocols. All traffic between users and the application occurs over HTTPS with TLS 1.2 • Connections between application and database are encrypted using TLS • Application servers, database servers exist in a private virtual network • Network Security groups are used to restrict access to application/database servers • IAM policies are used to limit employee access to cloud computing resources • OS Security patches are installed in a timely manner • AWS GuardDuty is used to detect anomalous cloud account activity • Data is encrypted in transit and at rest at a minimum of 128-bit AES • Annual training for employees and contracted personnel, covering: - FERPA law overview _ - COPPA law overview - State-specific requirements - Data security incident plans - Cybersecurity - How to handle requests for data access/erasure - How to verify identity for requests relating to customer data - SmartMusic privacy policy responsibilities • Please also see: ▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇▇.▇▇▇/privacy/ Upon expiration of the agreement, data may be securely destroyed or transferred, per and upon request from the EA, in a reasonable and agreed upon timeframe. Reporting and Contact The following process will be followed when responding to a suspected incident: 1.Confirmed or suspected incidents shall be reported promptly to MakeMusic's engineering management at ▇▇▇▇▇▇▇@▇▇▇▇▇▇▇▇▇.▇▇▇ or ▇▇▇▇▇@▇▇▇▇▇▇▇▇▇.▇▇▇. A report will be filed that includes detailed information about the incident including team members involved, timelines, and data involved.
View Source
Protective Protocols. 5.1.1 Either party may se protective network traffic management controls such as 7-digit and 10-digit code gaps on traffic toward each others network, when required to protect the public switched network from congestion due to facility failures, switch congestion or failure or focused overload. MCIm and BellSouth will immediately notify each other of any protective control action planned or executed.
View Source

Related to Protective Protocols

  • Protocols Each party hereby agrees that the inclusion of additional protocols may be required to make this Agreement specific. All such protocols shall be negotiated, determined and agreed upon by both parties hereto.

  • COVID-19 Vaccinations Contractor understands, acknowledges, and agrees that, pursuant to Article II of the General Appropriations Act, none of the General Revenue Funds appropriated to the Department of State Health Services (DSHS) may be used for the purpose of promoting or advertising COVID-19 vaccinations in the 2024-25 biennium. It is also the intent of the legislature that to the extent allowed by federal law, any federal funds allocated to DSHS shall be expended for activities other than promoting or advertising COVID-19 vaccinations. Contractor represents and warrants that it is not ineligible, nor will it be ineligible during the term of this Contract, to receive appropriated funding pursuant to Article II.

  • DISCIPLINE PROCEDURES 19.1 The Company shall be free to discharge employees for refusal to obey lawful orders, incompetence, misrepresentation, intoxication, or any just cause. An employee who has not completed his or her probationary period may be disciplined or discharged without just cause and without recourse to the Grievance and Arbitration procedure set forth in Article 20. 19.2 The Company shall be free to discipline any employee who commits an infraction, which, while not being sufficient to constitute just cause for discharge, is sufficient to warrant some lesser disciplinary action. However, no employee who has completed the probationary period will be discharged for offenses, which do not in and of themselves constitute just cause for discharge unless the employee has received two (2) prior written warnings within twelve ( 12) months of the offense. The issuance of two (2) prior warnings within a twelve (12) month period shall constitute just cause. Absent excused or extraordinary circumstances, warning notices shall be issued within ten (10) days after the Company knew or should have known of the offense but not more than thirty (30) days after the event. Each warning notice shall contain a place for the employee to sign to acknowledge receipt without admitting guilt. 19.3 In addition to those circumstances mentioned elsewhere in this Agreement, just cause circumstances for discharge shall include, but not be limited to: insubordination, theft, excessive absenteeism, gross negligence, failure to comply with reasonable rules, policies or directives promulgated by the Company and clearly communicated to the employee, use of unnecessary force or disrespectful treatment of a tenant, visitor or employee and inability or unwillingness to be trained to fulfill existing or modified security needs of the Company, the building owner or its tenants. The Union further understands and agrees that the Company provides an important service to its tenants of a personalized nature to fulfill their security needs, as those needs are perceived by the Company, the building owner and the tenants. Accordingly, the provisions of this Section shall be implemented and interpreted by the parties and by an arbitrator in arbitration proceedings so as to give significant consideration to such needs. 19.4 The Company will discharge any employee who is denied registration or whose registration is canceled by the State of Minnesota Board of Private Detective and Protective Agent Services or any other governmental agency. Discharge under this Article for failure to possess a license shall be without recourse to the Grievance Procedures of Article 20. 19.5 The employee and the Union recognize that the customer is the ultimate consumer and ultimately controls the access of the employee and the business of the Company. When a security-related incident occurs on a job site that is or can reasonably be construed as injurious to that customer, the employee, the Union, and the Company will cooperate in every way in the investigation of the incident until the incident is resolved and/or the customer is satisfied that all reasonable avenues have been pursued to their completion. The Union will not impede any steps which may assist the Company in convincing the customer of the thoroughness and/or reliability of its investigation, consistent with the Union's duty to provide fair and effective representation to its membership.

  • Protocol The attached Protocol shall be an integral part of this Agreement.