mirror of
https://github.com/MichaelCade/90DaysOfDevOps.git
synced 2024-12-22 22:33:12 +07:00
Add Day 5 - Open Source Security
This commit is contained in:
parent
891fc5a405
commit
7d0ba5ddd6
@ -0,0 +1,55 @@
|
||||
## Open Source Security
|
||||
|
||||
Open-source software has become widely used over the past few years due to its collaborative and community/public nature.
|
||||
|
||||
The term Open Source refers to software in the public domain that people can freely use, modify, and share.
|
||||
|
||||
The main reason for this surge of adoption and interest in Open Source is the speed of augmenting proprietary code developed in-house and this in turn can accelerate time to market. Meaning that leveraging OSS can speed up application development and help get your commercial product to market faster.
|
||||
|
||||
### What is Open-Source Security?
|
||||
|
||||
Open-source security refers to the practice of ensuring the safety and security of computer systems and networks that use open-source software. As we said above Open-source software is software that is freely available to use, modify, and distribute, and it is typically developed by a community of volunteers however there is a huge uptake from big software vendors that also contribute back to open-source, you only need to look at the Kubernetes repository to see which vendors are heavily invested there.
|
||||
|
||||
Because open-source software is freely available, it can be widely used and studied, which can help to improve its security. However, it is important to ensure that open-source software is used responsibly and that any vulnerabilities are addressed in a timely manner to maintain its security.
|
||||
|
||||
### Understanding OSS supply chain security
|
||||
I would normally document my findings based on a longer form video into a paragraph here but as this is 10mins I thought it made sense to link the resource here [Understanding Open-Source Supply Chain Security] (https://www.youtube.com/watch?v=pARGj6j0-ZY)
|
||||
|
||||
Be it a commercial product leveraging OSS or an OSS project using packages or other OSS code we must have an awareness from top to bottom and provide better visibility between projects.
|
||||
|
||||
### 3 As of OSS Security
|
||||
|
||||
Another resource I found useful here from IBM, will be linked below in the resources section.
|
||||
|
||||
- **Assess** - Look at the project health, how active is the repository, how responsive are the maintainers? If these show a bad sign, then you are not going to be happy about the security of the project.
|
||||
|
||||
At this stage, we can also check the security model, code reviews, data validations, and test coverage for security. How does the project handle CVEs?
|
||||
|
||||
What dependencies does this project have? Explore the health of these in turn as you need to be sure the whole stack is good.
|
||||
|
||||
- **Adopt** - If you are going to take this on within your software or as a standalone app within your own stack, who is going to manage and maintain it? Set some policies on who internally will overlook the project and support the community.
|
||||
|
||||
- **Act** - Security is the responsibility of everyone, not just the maintainers, as a user you should also act and assist with the project.
|
||||
|
||||
### Log4j Vulnerability
|
||||
|
||||
In early 2022 we had a vulnerability that seemed to massively hit the headlines (Log4j (CVE-2021-44228) RCE Vulnerability)
|
||||
|
||||
Log4j is a very common library for logging within Java. The vulnerability would in turn affect millions of java-based applications.
|
||||
|
||||
A malicious actor could use this vulnerability within the application to gain access to a system.
|
||||
|
||||
Two big things I mentioned,
|
||||
|
||||
- **millions** of applications will have this package being used.
|
||||
- **malicious actors** could leverage this to gain access or plant malware into an environment.
|
||||
|
||||
The reason I am raising this is that security never stops, the growth of Open-Source adoption has increased this attack vector on applications, and this is why there needs to be an overall effort on security from day 0.
|
||||
|
||||
## Resources
|
||||
|
||||
- [Open Source Security Foundation](https://openssf.org/)
|
||||
- [Snyk - State of open source security 2022](https://snyk.io/reports/open-source-security/)
|
||||
- [IBM - The 3 A's of Open Source Security](https://www.youtube.com/watch?v=baZH6CX6Zno)
|
||||
- [Log4j (CVE-2021-44228) RCE Vulnerability Explained](https://www.youtube.com/watch?v=0-abhd-CLwQ)
|
||||
|
@ -0,0 +1,4 @@
|
||||
## Hands-On: Building a weak app
|
||||
|
||||
Nobody really sets out to build a weak or vulnerable app... do they?
|
||||
|
@ -14,7 +14,9 @@ This will **not cover all things** "DevOps" but it will cover the areas that I f
|
||||
|
||||
[![ko-fi](https://ko-fi.com/img/githubbutton_sm.svg)](https://ko-fi.com/N4N33YRCS)
|
||||
|
||||
[![](https://dcbadge.vercel.app/api/server/vqwPrNQsyK)](https://discord.gg/vqwPrNQsyK)
|
||||
[![Discord Invite Link](https://dcbadge.vercel.app/api/server/vqwPrNQsyK)](https://discord.gg/vqwPrNQsyK)
|
||||
|
||||
![GitHub Repo Stars](https://img.shields.io/github/stars/michaelcade/90daysofdevops?style=social?)
|
||||
|
||||
The two images below will take you to the 2022 and 2023 edition of the learning journey.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user