Skip to content

CSI (Continuous Security Integration) Framework => Automated Security Testing for CI/CD Pipelines & Beyond

License

Notifications You must be signed in to change notification settings

spyd3r/csi

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

CSI

Table of Contents

Call to Arms

If you're willing to provide access to commercial security tools (e.g. Rapid7's Nexpose, Tenable Nessus, QualysGuard, HP WebInspect, IBM Appscan, etc) please PM us as this will continue to promote CSIs interoperability w/ industry-recognized security tools moving forward.

Intro

What is CSI

CSI (Continuous Security Integration) is an open security automation framework that aims to stand on the shoulders of security giants, promoting trust and innovation. Build your own custom automation drivers freely and easily using pre-built modules. If a picture is worth a thousand words, then a video must be worth at least a million...let's start out by planting a million seeds in your mind:

Creating an OWASP ZAP Scanning Driver Leveraging the csi Prototyper

Continuous Security Integration: Basics of Building Your Own Security Automation

Why CSI

It's easy to agree that while corporate automation is a collection of proprietary source code, the core modules used to produce automated solutions should be open for all eyes to continuously promote trust and innovation...broad collaboration is key to any automation framework's success, particularly in the cyber security arena.

How CSI Works

Leveraging various pre-built modules and the csi prototyper, you can mix-and-match modules to test, record, replay, and rollout your own custom security automation packages known as, "drivers."

The fastest way to get rolling w/ csi is to deploy a pre-built Kali Rolling box, available on Vagrant Cloud. This is a special deployment of Kali Rolling - WORKING rollouts of AFL w/ QEMU instrumentation ready-to-go, PEDA (Python Exploit Development Assistance for GDB), OpenVAS, latest clone of Metasploit, Arachni, Jenkins (w/ pre-canned jobs and the ability to create your own prior to deployment aka User-Land!), etc. These are just some of the numerous security and CI/CD tools made available for your convenience...updated on a daily basis.

An instance of DefectDojo is stood up on the box to facilitate common security tools integration, resulting in a centralized place to manage scan results, track the lifecycle of vulnerabilities, and analyze trends via metrics and reporting! CSI driver integration is made to be seamless w/ OS dependencies already installed. This is all made available for architectures such as AWS, Docker, VirtualBox, and/or VMware. See the Deploy section for more details.

CSI Modules Can be Mixed and Matched to Produce Your Own Tools

Also known as, "Drivers" CSI can produce all sorts of useful tools by mixing and matching modules. CSI

Clone CSI

Certain Constraints Mandate CSI be Installed in /csi: $ sudo git clone https://github.com/ninp0/csi.git /csi

Deploy

Basic Installation Dependencies

Deploy in AWS EC2

AWS EC2 Quick-Start

Deploy in Docker Container

Docker Quick-Start

Deploy in VirtualBox

VirtualBox Quick-Start

Deploy in VMware

VMware Quick-Start

General Usage

General Usage Quick-Start

It's wise to rebuild csi often as this repo has numerous releases/week (unless you're in the Kali box, then it's handled for you daily in the Jenkins job called, "selfupdate-csi":

$ /csi/vagrant/provisioners/csi.sh && csi
csi[v0.3.11]:001 >>> CSI.help

Driver Documentation

For a list of existing drivers and their usage

I hope you enjoy CSI and remember...ensure you always have permission prior to carrying out any sort of hacktivities. Now - go hacktivate all the things!

About

CSI (Continuous Security Integration) Framework => Automated Security Testing for CI/CD Pipelines & Beyond

Resources

License

Code of conduct

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Ruby 95.8%
  • Shell 4.2%