Secure Vertical Interfaces Sample Clauses

Secure Vertical Interfaces. The secure vertical interfaces describe services provided by the platform to applications. These services are used to compose security services or give/enhance security attributes to/of the system. While the safety vertical interfaces are related to the quality of service, the secure vertical interfaces provide functionalities that are designed to be used by the application to render security functions. The security measures of an application can be implemented by software, hardware or both. By using hardware, engineers can improve the performance of cryptographic algorithms, delivering extra performance to the application. As presented in §1.3, the result of project Evita and PRESERVE was a hardware architecture to address security needs of the applications running in security-critical platforms. The architecture component proposed was called Secure Hardware Extension (SHE). The SHE specification defines a set of functions and a programmer’s model (API) that allows a secure zone to coexist within any electronic control unit installed in the vehicle. Currently, manufacturers already produce chips equipped with SHE [23], which are basically a suite of security services provided by the platform such as the storage and management of security keys, plus encapsulating authentication, encryption and decryption algorithms that application code can access through the API. These features help maximize flexibility and minimize costs. Considering those services, and how they can influence safety characteristics of systems, we created a novel class of platform services to be represented in the ConSerts M contracts regarding the Vertical Interfaces. An application developer can, depending on the applications security needs, specify corresponding application demands. This class is called Security Services and they are represented in the contracts within the vertical demands or guarantees part with the following xml tags: <Vertical_Guarantee> <Security_Services> <Key_Management>10</Key_Management> </Security_Services> </Vertical_Guarantee> Within the Security_Services tag we can define the following security services: Key management <Key_Management></Key_Management> This service allows to store and retrieve keys from a secure part of the platform. The number of keys that the platform can handle or that an application requires is a variable property of this service. If more than one application running in the same platform requires keys to be handled by the platform, the ...
Sample 1
AutoNDA by SimpleDocs

Related to Secure Vertical Interfaces

  • Technical Interfaces 3.2.6.1 The Interconnection facilities provided by each Party shall be formatted using either Alternate Xxxx Inversion (AMI) line code with Superframe format framing or Bipolar 8-Zero Substitution with Extended Superframe (B8ZS ESF) format framing or any mutually agreeable line coding and framing.

  • Antivirus software All workstations, laptops and other systems that process and/or store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY must have installed and actively use comprehensive anti-virus software solution with automatic updates scheduled at least daily.

  • Network Interface Device 2.7.1 The NID is defined as any means of interconnection of the End User’s 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 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.

  • Local Interconnection Data Exchange for Billing 7.7.1 There are certain types of calls or types of Interconnection that require exchange of Billing records between the Parties, including, for example, alternate billed and Toll Free Service calls. The Parties agree that all call types must be routed between the networks, accounted for, and settled among the Parties. Certain calls will be handled via the Parties' respective operator service platforms. The Parties agree to utilize, where possible and appropriate, existing accounting and settlement systems to xxxx, exchange records and settle revenue.

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Integrated Digital Loop Carriers The feeder portion of some loops may be provide by means of Integrated Digital Loop Carrier (IDLC). IDLC provides a fiber optic cable transmission path that travels directly into BellSouth’s central office local switch. Where BellSouth uses IDLC ,if technically feasible and capacity does exist, BST will provide Al-Call with a Designed DS0 UVL by using alternative provisioning techniques including but not limited to such as “hairpinning” and DAC grooming. Alternative provisioning techniques will be provided at no additional cost to Al-Call . Hairpinning involves providing a DS0 signal from an IDLC-served loop to Al-Call ’s collocation equipment by using a dedicated pathway that traverses BellSouth’s central office switch. BellSouth will provide such DS0 signal to Al-Call by establishing a copper cross connect between the BellSouth switch and Al-Call ’s collocation equipment.

  • Server Software Subject to the terms and conditions of this XXXX, Vocera grants you the non-exclusive right to (i) install and run (“Use”) the Server Software on computer systems (each, a “Server Computer”) located at End User’s Facilities in the geographic territory designated above (“Territory”); (ii) to Use the Client Software in conjunction with Authorized Client Devices and such Server Computers; and (iii) for pilot licenses for certain Software provided on a trial basis, use such Software for the limited term specified by Vocera in writing. You may Use the standard Server Software on one primary Server Computer (or a primary cluster of computers suitably configured for productive use of the Server Software). You may install backup copies of the Server Software on backup Server Computers to provide redundancy in the event of failure of the primary Server Computer(s) but, unless you have acquired additional licenses or a failover license from Vocera, you may not run such backup or additional copies concurrently with the primary copies. Vocera grants you the right to use the applicable License Key issued by Vocera only to enable Use of the Server Software in conjunction with the licensed Server Computers. Server Software may be licensed for a Subscription Term as specified in the Quote.

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

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

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