Subcomponents Sample Clauses

Subcomponents. The SecaaS component is composed of some subcomponents, which belong to the aforementioned technology. In this sense, this solution is based on the ETSI GS NFV-SEC 013 specification [3], where different subcomponents are added to the initial architecture proposed for the NFV technology. The subcomponent architecture – and their interaction with other PALANTIR components – is presented in Figure 8 in more detail using the work performed during the first implementation and integration phase.
Sample 1
AutoNDA by SimpleDocs
Subcomponents. The TAR achieves its role in the PALANTIR architecture through three subcomponents, each implementing specific functions: • The Attestation Engine (AE) monitors SCHI by leveraging the Trusted Computing paradigm and extending it with runtime verification. Trusted Computing is the security paradigm, promoted by the Trusted Computing Group (TCG) [4] that builds on Roots of Trust (RoT) to protect critical data (e.g., cryptographic keys, secrets) and to detect subversion of the hardware, firmware, software, or configurations. In Trusted Computing, any firmware or software component is responsible for measuring any code or data that is security critical and to record the measurement in a RoT. This recursive architecture stops at the initial boot vector of a platform and the RoT, which together are called the Trusted Computing Base: the minimal set for component that are inherently trusted because their misbehaviour cannot be detected (i.e., they are not measured before being used). When the TAR wants to verify the integrity of a platform, the RoT is queried to securely retrieve the list of measurements recorded since boot through the Attestation Agent hosted in SCHI. Then the TAR compares this list of measurements with the expected software and configuration of the platform: an incorrect, missing, or additional measurement evidences an unexpected security posture of the platform: this protocol is called remote attestation. The expected baseline set of measurements are generated by a Reference Measurement plugin that is deployed in the SCO. This trust and attestation solution can be implemented using a Trusted Platform Module (TPM) [5] as the RoT, leveraging the Measured Boot feature of UEFI [6] and the Grub2 bootloader [7], and the Linux Integrity Measurement Architecture [8] on the platforms of the SCHI. While Trusted Computing mainly focuses on boot- and load-time measurement, coupled with periodic remote attestation, PALANTIR also supports runtime verification. The TAR leverages the memory inspection capability of the platform, when present, to detect any unexpected change of code or data already loaded in memory. Finally, the TAR verifies the hardware of the platforms by ensuring that their components have not been changed since manufacture – unless an authorised hardware modification happened. While such verification can be done through manual inspection of the platforms, the TAR automates such verification by leveraging emerging technologies in that field,...
Sample 1
Subcomponents. The PALANTIR Portal implements the aforementioned functionalities through some subcomponents, with the most important functionality being the real-time information stream, which depicts the current status of the infrastructure as well as any identified problems and alerts in real-time. Integration in this case is of utmost importance, as most components have some interaction with the Portal and its related subcomponents, which are listed below: • Central Portal and Security Dashboard User Interface (UI): The central Portal is the entry point for theplatform’s UI Through it, and depending on the user, views from the various implemented tools and mechanisms become accessible. These views include risks identification, analysis and management aspects, policy definition aspects, infrastructure management and orchestration aspects and billing, account, and performance visualisation aspects. These views are combined in the Security Dashboard UI. Key views in the dashboard UI are accounting views for tracking of profits, costs and purchases, and the visualisations of security analytics. • User management component: In order to achieve access control as well as the differentiation of views per stakeholder, a user management component is in place. Users, access control lists, and roles are kept in this subcomponent. • Indicators of Compromise (IoC) Database: This subcomponent exposes an IoC database, which allows for storage and communication of technical and non-technical information about malware samples, incidents, attack patterns, defence intelligence and attacker profiles. The IoC database can store all such information in standardised formats, such as Structured Threat Information Expression (STIX) [21] or Trusted Automated Exchange of Intelligence Information (TAXII) [22]. • Correlation mechanism: Automatic correlation mechanism that, by discovering relationships between attributes, can help when similar situations occur in different organizations. The attributes that, through correlation, provide recommended solutions, are indicators of malware, incidents, attacker profiles, and security intelligence. This mechanism makes heavy use of the IoC database for both storage and retrieval. This component facilitates knowledge sharing with Computer Emergency Response Teams (CERT) and Computer Incident Response Teams (CSIRT).
Sample 1
Subcomponents. The Attestation Engine is a distributed system that has subcomponents distributed throughout the PALANTIR infrastructure in order to maintain trustworthiness of the system.
Sample 1
Subcomponents. The FBM (Figure 6) is a fully virtualized system that consists of the Incidence Response (IR) and Recovery Service (RS) subcomponents. Both subcomponents are designed to carry out personalized intervention defined as a Finite State Machine (FSM). In more detail, the purpose of the FBM component is as follows: • A Finite State Machine (FSM) is a computing model that may be used to mimic sequential logic or to describe and regulate an execution flow. A state machine is a behaviour model with a finite number of states. Based on the current state and a provided input, the machine performs state transitions and creates outputs. A state is a description of a system's current state as it awaits the execution of a transition. • IR engine: a PALANTIR-protected infrastructure hosts one IR instance that is responsible for triggering mitigation policies when a threat/attack related to data breach is detected by the TI. • RS Engine: a PALANTIR-protected infrastructure hosts one RS instance that is responsible for triggering recovery policies when attestation faults are detected. In addition to automation and mitigation services offered by the SCO, the FSMs also include alerts/messages and interventions that require human intervention. In such cases, notifications or requests can be sent to the Dashboard based on the FSM result. The notification or request can then be handled by the PALANTIR operator.
Sample 1
Subcomponents 
Sample 1Sample 2

Related to Subcomponents

  • Components Patheon will purchase and test all Components (with the exception of Client-Supplied Components) at Patheon’s expense and as required by the Specifications.

  • Third Party Components The Products and Services may contain third party components (including open source software) subject to separate license agreements. To the limited extent a third party license expressly supersedes this XXXX, such third party license governs Customer’s use of that third party component.

  • Raw Materials Lonza shall procure all required Raw Materials as well as consumables other than those Raw Materials that are Customer Materials. Customer shall be responsible for payment for all consumables and Raw Materials ordered or irrevocably committed to be procured by Lonza hereunder. Upon cancellation of any Batch or termination of the Agreement, all unused Raw Materials shall be paid for by Customer within [***] days of invoice and at Customer’s option will either be (a) held by Lonza for future use for the production of Product, (b) delivered to Customer, or (c) disposed of by Lonza.

  • REPAIRED OR REPLACED PARTS / COMPONENTS Where the Contractor is required to repair, replace or substitute Product or parts or components of the Product under the Contract, the repaired, replaced or substituted Products shall be subject to all terms and conditions for new parts and components set forth in the Contract including Warranties, as set forth in the Additional Warranties Clause herein. Replaced or repaired Product or parts and components of such Product shall be new and shall, if available, be replaced by the original manufacturer’s component or part. Remanufactured parts or components meeting new Product standards may be permitted by the Commissioner or Authorized User. Before installation, all proposed substitutes for the original manufacturer’s installed parts or components must be approved by the Authorized User. The part or component shall be equal to or of better quality than the original part or component being replaced.

  • Unbundled Channelization (Multiplexing) 5.7.1 To the extent NewPhone is purchasing DS1 or DS3 or STS-1 Dedicated Transport pursuant to this Agreement, Unbundled Channelization (UC) provides the optional multiplexing capability that will allow a DS1 (1.544 Mbps) or DS3 (44.736 Mbps) or STS-1 (51.84 Mbps) Network Elements to be multiplexed or channelized at a BellSouth central office. Channelization can be accomplished through the use of a multiplexer or a digital cross-connect system at the discretion of BellSouth. Once UC has been installed, NewPhone may request channel activation on a channelized facility and BellSouth shall connect the requested facilities via COCIs. The COCI must be compatible with the lower capacity facility and ordered with the lower capacity facility. This service is available as defined in NECA 4.

  • Elements Defines the individual components under each indicator

  • Insulin Insulin will be treated as a prescription drug subject to a separate copay for each type prescribed.

  • Product ACCEPTANCE Unless otherwise provided by mutual agreement of the Authorized User and the Contractor, Authorized User(s) shall have thirty (30) days from the date of delivery to accept hardware products and sixty (60) days from the date of delivery to accept all other Product. Where the Contractor is responsible for installation, acceptance shall be from completion of installation. Failure to provide notice of acceptance or rejection or a deficiency statement to the Contractor by the end of the period provided for under this clause constitutes acceptance by the Authorized User(s) as of the expiration of that period. The License Term shall be extended by the time periods allowed for trial use, testing and acceptance unless the Commissioner or Authorized User agrees to accept the Product at completion of trial use. Unless otherwise provided by mutual agreement of the Authorized User and the Contractor, Authorized User shall have the option to run testing on the Product prior to acceptance, such tests and data sets to be specified by User. Where using its own data or tests, Authorized User must have the tests or representative set of data available upon delivery. This demonstration will take the form of a documented installation test, capable of observation by the Authorized User, and shall be made part of the Contractor’s standard documentation. The test data shall remain accessible to the Authorized User after completion of the test. In the event that the documented installation test cannot be completed successfully within the specified acceptance period, and the Contractor or Product is responsible for the delay, Authorized User shall have the option to cancel the order in whole or in part, or to extend the testing period for an additional thirty (30) day increment. Authorized User shall notify Contractor of acceptance upon successful completion of the documented installation test. Such cancellation shall not give rise to any cause of action against the Authorized User for damages, loss of profits, expenses, or other remuneration of any kind. If the Authorized User elects to provide a deficiency statement specifying how the Product fails to meet the specifications within the testing period, Contractor shall have thirty (30) days to correct the deficiency, and the Authorized User shall have an additional sixty (60) days to evaluate the Product as provided herein. If the Product does not meet the specifications at the end of the extended testing period, Authorized User, upon prior written notice to Contractor, may then reject the Product and return all defective Product to Contractor, and Contractor shall refund any monies paid by the Authorized User to Contractor therefor. Costs and liabilities associated with a failure of the Product to perform in accordance with the functionality tests or product specifications during the acceptance period shall be borne fully by Contractor to the extent that said costs or liabilities shall not have been caused by negligent or willful acts or omissions of the Authorized User’s agents or employees. Said costs shall be limited to the amounts set forth in the Limitation of Liability Clause for any liability for costs incurred at the direction or recommendation of Contractor.

  • Consumables During the design phase, Purchaser may participate in the selection of suppliers of consumables of the Supplier. In such case, the choice regarding the final selection of the said suppliers shall be mutually agreed between the Parties. Two suppliers shall be identified and selected for each type of consumables.

  • Combination Products If a LICENSED PRODUCT , DISCOVERY PRODUCT and/or THERAPEUTIC PROUCT is sold to any third party in combination with other products, devices, components or materials that are capable of being sold separately and are not subject to royalties hereunder (“OTHER PRODUCTS,” with the combination of products being referred to as “COMBINATION PRODUCTS” and the Other Product and Licensed Product in such Combination Product being referred to as the “COMPONENTS”), the NET SALES of such LICENSED PRODUCT, DISCOVERY PRODUCT and/or THERAPEUTIC PRODUCT included in such COMBINATION PRODUCT shall be calculated by multiplying the NET SALES of the COMBINATION PRODUCT by the fraction A/(A+B), where A is the average NET SALES price of such LICENSED PRODUCT, DISCOVERY PRODUCT and/or THERAPEUTIC PRODUCT in the relevant country, as sold separately, and B is the total average NET SALES price of all OTHER PRODUCTS in the COMBINATION PRODUCT in the relevant country, as sold separately. If, in any country, any COMPONENT is not sold separately, NET SALES for royalty determination shall be determined by the formula [C / (C+D)], where C is the aggregate average fully absorbed cost of the LICENSED PRODUCT, DISCOVERY PRODUCT and/or THERAPEUTIC PRODUCT components during the prior Royalty Period and D is the aggregate average fully absorbed cost of the other essential functional components during the prior Royalty Period, with such costs being determined in accordance with generally accepted accounting principles. To the extent that any SUBLICENSE INCOME relates to a COMBINATION PRODUCT or is otherwise calculated based on the value of one or more licenses or intellectual property rights held by the COMPANY, an AFFILIATE or SUBLICENSEE, COMPANY shall determine in good faith and report to THE PARTIES the share of such payments reasonably attributable to COMPANY’s or such AFFILIATE’s sublicense of the rights granted hereunder, based upon their relative importance and proprietary protection, which portion shall be the SUBLICENSE INCOME. THE PARTIES shall have the right to dispute such sharing determination in accordance with the dispute provisions of the AGREEMENT.

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