Server Infrastructure Clause Samples

The Server Infrastructure clause defines the requirements and standards for the hardware, software, and network resources that support the operation of a service or application. It typically outlines the responsibilities for maintaining servers, ensuring adequate capacity, and implementing security measures such as firewalls and backups. By clearly specifying these obligations, the clause helps ensure reliable service delivery and minimizes the risk of downtime or data breaches.
Server Infrastructure. All Allied Universal Customer systems would utilize Amazon Web Services data centers in Northern VA – Zero physical Access. Data centers are ISO 27001 compliant. • The Standard Allied Universal Application Architecture will be used for customers using the Air Watch MDM and HELIAUS® Mobile application. Only encrypted access is allowed via HTTPS for both mobile app and web portal and all data is encrypted in transit. Clients and employees are provided access via HELIAUS® web-portal access by user name and 8 characters or longer and require uppercase, lowercase, alpha, numeric, and non-alpha. All employee and client users require multifactor authentication via SMS text or authenticator app. Passwords must be reset every 90 days HELIAUS® includes server infrastructure and hosting costs within Allied Universal’s per-user per-month pricing, thus minimizing costs per customer and per user by spreading them among a vast base and over each customer's contract term. HELIAUS® manages and monitors the server infrastructure.
View Source
Server Infrastructure. Identifying certain lapses in specific best practices, aging systems that may impact function and performance, and opportunities to optimize and reduce risk of obsolescence.
View Source
Server Infrastructure. Every server is hardened and imaged to contain only the necessary services to operate. All hosts are subject to a regular patching and maintenance routine and are periodically scanned for vulnerabilities and security threats using industry-leading technology. All servers are controlled and managed by an automation system to ensure consistent configuration across the environment.
View Source
Server Infrastructure. Currently, a large number of primary schools each have a server infrastructure on site at the school. The SRS are developing a plan for the phased migration of these school infrastructures to the data centre in Blaenavon. This will put schools on the same platform as Secondary Schools. Where migration has taken place, the school will be connected to the data centre in Blaenavon for file storage, backups, printing, application delivery, email and Internet services. This is managed by the SRS with some delegated responsibilities to the school technician. Where a primary school is not migrated and has its own server infrastructure onsite the school technician is able to provide limited support however this will be based on age and state of equipment. It is important to note that wherever possible, the SRS, through the wider resources available to it, endeavour to assist in restoring ‘normal’ service within the school.
View Source
Server Infrastructure. The parties acknowledge that PowerChannel has not taken possession of the Server Infrastructure as specified in Section 5.3 of the License Agreement. AIM shall hold all rights, title and interest in the Server Infrastructure.
View Source

Related to Server Infrastructure

  • Infrastructure Modification of the location and/or sizing of the infrastructure for the Project that does not materially change the functionality of the infrastructure.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If WCS chooses to subtend a Verizon access Tandem, WCS’s NPA/NXX must be assigned by WCS to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 WCS 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 WCS’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office WCS utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow WCS’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at Onvoy’s own expense, shall: 2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment. 2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.

  • Connectivity User is solely responsible for providing and maintaining all necessary electronic communications with Exchange, including, wiring, computer hardware, software, communication line access, and networking devices.