sig-release
slsa
Our great sponsors
sig-release | slsa | |
---|---|---|
6 | 35 | |
515 | 1,422 | |
0.4% | 3.0% | |
9.1 | 8.7 | |
9 days ago | 5 days ago | |
Shell | Shell | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sig-release
- sig-release/releases/release-1.27 at master · kubernetes/sig-release · GitHub
-
KubeCon North America 2022: A Retrospective
As Wednesday kicked off, it was great to feel the buzz and excitement of folks so eager to learn and connect. From Day 1’s keynote, I really enjoyed the reminder that companies benefiting from Kubernetes and the CNCF ecosystem should be getting involved, giving back, and mentoring others. There was a lot of love to maintainers and contributors in the ecosystem, and as someone involved in the Kubernetes Release Team for Kubernetes v1.25 and v1.26, it was a huge honor to see my face up in there with the rest of the team! 💙
-
Kubernetes 1.23 Release
Shout out to the SIG Release team once again for all of their hard work to ship 1.23. Release management is hard and often thankless work, and I appreciate their efforts so much. Also, I want to give a big thank you to everyone who contributed to 1.23. When I see such a long list of changes, it’s clear that many people worked hard to get them done.
-
Kubernetes 1.22 Release
Today the 1.22 version of Kubernetes ships. As always, hats off to the members of SIG Release for all of their hard work.
-
Kubernetes 1.24 will be out next week - Learn what's new and what's deprecated - Dockershim removal, Network Policy Status field, CSI volume health monitoring, TimeZone support for CronJobs … And more!
Here you go. https://github.com/kubernetes/sig-release/discussions/1877
- Kubernetes 1.24 release delayed due to issue with Go | Push forward 1.24 Release date · Discussion #1877 · kubernetes/sig-release
slsa
- SLSA – Supply-Chain Levels for Software Artifacts
-
Dogbolt Decompiler Explorer
Short answer: not where it counts.
My work focuses on recognizing known functions in obfuscated binaries, but there are some papers you might want to check out related to deobfuscation, if not necessarily using ML for deobfuscation or decompilation.
My take is that ML can soundly defeat the "easy" and more static obfuscation types (encodings, control flow flattening, splitting functions). It's low hanging fruit, and it's what I worked on most, but adoption is slow. On the other hand, "hard" obfuscations like virtualized functions or programs which embed JIT compilers to obfuscate at runtime... as far as I know, those are still unsolved problems.
This is a good overview of the subject, but pretty old and doesn't cover "hard" obfuscations: https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=1566145.
https://www.jinyier.me/papers/DATE19_Obf.pdf uses deobfuscation for RTL logic (FGPA/ASIC domain) with SAT solvers. Might be useful for a point of view from a fairly different domain.
https://advising.cs.arizona.edu/~debray/Publications/generic... uses "semantics-preserving transformations" to shed obfuscation. I think this approach is the way to go, especially when combined with dynamic/symbolic analysis to mitigate virt/jit types of transformations.
I'll mention this one as a cautionary tale: https://dl.acm.org/doi/pdf/10.1145/2886012 has some good general info but glosses over the machine learning approach. It considers Hex-rays' FLIRT to be "machine learning", but FLIRT just hashes signatures, can be spoofed (i.e. https://siliconpr0n.org/uv/issues_with_flirt_aware_malware.p...), and is useless against obfuscation.
Eventually I think SBOM tools like Black Duck[1] and SLSA[2] will incorporate ML to improve the accuracy of even figuring out what dependencies a piece of software actually has.
[1]: https://www.synopsys.com/software-integrity/software-composi...
[2]: https://slsa.dev/
-
10 reasons you should quit your HTTP client
The dependency chain is certified! SLSA!
-
UEFI Software Bill of Materials Proposal
The things you mentioned are not solved by a typical "SBOM" but e.g. CycloneDX has extra fields to record provenance and pedigree and things like in-toto (https://in-toto.io/) or SLSA (https://slsa.dev/) also aim to work in this field.
I've spent the last six months in this field and people will tell you that this or that is an industry best practice or "a standard" but in my experience none of that is true. Everyone is still trying to figure out how best to protect the software supply chain security and things are still very much in flux.
-
Gittuf – a security layer for Git using some concepts introduced by TUF
It's multi-pronged and I imagine adopters may use a subset of features. Broadly, I think folks are going to be interested in a) branch/tag/reference protection rules, b) file protection rules (monorepo or otherwise, though monorepos do pose a very apt usecase for gittuf), and c) general key management for those who primarily care about Git signing.
For those who care about a and b, I think the work we want to do to support [in-toto attestations](https://github.com/in-toto/attestation) for [SLSA's upcoming source track](https://github.com/slsa-framework/slsa/issues/956) could be very interesting as well.
- SLSA • Supply-Chain Levels for Software Artifacts
-
Password-stealing Linux malware served for 3 years and no one noticed
It doesn't have to be. Corporations which are FedRAMP[1] compliant, have to build software reproducibly in a fully isolated environment, only from reviewed code.[2]
[1] https://en.wikipedia.org/wiki/FedRAMP
[2] https://slsa.dev/
-
OSCM: The Open Source Consumption Manifesto
SLSA stands for Supply chain Levels for Software Artifacts, and it is a framework that aims to provide a set of best practices for the software supply chain, with a focus on OSS. It was created by Google, and it is now part of the OpenSSF. It consists of four levels of assurance, from Level 1 to Level 4, that correspond to different degrees of protection against supply chain attacks. Our CTO Paolo Mainardi mentioned SLSA in a very good article on software supply chain security, and we also mentioned it in another article about securing OCI Artifacts on Kubernetes.
-
CLOUD SECURITY PODCAST BY GOOGLE - EP116 SBOMs: A Step Towards a More Secure Software Supply Chain -
SLSA.dev
- Supply Chain Levels for Software Artifacts (SLSA)
What are some alternatives?
examples - Example apps and instrumentation for Honeycomb
grype - A vulnerability scanner for container images and filesystems
awesome-argo - A curated list of awesome projects and resources related to Argo (a CNCF graduated project)
ClojureDart - Clojure dialect for Flutter and Dart
awesome-cloudnative-trainings - Awesome Trainings from Cloud Native Computing Foundation Projects and Kubernetes related software
DependencyCheck - OWASP dependency-check is a software composition analysis utility that detects publicly disclosed vulnerabilities in application dependencies.
enhancements - Enhancements tracking repo for Kubernetes
trivy - Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more
opentelemetry-examples - Example code and resources for working with OpenTelemetry, provided by Lightstep
sig-security - 🔐CNCF Security Technical Advisory Group -- secure access, policy control, privacy, auditing, explainability and more!
gateway - Manages Envoy Proxy as a Standalone or Kubernetes-based Application Gateway
checkov - Prevent cloud misconfigurations and find vulnerabilities during build-time in infrastructure as code, container images and open source packages with Checkov by Bridgecrew.