All Projects → OWASP → Software-Component-Verification-Standard

OWASP / Software-Component-Verification-Standard

Licence: CC-BY-SA-4.0 license
Software Component Verification Standard (SCVS)

Programming Languages

python
139335 projects - #7 most used programming language
shell
77523 projects
lua
6591 projects

Projects that are alternatives of or similar to Software-Component-Verification-Standard

Cheatsheetseries
The OWASP Cheat Sheet Series was created to provide a concise collection of high value information on specific application security topics.
Stars: ✭ 19,302 (+23439.02%)
Mutual labels:  best-practices, owasp
specification
Software Bill of Material (SBOM) standard designed for use in application security contexts and supply chain component analysis
Stars: ✭ 129 (+57.32%)
Mutual labels:  supply-chain, owasp
dependency-check-py
🔐 Shim to easily install OWASP dependency-check-cli into Python projects
Stars: ✭ 44 (-46.34%)
Mutual labels:  owasp, software-supply-chain
Wstg
The Web Security Testing Guide is a comprehensive Open Source guide to testing the security of web applications and web services.
Stars: ✭ 3,873 (+4623.17%)
Mutual labels:  best-practices, owasp
datree
Prevent Kubernetes misconfigurations from reaching production (again 😤 )! From code to cloud, Datree provides an E2E policy enforcement solution to run automatic checks for rule violations. See our docs: https://hub.datree.io
Stars: ✭ 5,744 (+6904.88%)
Mutual labels:  best-practices
training-application-security
This repository for training application security.
Stars: ✭ 25 (-69.51%)
Mutual labels:  owasp
www-project-vulnerable-web-applications-directory
The OWASP Vulnerable Web Applications Directory (VWAD) Project - OWASP Web Site
Stars: ✭ 10 (-87.8%)
Mutual labels:  owasp
webdriverio-zap-proxy
Demo - how to easily build security testing for Web App, using Zap and Glue
Stars: ✭ 58 (-29.27%)
Mutual labels:  owasp
sigstore
Common go library shared across sigstore services and clients
Stars: ✭ 285 (+247.56%)
Mutual labels:  supply-chain
CSharpHandbook
The focus of this document is on providing a reference for writing C#. It includes naming, structural and formatting conventions as well as best practices for writing clean, safe and maintainable code. Many of the best practices and conventions apply equally well to other languages.
Stars: ✭ 25 (-69.51%)
Mutual labels:  best-practices
theBookOfNoah
Everything ive learned developing web applications
Stars: ✭ 22 (-73.17%)
Mutual labels:  best-practices
basetemplate9
TYPO3 v9 LTS Template Foundation - Use it as a base for your website configuration. Add all your Stylesheets, JavaScripts and Templates.
Stars: ✭ 15 (-81.71%)
Mutual labels:  best-practices
dependency-check-plugin
Jenkins plugin for OWASP Dependency-Check. Inspects project components for known vulnerabilities (e.g. CVEs).
Stars: ✭ 107 (+30.49%)
Mutual labels:  owasp
Y-BP
YFE Team 前端最佳实践
Stars: ✭ 28 (-65.85%)
Mutual labels:  best-practices
symfony-lts-docker-starter
🐳 Dockerized your Symfony project using a complete stack (Makefile, Docker-Compose, CI, bunch of quality insurance tools, tests ...) with a base according to up-to-date components and best practices.
Stars: ✭ 39 (-52.44%)
Mutual labels:  best-practices
mongoDB-Atlas
Best Practices of mongoDB in general and the cloud version of the database(Atlas)
Stars: ✭ 37 (-54.88%)
Mutual labels:  best-practices
torinotech.github.io
torinotech.github.io
Stars: ✭ 16 (-80.49%)
Mutual labels:  best-practices
PackageProject.cmake
🏛️ Help other developers use your project. A CMake script for packaging C/C++ projects for simple project installation while employing best-practices for maximum compatibility.
Stars: ✭ 48 (-41.46%)
Mutual labels:  best-practices
depsbot
⚙️ GitHub action to check freshness of your deno dependencies
Stars: ✭ 28 (-65.85%)
Mutual labels:  best-practices
hlf1.4-supply-chain
Supply chain proof of concept in Hyperledger Fabric. Network with four companies and a specific chaincode exposed as rest API
Stars: ✭ 30 (-63.41%)
Mutual labels:  supply-chain

Build Status GitHub Slack Twitter

OWASP Software Component Verification Standard

The Software Component Verification Standard (SCVS) is a community-driven effort to establish a framework for identifying activities, controls, and best practices, which can help in identifying and reducing risk in a software supply chain.

Managing risk in the software supply chain is important to reduce the surface area of systems vulnerable to exploits, and to measure technical debt as a barrier to remediation.

Measuring and improving software supply chain assurance is crucial for success. Organizations with supply chain visibility are better equipped to protect their brand, increase trust, reduce time-to-market, and manage costs in the event of a supply chain incident.

Software supply chains involve:

  • technology
  • people
  • processes
  • institutions
  • and additional variables

Raising the bar for supply chain assurance requires the active participation of risk managers, mission owners, and business units like legal and procurement, which have not traditionally been involved with technical implementation.

Determination of risk acceptance criteria is not a problem that can be solved by enterprise tooling: it is up to risk managers and business decision makers to evaluate the advantages and trade-offs of security measures based on system exposure, regulatory requirements, and constrained financial and human resources. Mandates that are internally unachievable, or that bring development or procurement to a standstill, constitute their own security and institutional risks.

SCVS is designed to be implemented incrementally, and to allow organizations to phase in controls at different levels over time.

SCVS has the following goals:

  • Develop a common set of activities, controls, and best-practices that can reduce risk in a software supply chain
  • Identify a baseline and path to mature software supply chain vigilance
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].