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.
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.
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:
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.
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.
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.