Mittn: Security test tool runner for test automation in CI
Switch branches/tags
Nothing to show
Clone or download
Latest commit 7808552 Aug 11, 2016

README.rst

Mittn

"For that warm and fluffy feeling"

Background

Mittn is an evolving suite of security testing tools to be run in Continuous Integration context. It uses Python and Behave.

The idea is that security people or developers can define a hardening target using a human-readable language, in this case, Gherkin.

The rationale is:

  • Once the initial set of tests is running in test automation, new security test cases can be added based on existing ones without having to understand exactly how the tools are set up and run.
  • Existing functional tests can be reused to drive security tests.
  • Test tools are run automatically in Continuous Integration, catching regression and low-hanging fruit, and helping to concentrate exploratory security testing into areas where it has a better bang-for-buck ratio.

Mittn was originally inspired by Gauntlt (http://gauntlt.org/). You might also want to have a look at BDD-Security (http://www.continuumsecurity.net/bdd-intro.html) that is a pretty awesome system for automating security testing, and offers similar functionality with OWASP Zaproxy.

Installation

Exact installation varies by the test tool you want to use. See the docs/ directory for detailed instructions.

NOTE: Backwards compatibility of false positive databases has been broken. The last version to be compatible with the original database schema is tagged "v0.1" on GitHub.

Features

Currently, the tool implements:

If you'd like something else to be supported, please open an issue ticket against the GitHub project.

As you can see, all the heavy lifting is done by existing tools. Mittn just glues it together.

Contact information

If you have questions about the usage, please open a ticket in the GitHub project with a "Question" tag.

If you have found a bug, please file a ticket in the GitHub project.

If necessary, you can also email opensource@f-secure.com, but opening a ticket on GitHub is preferable.