Skip to content
プロジェクト

sk3pp3r/DevSecOps-Arsenal

GitHubで見る

sk3pp3r/DevSecOps-Arsenal has 31 GitHub stars and 4 forks. GitHot measured 0 stars in 24 hours. Last checked 2026-11-14 18:39 UTC. Last push 2026-10-08.

この数値の測り方

計測したスター増加

24時間
0
7日間
履歴を収集中
15日間
履歴を収集中
1か月
履歴を収集中

期間ごとの純増数です。期間は重複しており、日別の値ではありません。未計測の値は空欄です。スター数は注目度の指標であり、品質の保証ではありません。

概要

A curated hub of DevSecOps tools to secure workflows, optimized for CI/CD and more

セキュリティ

⚙️ DevSecOps Arsenal ⚙️

Welcome to the DevSecOps Arsenal — a comprehensive, curated collection of tools, methodologies, and resources to seamlessly integrate security into every stage of your SDLC and DevOps workflows.

DevSecOps_HaimCohen For interactive interface click here


📜 Table of Contents

Section Description
What is DevSecOps? 🤔 Understanding the integration of security into the DevOps lifecycle.
What is SDLC and SSDLC? 🔍 Overview of SDLC and SSDLC practices.
Shift-Left SSDLC 🔄 Moving security and QA earlier in the development lifecycle.
Tooling 🛠️ A curated list of DevSecOps tools categorized by use case.
Methodologies, Whitepapers, and Architecture 📚 Resources to deepen understanding of DevSecOps.
Contribution Rules 🤝 Guidelines for contributing to the DevSecOps Arsenal.

🤔 What is DevSecOps?

DevSecOps ensures security is integrated at every phase of the DevOps lifecycle—planning, coding, building, testing, releasing, deploying, operating, and monitoring. It emphasizes automation, collaboration, and enforcement to bridge development, security, and operations. Learn more:


🔍 What is SDLC and SSDLC?

Software Development Life Cycle (SDLC)

The SDLC is a framework that defines the processes and phases involved in software development, including:

  1. Planning 📝
  2. Analysis 📊
  3. Design 🎨
  4. Implementation 💻
  5. Testing 🧪
  6. Deployment 🚀
  7. Maintenance 🔄

Secure Software Development Life Cycle (SSDLC)

SSDLC integrates security practices into each phase of the SDLC. It ensures vulnerabilities are addressed early, reducing risks and costs. Key practices include:

  • Threat Modeling during planning and design.
  • Static Analysis during development.
  • Dynamic Testing before deployment.

How They Work Together

The SSDLC augments the SDLC by embedding security checks at every stage. This alignment ensures that security becomes a fundamental part of the development process rather than an afterthought, fostering secure and high-quality software.


🔄 Shift-Left SSDLC

Concept

Shift-Left SSDLC refers to integrating security and quality assurance (QA) earlier in the software development process—shifting activities typically done later, such as testing and security checks, to earlier phases like planning and coding.

Significance

By addressing issues earlier:

  • Cost savings: Fixing vulnerabilities in the design phase is cheaper than post-deployment.
  • Improved software quality: Early detection enhances the overall reliability and security of the software.
  • Faster delivery: Reduced rework shortens development cycles.

Methodologies and Best Practices

  1. Early Threat Modeling: Incorporate tools like ThreatSpec to identify potential risks during planning.
  2. Pre-Commit Hooks: Use tools like Git-Secrets to prevent sensitive data from being committed.
  3. Static Code Analysis: Implement tools like Semgrep during development.
  4. Collaborative Development: Foster teamwork between developers, QA, and security teams.
  5. Continuous Feedback Loops: Use CI/CD pipelines to automate testing and provide feedback.

Recommended Reading 📖: Shift-Left SSDLC

This article focuses on enabling organizations to implement Shift-Left principles effectively by providing integrations and best practices for embedding security and QA into the earliest stages of development. 🌟


🛠️ Tooling

Category Tool Name & Description GitHub Stars
Pre-Commit Time Tools ⚡ Git-Secrets: Detects secrets in commits. GitHub stars
SonarLint: IDE-based tool for real-time code quality checks. GitHub stars
ThreatSpec: Threat modeling as code for early risk identification. GitHub stars
Gitleaks: Detect and prevent hardcoded secrets like passwords, api keys, and tokens in git repos. GitHub stars
pre-commit: Framework for managing and maintaining git pre-commit hooks. GitHub stars
Secrets Management 🔒 TruffleHog: Scans repositories for secrets. GitHub stars
HashiCorp Vault: Provides secure access and storage for secrets. GitHub stars
Mozilla SOPS: Encrypts secrets in YAML and JSON files. GitHub stars
AWS Secrets Manager: Securely store and manage secrets in AWS. GitHub stars
Sealed Secrets: Kubernetes controller for one-way encrypted secrets. GitHub stars
OSS Dependency Management 📦 Snyk: Identifies and fixes vulnerabilities in dependencies. GitHub stars
CycloneDX: Creates software BOMs (Bill of Materials) for tracking dependencies. GitHub stars
Dependabot: Automated dependency updates and security alerts. GitHub stars
Renovate: Automated dependency updates with flexible configuration. GitHub stars
Supply Chain Security 🔗 Tekton Chains: Provides Kubernetes-native supply chain security. GitHub stars
SLSA Framework: Offers standards for supply-chain security. GitHub stars
Sigstore: Tools for signing, verifying and protecting software. GitHub stars
in-toto: Framework to secure the integrity of software supply chains. GitHub stars
SAST 🛡️ Semgrep: High-quality static analysis. GitHub stars
Bandit: Python-specific security linter. GitHub stars
SonarQube: Continuous code quality and security analysis. GitHub stars
CodeQL: Semantic code analysis engine for security vulnerabilities. GitHub stars
DAST 🌐 OWASP ZAP: Dynamic scanner for web vulnerabilities. GitHub stars
Nuclei: Template-based vulnerability scanning. GitHub stars
Burp Suite: Web application security testing platform. -
Acunetix: Automated web vulnerability scanner. -
Darkmoon: Open source autonomous penetration testing platform where 50 specialist agents over MCP drive 50+ offensive tools across web, API, Active Directory, Kubernetes and cloud with reproducible proof of exploitation. GitHub stars
Continuous Deployment 🚀 Trivy: Scans containers and configurations for vulnerabilities. GitHub stars
Terrascan: Static analysis for Infrastructure as Code. GitHub stars
StackStorm: Automation platform for DevSecOps workflows. GitHub stars
Anchore: Container image scanning and policy enforcement. GitHub stars
Clair: Vulnerability static analysis for containers. GitHub stars
Kubernetes Security 🌀 Kubescape: Kubernetes compliance and hardening scanner. GitHub stars
Kube-Bench: Benchmarks Kubernetes clusters against CIS standards. GitHub stars
Kyverno: Kubernetes native policy management. GitHub stars
Cloud Security & Compliance 🏛️ Prowler: Open-source CSPM that automates security and compliance across any cloud environment. GitHub stars
CloudMapper: Visualizes cloud architecture and identifies security risks in AWS environments. GitHub stars
ScoutSuite: Multi-cloud security auditing tool for AWS, Azure, GCP, and Alibaba Cloud. GitHub stars
Runtime Security & Monitoring 🔍 Wazuh: Open-source SIEM/EDR for runtime threat detection, log analysis, and incident response. GitHub stars
Falco: Cloud-native runtime security tool for detecting anomalous behavior in real time. GitHub stars
osquery: SQL-based host monitoring and analytics tool for security visibility. GitHub stars
IaC Security 🏗️ Checkov: Finds misconfigurations in IaC templates. GitHub stars
KICS: Scans IaC files for vulnerabilities. GitHub stars
tfsec: Security scanner for Terraform code. GitHub stars
Snyk IaC: Infrastructure as Code security scanning. GitHub stars
Vulnerability Management DefectDojo: Platform for centralized vulnerability management. GitHub stars
ArcherySec: ASOC, ASPM, DevSecOps, Vulnerability Management Using ArcherySec. GitHub stars
VulnWhisperer: Vulnerability management dashboard. GitHub stars
VulnIQ: Vulnerability intelligence and management platform. GitHub stars

📚 Methodologies, Whitepapers, and Architecture

Resource Description
Principles of Chaos Engineering Guidelines to build resilient systems.
OWASP DevSecOps Guidelines Comprehensive DevSecOps best practices.

🤝 Contribution Rules

  1. Active, Open Source: Add tools that are currently active and open-source.
  2. Relevance: Ensure submissions align with the DevSecOps methodology.
  3. Avoid Duplication: Check existing tools before adding new ones.
  4. Provide Details: Include clear descriptions and tool relevance.

How to Contribute

  1. Fork the repository.
  2. Create a new branch.
  3. Submit a Pull Request.

🌟 Let's build a safer DevSecOps ecosystem together! 🌟