JBoss Middleware for OpenShift Container Platform Clause Samples

JBoss Middleware for OpenShift Container Platform. Red Hat JBoss Middleware Software Subscriptions in Table 1 include access to the Red Hat JBoss Middleware Software enabled for Red Hat OpenShift Container Platform (i.e. the Software described in Table 3 below (“JBoss OpenShift Enabled Software”). The JBoss OpenShift Enabled Software is supported when deployed on Red Hat OpenShift Container Platform, which requires a separate active paid Software Subscription. The capacity restrictions in Table 3 below apply to the Red Hat JBoss OpenShift Enabled Software. Red Hat JBoss Middleware Software Subscriptions listed in Table 1 are not configured for use with Red Hat OpenShift Container Platform.

Related to JBoss Middleware for OpenShift Container Platform

  • DNS name server availability Refers to the ability of a public-­‐DNS registered “IP address” of a particular name server listed as authoritative for a domain name, to answer DNS queries from an Internet user. All the public DNS-­‐registered “IP address” of all name servers of the domain name being monitored shall be tested individually. If 51% or more of the DNS testing probes get undefined/unanswered results from “DNS tests” to a name server “IP address” during a given time, the name server “IP address” will be considered unavailable.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store County PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the County Information Security Office.

  • Please see the current Washtenaw Community College catalog for up-to-date program requirements Conditions & Requirements

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

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following: