Credential Verification for Container Native Functions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In distributed computing environments, there is a security risk when container native functions (CNFs) with privileged capabilities are executed on devices without proper credential checks, potentially allowing unauthorized access and manipulation, especially in mission-critical operations.
Innovation Solution
Implementing a system that verifies both the CNF and device credentials for privileged capabilities through a data structure storing process-level and file handle level capabilities, ensuring that only devices with the necessary credentials can execute CNFs, thereby enhancing security by prohibiting execution if either the CNF or device lacks the required credentials.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If CNFs are allowed to execute on any device in the distributed computing environment, then the ease of operation and deployment is improved, but the security risk and potential for unauthorized access increases
Solution Approach 1:
The system performs preliminary credential verification before allowing CNF execution on a device. The credential checker verifies both the CNF's privileged capabilities and the device's associated credentials in advance, ensuring that only authorized CNFs can execute on authorized devices. This preliminary action prevents unauthorized access while maintaining ease of operation for legitimate CNFs.
2Reliability
If credential verification is performed for both CNF and device, then the security is improved, but the device complexity and verification process increases
Solution Approach 1:
The system introduces a credential checker as an intermediary component that handles the complexity of credential verification. This mediator verifies both CNF credentials and device credentials against each other, simplifying the overall verification process. The credential checker acts as a centralized authority that manages the complexity of credential matching without burdening individual devices or CNFs with complex verification logic.
3Object-affected harmful factors
If device-level privilege capabilities are implemented, then the security against unauthorized access is improved, but the adaptability and flexibility of CNF execution is reduced
Solution Approach 1:
The system applies local quality by assigning specific credentials to specific devices based on their security clearance levels. Each device has associated credentials that define its authorized capabilities, and the credential checker verifies whether the CNF's requested operations are permitted on that specific device. This localized approach maintains security while allowing flexible execution of CNFs on appropriate devices.
Data Source
AI summary
Privilege capabilities can be implemented for devices used for container native function (CNF) operations according to some aspects described herein. In one example, a system can receive a request for executing a CNF using a device in a computing cluster. The CNF can involve an operation associated with a privileged capability. The system can determine the CNF is associated with a first credential for the privileged capability based on a data structure that stores process-level capabilities for the CNF and file handle level capabilities for the device. The system can determine the device is associated with a second credential for the privileged capability based on the data structure. In response to determining that the CNF is associated with the first credential and the device is associated with the second credential, the system can execute the CNF using the device in the computing cluster.