Dell Products Inc.

Emc IP Holding Company LLC

Raveendra Babu Madala

Santosh Hanamant Gore

Viswanath Ponnuru

Rishi Mukherjee

Sumanth Vidyadhara

Prasoon Kumar Sinha

Anusha Bhaskar

Sudhir Vittal Shetty

Chandrashekar Nelogal

Parmeshwr Prasad

Ravishankar Kanakapura Nanjundaswamy

Muniswamy Setty K S

Ravishankar N Kanakapura

Sujit Jadhav

Kevin Thomas Marks

Srikanth Kondapi

Vivekanandh Narayanasamy Rajagopalan

Ramesha He

Amit Pratap Singh

Krishnakumar Narasimhan

Rushyendra Velamuri

Soorej Ponnandi

Vaideeswaran G

Samir Paitod

Vivek Sundaresan

Ravikanth Chaganti

Vijay Bharat Nijhawan

Wade Andrew Butcher

Cyril Jose

Balaji Bapu Gururaja Rao

Krishnaprasad Koladi

Abhishek Gupta

Rajib Saha

Donald W Gerhart

Pushkala Iyer

Terry Wayne Liles

Deepu Syam Sreedhar M

Akshata Sheshagiri Naik

Raghavendra Venkataramudu

Praveen S Lalgoudar

Abhijit Rajkumar Khande

Chandrasekhar Revuri

Alaa A Yousif

Chandrasekhar R

Raajeev Kalyanaraman

Palani Raja Zeavelou

Shuva Brata Deb

Winston X Fernandes

Sivakumar Swamy

Sathish Kumar Ponnusamy

Muniswamy Setty

Bala Balaji Gupta M

Sura Rajashekar Reddy

Vulnerability proofing a node (e.g., an Information handling System (IHS)) while onboarding the node to a container orchestration platform may include detecting onboarding of the node IHS to the container orchestration platform, which includes vulnerability management service instructions and an onboarding handler component. The onboarding including configuring (a) hardware component(s) of the IHS, and the vulnerability proofing may include executing the vulnerability management service instructions, which results in accessing (a) catalog(s) specifying known vulnerabilities of hardware components of the IHS and determining whether any of the configuring of any of the configurations of (a) hardware component(s) of the IHS are identified as vulnerable in the catalog(s). The onboarding of the IHS to the container orchestration platform by the IHS may be blocked until configuring the hardware component(s) of the IHS is modified to include no configuring of the hardware component(s) with vulnerabilities identified in the catalog(s).

Vulnerability proofing a node while onboarding to a container orchestration platform

Vulnerability proofing container orchestration platform deployment includes a remote access controller detecting a container orchestration platform installer comprising vulnerability management service instructions and executing the vulnerability management service instructions. This causes the remote controller to identify configurations for one or more of the hardware component(s) of the IHS in the container orchestration platform installer, access a plurality of catalogs specifying known vulnerabilities of hardware components and determine whether the hardware component configuration(s) in the container orchestration platform installer are identified as vulnerable in one or more of the catalogs. The remote controller blocks use of the container orchestration platform installer by the IHS until the hardware component configurations within the container orchestration platform installer are modified to include no configurations with vulnerabilities identified in the plurality of catalogs.

Vulnerability proofing container orchestration platform deployment

Managing computing workloads within a computing environment including identifying computing parameters of datacenter elements of each computing cluster of a computing environment; for each computing cluster of the computing environment: determining a health of the power device of the computing cluster; for each computing node of the computing cluster: determining a processing load of the computing node; determining a computing cost associated with a geo-location of the computing node; calculating, for each computing cluster, an availability of computing resources of the computing cluster based on the computing parameters of the data center elements of the computing cluster, the health of the power device of the computing cluster, the processing load of each computing node of the computing cluster, and the computing cost of each computing node of the computing cluster; generating a ranking of each computing cluster based on the availability of the computing resources of the computing cluster.

Managing computing workloads within a computing environment

Systems and methods are provided for vulnerability proofing the administration of hardware components of an IHS. A proposed configuration for a hardware component of the IHS is detected. Multiple catalogs specifying known vulnerabilities of hardware components are accessed, such as a catalog of known vulnerabilities provided by a manufacturer of the hardware component and such as a catalog of known vulnerabilities provided by a manufacturer of the IHS. The proposed configuration of the hardware component is evaluated as being vulnerable in the first catalog and also in the second catalog. If the proposed configuration is identified as vulnerable in either the first catalog or in the second catalog, the hardware component is disabled until the proposed configurations for the hardware component are changed to include no configurations with vulnerabilities identified in either the first or second catalogs.

Systems and methods for aggregated vulnerability proofing of an IHS

Systems and methods are provided for vulnerability proofing the launching of application instances by an IHS (Information Handling System). The launching of an application instance on the IHS is detected, where the application instance is launched using an application template that includes configurations for one or more hardware components of the IHS. One or more catalogs are accessed that specify known vulnerabilities of hardware components. Hardware component configurations included in the application template are identified as vulnerable in one or more of the catalogs. If the application template includes configurations that are identified as vulnerable in the catalogs, launching of the application is prevented until the hardware component configurations within the application template are modified to include no configurations with vulnerabilities identified in the catalogs.

Systems and methods for vulnerability proofing when configuring an IHS

A datacenter includes a heterogeneous node group efficiency management system that is coupled to node devices and that, based on a power consumption and performance associated with each node device, generates node group rankings that it uses to group subsets of the node devices into respective heterogeneous node groups. The heterogeneous node group efficiency management system then identifies workload characteristic(s) and performance requirement(s) for a workload provided for deployment, identifies a first heterogeneous node group that satisfies the performance requirement for the workload, and identifies first node device(s) that are included in the first heterogeneous node group and that are configured to perform the first workload having the workload characteristic(s) with a higher power efficiency than second node device(s) that are included in the first heterogeneous node group. The heterogeneous node group efficiency management system then deploys the workload on the first node device(s) in the first heterogeneous node group.

Heterogeneous node group efficiency management system

Systems and methods are provided for vulnerability proofing updates to an IHS (Information Handling System). An update system receives a notification of an update including updated configurations for hardware components of the IHS. The update system queries the IHS for vulnerability proofing requirements for updates that modify configurations of hardware components of the IHS. In response to the query, vulnerability proofing requirements are retrieved from a persistent data storage of the IHS and transmitted to the update system, where the vulnerability proofing requirements specify catalogs of known vulnerabilities of hardware components. The update system determines whether the updated configurations are identified as vulnerable in the one or more of catalogs. If the updated configurations are not identified in the catalogs, the update is transmitted to the IHS. If configurations from the update are identified in the catalogs, the update is terminated and the IHS is notified.

Systems and methods for vulnerability proofing when generating IHS updates

Systems and methods are provided for vulnerability proofing the installation of new hardware components in an IHS (Information Handling System). The coupling of a new hardware component to the IHS is detected. A profile is identified that is to be used in provisioning the new hardware component that has been coupled to the IHS. The profile may include various configurations for the coupled hardware component. One or more catalogs are accessed that specify known vulnerabilities of hardware components. Configurations from the profile for the coupled hardware component are used to identify any configuration that have known vulnerabilities that are listed in the catalogs. If known vulnerabilities are identified in the configuration for the new hardware component, further use of the new hardware component by the IHS is disabled until the profile is modified to include no configurations with vulnerabilities identified in the catalogs.

Systems and methods for vulnerability proofing when adding and replacing IHS hardware

Systems and methods provide vulnerability proofing procedures for booting of an IHS (Information Handling System). A request to boot the IHS is detected. One or more boot configurations are determined that include configurations for operation of one or more of the hardware components of the IHS. One or more catalogs are accessed that specify known vulnerabilities of hardware components. The boot configurations are used to identify any hardware component configurations that have known vulnerabilities that are listed in the catalogs. If known vulnerabilities are identified in the boot configuration, further booting of the IHS may be disabled until the boot configuration is modified to include no configurations with vulnerabilities identified in the catalogs.

Systems and methods for vulnerability proofing when booting an IHS

In one or more embodiments, one or more systems, one or more methods, and/or one or more processes may determine first thermal attribute values associated with multiple information handling systems (IHSs) with respect to a period of time as the IHSs execute a first workload; determine multiple variance ranges respectively associated with the first thermal attributes; periodically determine second thermal attribute values associated with the IHSs as the IHSs execute a second workload; determine that a thermal attribute value of the second thermal attribute values exceeds a respective variance range of the variance ranges as a first information handling system (IHS) of the IHSs executes the second workload; generate an alert based at least on the thermal attribute value exceeding the respective variance range; and in response to the alert, transfer at least a portion of the second workload from the first IHS to a second IHS of the IHSs.

Managing workload execution across MultipleDiffering information handling systems UtilizingThermal profiles

Systems and methods are provided for vulnerability proofing updates to an IHS. An update package is detected that includes configurations for one or more of the hardware components of the IHS. One or more catalogs are accessed that specify known vulnerabilities of hardware components. The updated configurations of the hardware component that are included in the update package are used to identify any hardware component configurations that have known vulnerabilities that are listed in the catalogs. If known vulnerabilities are identified in the updated configurations, further booting of the IHS may be disabled until the update package is modified to include no configurations with vulnerabilities identified in the catalogs.

Systems and methods for vulnerability proofing when updating an IHS

Systems and methods are provided for vulnerability proofing an IHS (Information Handling System) while being administered using a bootable image. Launching of a bootable image by the one or more CPUs is detected and one or more IHS configurations to be made using the bootable image are identified. One or more catalogs specifying known vulnerabilities of hardware components are accessed and used to determine whether any of the IHS configurations to be made using the bootable image are identified as vulnerable in one or more of the catalogs. Configuration of the IHS using the bootable image is blocked until the configurations to be made using the bootable image are modified to include no configurations with vulnerabilities identified in the plurality of catalogs.

Systems and methods for vulnerability proofing when using a bootable image

Systems and methods provided vulnerability proofing of an IHS (Information Handling System) while it is being provisioned for deployment, such as upon receipt at a datacenter. An initial provisioning of the IHS is detected, where no provisioning of the IHS has been conducted other than the factory provisioning of the IHS. A profile is identified that is to be used in provisioning the IHS, where the profile includes configurations for one or more hardware components of the IHS. One or more catalogs are accessed that specify known vulnerabilities of hardware components. For each of the hardware configurations in the profile, configurations that are vulnerable are identified based on the catalogs of known vulnerabilities. If vulnerabilities are identified, further provisioning of the IHS is blocked until the profile is modified to include no hardware configurations with vulnerabilities identified in the catalogs.

Systems and methods for vulnerability proofing during IHS provisioning

Systems and methods are provided for vulnerability proofing the use of risk scores in the administration of hardware components of an IHS (Information Handling System). Proposed configurations for a first of the hardware components of the IHS are detected, where the proposed configurations are associated with a risk score. Catalogs specifying known vulnerabilities of hardware components are accessed and used to determine whether any of the proposed configurations of the first hardware component are identified as vulnerable in one or more of the catalogs. When a vulnerability for the proposed configuration is identified in the catalogs, the risk score of the configuration is increased based on the vulnerabilities identified in the plurality of catalogs. When the risk score is increased to an elevated level, the hardware component is disabled until the proposed configurations are changed to include no configurations with vulnerabilities identified in the catalogs.

Systems and methods for context-aware vulnerability risk scores

Systems and methods are provided for vulnerability proofing the use of machine learning recommendations by an IHS. A machine learning recommendation is detected that provides configurations for one or more of the hardware components of the IHS. Catalogs specifying known vulnerabilities of hardware components are accessed to determine whether any of the hardware configurations from the machine learning recommendations are identified as vulnerable in one or more of the catalogs. If a machine learning recommendation is identified as vulnerable, use of the machine learning recommendation by the IHS is blocked until the recommendation is modified to include no recommended hardware configurations with vulnerabilities identified in the catalogs.

Systems and methods for vulnerability proofing machine learning recommendations

Growing community of inventors

Bengaluru, India

Raveendra Babu Madala