Executable Code Validation Pipeline With Cloud Data Isolation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Third-party cloud environments lack secure mechanisms for validating computer executable code that interacts with protected data, posing risks of unauthorized access and data leakage.
Innovation Solution
A pipeline is implemented within the cloud environment that uses multiple accounts with varying access levels, including sandbox, on-boarding, preparation, and run accounts, to securely validate and test executable code, with features like multi-factor authentication, data traffic logging, and isolation through virtual private clouds, ensuring controlled access and data protection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple accounts with varying access levels are implemented in the pipeline, then security against data leakage is improved, but device complexity increases
Solution Approach 1:
The pipeline is segmented into multiple distinct accounts (first account, second account, third account) each with progressively restricted access levels. The first account has full access to both protected data and executable code, the second account has reduced access to code and increased access to data, and the third account has minimal access. This segmentation isolates security risks and prevents data leakage while maintaining necessary functionality at each stage.
Solution Approach 2:
Each account in the pipeline is configured with specific local quality characteristics - different access levels to protected data and executable code tailored to its functional requirements. The first account is optimized for code development with full access, the second account balances access for validation, and the third account provides restricted access for secure execution. This local quality approach ensures each component has precisely the access it needs without excess.
2Reliability
If access to protected data is restricted in later pipeline stages, then security is improved, but ease of operation deteriorates
Solution Approach 1:
Code validation and testing are performed in advance in the first and second accounts where broader access is permitted. The executable code is thoroughly validated against the protected data in the second account before being transferred to the third account with restricted access. This preliminary action ensures security requirements are met before data access is limited, maintaining ease of operation during critical validation phases.
Solution Approach 2:
The second account serves as an intermediary between the first account (full access) and the third account (restricted access). It provides a transition zone where code can be validated with increased data access while still maintaining security controls. This intermediary account facilitates smooth operation by bridging the gap between development needs and security requirements.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A pipeline for securely validating computer executable code in a third-party cloud environment is provided. The pipeline comprises an on-boarding account and a run account. The on-boarding account is configured to allow the user to access computer executable code input into the third-party cloud environment from the user and prevent the user from accessing the protected data input into the third-party cloud environment from a secure provider. The on-boarding account is also configured to transmit the computer executable code from the on-boarding account to another account in the third-party cloud environment if a first predetermined criterion is met. The run account is configured to allow the user to execute the computer executable code with the protected data and prevent the user from accessing the computer executable code. Moreover, a process for generating the pipeline and a method of securely validating computer executable code in a third-party cloud environment using the pipeline is provided.