PulseExploreJournal ClubDebatesTrendingResearchersJournals
Instagram
HomeExploreJournal ClubTrending
Synapse
⌘+K
Synapse
February 12, 2026Software1 citationsOpen Access

Integrating Continuous Compliance into DevSecOps Pipelines: A Data Engineering Perspective

View Full Paper
AZAleksandr Zakharchenko

Key Points

  • The aim is to integrate continuous compliance into DevSecOps practices to enhance regulatory and security adherence.
  • Introduced the Continuous Compliance Framework (CCF) as a data-centric architecture.
  • Embedded compliance validation directly into CI/CD pipelines using policies-as-code.
  • Developed a Compliance Data Lakehouse for transforming pipeline artifacts into queryable compliance data.
  • Achieved full policy lifecycle enforcement with minimal pipeline overhead.
  • Demonstrated sub-second latency for policy evaluations.
  • Showed that compliance can be embedded into the software delivery process without slowing down deployment.

Abstract

Modern DevSecOps environments face a persistent tension between accelerating deployment velocity and maintaining verifiable compliance with regulatory, security, and internal governance standards. Traditional snapshot-in-time audits and fragmented compliance tooling struggle to capture the dynamic nature of containerized, continuous delivery, often resulting in compliance drift and delayed remediation. This paper introduces the Continuous Compliance Framework (CCF), a data-centric reference architecture that embeds compliance validation directly into CI/CD pipelines. The framework treats compliance as a first-class, computable system property by combining declarative policies-as-code, standardized evidence collection, and cryptographically verifiable attestations. Central to the approach is a Compliance Data Lakehouse that transforms heterogeneous pipeline artifacts into a queryable, time-indexed compliance data product, enabling audit-ready evidence generation and continuous assurance. The proposed architecture is validated through an end-to-end synthetic microservice implementation. Experimental results demonstrate full policy lifecycle enforcement with a minimal pipeline overhead and sub-second policy evaluation latency. These findings indicate that compliance can be shifted from a post hoc audit activity to an intrinsic, verifiable property of the software delivery process without materially degrading deployment velocity.

Ask AI
Helpful
Bookmark
Share
View Full Paper

Cite This Study

Aleksandr Zakharchenko (2026) studied this question.

synapsesocial.com/papers/698d6dd15be6419ac0d53129https://doi.org/10.3390/software5010006
Ask AI
Helpful
Bookmark
Share
View Full Paper