Cloud Data Platform Preview Onboarding for Safe Endpoint Expansion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in efficiently monitoring and managing data from diverse compute assets in cloud environments, including data security, compliance, and anomaly detection, with a lack of comprehensive data analytics and real-time reporting capabilities.

Innovation Solution

A data platform is deployed to collect, process, and analyze data from cloud environments, utilizing agents to monitor compute assets, and generate polygraphs to identify anomalies and provide real-time insights through user interfaces, supported by data ingestion, processing, and storage resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If comprehensive data collection from diverse compute assets is implemented, then data analytics capability and monitoring coverage are improved, but system complexity and data processing overhead increase

Engineering Contradiction:
Improvemonitoring coverageVSAvoidsystem complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system segments data collection by implementing separate agents for different compute asset types (compute instances, storage, networking, containers, Kubernetes nodes) and organizing data into structured schemas. This segmentation allows comprehensive monitoring while managing complexity through modular, type-specific collection mechanisms.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements a universal data collection framework that handles multiple compute asset types through a common architecture. The agent framework, data schemas, and processing pipeline serve multiple purposes across different asset types, reducing overall system complexity while maintaining comprehensive coverage.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Speed

If real-time data processing and anomaly detection are implemented, then detection speed and security monitoring are improved, but computational resources and processing time increase

Engineering Contradiction:
Improvedetection speedVSAvoidcomputational resources
Core Design Contradiction:
SpeedVSUse of energy by moving object

Solution Approach 1:

The system performs preliminary data processing and normalization at the collection stage, transforming raw data into structured formats before analysis. This preliminary action reduces the computational burden during real-time anomaly detection by preorganizing data in efficient formats.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system extracts and prioritizes critical data elements for real-time analysis while filtering out less relevant information. By focusing computational resources on high-value data points and using sampling techniques, the system achieves fast anomaly detection without processing every data point in full detail.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If data from multiple cloud providers and diverse compute assets is collected, then monitoring comprehensiveness is improved, but data integration complexity and compatibility issues increase

Engineering Contradiction:
Improvemonitoring comprehensivenessVSAvoiddata integration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system employs a universal data schema and standardized agent framework that works across multiple cloud providers and compute asset types. This universality allows the same collection and processing infrastructure to handle diverse data sources without requiring provider-specific custom implementations.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system introduces standardized data schemas and format conversions as intermediaries between diverse data sources and the analysis pipeline. These intermediaries translate various cloud provider formats into a common internal representation, simplifying integration while maintaining comprehensive multi-provider monitoring.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Measurement precision

If detailed data collection and polygraph generation are implemented, then anomaly detection accuracy is improved, but data storage requirements and processing overhead increase

Engineering Contradiction:
Improveanomaly detection accuracyVSAvoiddata storage requirements
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The system extracts only the essential data elements needed for anomaly detection and polygraph generation, filtering out redundant information. By focusing on critical attributes and using selective collection, the system maintains detection accuracy while reducing storage requirements.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs preliminary data aggregation and indexing during collection, organizing data in ways that facilitate efficient polygraph generation and anomaly detection. This preorganization reduces the need for extensive data processing and storage during analysis phases.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12500911B1Expanding data collection from a monitored cloud environment
Publication Date: 2025.12.16 FORTINET INC
  • US12500911B1 patent drawing
  • US12500911B1 patent drawing
  • US12500911B1 patent drawing

AI summary

An example method includes: receiving, by a data platform configured to collect data from a plurality of service endpoints of a cloud environment, a request to onboard an additional service endpoint for data collection by the data platform; collecting, by the data platform operating in a preview mode of operation based on the request, first data from the plurality of service endpoints and second data from the additional service endpoint; monitoring, by the data platform operating in the preview mode of operation based on the request, for errors associated with the collecting of the first data and the second data; disabling, by the data platform when the monitoring detects an error within a defined period, data collection from the additional service endpoint; and integrating, by the data platform when the monitoring does not detect an error within the defined period, the additional service endpoint into normal data collection.