Repository Proxy for On-Premise Software Delivery Compliance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing continuous delivery infrastructures and software repositories face challenges in adapting to on-premise delivery requirements, such as embargo checks and license checks, which are costly and difficult to implement, especially when trying to maintain continuous delivery qualities similar to cloud-hosted deployments.
Innovation Solution
A computer-implemented method using a repository proxy with a transparent, terminating network proxy to manage software artifact access, perform embargo and license checks, and create audit logs, allowing secure and compliant on-premise software delivery while maintaining uniformity with cloud-hosted deployments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If continuous delivery pipelines directly access software repositories without additional packing and production steps, then delivery frequency is improved, but compliance with regulatory regimes (export control, embargo checks) deteriorates
Solution Approach 1:
A repository proxy is introduced as an intermediary component between the continuous delivery pipeline and the software repository. The proxy intercepts requests, performs embargo checks and license validations, and forwards compliant requests to the repository. This allows continuous delivery to proceed at high frequency while ensuring regulatory compliance through the proxy's filtering mechanism.
2Adaptability or versatility
If third-party continuous delivery infrastructures are adapted for on-premise delivery requirements, then compliance capability is improved, but system complexity and cost increase
Solution Approach 1:
The compliance functionality is segmented into a separate repository proxy component rather than modifying the entire continuous delivery infrastructure. The proxy handles compliance checks independently, leaving the core CD pipeline unchanged. This reduces system complexity by isolating the adaptation requirement to a single modular component.
Solution Approach 2:
The repository proxy serves as an intermediary that adds compliance capability without requiring changes to existing third-party CD infrastructure. It sits between the pipeline and repository, performing embargo and license checks while allowing the original infrastructure to remain unchanged, thus avoiding the complexity of adapting multiple components.
3Adaptability or versatility
If open source projects are forked and enhanced for enterprise-proprietary manner, then customization for on-premise requirements is improved, but maintenance difficulty and community adoption hurdle increase
Solution Approach 1:
Instead of forking and modifying open source projects, the solution uses a repository proxy that copies the functionality of access control and auditing at the network layer. The proxy implements enterprise requirements through configuration rather than code modification, avoiding the maintenance burden of proprietary forks while achieving the same customization goals.
4Reliability
If network proxies are used to intercept traffic for access control, then security and compliance monitoring is improved, but entities that do not support network proxies cannot be monitored
Solution Approach 1:
The repository proxy is designed to work with any software repository regardless of whether the repository itself supports network proxies. By placing the proxy in front of the repository, it provides universal access control and monitoring capabilities that are independent of the repository's native proxy support, thus achieving both security monitoring and broad compatibility.
Data Source
AI summary
Implementations of the present disclosure include methods, systems, and computer-readable storage mediums for receiving a request for at least one software artifact stored within a software repository of one or more software repositories of an enterprise, the request being received from a continuous delivery (CD) pipeline associated with an on-premise landscape of a customer, and including a user identifier, and at least one uniform resource locator (URL) indicating a location of a respective software artifact within the software repositories, providing, the request to a repository proxy of the enterprise, the repository proxy including a transparent, terminating network proxy, providing, by the repository proxy, an audit log entry associated with the request, the audit log entry being recorded in an audit log, and transmitting, by the repository proxy, a response to the request, the response including the software artifact retrieved from the software repositories based on the at least one URL.