Secure Channel Clause Samples

Secure Channel. A secure channel in OPC UA is a communication path established between an OPC UA client and server that have authenticated each other using certain OPC UA services and for which security parameters have been negotiated and applied.
View Source
Secure Channel. Optionally, the media channel may be secured (encrypted and authenticated) via SRTP/SRTCP. The channel is considered to be secure when the two communicating devices have negotiated secure media and the security association parameters. How the security associations are accomplished is outside the scope of this document; however the following are generally relevant considerations to a TIP device implementation: First, the security establishment process occurs before any media related activity occurs on the UDP channel. Second, with a secure media channel, Datagram Transport Layer Security (DTLS) [13, 14] packets may also occur within the media channel. These packets can be de- multiplexed from RTP traffic by examination of the first byte of the packet. The details are described in section 5.1.2 of [14]. Third, once security association is established, secure TIP negotiation can start For a message flow of a secure TIP control channel setup using DTLS, refer to section 7.2. The following are specific TIP protocol items used to facilitate multipoint encryption: TIP devices MAY use Encrypted Key Transport (EKT) extension to SRTP [12] to coordinate SRTP contexts between transmitters and receivers in a multipoint session where the MCU does not decrypt and re-encrypt packets. Note that a TIP endpoint MUST NOT encrypt the Audio Activity Metric (see section 4.2.5.2) or the Video Refresh Flag (see section 4.2.5.4), so that entities such as MCU do not need to perform crypto operations to read the relevant information. A TIP MCU device that sets the TIP multipoint focus parameter (see section 4.2.1) has negotiated EKT capability if it is communicating with an endpoint that has indicated in TIP its ability to receive EKT security parameters (see section 4.2.5). A TIP endpoint has negotiated EKT capability if it is communicating with a TIP MCU that has indicated in TIP its ability to transmit EKT security parameters (see section 4.2.5). A TIP MCU that has negotiated EKT capability MUST send an SPIMAP (see section 4.2.6) packet every 250 msec until one or more of the following conditions are met: a- MCU receives an ACK packet for its SPIMAP packet. b- MCU receives an SRTP or SRTCP packet with an EKT extension that has the SPI value that was specified in the SPIMAP packet c- After recommended interval of 5 seconds have passed In the above (a) & (b) conditions, the MCU should consider EKT negotiated. In condition (c), the MCU MUST consider EKT negotiation to have failed. An...
View Source
Secure Channel. All internet-facing connections established under a Framework Agreement shall utilize the Internet Engineering Task Force (IETF) Transport Layer Security (TLS) protocol,10 version 1.2 with BCP-195,11 or a later version of TLS, as further specified in the Secure Channel requirements of the QTF. 12 This will help enable the TLS-protected communication channel to operate with appropriate levels of protection and prohibit less secure methods. Timeline to adopt: This requirement shall be implemented within six (6) months of the SOP publication date.
View Source

Related to Secure Channel

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (eff. Sept. 1, 2023, Section 2275.0102(a)(1), pursuant to House Bill 4595, Acts 2023, 88th Leg., R.S.) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102 (eff. Sept. 1, 2023, Section 2275.0102, pursuant to House Bill 4595, Acts 2023, 88th Leg., R.S.), Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103 (eff. Sept. 1, 2023, Section 2275.0103, pursuant to House Bill 4595, Acts 2023, 88th Leg., R.S.), or (2) headquartered in any of those countries.

  • Trunk Group Connections and Ordering 5.2.1 For both One-Way and Two-Way Interconnection Trunks, if Onvoy wishes to use a technically feasible interface other than a DS1 or a DS3 facility at the POI, the Parties shall negotiate reasonable terms and conditions (including, without limitation, rates and implementation timeframes) for such arrangement; and, if the Parties cannot agree to such terms and conditions (including, without limitation, rates and implementation timeframes), either Party may utilize the Agreement’s dispute resolution procedures. 5.2.2 When One-Way or Two-Way Interconnection Trunks are provisioned using a DS3 interface facility, if Onvoy orders the multiplexed DS3 facilities to a Frontier Central Office that is not designated in the NECA 4 Tariff as the appropriate Intermediate Hub location (i.e., the Intermediate Hub location in the appropriate Tandem subtending area based on the LERG), and the provision of such facilities to the subject Central Office is technically feasible, the Parties shall negotiate in good faith reasonable terms and conditions (including, without limitation, rates and implementation timeframes) for such arrangement; and, if the Parties cannot agree to such terms and conditions (including, without limitation, rates and implementation timeframes), either Party may utilize the Agreement’s dispute resolution procedures. 5.2.3 Each Party will identify its Carrier Identification Code, a three or four digit numeric code obtained from Telcordia, to the other Party when ordering a trunk group. 5.2.4 For multi-frequency (MF) signaling each Party will out pulse ten (10) digits to the other Party, unless the Parties mutually agree otherwise. 5.2.5 Each Party will use commercially reasonable efforts to monitor trunk groups under its control and to augment those groups using generally accepted trunk- engineering standards so as to not exceed blocking objectives. Each Party agrees to use modular trunk-engineering techniques for trunks subject to this Attachment.

  • Vlastnictví Zdravotnické zařízení si ponechá a bude uchovávat Zdravotní záznamy. Zdravotnické zařízení a Zkoušející převedou na Zadavatele veškerá svá práva, nároky a tituly, včetně práv duševního vlastnictví k Důvěrným informacím (ve smyslu níže uvedeném) a k jakýmkoli jiným Studijním datům a údajům.

  • Games The Private Party shall not be entitled to introduce any arcade type amusement or gaming machines into the Restaurant Facility without the prior written approval of SANParks.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.