Security Capabilities Catalogue Sample Clauses

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.4). Of these interactions, the most significant ones involve the SO and the dashboard. In summary, the SCC offers several key functionalities, including the registration and validation of SCs, secure onboarding of service components to the SO, search functionality within the catalogue, and access to metadata for SCs by the dashboard and other PALANTIR components.
Sample 1
AutoNDA by SimpleDocs
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 3.3-1 describes how each requirement maps to the technical specification that is to be fulfilled in the SCC subcomponent, as well as the internal modules that contribute to the specification. Table 3.3-1: adapted technical specifications for SCC. Req. ID Requirement description SCR SCDV SCPM SCC-O SCS SCMA
Sample 1
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. Figure 4.3-1: SCC technologies layout.
Sample 1
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...
Sample 1
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. Req. ID Requirement description SCR SCDV SCPM SCC-O SCS SCMA 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.
Sample 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.

  • Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.

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

  • 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

  • Exception Where Databases Contain Sufficient Information A Reporting Financial Institution is not required to perform the paper record search described in subparagraph D.2. of this section if the Reporting Financial Institution’s electronically searchable information includes the following:

  • Industry Troubleshooter Where a difference arises between the parties relating to the dismissal, discipline, or suspension of an employee, or to the interpretation, application, operation, or alleged violation of this Agreement, including any question as to whether a matter is arbitrable, during the term of the Collective Agreement, Xxxxx XxXxxxxxxx, Xxxx Xxxxxx, Xxxxx Xxxxxxxx, or a substitute agreed to by the parties, shall at the request of either party:

  • wire Unbundled ISDN Digital Loops These will be provisioned according to industry standards for 2-Wire Basic Rate ISDN services and will come standard with a test point, OC, and a DLR. NewPhone will be responsible for providing BellSouth with a Service Profile Identifier (SPID) associated with a particular ISDN-capable Loop and customer. With the SPID, BellSouth will be able to adequately test the circuit and ensure that it properly supports ISDN service.

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

  • Mail Order Catalog Warnings In the event that, the Settling Entity prints new catalogs and sells units of the Products via mail order through such catalogs to California consumers or through its customers, the Settling Entity shall provide a warning for each unit of such Product both on the label in accordance with subsection 2.4 above, and in the catalog in a manner that clearly associates the warning with the specific Product being purchased. Any warning provided in a mail order catalog shall be in the same type size or larger than other consumer information conveyed for such Product within the catalog and shall be located on the same display page of the item. The catalog warning may use the Short-Form Warning content described in subsection 2.3(b) if the language provided on the Product label also uses the Short-Form Warning.

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