rylyade1/SecurityRAT-ASVS-Importer

Script to import ASVS controls to SecurityRAT in the blink of an eye.

SecurityRAT-ASVS-Importer

Script to generate and import ASVS controls to SecurityRAT in the blink of an eye.

TL;DR: If you just need the ASVS requirements in SQL format and don't care about the script, go to the output folder. 😉

Rationale

SecurityRAT ("Security Requirement Automation Tool") is a tool helping you manage security requirements in your agile development projects. In a nutshell, you specify the properties of an application (usually, we use the name "artifact") that you’re developing. Based on these properties, the tool gives you a list of security requirements you should fulfill. ¹

At the time of writing, there are no scripts (that I know) to automate the generation and importation of ASVS security controls into the SecurityRAT tool.

Importing ASVS controls manually has the following drawdowns:

1. Time-consuming. 4.0.3 version of ASVS contains nearly 300 security controls and gets updated frequently.
2. Prone to human error.

The SecurityRAT creators also released the SecurityRAT-Requirements repository that contains SQL dumps ready to import.

Potential improvements:

1. The ASVS controls are not updated to the last version.
2. Just English language available, and the current ASVS version is also in Spanish and Simplified Chinese (at least in CSV format).
3. You need to import them manually to the DB.

Features

SecurityRAT-ASVS-Importer tries to address the above points of improvement with the following features:

• Fetches the latest ASVS version available.
• Let you choose among the available languages (English, Spanish or Simplified Chinese).
• Automatically imports all requirements into SecurityRAT database specifying a running DB container.
• It just takes ~4 seconds to perform all the tasks! 🏎️

Installation and usage

git clone https://github.com/mllamazares/SecurityRAT-ASVS-Importer
cd SecurityRAT-ASVS-Importer
bash secrat_asvs_importer.sh -h

Quick-start

1. Get SecurityRAT up and running (preferably using Docker):

   git clone https://github.com/SecurityRAT/SecurityRAT-dockercompose.git
   cd SecurityRAT-dockercompose
   docker-compose up

2. In a different session, clone this repo and open the folder:

   git clone https://github.com/mllamazares/SecurityRAT-ASVS-Importer
   cd SecurityRAT-ASVS-Importer

3. Once step 1 has finished, auto-import the latest ASVS Spanish version to SecurityRAT using the following command:

   $ bash secrat_asvs_importer.sh -l es -d securityrat-mariadb
   [+] Searching latest ASVS relase...
       The latest ASVS version is 4.0.3
   [+] Downloading the es version of ASVS in CSV format...
       ./csv/asvs_4.0.3_es.csv file downloaded!
   [+] Creating SQL dump with the required configuration...
       ./sql/output/secrat_asvs_final_4.0.3_es.sql file generated!
   [+] Loading SQL requirements into SecurityRAT database...
   [+] All done! Bye!
   

To verify that the requirements are indeed loaded:

1. Navigate to http://localhost:9002/ and login with admin/admin (yep, you should change this in the future).
2. Click on Define a new artifact.
3. Select the ASVS chapter and level that you need and smash the Generate button.
4. There you go! Now you have an updated version of the ASVS controls in Spanish! 😎

Options

$ bash secrat_asvs_importer.sh -h
    NAME
        SecurityRAT ASVS Importer

    DESCRIPTION
        - Small script to import ASVS controls to SecurityRAT in the blink of an eye.
        - GitHub: https://github.com/mllamazares/SecurityRAT-ASVS-importer
        - Author: https://www.linkedin.com/in/mllamazares/

    SYNOPSIS
        ./secrat_asvs_importer.sh [OPTIONS]

    OPTIONS
        -l <language> 
            The language of the ASVS controls. Avaiable options are en, es or zh-cn. Default is en
        -d <securityrat_docker_db_container>
            The running docker container that contains the SecurityRAT database where will overwrite the requirements.
            Example: securityrat-mariadb
        -h
            Prints this message (duh).

TODO

• Create an enhanced categorization of the requirements.
  • For sure I will map STRIDE-vs-ASVS, but I'm open to suggestions.
• Migrate to Python for better portability and ease of collaboration.
• Extend to different security standards like BSI C5.

Footnotes

1. Extracted from https://securityrat.github.io/ ↩