Network Traffic Samples Sample Clauses

Network Traffic Samples. Crown Castle may collect small samples of network traffic for (i) support and maintenance of Product performance, and/or (ii) troubleshooting, prevention or correction of service impacting incidents or for correcting and defending against malicious and improper usage of Crown Castle Network and products (e.g. DDoS attacks, Botnet activity) (“Network Traffic Samples”). Network Traffic Samples typically include source and destination IP addresses, source and destination ports, and partial or in some cases full payload data, and may be stored in a secure system for historic, troubleshooting, or reporting purposes for up to one year. The collection of Network Traffic Samples is inherent in Crown Castle providing the Product. Crown Castle does not otherwise utilize Network Traffic Samples for any other purpose, including, but not limited to, collecting data for marketing or sales purposes, or selling or transferring of data to third parties. Crown Castle utilizes security best practices and provides reasonable and adequate protections to the systems that collect and store Network Traffic Samples. Crown Castle is unable to decrypt any Network Traffic Samples that are encrypted therefore, Crown Castle highly recommends that Licensee encrypt its network traffic.
AutoNDA by SimpleDocs
Network Traffic Samples. Planet may collect small samples of network traffic for (i) support and maintenance of Product performance, and/or (ii) troubleshooting, prevention or correction of service impacting incidents or for correcting and defending against malicious and improper usage of Planet’s Network and products (e.g. DDoS attacks, Botnet activity) (“Network Traffic Samples”). Network Traffic Samples typically include source and destination IP addresses, source and destination ports, and partial or in some cases full payload data, and may be stored in a secure system for historic, troubleshooting, or reporting purposes for up to one year. The collection of Network Traffic Samples is inherent in Planet providing the Product. Planet does not otherwise utilize Network Traffic Samples for any other purpose, including, but not limited to, collecting data for marketing or sales purposes, or selling or transferring of data to third parties. Planet utilizes security best practices and provides reasonable and adequate protections to the systems that collect and store Network Traffic Samples. Planet is unable to decrypt any Network Traffic Samples that are encrypted therefore, Planet highly recommends that Licensee encrypt its network traffic.
Network Traffic Samples. Company may collect small samples of network traffic for (i) support and maintenance of Product performance, and/or (ii) troubleshooting, prevention or correction of service impacting incidents or for correcting and defending against malicious and improper usage of Company Network and products (e.g. DDoS attacks, Botnet activity) (“Network Traffic Samples”). Network Traffic Samples typically include source and destination IP addresses, source and destination ports, and partial or in some cases full payload data, and may be stored in a secure system for historic, troubleshooting, or reporting purposes for up to one year. The collection of Network Traffic Samples is inherent in Company providing the Product. Company does not otherwise utilize Network Traffic Samples for any other purpose, including, but not limited to, collecting data for marketing or sales purposes, or selling or transferring of data to third parties. Company utilizes security best practices and provides reasonable and adequate protections to the systems that collect and store Network Traffic Samples. Company is unable to decrypt any Network Traffic Samples that are encrypted therefore, Company highly recommends that Licensee encrypt its network traffic.

Related to Network Traffic Samples

  • Transit Traffic The following rates will apply:

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Network Interface Device (NID) 2.7.1 The NID is defined as any means of interconnection of end-user customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single-line termination device or that portion of a multiple-line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the end user’s customer-premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the end user each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable.

  • SHOP DRAWINGS, PRODUCT DATA AND SAMPLES 4.12.1 Shop Drawings are drawings, diagrams, schedules and other, data specially prepared for the Work by the Contractor or any Subcontractor, manufacturer, supplier or distributor to illustrate some portion of the Work.

  • Network Access Control The VISION Web Site and the Distribution Support Services Web Site (the “DST Web Sites”) are protected through multiple levels of network controls. The first defense is a border router which exists at the boundary between the DST Web Sites and the Internet Service Provider. The border router provides basic protections including anti-spoofing controls. Next is a highly available pair of stateful firewalls that allow only HTTPS traffic destined to the DST Web Sites. The third network control is a highly available pair of load balancers that terminate the HTTPS connections and then forward the traffic on to one of several available web servers. In addition, a second highly available pair of stateful firewalls enforce network controls between the web servers and any back-end application servers. No Internet traffic is allowed directly to the back-end application servers. The DST Web Sites equipment is located and administered at DST’s Winchester data center. Changes to the systems residing on this computer are submitted through the DST change control process. All services and functions within the DST Web Sites are deactivated with the exception of services and functions which support the transfer of files. All ports on the DST Web Sites are disabled, except those ports required to transfer files. All “listeners,” other than listeners required for inbound connections from the load balancers, are deactivated. Directory structures are “hidden” from the user. Services which provide directory information are also deactivated.

  • Electrical appliance safety The Hirer shall ensure that any electrical appliances brought by them to the premises and used there shall be safe, in good working order, and used in a safe manner in accordance with the Electricity at Work Regulations 1989. Where a residual circuit breaker is provided the hirer must make use of it in the interests of public safety.

  • Traffic Control The Surveyor shall control traffic in and near surveying operations adequately to comply with provisions of the latest edition of the Texas Manual on Uniform Traffic Control Devices – Part VI which can be found on the State’s internet site. In the event field crew personnel must divert traffic or close traveled lanes, a Traffic Control Plan based upon principles outlined in the latest edition of the Texas Manual on Uniform Traffic Control Devices – Part VI shall be prepared by the Surveyor and approved by the State prior to commencement of field work. A copy of the approved plan shall be in the possession of field crew personnel on the job site at all times and shall be made available to the State’s personnel for inspection upon request.

  • CONTRACT WORK HOURS AND SAFETY STANDARDS As per the Contract Work Hours and Safety Standards Act (40 U.S.C. 3701-3708), where applicable, all Customer Purchase Orders in excess of ,000 that involve the employment of mechanics or laborers must include a provision for compliance with 40 U.S.C. 3702 and 3704, as supplemented by Department of Labor regulations (29 CFR Part 5). Under 40 U.S.C. 3702 of the Act, each contractor must be required to compute the wages of every mechanic and laborer on the basis of a standard work week of 40 hours. Work in excess of the standard work week is permissible provided that the worker is compensated at a rate of not less than one and a half times the basic rate of pay for all hours worked in excess of 40 hours in the work week. The requirements of 40 U.S.C. 3704 are applicable to construction work and provide that no laborer or mechanic must be required to work in surroundings or under working conditions which are unsanitary, hazardous or dangerous. These requirements do not apply to the purchases of supplies or materials or articles ordinarily available on the open market, or contracts for transportation or transmission of intelligence.

  • Brand Name Drugs If the subscriber chooses a brand name drug when a bioequivalent generic drug is available, the subscriber is required to pay the standard copayment plus the difference between the cost of the brand name drug and the generic. Amounts above the copay that an individual elects to pay for a brand name instead of a generic drug will not be credited toward the out-of-pocket maximum.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

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