Week 6 Scientific Paper Proposal #2854
Merged
Conversation
This file contains hidden or 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
|
Your proposal looks good, looking forward to your presentation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Assignment Proposal
Title
Names and KTH ID
Deadline
Category
Description
We intend to present the paper "Control and Data Flow in Security Smell Detection for Infrastructure as Code: Is It Worth the Effort?" published in "2023 IEEE/ACM". This paper investigates the detection of security smells—bad practices that may lead to vulnerabilities—in IaC scripts. The authors propose GASEL, a detector based on Program Dependence Graphs (PDGs). Security smells are identified using graph queries over these PDGs. Additionally, the paper conducts an evaluation on a curated oracle of 243 real-world smells and a dataset of 15,000+ Ansible scripts.
Paper link: https://ieeexplore.ieee.org/abstract/document/10174011
Relevance
This paper is relevant to DevSecOps as it ensures security by addressing "security smells" in IaC, being common patterns for security flaws. This is relevant and important to avoid writing insecure code that follows such risky patterns while writing IaC scripts.