HTML Form Source Code Analysis for Dynamic Security Rule Derivation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing web application security measures are inconsistently implemented, leaving vulnerabilities in web forms that can be exploited by attackers to breach network security.

Innovation Solution

A computer-implemented method and system that dynamically derive detection rules from the source code of HTML forms, allowing for real-time blocking of malicious parameter content that violates these derived rules.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If safeguards are implemented to protect web forms, then security protection is improved, but implementation consistency deteriorates

Engineering Contradiction:
Improvesecurity protectionVSAvoidimplementation consistency
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The system automatically derives protection rules from the HTML form source code itself, eliminating the need for manual rule configuration. The HTML code contains embedded rules (such as required fields, pattern constraints, min/max values) that the system extracts and applies automatically, making the protection mechanism self-configuring and consistent without requiring developer intervention.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system introduces an intermediary component that sits between the web server and the attacker, automatically analyzing incoming requests against derived rules. This intermediary layer handles the complexity of rule derivation and enforcement, shielding developers from implementation inconsistencies while maintaining strong security protection.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If manual rule configuration is used for protection, then rule accuracy is improved, but automation level deteriorates

Engineering Contradiction:
Improverule accuracyVSAvoidautomation level
Core Design Contradiction:
Measurement precisionVSExtent of automation

Solution Approach 1:

The protection rules are automatically derived from the HTML form source code itself, which contains the authoritative definition of valid inputs. The system extracts rules such as required fields, pattern constraints, and value ranges directly from the HTML attributes, ensuring high accuracy without manual configuration while achieving full automation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system handles multiple types of HTML form validation rules universally through a single automated derivation process. It can extract various constraint types (patterns, min/max values, required fields) from different HTML elements and apply them consistently, achieving both high accuracy and full automation across diverse form scenarios.

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

3Reliability

If comprehensive protection rules are applied, then security coverage is improved, but system complexity deteriorates

Engineering Contradiction:
Improvesecurity coverageVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system extracts only the necessary protection rules directly from the HTML form source code, separating the essential validation constraints from the rest of the form definition. By deriving rules solely from embedded HTML attributes rather than requiring separate rule configurations, the system achieves comprehensive security coverage while minimizing added complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS12335312B2Dynamic protection of web forms
Publication Date: 2025.06.17 SAP SE
  • US12335312B2 patent drawing
  • US12335312B2 patent drawing
  • US12335312B2 patent drawing

AI summary

The source code of an HTML form can be analyzed to derive parameter rules that are subsequently enforced when apparent content of the HTML form is received. Such parameter rules can be drawn from client-side restrictions that are extracted from the HTML source, which are then enforced to prevent content violating the rules from reaching the backend. A proxy can sit between the application and the apparent browser. Dynamically generated HTML can be supported via a headless browser that mirrors HTML that would be present at a browser. Useful for preventing HTML form-based attacks and identifying clear cases of malicious HTML form requests.