Security Capabilities Catalogue Sample Clauses

Security Capabilities Catalogue. The SCC is composed of modules related to the storage, onboarding, searching, and accessing data about SCs. The SCC provides functionality to other components and subcomponents within other WPs, and contributes to the actualisation of functionality related to subcomponents of the SCO. Table 4 describes how each requirement maps to the technical specification that the SCC subcomponent must filfill, as well as the internal modules that contribute to the specification. Table 4: technical specifications for SCC. R1.3.1 The platform SHALL be able to instantiate security capabilities. ✓ ✓ ✓ ✓ -- -- SCC_S1 In order for the SO to instantiate SCs, the SC shall first need to be registered and onboarded to the SO, which is done through the SCC.
AutoNDA by SimpleDocs
Security Capabilities Catalogue. PALANTIR has a single storage subcomponent for SCs, allowing security developers to make new functionalities available to client enterprises of the platform. The SCC is the subcomponent of the SCO that is mainly concerned with securely storing SCs as sets of metadata, serving SC metadata to other PALANTIR components, such as the Billing and SM (T4.3) and the TAR (T4.4), and securely onboarding SC packages to the SO. The SCC also tightly integrates with the UI frontend of the PALANTIR Portal (T4.1), which will be further elaborated upon in D4.1, allowing for visually defining and managing SCs. The SCC stores the metadata of the SC packages in a trusted way, keeping the SC software image reference, the security and privacy specifications, billing information and other VNF operational metadata. The packages are essentially functional, and include all necessary metadata about SCs, which are stored in the catalogue, along with attestation data about the aforementioned metadata and the main software of the SC. The software of the capabilities is, in turn, packaged as images, such as images for containers or Virtual Machines (VMs). These software images are not stored within the SCC, but only the references to registries that hold them, and the specific image ID and version to use. Only during the registration and onboarding process is the image fetched, and appropriately packaged along with all the descriptors, the accompanying operational and security metadata, and sent to the SO. The SO, in turn, proceeds further with the onboarding process once it obtains the SC packages. During this step, the SO also requests the appropriate tools to register the image or images associated to the SC package, in order to later quickly instantiate and configure the desired capabilities. The SO may further query the SCC in case any more metadata or execution parameters are updated since the onboarding, and for any environment variables not included in the package, during the deployment. The SCC is also searchable, by making search queries based on stored metadata. The RAF component can identify the proper SCs by searching for SCs and correlating with the outcome of its own analysis. The SCC search and fetch functionality is also used by the Security and the Accounting Dashboards, so as to leverage the UI of the Portal, to enact the deployment of SCs or to have an inspection of the overall deployment, through a combination with the interfaces of the SO and the Billing components...
Security Capabilities Catalogue. In D3.1, the SCC was introduced as a subcomponent of SCO, with interactions taking place between the SO, the dashboard (T4.1), Billing Dashboard and SM (T4.3) and TAR (T4.
Security Capabilities Catalogue. The implementation has undergone some changes since D3.1. Some new functionalities have been added to the SCC. Also, the authentication mechanism has been changed. The rest of the technology stack is the same as D3. 1. The new implementation is depicted in figure 4.3-1, and more details on the implementation changes are described in section 4.3.1.

Related to Security Capabilities Catalogue

  • Security Cameras Security cameras have been installed throughout the Facility; however, they will not routinely be used in areas where there is an expectation of privacy, such as restrooms or patient care areas.

  • Financial Management System Subrecipient shall establish and maintain a sound financial management system, based upon generally accepted accounting principles. Contractor’s system shall provide fiscal control and accounting procedures that will include the following: i. Information pertaining to tuition rates, payments, and educational assistance payments; and

  • Changes in Equipment, Systems, Etc USBFS reserves the right to make changes from time to time, as it deems advisable, relating to its systems, programs, rules, operating schedules and equipment, so long as such changes do not adversely affect the services provided to the Trust under this Agreement.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS 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 DHCS Information Security Office.

  • Operator’s Security Contact Information Xxxxxxx X. Xxxxxxx Named Security Contact xxxxxxxx@xxxxxxxxx.xxx Email of Security Contact (000) 000-0000 Phone Number of Security Contact

  • The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.

  • Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.

  • Local Circuit Switching Capability, including Tandem Switching Capability 4.1.3.1 Definition 4.1.3.2 Notwithstanding BellSouth’s general duty to unbundle local circuit switching, BellSouth shall not be required to unbundle local circuit switching for <<customer_name>> when <<customer_name>> serves end-users with four (4) or more voice-grade (DS-0) equivalents or lines in locations served by BellSouth’s local circuit switches, which are in the following MSAs: Atlanta, GA; Miami, FL; Orlando, FL; Ft. Lauderdale, FL; Charlotte-Gastonia-Rock Hill, NC; Greensboro-Winston Salem-High Point, NC; Nashville, TN; and New Orleans, LA, and BellSouth has provided non-discriminatory cost based access to the Enhanced Extended Link (EEL) throughout Density Zone 1 as determined by NECA Tariff No. 4 as in effect on January 1, 1999. 4.1.3.3 In the event that <<customer_name>> orders local circuit switching for a single end user account name at a single physical end user location with four (4) or more 2-wire voice-grade loops from a BellSouth central office in an MSA listed above, BellSouth shall charge <<customer_name>> the market based rate in Exhibit C for use of the local circuit switching functionality for the affected facilities. 4.1.3.4 A featureless port is one that has a line port, switching facilities, and an interoffice port. A featured port is a port that includes all features then capable or a number of then capable features specifically requested by <<customer_name>>. Any features that are not currently then capable but are technically feasible through the switch can be requested through the NBR/BFR process. 4.1.3.5 BellSouth will provide to <<customer_name>> customized routing of calls: (i) to a requested directory assistance services platform; (ii) to an operator services platform pursuant to Section 10 of Attachment 2; (iii) for <<customer_name>>’s PIC’ed toll traffic in a two (2) PIC environment to an alternative OS/DA platform designated by <<customer_name>>. <<customer_name>> customers may use the same dialing arrangements as BellSouth customers. 4.1.3.6 Remote Switching Module functionality is included in Switching Capability. The switching capabilities used will be based on the line side features they support. 4.1.3.7 Switching Capability will also be capable of routing local, intraLATA, interLATA, and calls to international customer’s preferred carrier; call features (e.g. call forwarding) and Centrex capabilities. 4.1.3.8 Where required to do so in order to comply with an effective Commission order, BellSouth will provide to <<customer_name>> purchasing local BellSouth switching and reselling BellSouth local exchange service under Attachment 1, selective routing of calls to a requested directory assistance services platform or operator services platform. <<customer_name>> customers may use the same dialing arrangements as BellSouth customers, but obtain a <<customer_name>> branded service.

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

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

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!