Network Security Policy Self-Healing Across Functional Domains

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Enterprises face challenges in configuring network security policies across multiple cloud networks, as policies copied from one subsystem may not be ideal for another, leading to vulnerabilities and inefficiencies.

Innovation Solution

A system analyzes security policies across functional domains to identify and update policies that are not being used, recommending adjustments or removals to ensure they are appropriate for the new environment, thereby reducing vulnerabilities and simplifying configuration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If security policies are copied from one subsystem to another to save configuration time, then configuration efficiency is improved, but the policies may become inappropriate for the new environment creating security vulnerabilities

Engineering Contradiction:
Improveconfiguration efficiencyVSAvoidsecurity appropriateness
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary analysis of security policies before they are deployed to functional domains. The policy analysis component examines copied policies to identify potential issues with network flow, security groups, and infrastructure compatibility before deployment, preventing inappropriate policies from being applied and creating security vulnerabilities.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where policy analysis results are used to improve future policy copying and deployment decisions. The system learns from analyzed policy issues and adjusts its behavior to avoid similar problems, continuously improving the balance between configuration efficiency and security appropriateness.

Inventive Principle:
Principle #23Feedback

2Reliability

If security policies are manually configured for each subsystem to ensure appropriateness, then security reliability is improved, but the configuration process becomes time-consuming and complex

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

Solution Approach 1:

The system enables copying of security policies between functional domains while incorporating automated analysis. Instead of requiring manual recreation of policies for each subsystem, the system copies policies efficiently and then analyzes them to ensure appropriateness, significantly reducing configuration time while maintaining security reliability.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The policy analysis component automatically examines copied policies for appropriateness without requiring manual intervention. The system self-services by analyzing network flow data, security group configurations, and infrastructure details to determine if copied policies are suitable, eliminating the need for time-consuming manual verification.

Inventive Principle:
Principle #25Self-service

3Speed

If copied security policies are deployed without analysis to maximize speed, then deployment speed is improved, but inappropriate policies create security vulnerabilities

Engineering Contradiction:
Improvedeployment speedVSAvoidsecurity vulnerabilities
Core Design Contradiction:
SpeedVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary policy analysis before deployment to identify potential security vulnerabilities. By analyzing policies in advance rather than after deployment, the system maintains fast deployment speeds while preventing harmful policies from being applied, avoiding the need for slow post-deployment remediation.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If all security policies are retained after copying to ensure coverage, then security coverage is improved, but unused or inappropriate policies increase system complexity and potential vulnerabilities

Engineering Contradiction:
Improvesecurity coverageVSAvoidpolicy management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The policy analysis component extracts and identifies inappropriate or unused policies from the copied set. By separating problematic policies from appropriate ones, the system maintains necessary security coverage while removing unnecessary complexity and potential vulnerabilities, achieving a optimized policy set.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS12526323B2Self healing network security policy management
Publication Date: 2026.01.13 SALESFORCE INC
  • US12526323B2 patent drawing
  • US12526323B2 patent drawing
  • US12526323B2 patent drawing

AI summary

In some embodiments, a method determines a first functional domain that includes a group of security policies that have been copied from a second functional domain. Network flow data is queried to determine network traffic that is associated with a security policy in the group of security policies in the first functional domain. The method analyzes utilization of the security policy based on the network traffic. Based on the analyzing, a recommendation is generated to change the security policy in the first functional domain.