Security Orchestrator Sample Clauses

Security Orchestrator. The architecture of the Security Orchestrator (SO) was first introduced in D3.1 and underwent minor alterations. Yet, overall the same interactions and distribution of logic still apply. This subcomponent contains the following modules: (i) Authentication and Authorisation Control (AAC); (ii) API; (iii) Attestation and Remediation (ATR); (iv) Configuration (CFG); (v) Life-Cycle Management (LCM); (vi) Monitoring (MON); (vii) Package (PKG); (viii) Policies (POL). The SO interacts with both the PALANTIR components from WP3 (i.e. with the SCs and SCC) and from WP4, such as with the Service Matching (SM), TAR and Dashboard. It also interacts with some third-party tools that are not considered part of the PALANTIR platform itself. This is the case of Open Source MANO (OSM), acting as the Network Function Virtualisation Orchestrator (NFVO); as well as sending notification events through the Xxxxx message broker and requesting low-level infrastructure information, directly requested to the Kubernetes cluster – which, in the end, act as the Virtualised Infrastructure Manager (VIM). The NFVO is a key piece for the SC orchestration, as it allows onboarding or registering the SCs (or VNFs and NSs) and managing its life-cycle operations. The SO leverages such functionality and complements with logic not covered by the NFVO, such as keeping observability on the managed deployment and protected infrastructure, track specific monitoring information or nodes, determining the adequacy of deploying and configuring or reuse an instance to directly apply the configuration or bind actions and infrastructure to specific tenants, among others.
Sample 1
AutoNDA by SimpleDocs
Security Orchestrator. The SO comprises all modules related to the orchestration and life-cycle management of SCs, along with its monitoring. Given the central position it occupies in the architecture, it also provides ancillary functionality to other components and subcomponents within WP3 and WP4. Table 3.2-1 describes how the requirements map to the technical specifications that were fulfilled in the SO subcomponent, as well as the internal modules that contribute to each specification. The next subsection explains in detail the changes on the specifications and/or requirements. Table 3.2-1: adapted technical specifications for SO. Req. ID Requirement description A A C A P I A T R C F G L C M M O N P K G P O L
Sample 1
Security Orchestrator. The implementation of the SO continued from the stage in D3.1, both in terms of adopted technologies and regarding specific implementation choices per module. There were a number of changes from the landscape depicted in D3.1, which are described in the following section.
Sample 1
Security Orchestrator. 2.1.4.1 Function The Security Orchestrator (SO) functions provided in deliverable D2.2 [27] have been extended to orchestrate and enforce the new 5G security slice policies. This is, apart from regular security policies orchestration and enforcement, 5G security slice policies can be orchestrated and enforced. To this aim, new features like multiple orchestration and allocation algorithms are provided. In fact, Trust- based 5G security slice orchestration and allocation has been provided as orchestration algorithm for 5G slices. As it also drives the security management by interacting through the integration fabric with different MANOs and Controllers, Slice MANO interactions are also provided as new feature. As part of the evolved functionalities, proactive/reactive policies enforcement contemplates deployment / configuration of 5G slices as well as the dynamic configuration of each 5G service/security asset/enabler that compose the slice. The SO feeds data services with enforcement results, and it is also fed from data services to retrieve infrastructure information used during orchestration and allocation processes.
Sample 1
Security Orchestrator. The SO comprises all modules related to the orchestration and life-cycle management of SCs, along with its monitoring. Given the central position it occupies in the architecture, it also provides ancillary functionality to other components and subcomponents within WP3 and WP4. Table 3 describes how the requirement maps to the technical specification that is to be fulfilled in the SO subcomponent, as well as the internal modules that contribute to the specification. Table 3: technical specifications for SO. Req. ID Requirement description A A C A P I A T R C F G L C M M O N P K G P O L Document name: D3.1 PALANTIR Secure Services Ecosystem - First Release Page: 31 of 60 Reference: 1.0 Dissemination: PU Version: 1.0 Status: Final
Sample 1

Related to Security Orchestrator

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

  • Security Badging Any Company employee, or any employee of its contractors or agents, that require unescorted access to the Security Identification Display Area (SIDA) to perform work under this Agreement will be badged with an Airport identification badge (hereinafter referred to as "Badge") provided by Authority’s ID Badging Department and will be subject to an FBI fingerprint-based criminal history records check (CHRC) and an annual Security Threat Assessment (STA). A new or renewed Badge will not be issued to an individual until the results of the CHRC and the STA are completed and indicate that the applicant has not been convicted of a disqualifying criminal offense. If the CHRC or STA discloses a disqualifying criminal offense, the individual’s new or renewed badge application will be rejected. The costs of the CHRC and the annual STA will be paid by Company. These costs are subject to change without notice, and Company will be responsible for paying any increase in the costs. All badged employees of Company and its contractors or agents will comply with Authority's regulations regarding the use and display of Badges. Company will be assessed a fine for each Badge that is lost, stolen, unaccounted for or not returned to Authority at the time of Badge expiration, employee termination, termination of the Agreement, or upon written request by Authority. This fine will be paid by Company within 15 days from the date of invoice. The fine is subject to change without notice, and Company will be responsible for paying any increase in the fine. If any Company employee is terminated or leaves Company’s employment, Authority must be notified immediately, and the Badge must be returned to Authority promptly.

  • Contractor Security Clearance Customers may designate certain duties and/or positions as positions of “special trust” because they involve special trust responsibilities, are located in sensitive locations, or have key capabilities with access to sensitive or confidential information. The designation of a special trust position or duties is at the sole discretion of the Customer. Contractor or Contractor’s employees and Staff who, in the performance of this Contract, will be assigned to work in positions determined by the Customer to be positions of special trust, may be required to submit to background screening and be approved by the Customer to work on this Contract.

  • Security Bond The security bond provides protection to Owner if Contractor presents an acceptable guaranteed maximum price (“GMP”) to Owner but is unable to deliver the required payment and performance bonds within the time period stated below.

  • Security Officer Contractor shall designate a Security Officer to oversee its data security program who shall be responsible for carrying out the requirements of this section and for communicating on security matters with the Department.

  • Password Security You are responsible for maintaining adequate security and control of any and all User IDs, Passwords, hints, personal identification numbers (PINs), or any other codes that you use to access the Account. Do not discuss, compare, or share information about your account number or password unless you are willing to give them full use of your money. Any loss or compromise of the foregoing information and/or your personal information may result in unauthorized access to your Account by third-parties and the loss or theft of any funds held in your Account and any associated accounts, including your Account. Checks and electronic withdrawals are processed by automated methods, and anyone who obtains your account number or access device could use it to withdraw money from your account, with or without your permission. You are responsible for keeping your email address and telephone number up to date in order to receive any notices or alerts that we may send you. We assume no responsibility for any loss that you may sustain due to compromise of your account login credentials due to no fault of ours and/or your failure to follow or act on any notices or alerts that we may send to you. If you believe your Account information has been compromised, or that someone has transferred or may transfer money from your account without your permission, contact us immediately, through Synapse, at xxxx@xxxxxxxxx.xxx or call at +0(000) 000-0000. You agree to promptly review all Account and transaction records and other Communications that we make available to you and to promptly report any discrepancy to us.

  • Cybersecurity (i)(x) There has been no security breach or other compromise of or relating to any of the Company’s or any Subsidiary’s information technology and computer systems, networks, hardware, software, data (including the data of its respective customers, employees, suppliers, vendors and any third party data maintained by or on behalf of it), equipment or technology (collectively, “IT Systems and Data”) and (y) the Company and the Subsidiaries have not been notified of, and has no knowledge of any event or condition that would reasonably be expected to result in, any security breach or other compromise to its IT Systems and Data; (ii) the Company and the Subsidiaries are presently in compliance with all applicable laws or statutes and all judgments, orders, rules and regulations of any court or arbitrator or governmental or regulatory authority, internal policies and contractual obligations relating to the privacy and security of IT Systems and Data and to the protection of such IT Systems and Data from unauthorized use, access, misappropriation or modification, except as would not, individually or in the aggregate, have a Material Adverse Effect; (iii) the Company and the Subsidiaries have implemented and maintained commercially reasonable safeguards to maintain and protect its material confidential information and the integrity, continuous operation, redundancy and security of all IT Systems and Data; and (iv) the Company and the Subsidiaries have implemented backup and disaster recovery technology consistent with industry standards and practices.

  • E7 Security E7.1 The Authority shall be responsible for maintaining the security of the Authority’s Premises in accordance with its standard security requirements. The Contractor shall comply with all security requirements of the Authority while on the Authority’s Premises, and shall ensure that all Staff comply with such requirements.

  • Security Management The Contractor shall comply with the requirements of the DOD 5200.1-M and the DD Form 254. Security of the Contractor’s electronic media shall be in accordance with the above documents. Effective Program Security shall require the Contractor to address Information Security and Operations Security enabled by the Security Classification Guides. The Contractor’s facility must be able to handle and store material up to the Classification Level as referenced in Attachment J-01, DD Form 254.

  • UNION SECURITY AND DUES CHECK-OFF 4:01 The Employer agrees to deduct the amount of monthly dues as determined by the Union from the salaries of each and every employee covered by this Agreement. The Employer also agrees to deduct from each and every employee covered by this Agreement the amount of any general assessment levied by the Union, with the proviso that such an assessment shall be limited to one (1) per calendar year, and that such assessment formula can be operated through the Employer‟s present payroll system.

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