Open projects & shared guidance

Good work starts
with good resources.

A curated starting point for open-source security software, developer tools, training, and shared guidance. Reviewed November 17, 2026.

These are links to independent projects, not software installed or operated by Ciphrus. Review each project’s license, dependencies, permissions, and deployment requirements. Open source does not remove infrastructure or operating costs, and hosted services may have paid plans.

9 projects available

Guidance

OWASP ASVS

Define application security requirements before you build or review a web application.

Use for a scoped requirements discussion; applying the standard does not itself certify an application.

Where it runs: Read online / downloadable standard

Guidance

OWASP Cheat Sheet Series

Find focused implementation guidance for authentication, access control, input handling, and other development topics.

Choose guidance relevant to the application and verify it against the current implementation.

Where it runs: Read online

Testing

ZAP

Explore an open-source web application testing proxy and scanner for an authorized assessment.

Use within a clearly authorized scope; a scan does not establish that an application is secure.

Where it runs: Desktop or controlled testing environment

Monitoring

Wazuh

Explore endpoint and workload security monitoring with an open-source platform.

Plan deployment, agent access, storage, alert ownership, and ongoing operation before adopting it.

Where it runs: Server infrastructure and endpoint agents

Monitoring

osquery

Query operating-system information through a SQL-style interface for inventory and investigation.

The questions you run, deployment permissions, and handling of collected information need an operating plan.

Where it runs: Supported endpoint installation

Software supply chain

Syft

Generate a software bill of materials from supported images and filesystems.

An inventory helps identify components; it does not, by itself, show whether all components are safe.

Where it runs: Command-line or CI environment

Software supply chain

Trivy

Inspect supported artifacts and environments for reported vulnerabilities and configuration issues.

Review findings in context and track remediation. Coverage depends on the artifact, data sources, and configuration.

Where it runs: Command-line or CI environment

Software supply chain

OpenSSF Scorecard

Review automated indicators of an open-source project’s security practices.

A score is an input to due diligence, not proof that a dependency is secure or suitable for your application.

Where it runs: Project report or supported CLI workflow

Learning

OWASP Juice Shop

Practice application security concepts in an intentionally vulnerable training application.

Run in an isolated learning environment. Do not install a deliberately vulnerable lab on your production website.

Where it runs: Isolated local lab

Public vulnerability data

Public datasets have their own terms and update schedules. The Ciphrus security updates board brings together CISA known-exploited entries and a sample of recent CVE List record changes, with source dates and retrieval status.

CISA KEV data · Official CVE List · NIST National Vulnerability Database

Project names belong to their respective maintainers. Listing a project does not imply endorsement, partnership, or an assessment of its suitability for your environment.