Build and Maintain a Secure Network Sample Clauses

The "Build and Maintain a Secure Network" clause requires parties to establish and continuously uphold robust security measures for their network infrastructure. This typically involves implementing firewalls, regularly updating security protocols, and monitoring network traffic to prevent unauthorized access or data breaches. By mandating these practices, the clause helps protect sensitive information, reduce the risk of cyberattacks, and ensure ongoing compliance with security standards.
Build and Maintain a Secure Network. 5.1 Protect Internet connections with dedicated, industry-recognized Firewalls that are configured and managed using industry best security practices. 5.2 Internal private Internet Protocol (IP) addresses must not be publicly accessible or natively routed to the Internet. Network address translation (NAT) technology should be used. 5.3 Administrative access to Firewalls and servers must be performed through a secure internal wired connection only. 5.4 Any stand alone computers that directly access the Internet must have a desktop Firewall deployed that is installed and configured to block unnecessary/unused ports, services and network traffic. 5.5 Encrypt Wireless access points with a minimum of WEP 128 bit encryption, WPA encryption where available. 5.6 Disable vendor default passwords, SSIDs and IP Addresses on Wireless access points and restrict authentication on the configuration of the access point.
View SourceView Similar (16)
Build and Maintain a Secure Network. Protect Internet connections with dedicated, industry-recognized firewalls that are configured and managed using industry standard security practices. • Internal private internet protocol (IP) addresses must not be publicly accessible or natively routed to the Internet. Network address translation (NAT) technology should be used. • Any stand-alone computers that directly access the Internet must have a desktop firewall deployed that is installed and configured to block unnecessary/unused ports, services and network traffic. • Encrypt wireless access points with a minimum of Wi-Fi protected access (WPA) encryption security standard. • Disable end-user default passwords, SSIDs and IP addresses on wireless access points and restrict authentication on the configuration of the access point.
View SourceView Similar (9)
Build and Maintain a Secure Network. 5.1 Protect Internet connections with dedicated, industry-recognized firewalls that are configured and managed using industry best security practices. 5.2 Internal private Internet Protocol (IP) addresses must not be publicly accessible or natively routed to the Internet. Network address translation (NAT) technology should be used. 5.3 Administrative access to firewalls and servers must be performed through a secure internal wired connection only. 5.4 Any stand-alone computers that directly access the Internet must have a desktop firewall deployed that is installed and configured to block unnecessary/unused ports, services, and network traffic. 5.5 Change vendor defaults including but not limited to passwords, encryption keys, SNMP strings, and any other vendor defaults. 5.6 For wireless networks connected to or used for accessing or transmission of Experian data, ensure that networks are configured and firmware on wireless devices updated to support strong encryption (for example, IEEE 802.11i) for authentication and transmission over wireless networks. 5.7 When using service providers (e.g. software providers) to access ACRAnet systems, access to third party tools/services must require multi-factor authentication.
View SourceView Similar (8)
Build and Maintain a Secure Network. 1. Install and maintain a firewall configuration to protect cardholder data 2. Do not use vendor-supplied defaults for system passwords and other security parameters
View SourceView Similar (2)
Build and Maintain a Secure Network. 5.1 Protect Internet connections with dedicated, industry-recognized firewalls that are configured and managed using industry best security practices. 5.2 Internal private Internet Protocol (IP) addresses must not be publicly accessible or natively routed to the Internet. Network address translation (NAT) technology should be used. 5.3 Administrative access to firewalls and servers must be performed through a secure internal wired connection only. 5.4 Any stand-alone computers that directly access the Internet must have a desktop firewall deployed that is installed and configured to block unnecessary/unused ports, services, and network traffic. 5.5 Change vendor defaults including but not limited to passwords, encryption keys, SNMP strings, and any other vendor defaults. 5.6 For wireless networks connected to or used for accessing or transmission of RPS data, ensure that networks are configured and firmware on wireless devices updated to support strong encryption (for example, IEEE 802.11i) for authentication and transmission over wireless networks. 5.7 When using service providers (e.g. software providers) to access RPS systems, access to third party tools/services must require multi-factor authentication.
View Source
Build and Maintain a Secure Network. CLIENT understands and agrees that they must build and maintain a secure network. These measures include: ● Protecting Internet connections with dedicated, industry­recognized firewalls that are configured and managed using industry best security practices. ● Internal private Internet Protocol (IP) addresses must not be publicly accessible or natively routed to the Internet. Network address translation (NAT) technology should be used. ● Administrative access to firewalls and servers must be performed through a secure internal wired connection only. ● Any stand­alone computers that directly access the Internet must have a desktop firewall deployed that is installed and configured to block unnecessary/unused ports, services, and network traffic. ● Encrypt wireless access points with a minimum of WEP 128 bit encryption, WPA encryption where available. ● Disable vendor default passwords, SSIDs and IP addresses on wireless access points and restrict authentication on the configuration of the access point.
View Source
Build and Maintain a Secure Network. Protect Internet connections with dedicated, industry-recognized Firewalls that are configured and managed using industry best security practices. Internal private Internet Protocol (IP) addresses must not be publicly accessible or natively routed to the Internet. Network address translation (NAT) technology should be used. Administrative access to Firewalls and servers must be performed through a secure internal wired connection only. Any Stand alone computers that directly access the Internet must have a desktop Firewall deployed that is installed and configured to block unnecessary/unused ports, services, and network traffic. Encrypt Wireless access points with a minimum of WEP 128 bit encryption, WPA encryption where available. Disable vendor default passwords, SSIDs and IO Addresses on Wireless access points and restrict authentication on the configuration of the access point.
View Source
Build and Maintain a Secure Network. (A) Protect Internet connections with dedicated, industry-recognized firewalls that are configured and managed using industry best security practices. (B) Internal private Internet Protocol (IP) addresses must not be publicly accessible or natively routed to the Internet. Network address translation (NAT) technology should be us e d . (C) Administrative access to firewalls and servers must be performed through a secure internal wired connection only. (D) Any standalone computers that directly access the Internet must have a desktop firewall deployed that is installed and configured to block unnecessary/unused ports, services, and network traffic. (E) Encrypt wireless access points with a minimum of WEP 128-bit encryption, WPA encryption where available. (F) Disable vendor default passwords, SSIDs and IP Addresses on wireless access points and restrict authentication on the configuration of the access point.
View Source

Related to Build and Maintain a Secure Network

  • NETWORK MAINTENANCE AND MANAGEMENT 38.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government, escalation processes, etc.) to achieve this desired result. 38.2 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a twenty four (24)-hour contact number for Network Traffic Management issues to the other’s surveillance management center. 38.3 Each Party maintains the right to implement protective network traffic management controls, such as “cancel to”, “call gapping” or seven (7)-digit and ten (10)-digit code gaps, to selectively cancel the completion of traffic over its network, including traffic destined for the other Party’s network, when required to protect the public-switched network from congestion as a result of occurrences such as facility failures, switch congestion or failure or focused overload. Each Party shall immediately notify the other Party of any protective control action planned or executed. 38.4 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes shall not be used to circumvent normal trunk servicing. Expansive controls shall be used only when mutually agreed to by the Parties. 38.5 The Parties shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes to prevent or mitigate the impact of these events on the public-switched network, including any disruption or loss of service to the other Party’s End Users. Facsimile (FAX) numbers must be exchanged by the Parties to facilitate event notifications for planned mass calling events. 38.6 Neither Party shall use any Interconnection Service provided under this Agreement or any other service related thereto or used in combination therewith in any manner that interferes with or impairs service over any facilities of AT&T-21STATE, its affiliated companies or other connecting telecommunications carriers, prevents any carrier from using its Telecommunications Service, impairs the quality or the privacy of Telecommunications Service to other carriers or to either Party’s End Users, causes hazards to either Party’s personnel or the public, damage to either Party’s or any connecting carrier’s facilities or equipment, including any malfunction of ordering or billing systems or equipment. Upon such occurrence either Party may discontinue or refuse service, but only for so long as the other Party is violating this provision. Upon any such violation, either Party shall provide the other Party notice of the violation at the earliest practicable time. 38.7 AT&T TENNESSEE hereby commits to provide Disaster Recovery to CLEC according to the plan below. 38.7.1 AT&T TENNESSEE Disaster Recovery Plan 38.7.2 In the unlikely event of a disaster occurring that affects AT&T TENNESSEE’s long-term ability to deliver traffic to a CLEC, general procedures have been developed by AT&T TENNESSEE to hasten the recovery process in accordance with the Telecommunications Service Priority (TSP) Program established by the FCC to identify and prioritize telecommunication services that support national security or emergency preparedness (NS/EP) missions. A description of the TSP Program as it may be amended from time to time is available on AT&T TENNESSEE’s Wholesale – Southeast Region Web site. Since each location is different and could be affected by an assortment of potential problems, a detailed recovery plan is impractical. However, in the process of reviewing recovery activities for specific locations, some basic procedures emerge that appear to be common in most cases. 38.7.3 These general procedures should apply to any disaster that affects the delivery of traffic for an extended time period. Each CLEC will be given the same consideration during an outage, and service will be restored as quickly as possible. AT&T TENNESSEE reserves the right to make changes to these procedures as improvements become available or as business conditions dictate. 38.7.4 This plan will cover the basic recovery procedures that would apply to every CLEC.

  • Support and Maintenance Where Licensee purchases support and/or maintenance services, Licensee’s initial support and/or maintenance term will begin upon delivery to Licensee of the Licensed Software and continue for one (1) year thereafter (or the length of the term if less than a year for any subscription/term license) unless otherwise specified in the applicable annual support and/or maintenance agreement, Product Order, or other written agreement executed between Licensor and Licensee. Where Licensee purchases support and/or maintenance for any Licensed Software, Licensee hereby agrees that it shall purchase such support and/or maintenance services for all of Licensee’s licensed units of such Licensed Software product. Support and/or maintenance services provided by Licensor will be subject to Licensor’s then current applicable standard annual support and/or maintenance agreement unless otherwise agreed by the parties in writing.

  • Support and Maintenance Services Information about Teradici’s support and maintenance for the Licensed Product may be found at ▇▇▇▇▇://▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇.

  • Access Toll Connecting Trunk Group Architecture 8.2.1 If Reconex chooses to subtend a Verizon access Tandem, Reconex’s NPA/NXX must be assigned by Reconex to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center subtends as identified in the LERG. 8.2.2 Reconex shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from Reconex’s Customers. 8.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office Reconex utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the Tandem Verizon utilizes to provide Exchange Access in such LATA. 8.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow Reconex’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access tandem.

  • Account Maintenance Trade Allocations Trade Reporting; (Futures) Daily Trade Checkout Daily Statement Reconciliation