Cloud Native Application Threat Detection via Build Pipeline Webhook

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud native applications often deploy third-party and open-source containers that lack cyber security assessments, posing a risk as they progress through the development pipeline without being evaluated for potential threats.

Innovation Solution

A method and system are implemented to configure a webhook within the build pipeline that forwards exact copies of cloud native applications to a threat detection service for security assessment, allowing or halting the build process based on the assessment results.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If third-party and open-source containers are used without security assessment, then development speed and ease of deployment are improved, but security vulnerability and system reliability deteriorate

Engineering Contradiction:
Improvedevelopment speedVSAvoidsecurity vulnerability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs security assessment actions before the containers are deployed to the cloud native application. By scanning container images and detecting vulnerabilities in advance (during the build pipeline), the system prevents insecure containers from reaching production, thus resolving the contradiction between rapid deployment and security reliability

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The build pipeline acts as an intermediary between container creation and application deployment. It inserts a security scanning step that mediates between the speed of development and the requirement for security assessment, allowing containers to be quickly built but not immediately deployed without passing security validation

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If security assessment is performed on all containers, then system reliability is improved, but build pipeline complexity and processing time increase

Engineering Contradiction:
Improvesecurity assessment coverageVSAvoidbuild pipeline complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The security assessment is segmented into discrete scanning steps within the build pipeline. Instead of a monolithic security check, the system breaks down the assessment into specific phases (image scanning, vulnerability detection, risk evaluation) that can be independently configured and executed, reducing overall complexity while maintaining comprehensive coverage

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system enables self-service security assessment where the build pipeline automatically scans and evaluates containers without requiring manual intervention. The automated nature of the process reduces operational complexity while ensuring consistent security assessment coverage across all containers

Inventive Principle:
Principle #25Self-service

3Reliability

If manual security assessment is required from developers, then security vulnerability is reduced, but developer workload and time consumption increase

Engineering Contradiction:
Improvesecurity vulnerabilityVSAvoiddeveloper time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The build pipeline performs self-service security assessment automatically. Instead of requiring developers to manually scan and validate containers, the system autonomously executes security scans, detects vulnerabilities, and makes deployment decisions, thereby eliminating developer time consumption while maintaining high security standards

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback mechanisms where security assessment results automatically feed back into the build pipeline. When vulnerabilities are detected, the system provides immediate feedback to block deployment, and when containers pass assessment, feedback allows progression. This automated feedback loop eliminates manual developer review time while ensuring security reliability

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10685115B1Method and system for implementing cloud native application threat detection
Publication Date: 2020.06.16 EMC IP HLDG CO LLC
  • US10685115B1 patent drawing
  • US10685115B1 patent drawing
  • US10685115B1 patent drawing

AI summary

A method and system for implementing cloud native application threat detection. Specifically, the disclosed method and system entail configuring a webhook within a build pipeline for cloud native applications, which when triggered by the detection of modifications to container configuration and/or definition files associated with the cloud native applications, forwards exact copies of the cloud native applications to a threat detection service for cyber security assessing. Further, based on the assessing, cloud native applications may be impeded from continuing, or alternatively, may be permitted to continue along, the build pipeline.