Website Locking via Read-Only Permission Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing website hosting systems lack optimal means to protect against website corruption, particularly in files, directories, folders, databases, and database tables, making them vulnerable to hacking and unauthorized modifications.

Innovation Solution

A system and method for locking a website by using a website management server to change access permissions to 'read-only' for directories, folders, files, and database tables, thereby preventing unauthorized modifications, and a method to suggest access permission changes by scanning for static content to recommend 'read-only' settings.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If access permissions are changed to 'read-only' for website files and databases, then security against unauthorized modifications is improved, but the ability to make dynamic changes to the website is worsened

Engineering Contradiction:
ImprovesecurityVSAvoiddynamic content modification
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system segments website files into different categories (static vs. dynamic) and applies different access permissions to each segment. Static files receive read-only permissions while dynamic files retain read-write permissions, allowing security to be applied selectively rather than universally.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different access permissions are applied to different parts of the website based on their characteristics. The system identifies specific files and directories that require read-only protection versus those that need write access, creating local variations in permission quality rather than a uniform permission structure.

Inventive Principle:
Principle #3Local quality

2Object-affected harmful factors

If access permissions are changed to 'read-only' for all website files, then protection against hacking is improved, but the functionality of dynamic content is worsened

Engineering Contradiction:
Improvehacking vulnerabilityVSAvoidwebsite functionality
Core Design Contradiction:
Object-affected harmful factorsVSEase of operation

Solution Approach 1:

Instead of applying read-only permissions to all website files (excessive action), the system applies read-only permissions only to static files that do not require dynamic modification. This partial application of the permission change protects against hacking while preserving the functionality of dynamic content.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system segments the website file structure to distinguish between static and dynamic files, applying read-only permissions only to the static portion while leaving dynamic files with appropriate write permissions, thus protecting against hacking without compromising functionality.

Inventive Principle:
Principle #1Segmentation

3Reliability

If manual permission changes are implemented for each file, then security control is improved, but the complexity of management is worsened

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

Solution Approach 1:

The system automatically identifies static versus dynamic files and applies appropriate read-only permissions without requiring manual intervention for each file. The automated classification and permission application process reduces management complexity while maintaining security control.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system changes the permission parameter automatically based on file characteristics (static vs. dynamic classification). This automated parameter change approach eliminates the need for manual permission setting for each file, reducing management complexity while maintaining security.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS8453214B1Methods of locking a website
Publication Date: 2013.05.28 GO DADDY OPERATING CO LLC
  • US8453214B1 patent drawing
  • US8453214B1 patent drawing
  • US8453214B1 patent drawing

AI summary

Methods of the present inventions allow for locking a website. An exemplary method may comprise the steps of hosting a website on at least one server communicatively coupled to a network, receiving a request to lock the website, and, responsive to the request, changing access permissions to “read-only” for a directory, folder, file, database, or database table rendering the website functional.