-
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.
scientific paper proposal - week 6 (#2552)
* week 4: presentation proposal * demo proposal: week 5 * scientific paper proposal - week 6 --------- Co-authored-by: Florian Immig <[email protected]>
- Loading branch information
Showing
1 changed file
with
28 additions
and
0 deletions.
There are no files selected for viewing
28 changes: 28 additions & 0 deletions
28
contributions/scientific-paper/week6/peiyang-immig/README.md
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,28 @@ | ||
# Assignment Proposal | ||
|
||
## Title | ||
|
||
The Seven Sins: Security Smells in Infrastructure as Code Scripts | ||
|
||
## Names and KTH ID | ||
|
||
- Peiyang Zheng ([email protected]) | ||
- Florian Jerome Immig ([email protected]) | ||
|
||
## Deadline | ||
|
||
- Week 6 | ||
|
||
## Category | ||
|
||
- Scientific paper | ||
|
||
## Description | ||
|
||
We plan to present the paper titled "The Seven Sins: Security Smells in Infrastructure as Code Scripts", which provides an empirical study on security smells in infrastructure as code (IaC) scripts. The authors identify seven distinct security smells, such as hard-coded secrets and invalid IP address binding, which could lead to potential security breaches. They propose a static analysis tool, Security Linter for Infrastructure as Code scripts (SLIC), to detect these smells and highlight their prevalence and persistence in real-world IaC scripts. | ||
Link: https://ieeexplore.ieee.org/document/8812041 | ||
|
||
**Relevance** | ||
|
||
Understanding and mitigating security smells in IaC scripts is crucial for ensuring the security and robustness of automated infrastructure management in DevOps practices such as Infrastructure as Code. | ||
|