RFC on a SOPS security linter / compliance checker
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
Hi,
first of all I would like to express my deepest gratitude for SOPS - it is a game changer for managing operational secrets!
We are currently working on an Open Source SOPS file security linter and compliance checker and would be happy for more thoughts from the SOPS community: https://github.com/Bonial-International-GmbH/sops-compliance-checker/pull/1/files and comments / suggestions are welcome there or here in this issue.
The purpose is to check SOPS files for correct and compliant usage without decrypting the SOPS files to ensure that all SOPS files are configured in the desired fashion. The goal is to provide a security linter that safeguards the security of the data protected by the SOPS files against common mistakes and against malicious configurations.
See the slides or English video / German video of my Cloud & Offline Secrets Management - Managing operational secrets with SOPS talk for more background and the motivation.
Kind regards,
Schlomo Schapiro
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue points to an external sops-compliance-checker pull request, slides, and talks rather than files or tests in this repository. Start by reviewing that proposal and the SOPS issue context; done is not defined here because this is a request for feedback, not a scoped change.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100