MIB OID Access Control with Tiered Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication systems lack a mechanism to manage access to Management Information Base (MIB) databases where values with different security levels coexist, leading to potential unauthorized access and security vulnerabilities.
Innovation Solution
Implement a controller in communication devices and terminal devices that authenticate users based on specific user roles, allowing access to MIB values with varying security levels by determining if the user is an administrator or a public user, and executing access requests accordingly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If uniform access control is applied to all MIB values, then security is simplified, but security levels cannot be differentiated
Solution Approach 1:
The patent applies local quality by differentiating access control policies based on the security level of individual MIB values. Each MIB value is assigned a security level (first security level or second security level), and access rights are selectively applied: users can access first-level values without authentication while second-level values require administrator authentication. This resolves the contradiction by enabling differentiated security without requiring complete system redesign.
Solution Approach 2:
The patent segments the MIB database into two distinct categories based on security levels. The controller divides access control into separate handling mechanisms: one for first-level values (public access) and another for second-level values (administrator-only access). This segmentation allows independent management of security policies for different data types, resolving the complexity issue while maintaining adaptability.
2Reliability
If authentication is required for all access, then security is improved, but accessibility for public information deteriorates
Solution Approach 1:
The patent applies local quality by implementing selective authentication requirements based on MIB value security levels. First-level values (public information) allow access without authentication, maintaining ease of operation for public data. Second-level values (sensitive information) require administrator authentication, ensuring reliability for critical data. This localized approach resolves the contradiction between security and accessibility.
Solution Approach 2:
The patent applies partial action by requiring authentication only for the subset of MIB values that necessitate it (second-level values), rather than universally. This partial authentication approach maintains high accessibility for public information while providing necessary security protection for sensitive data, resolving the contradiction between ease of operation and reliability.
3Ease of operation
If no authentication mechanism is implemented, then ease of operation is maintained, but security against unauthorized access deteriorates
Solution Approach 1:
The patent applies local quality by implementing authentication only for specific MIB values (second-level) that are susceptible to unauthorized access, while leaving first-level values accessible without authentication. This localized security measure maintains ease of operation for public information while providing targeted protection against harmful factors for sensitive data.
Solution Approach 2:
The patent converts the potential harm of unauthorized access into a benefit by using security level differentiation to naturally guide user behavior. The clear classification of MIB values into public and restricted categories helps users understand what can be accessed freely versus what requires administrator privileges, transforming the security mechanism into an intuitive access guide that prevents unauthorized access while maintaining operational ease.
Data Source
AI summary
A communication device may include: a database storing, for each of a plurality of OIDs of MIB, a value in association with the OID; and a controller configured to execute access to a value in the database according to an access request, wherein in a case where the access request includes a first OID and the user of a terminal device is not authenticated as a specific user, the controller executes access to the first value, and in a case where the access request includes a second OID and the user of the terminal device is not authenticated as the specific user, the access to the second value is not executed.