Full Code of boxyhq/awesome-oss-devsec for AI

Repository: boxyhq/awesome-oss-devsec
Branch: main
Commit: 9a78d1b5a544
Files: 10
Total size: 29.8 KB

Directory structure:
gitextract_p7kgvx6g/

├── .github/
│   └── dependabot.yml
├── .gitignore
├── .nojekyll
├── CODE_OF_CONDUCT.md
├── COMPLIANCE.adoc
├── LICENSE
├── README.adoc
├── SUMMARY.adoc
├── book.json
└── package.json

================================================
FILE CONTENTS
================================================

================================================
FILE: .github/dependabot.yml
================================================
# To get started with Dependabot version updates, you'll need to specify which
# package ecosystems to update and where the package manifests are located.
# Please see the documentation for all configuration options:
# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates

version: 2
updates:
  - package-ecosystem: "npm" # See documentation for possible values
    directory: "/" # Location of package manifests
    schedule:
      interval: "weekly"


================================================
FILE: .gitignore
================================================
node_modules
_book


================================================
FILE: .nojekyll
================================================


================================================
FILE: CODE_OF_CONDUCT.md
================================================
# Contributor Covenant Code of Conduct

## Our Pledge

We as members, contributors, and leaders pledge to make participation in our
community a harassment-free experience for everyone, regardless of age, body
size, visible or invisible disability, ethnicity, sex characteristics, gender
identity and expression, level of experience, education, socio-economic status,
nationality, personal appearance, race, religion, or sexual identity
and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming,
diverse, inclusive, and healthy community.

## Our Standards

Examples of behavior that contributes to a positive environment for our
community include:

- Demonstrating empathy and kindness toward other people
- Being respectful of differing opinions, viewpoints, and experiences
- Giving and gracefully accepting constructive feedback
- Accepting responsibility and apologizing to those affected by our mistakes,
  and learning from the experience
- Focusing on what is best not just for us as individuals, but for the
  overall community

Examples of unacceptable behavior include:

- The use of sexualized language or imagery, and sexual attention or
  advances of any kind
- Trolling, insulting or derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others' private information, such as a physical or email
  address, without their explicit permission
- Other conduct which could reasonably be considered inappropriate in a
  professional setting

## Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of
acceptable behavior and will take appropriate and fair corrective action in
response to any behavior that they deem inappropriate, threatening, offensive,
or harmful.

Community leaders have the right and responsibility to remove, edit, or reject
comments, commits, code, wiki edits, issues, and other contributions that are
not aligned to this Code of Conduct, and will communicate reasons for moderation
decisions when appropriate.

## Scope

This Code of Conduct applies within all community spaces, and also applies when
an individual is officially representing the community in public spaces.
Examples of representing our community include using an official e-mail address,
posting via an official social media account, or acting as an appointed
representative at an online or offline event.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the community leaders responsible for enforcement at
deepak@boxyhq.com.
All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the
reporter of any incident.

## Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining
the consequences for any action they deem in violation of this Code of Conduct:

### 1. Correction

**Community Impact**: Use of inappropriate language or other behavior deemed
unprofessional or unwelcome in the community.

**Consequence**: A private, written warning from community leaders, providing
clarity around the nature of the violation and an explanation of why the
behavior was inappropriate. A public apology may be requested.

### 2. Warning

**Community Impact**: A violation through a single incident or series
of actions.

**Consequence**: A warning with consequences for continued behavior. No
interaction with the people involved, including unsolicited interaction with
those enforcing the Code of Conduct, for a specified period of time. This
includes avoiding interactions in community spaces as well as external channels
like social media. Violating these terms may lead to a temporary or
permanent ban.

### 3. Temporary Ban

**Community Impact**: A serious violation of community standards, including
sustained inappropriate behavior.

**Consequence**: A temporary ban from any sort of interaction or public
communication with the community for a specified period of time. No public or
private interaction with the people involved, including unsolicited interaction
with those enforcing the Code of Conduct, is allowed during this period.
Violating these terms may lead to a permanent ban.

### 4. Permanent Ban

**Community Impact**: Demonstrating a pattern of violation of community
standards, including sustained inappropriate behavior, harassment of an
individual, or aggression toward or disparagement of classes of individuals.

**Consequence**: A permanent ban from any sort of public interaction within
the community.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 2.0, available at
https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.

Community Impact Guidelines were inspired by [Mozilla's code of conduct
enforcement ladder](https://github.com/mozilla/diversity).

[homepage]: https://www.contributor-covenant.org

For answers to common questions about this code of conduct, see the FAQ at
https://www.contributor-covenant.org/faq. Translations are available at
https://www.contributor-covenant.org/translations.


================================================
FILE: COMPLIANCE.adoc
================================================
[cols="2,6a,6a",stripes=none]
|===
3+<h| Compliance frameworks and certifications
h| Name
h| Description
h| Tools and Resources

| MVSP
| Minimum Viable Secure Product is a minimalistic security checklist for B2B software and business process outsourcing suppliers. Designed with simplicity in mind, the checklist contains only those controls that must, at a minimum, be implemented to ensure a reasonable security posture.
| * https://mvsp.dev/mvsp.en/index.html[MVSP]

| ISO 27001
| ISO/IEC 27001 is an international standard on how to manage information security. The standard was originally published jointly by the International Organization for Standardization and the International Electrotechnical Commission in 2005 and then revised in 2013.
| * https://github.com/SerNet/verinice[Verinice]
* https://www.opensourcegrc.org/compliance-requirements?main=3[Open Source GRC]
* https://www.eramba.org/community-downloads[eramba]

| SOC2
| Developed by the American Institute of CPAs (AICPA), SOC 2 defines criteria for managing customer data based on five “trust service principles”—security, availability, processing integrity, confidentiality and privacy.

* Type I report is evaluation at a single point in time and can be achieved faster but provides less assurance to your clients.
* Type II report is evaluation over an extended period of time (3-12 months) and provides more assurance to your clients.
| * https://www.strongdm.com/comply[strongdm Comply]

| GDPR
| The General Data Protection Regulation is a regulation in EU law on data protection and privacy in the European Union and the European Economic Area. The GDPR is an important component of EU privacy law and of human rights law, in particular Article 8 of the Charter of Fundamental Rights of the European Union.
| * https://www.eramba.org/community-downloads[eramba]
* https://www.opensourcegrc.org/compliance-requirements?main=19[Open Source GRC]

| PCI DSS
| The Payment Card Industry Data Security Standard (PCI DSS) is a widely accepted set of policies and procedures intended to optimize the security of credit, debit and cash card transactions and protect cardholders against misuse of their personal information.
| * https://github.com/SerNet/verinice[Verinice]
* https://www.eramba.org/community-downloads[eramba]
* https://www.opensourcegrc.org/compliance-requirements?main=2[Open Source GRC]

| HIPAA
| The Health Insurance Portability and Accountability Act of 1996 (HIPAA) is a federal law that required the creation of national standards to protect sensitive patient health information from being disclosed without the patient's consent or knowledge.
| * https://www.eramba.org/community-downloads[eramba]
* https://www.opensourcegrc.org/compliance-requirements?main=11[Open Source GRC]

| HITRUST CSF
| Organizations that create, access, store, or exchange sensitive information can use the HITRUST Common Security Framework (CSF) assessment as a roadmap to data security and compliance. The HITRUST CSF assurance program combines aspects from common security frameworks like ISO, NIST, PCI, and HIPAA.
| * https://www.eramba.org/community-downloads[eramba]
* https://www.opensourcegrc.org/compliance-requirements?main=17[Open Source GRC]

| CSA STAR
| The Security, Trust, Assurance, and Risk (STAR) Registry is a publicly accessible registry that documents the security and privacy controls provided by popular cloud computing offerings. STAR encompasses the key principles of transparency, rigorous auditing, and harmonization of standards outlined in the Cloud Controls Matrix (CCM).
| * https://cloudsecurityalliance.org/star/[Cloud Security Alliance]

|===

================================================
FILE: LICENSE
================================================
                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.


================================================
FILE: README.adoc
================================================
:!last-update-label:
:compat-mode!:
Awesome Open-Source Developer Security Tools
============================================
BoxyHQ team <hello@boxyhq.com>
v0.1.0, 2022-08-30

https://github.com/boxyhq/awesome-oss-devsec[⭐ Star us on GitHub]

List of awesome open-source developer security tools. Maintained by https://boxyhq.com[BoxyHQ], and heavily inspired by https://mvsp.dev/mvsp.en/index.html[MVSP].

It includes security principles and controls relevant to popular compliance certifications (like ISO27001, SOC2, MVSP, etc.). Also check this list of link:COMPLIANCE.adoc[popular compliance frameworks and certifications]

Interested in the future of developer security? Join our https://discord.com/invite/uyb7pYt4Pa[Discord] community to share and collaborate.

We'd love your feedback and contributions to this list. Please submit a GitHub issue or PR.

[cols="2a,6a,2a,2a",stripes=none]
|===
4+<h| Business controls
h| Control
h| Description
h| Compliance Controls
h| Tools

| Vulnerability Reports
| * Publish the point of contact for security reports on your website
* Respond to security reports within a reasonable time frame
| * https://mvsp.dev/mvsp.en/index.html[MVSP 1.1]
* ISO 27001 A.12.6.1
* SOC2 CC7.1
|

| Customer Testing
| * On request, enable your customers or their delegates to test the security of your application
* Test on a non-production environment if it closely resembles the production environment in functionality
* Ensure non-production environments do not contain production data
| * https://mvsp.dev/mvsp.en/index.html[MVSP 1.2]
* ISO 27001 A.12.6.1
* SOC2 CC7.1
|

| External Testing
| Contract a security vendor to perform annual, comprehensive penetration tests on your systems
| * https://mvsp.dev/mvsp.en/index.html[MVSP 1.4]
* ISO 27001 A.12.6.1
* SOC2 CC7.1
|

| Training
| Implement role-specific security training for your personnel that is relevant to their business function
| * https://mvsp.dev/mvsp.en/index.html[MVSP 1.5]
* ISO 27001 A.7.2.2
* SOC2 CC2.2
|

| Compliance
| * Comply with all industry security standards relevant to your business such as PCI DSS, HITRUST, ISO27001, and SSAE 18
* Comply with local laws and regulations in jurisdictions applicable to your company and your customers, such as GDPR, Binding Corporate Rules, and Standard Contractual Clauses
| * https://mvsp.dev/mvsp.en/index.html[MVSP 1.6]
* ISO 27001
* SOC2
| * https://github.com/deepfence/ThreatMapper[Deepfence ThreatMapper]
* https://hub.steampipe.io/mods?objectives=compliance[Steampipe Compliance Mods]

| Incident Management
| * Notify your customers about a breach without undue delay, no later than 72 hours upon discovery
  * Include the following information in the notification:
  ** Relevant point of contact
  ** Preliminary technical analysis of the breach
  ** Remediation plan with reasonable timelines
| * https://mvsp.dev/mvsp.en/index.html[MVSP 1.7]
* ISO 27001 A.16.1
* SOC2 CC7.3
|

4+<h| Application Design Controls
h| Control
h| Description
h| Compliance Controls
h| Tools

| Single Sign-On
| Implement single sign-on using modern and industry standard protocols
| * https://mvsp.dev/mvsp.en/index.html[MVSP 2.1]
* ISO 27001 A.9.4.2
* SOC2 CC6.1
| * https://github.com/boxyhq/jackson[BoxyHQ SAML Jackson]

| Access Control
| * Implement strict access control in your application guarding resources as needed
* Allow easy provisioning and de-provisioning of users
| * ISO 27001 A.9.1.1, A.9.2.1
* SOC2 CC6.1
| * https://www.aserto.com[Aserto]
* https://github.com/boxyhq/jackson#directory-sync[BoxyHQ Directory Sync]
* https://github.com/casbin/casbin[Casbin]
* https://cerbos.dev[Cerbos]
* https://github.com/ory/keto[Keto]
* https://github.com/osohq/oso[Oso]
* https://github.com/permitio/opal[OPAL]

| HTTPS-Only
| * Redirect traffic from HTTP protocol (port 80) to HTTPS (port 443)
  * Produce a clear scan using a widely adopted TLS scanning tool
  * Include the Strict-Transport-Security header on all pages with the `includeSubdomains` directive
| * https://mvsp.dev/mvsp.en/index.html[MVSP 2.2]
* ISO 27001 A.10.1.1
* SOC2 CC6.7
| * https://hub.steampipe.io/plugins/turbot/net[Steampipe Net Plugin]
* https://github.com/drwetter/testssl.sh[testssl.sh]


| Dependency Patching
| Apply security patches with a severity score of "medium" or higher, or ensure equivalent mitigations are available for all components of the application stack within one month of the patch release
| * https://mvsp.dev/mvsp.en/index.html[MVSP 2.6]
* ISO 27001 A.12.6.1
* SOC2 CC7.1
| * https://owasp.org/www-project-dependency-check[OWASP Dependency Check]
* https://owasp.org/www-project-dependency-track[OWASP Dependency Track]

| Logging
| Keep logs of:

  * Users logging in and out
  * Read, write, delete operations on application and system users and objects
  * Security settings changes (including disabling logging)
  * Application owner access to customer data (access transparency)

Logs must include user ID, IP address, valid timestamp, type of action performed, and object of this action.
Logs must be stored for at least 30 days, and should not contain sensitive data or payloads. 
| * https://mvsp.dev/mvsp.en/index.html[MVSP 2.7]
* ISO 27001 A.12.4.1
* SOC2 CC7.2
| * https://github.com/retracedhq[BoxyHQ Audit Logs]
* https://www.elastic.co/elastic-stack[ELK Stack]
* https://www.fluentd.org[FluentD]
* https://steampipe.io[Steampipe]

| Backup and Disaster Recovery
| * Securely back up all data to a different location than where the application is running
  * Maintain and periodically test disaster recovery plans
  * Periodically test backup restoration
| * https://mvsp.dev/mvsp.en/index.html[MVSP 2.8]
* ISO 27001 A.17.1
* SOC2 A1.3
|

| Encryption
| Use available means of encryption to protect sensitive data in transit between systems and at rest in online data storages and backups
| * https://mvsp.dev/mvsp.en/index.html[MVSP 2.9]
* ISO 27001 A.10.1
* SOC2 CC6.1
* GDPR
* HIPAA
| * BoxyHQ Privacy Vault (coming soon)

4+<h| Application Implementation Controls
h| Control
h| Description
h| Compliance controls
h| Tools

| List of Sensitive Data
| Maintain a list of sensitive data types that the application is expected to process
| * https://mvsp.dev/mvsp.en/index.html[MVSP 3.1]
* ISO 27001 A.10.1
* SOC2 CC6.1
* GDPR
* HIPAA
| * BoxyHQ Privacy Vault (coming soon)
* https://github.com/Bearer/bearer[Bearer]

| Data Flow Diagram
| Maintain an up-to-date diagram indicating how sensitive data reaches your systems and where it ends up being stored
| * https://mvsp.dev/mvsp.en/index.html[MVSP 3.2]
* ISO 27001 A.10.1
* SOC2 CC6.1
* GDPR
* HIPAA
| * BoxyHQ Privacy Vault (coming soon)

| Vulnerability Prevention
| Train your developers and implement development guidelines to prevent at least the following vulnerabilities:

  * Authorization bypass
  * Insecure session ID
  * Injections
  * Cross-site scripting
  * Cross-site request forgery
  * Use of vulnerable libraries
| * https://mvsp.dev/mvsp.en/index.html[MVSP 3.3]
* ISO 27001 A.12.6.1
* SOC2 CC7.1
| * https://owasp.org/www-project-top-ten[OWASP Top Ten]
* https://owasp.org/www-project-zap/[OWASP Zap]
* https://hub.steampipe.io/mods/turbot/net_insights[Steampipe Net Insights mod]
* https://wapiti-scanner.github.io[Wapiti Scanner]
* https://github.com/Bearer/bearer[Bearer]
* https://codemodder.io[Codemodder]

| Infrastructure and Cloud Security
| Perform audits, continuous monitoring, hardening and forensics readiness for your infrastructure and cloud assets.
| * ISO 27001 A.12.6.1
* SOC2 CC7.1
| * https://github.com/bridgecrewio/AirIAM[AirIAM]
* https://github.com/aquasecurity/cloudsploit[Cloudsploit]
* https://github.com/deepfence/ThreatMapper[Deepfence ThreatMapper]
* https://github.com/controlplaneio/kubesec[Kubesec Kubernetes security]
* https://github.com/prowler-cloud/prowler[Prowler for AWS]
* https://hub.steampipe.io/mods?objectives=compliance,security[Steampipe Compliance & Security mods]
* https://github.com/aquasecurity/trivy[Trivy container scanner]



4+<h| Code Security
h| Control
h| Description
h| Compliance controls
h| Tools

| Data Leakage Prevention
| Protect secrets from leaking into code, logs and unwanted systems.
| * ISO 27001 A.12.6.1
* SOC2 CC7.1
| * https://github.com/GitGuardian/ggshield[GitGuardian]
* https://github.com/zricethezav/gitleaks[Gitleaks]
* https://hub.steampipe.io/plugins/turbot/code[Steampipe Code Plugin]
* https://github.com/Bearer/bearer[Bearer]

| Zero Trust Principles
| Keep data encrypted from end-to-end and have no listening ports for malware/ransomeware to spread etc.
| * https://doi.org/10.6028/NIST.SP.800-207[NIST Special Publication 800-207]
| * https://github.com/openziti/ziti[OpenZiti] (numerous SDKs)
|===


================================================
FILE: SUMMARY.adoc
================================================
= Summary

. link:README.adoc[DevSec Tools]
. link:COMPLIANCE.adoc[Compliance frameworks and certifications]

================================================
FILE: book.json
================================================
{
  "plugins": [
    "@honkit/honkit-plugin-ga"
  ],
  "pluginsConfig": {
    "ga": {
      "trackingID": "G-SPZEPCS1QS",
      "anonymizeIP": true
    }
  }
}

================================================
FILE: package.json
================================================
{
  "name": "awesome-oss-devsec",
  "version": "0.1.0",
  "description": "An awesome list of OSS developer-first security tools",
  "main": "index.js",
  "scripts": {
    "build": "honkit build",
    "dev": "honkit serve",
    "help": "honkit --help"
  },
  "repository": {
    "type": "git",
    "url": "git+https://github.com/boxyhq/awesome-oss-devsec.git"
  },
  "keywords": [
    "security"
  ],
  "author": "Deepak Prabhakara",
  "license": "Apache-2.0",
  "bugs": {
    "url": "https://github.com/boxyhq/awesome-oss-devsec/issues"
  },
  "homepage": "https://github.com/boxyhq/awesome-oss-devsec#readme",
  "devDependencies": {
    "honkit": "6.0.2",
    "@honkit/honkit-plugin-ga": "1.0.1"
  },
  "engines": {
    "node": ">=20.11.0"
  }
}