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 the other Party’s network, when required to protect the public switched network from congestion due to facility failures, switch congestion or failure, or focused overload. Each Party will provide appropriate industry standard notification to the other Party of any such protective control action which has been executed by that Party. To the extent that prior notification is commercially reasonable and consistent with industry practice, each Party will provide prompt notification to the other Party of any such protective control action which will be executed by the Party.
Protective Protocols. Either Party may use protective network traffic management controls such as 7-digit and 10-digit code gaps on traffic toward the other Party’s network, when required to protect the public switched network from congestion due to facility failures, switch congestion or failure, or focused overload. AT&T and BA 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 • Annual training for employees and contracted personnel, covering: - FERPA law overview Exhibit I - Provider Data Security & Privacy Plan _ - 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: xxxxx://xxx.xxxxxxxxx.xxx/privacy/ Data Destruction: 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. Data Incident Response Plan: Data Incident Response Plan: 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 xxxxxxx@xxxxxxxxx.xxx or xxxxx@xxxxxxxxx.xxx. A report will be filed that includes detailed information about the incident including team members involved, timelines, and data involved.
Protective Protocols. 46 5.2 Expansive Protocols 46 5.3 Mass Calling 46 6.0 Forecasting/Servicing Responsibilities 46 7.0 Trunk Servicing 46 ATTACHMENT 5: INTENTIONALLY LEFT BLANK 48 ATTACHMENT 6: UNBUNDLED NETWORK ELEMENTS (UNES) 49 1.0 Introduction 49 2.0 Unbundled Loops 52 3.0 NETWORK INTERFACE DEVICE (NID) 53 4.0 Cross-Connects 56 5.0 Provisioning/Maintenance of Network Elements on an Unbundled Basis 56 6.0 Maintenance of Elements 57 7.0 Performance of Network Elements 58 8.0 Pricing 58
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) Data Destruction: 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. Data Incident Response: The following process will be followed when responding to a suspected incident:
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.
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. PAETEC and CenturyLink 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 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.
