Skip to content
This repository has been archived by the owner on Apr 30, 2021. It is now read-only.

[Policy as code] Technical design #223

Open
v1r7u opened this issue May 5, 2020 · 1 comment
Open

[Policy as code] Technical design #223

v1r7u opened this issue May 5, 2020 · 1 comment
Labels
area/documentation Improvements or additions to documentation kind/question Discussion item lifecycle/backlog General backlog pile. Any idea, which could be taken into work priority/low Low priority issues size/L

Comments

@v1r7u
Copy link
Contributor

v1r7u commented May 5, 2020

Policy-as-code projects can help customers to define custom rules on their resources and have the potential to supersede specific scanners (like, polaris, azsk, etc).

We have to design how to integrate external policy-as-code solution to Joseki.

Potential policy-as-code solutions:

@v1r7u v1r7u added area/documentation Improvements or additions to documentation kind/question Discussion item lifecycle/backlog General backlog pile. Any idea, which could be taken into work size/L priority/low Low priority issues labels May 5, 2020
@v1r7u
Copy link
Contributor Author

v1r7u commented May 5, 2020

As the very first step, let's find out for what kind of scenarios it could be used

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/documentation Improvements or additions to documentation kind/question Discussion item lifecycle/backlog General backlog pile. Any idea, which could be taken into work priority/low Low priority issues size/L
Projects
None yet
Development

No branches or pull requests

1 participant