Distributed Server Security Policy Coordination

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing computer systems face challenges in effectively interfering with malware operations, particularly in e-commerce environments where 'Man in the Browser' attacks can intercept sensitive information, and existing security measures lack efficient coordination and scalability to adapt to changing threats.

Innovation Solution

A system of multiple servers that coordinate with each other to modify and serve web code in a polymorphic manner, applying security countermeasures dynamically and adapting to failures without centralized management, ensuring consistent security policies across the network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple servers are used to provide redundancy and scalability, then system reliability and adaptability improve, but device complexity and coordination difficulty increase

Engineering Contradiction:
Improvesystem reliabilityVSAvoidcoordination complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The server system implements self-organization through automatic leader election and dynamic policy distribution. When a leader server fails, remaining servers automatically elect a new leader without external intervention. The leader server dynamically identifies and distributes security policies to follower servers based on their current state, eliminating the need for manual configuration or centralized management infrastructure.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system employs dynamic role assignment where servers can transition between leader and follower roles based on operational status. The leader server dynamically adjusts policy distribution timing and content based on follower server responses and system state changes. This dynamic behavior allows the system to adapt to failures and scale without fixed hierarchical structures.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If security policies are dynamically changed to adapt to threats, then security effectiveness improves, but system complexity and synchronization difficulty increase

Engineering Contradiction:
Improvesecurity adaptabilityVSAvoidpolicy synchronization complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The leader server implements feedback-driven policy distribution by monitoring follower server states and adjusting policy updates accordingly. Follower servers provide feedback through their responses to leader communications, allowing the system to synchronize policies dynamically without requiring complex acknowledgment protocols or state tracking infrastructure.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

Security policies are prepared and staged in advance by the leader server before distribution. The leader server maintains a queue of pending policy updates and distributes them proactively to follower servers as they become available, rather than waiting for requests or events. This preliminary action ensures policies are ready for immediate deployment when needed.

Inventive Principle:
Principle #10Preliminary action

3Object-affected harmful factors

If polymorphic code alteration is applied to thwart malware, then security effectiveness improves, but processing time and computational overhead increase

Engineering Contradiction:
Improvemalware effectivenessVSAvoidcode processing time
Core Design Contradiction:
Object-affected harmful factorsVSLoss of time

Solution Approach 1:

The system applies polymorphic alteration selectively to only the portions of code most susceptible to malware exploitation, rather than transforming entire codebases. The leader server identifies critical security-sensitive code sections and applies transformations only to those areas, reducing processing overhead while maintaining security effectiveness against targeted attacks.

Inventive Principle:
Principle #16Partial or excessive action

4Stability of the object's composition

If centralized management is used to coordinate security policies, then policy consistency improves, but system scalability and fault tolerance worsen

Engineering Contradiction:
Improvepolicy consistencyVSAvoidsystem scalability
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The system segments the policy management function by distributing it across multiple leader servers over time. Rather than requiring a single centralized authority, the leader role and its associated policy distribution responsibilities are segmented and reassigned dynamically based on server availability. This allows policy consistency to be maintained through the current leader while enabling system scalability and fault tolerance.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9825995B1Coordinated application of security policies
Publication Date: 2017.11.21 SHAPE SECURITY INC
  • US9825995B1 patent drawing
  • US9825995B1 patent drawing
  • US9825995B1 patent drawing

AI summary

A computer-implemented method includes receiving, at a first server sub-system, content served to a client computing device; transcoding, with the first server sub-system, the received content using a policy received from a second security sub-system; determining, with the first server sub-system that the second server sub-system has likely ceased operating properly; receiving a request to vote on a leader server sub-system from one or more server sub-systems, and voting for from of the one or more server sub-systems; and subsequently transcoding received content according to a policy received from another of the server sub-systems that is not the second server sub-system.