-
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.
- Loading branch information
Showing
1 changed file
with
31 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,31 @@ | ||
# Assignment Proposal | ||
|
||
## Title | ||
|
||
Using Semgrep to find vulnerabilities | ||
|
||
## Names and KTH ID | ||
|
||
- Viktor Fornstad ([email protected]) | ||
- Gustav Henningsson ([email protected]) | ||
|
||
## Deadline | ||
|
||
- Week 6 | ||
|
||
## Category | ||
|
||
- Demo | ||
|
||
## Description | ||
|
||
We want to demo the static analysis tool called Semgrep. In the demo we will: | ||
- Connect Semgrep to a Github repo | ||
- Run Semgrep, with the basic rule-set, on the repo | ||
- Show and explain the information given by Semgrep | ||
- Create a custom rule that can be used with Semgrep | ||
We will also explain why it is important to use static analysis tools for DevSecOps. | ||
|
||
**Relevance** | ||
|
||
There are hundreds of different vulnerabilities that exist and it's therefor difficult for your average developer to know of and remember all of them. To know why and how to use static analysis tools to identify vulnerabilities is important to combat this problem. |