Security Capabilities Orchestration (SCO) Sample Clauses

Security Capabilities Orchestration (SCO). In the PALANTIR platform, the Security Capabilities Orchestration component oversees the overall management of the security capabilities (i.e., security network services, policies, configurations, and similar features), considering their deployment and reconfiguration, as well as part of their monitoring. Specifically, it oversees: • The interaction of the Security Orchestrator (SO) with the NFV Management and Orchestration (MANO) related to the SecaaS services registered in the Security Capabilities Catalogue (SCC): the onboarding of such packages, their instantiation/deployment and configuration in a given infrastructure (VIM), depending on the deployment mode (cloud, lightweight, edge). • The enforcement of the security policies and configuration provided as an output of threat mitigation recommendations or as result of attestation reports. At this layer, reconfiguration takes place on specific services running inside the SecaaS instances. • The monitoring of general or custom metrics on the SC instances and the NFVI environment, such as the VIM or partial data from the SCHI, such as its total availability of resources. Besides the monitoring, it permits the generation of alerts based that relate to specific metrics and thresholds; so, any registered legitimate condition that operates on a metric hitting a specific threshold can be reported, potentially used to display and/or enforce logic in upper layers. • The interaction with other PALANTIR components and the required retrieval, adaptation, and aggregation of any data to be used by such other components (e.g., for monitoring or attestation purposes). The SCO leverages 3rd party tools for the management of the NFVI infrastructure (VIM), on the orchestration of xNFs (NFV MANO). Such tools are integrated with this component yet, since alien to PALANTIR, these cannot be considered part of SCO and are thus not bundled with it.
AutoNDA by SimpleDocs

Related to Security Capabilities Orchestration (SCO)

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

  • Financial Management Standards The financial management systems of Grantee must meet the following standards:

  • 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 Monitoring City staff shall monitor, review, and evaluate the financial procedures of the Subrecipient through documents submitted to the City and on-site monitoring. The Subrecipient shall provide and make available to the City such reports and records that will be necessary for a proper financial evaluation. With reasonable notice being given to the Subrecipient, the City may schedule at least one on-site visit and other visits that may be needed during the course of this Agreement.

  • FINANCIAL MANAGEMENT AND OVERSIGHT Measure 2a Is the school meeting financial reporting and compliance requirements?

  • Financial Management (a) The Recipient shall ensure that a financial management system is maintained in accordance with the provisions of Section 2.09 of the Standard Conditions.

  • Patch Management All workstations, laptops and other systems that process and/or 20 store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or 21 transmits on behalf of COUNTY must have critical security patches applied, with system reboot if 22 necessary. There must be a documented patch management process which determines installation 23 timeframe based on risk assessment and vendor recommendations. At a maximum, all applicable 24 patches must be installed within thirty (30) calendar or business days of vendor release. Applications 25 and systems that cannot be patched due to operational reasons must have compensatory controls 26 implemented to minimize risk, where possible.

  • Financial Management Services ‌ Definition: Financial Management Services includes the planning, directing, monitoring, organizing, and controlling of the monetary resources of an organization. Examples: Service areas that are included under the Financial Management Services discipline include, but are not limited to the following:

  • 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

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

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