Skip to content

Latest commit

 

History

History
91 lines (61 loc) · 4.83 KB

README.md

File metadata and controls

91 lines (61 loc) · 4.83 KB

Tcsfw

This is early version of the Tool-driven security assessment (TDSA) framework. The framework is intended to support automated security assessment of Internet of Things (IoT) and other systems by running common security tools. (The name is acronym from Transparent Cybersecurity Framework, which is name used in a research paper, but things have developed and the name is TDSA now.)

The project is part of the upcoming PhD thesis of the author. Orginally, the project was created to demonstrate the TDSA approach for research purposes, but the goal is to make it a real-world usable security assessment framework. The research will be published in the PhD disseration, which is under works. On the mean time, there are two published research papers:

Kaksonen, R., Halunen, K., Laakso, M., & Röning, J. (2023). Transparent Security Method for Automating IoT Security Assessments. In The 18th International Conference on Information Security Practice and Experience (ISPEC). Springer International Publishing.

Kaksonen, R., Halunen, K., Laakso, M., & Röning, J. (2024). Automating IoT Security Standard Testing by Common Security Tools. In ICISSP - 10th International Conference on Information Systems Security and Privacy. (p. 42-53). SciTePres

The functionality of the framework is currently limited to reading output of several different "security" tools, mapping them into security statement and claims, and given verdicts for the claims. Security statement describes relevant portions of a system, e.g. attack surface and security controls. Claim (requirement, test) is security-relevant assertion which can be verified. The verification is done by running supported tools, which output is them used to pass verdict for the claim.

Future plans

On the long run the framework is intended to cover the collection of the tool outputs and provide more rich processing options and API for the claim verdicts. Check the roadmap for upcoming features.

Usage

Security statement are created by Python Domain Specific Language (DSL). The idea is that security statement are created as Python applications, with one or several statements per application. Thus, the first thing is to create a Python application project. I recommend creating a virtual environment for the project (there are many guides in the Internet). For example

$ mkdir my_ss
$ cd my_ss
$ python 3.11 -m venv .venv
$ source .venv/bin/activate

After that, you must install the framework from Github. Then you can start working with you security statement using your favorite editor or IDE. The framework comes with sample security statements in directory samples/. The security statements description are in a Domain Specific Language (DSL).

Assuming your security statement is statement.py, you execute it as follows:

$ python statement.py

Providing tool data

Once the security statement is defined, it can be verified. The verification is tool-driven based on output from the tools. Tool results must be stored in a batch directory structure, which is specified by --read argument, e.g.

$ python statement.py --read <batch-dir>

The --read and --http-server arguments can be combined to inspecft the verification results using the UI.

Batch files can be provided through API in a zip-file to endpoint api1/batch. The content type must be set to application/zip and authorization-cookie must be set. This can be done e.g by curl-command, like this:

$ curl -v -X POST --data-binary @<batch-file>.zip  \
   -H "Content-Type: application/zip" -b "authorization=xxx" \
   http://localhost:8180/api1/batch

More options

The framework has additional command-line options.

API server

The framework can run as API server. The server can only run a single security statement or it can dynamically load them by API calls.

The servers are inteded to be run Docker containers. The containers can bundled into a deployment, see tcsfw UI documentation.

Client tool

The API can be used by client tool tcsfw.

Sample security statements

A security statement for Ruuvi gateway and tags (https://ruuvi.com/) was developed during research. The statement is in directory samples/ruuvi/. The data for verifying the security statement is available for academic research, please request it from Rauli. Remember to tell the goals of the research and the organization performing it. Right to refuse requests is reserved.

The security statement for Ruuvi is executed like this, assuming working directory is the Tcsfw root:

$ python samples/ruuvi/ruuvi.py

The command dumps some basic information about the security statement.

License

The project is published with MIT license.