Secure MIB Setting Writes via Authenticated Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication schemes for writing setting values in Management Information Base (MIB) databases, such as SNMP, lack sufficient security, making them vulnerable to unauthorized access and modification.
Innovation Solution
Implementing a second communication scheme that includes encryption and authentication, such as HTTPS, to securely write setting values in MIB databases, while allowing selective use of SNMP for less sensitive operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If SNMP is used to write setting values in MIB database, then ease of operation is improved, but security is worsened
Solution Approach 1:
The patent segments the MIB database into multiple security zones (first MIB area with lower security requirements and second MIB area with higher security requirements). This allows different communication schemes to be applied to different portions of the database, enabling ease of operation for non-critical data while ensuring security for critical data.
Solution Approach 2:
The patent applies different security measures to different locations within the MIB database structure. The second MIB area, which contains critical setting values, is protected with enhanced security mechanisms including authentication and encrypted communication schemes, while other areas maintain standard access.
2Reliability
If encryption and authentication are implemented for writing setting values, then security is improved, but device complexity is worsened
Solution Approach 1:
The patent divides the MIB database into security zones, implementing complex security measures only where necessary. This segmentation allows the system to maintain high security for critical data while avoiding unnecessary complexity in other areas.
Solution Approach 2:
Enhanced security features including authentication and encrypted communication schemes are applied locally to the second MIB area rather than system-wide. This localized approach ensures security where needed while minimizing the impact on overall device complexity.
3Reliability
If secure communication scheme is used for all MIB operations, then security is improved, but ease of operation is worsened
Solution Approach 1:
The patent segments the MIB database into multiple areas with different security requirements. The first MIB area allows simpler access methods maintaining ease of operation, while the second MIB area implements secure communication schemes only where critical data protection is needed.
Solution Approach 2:
Different communication schemes are applied to different portions of the MIB database based on the sensitivity of the data. Critical setting values in the second MIB area use encrypted and authenticated communication, while other areas maintain standard access procedures.
Data Source
AI summary
A first communication device may include: a database configured to, for each of a plurality of OIDs of MIB, store the OID in association with a setting value; and a controller, wherein the controller is configured to: receive a writing request from a second communication device by using a second communication scheme different from a first communication scheme including SNMP, the writing request including an OID and a setting value, and the second communication scheme including at least one of encryption of communication data and authentication of a sender of the writing request; and in a case where the writing request is received from the second communication device, write the setting value included in the writing request in the database in association with the OID included in the writing request.