-
Notifications
You must be signed in to change notification settings - Fork 425
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Week 6 Presentation Proposal (#2512)
- Loading branch information
1 parent
ae53a1b
commit d159af6
Showing
1 changed file
with
27 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
# Assignment Proposal | ||
|
||
## Title | ||
|
||
Integrating Organizational Policies Using Open Policy Agent | ||
|
||
## Names and KTH ID | ||
- Christopher Sapinski ([email protected]) | ||
- Katsutoshi Amano ([email protected]) | ||
|
||
## Deadline | ||
|
||
- Week 6 | ||
|
||
## Category | ||
|
||
- Presentation | ||
|
||
## Description | ||
|
||
Open Policy Agent is a tool to write and execute policies for different services. These policies check for compliance and encompass a wide variety of options. | ||
We will highlight the use of OPA to ensure Terraform plans follow policy, while also mentioning the other places that OPA can and should be used. | ||
|
||
**Relevance** | ||
|
||
With the wide variety of tools, it can be a nightmare to try and maintain security for all of them. Instead of writing specific policy code for each different product, OPA unifies the toolset. | ||
This makes it much easier to maintain. These rules can include security specifications such as who can access data. |