Skip to content

Pipeline Tampering Risks & Prevention #47

Description

@ducthinh993

Hi folks,
As a DevSecOps practitioner for many sizes of development, there is a critical one for maintaining DevSecOps Pipeline to prevent integrity violation and DRY principle with the pipeline consuming

Abstraction Ideas:

  • Pipeline definition store as separate repos
  • Consuming pipeline as git sub-modules
  • Pipeline call should be visible and measured

Benefits:

  • Pipeline enforcement
  • Pipeline integrity
  • Pipeline scalability

I'm happy to help but not so sure which category should we put it on

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentationenhancementNew feature or requestideaShare a good idea

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions