Open-Source tool to help secure Your CICD workloads
Security tools can be quite expensive, and many of them only address a single aspect of your security needs. But what if they didn’t have to? Take a closer look at Mixeway Flow, an all-in-one solution designed to simplify and unify your security processes without breaking the bank.
No External Tools Needed
Mixeway Flow comes with built-in open-source security vulnerability scanners, ready to be used without any additional software or costs.
Unified Vulnerability Dashboard
Access all detected vulnerabilities along with the necessary details on a single, user-friendly dashboard, streamlining your security management.
Seamless CI/CD Integration
No need to modify your existing CI/CD pipeline. Mixeway Flow works effortlessly with webhooks from your GitLab or GitHub projects, integrating security without disrupting your workflow.
Robust RBAC Implementation
Mixeway Flow includes a properly designed Role-Based Access Control (RBAC) system, ensuring each team member has access only to the scope necessary for their role, enhancing security and efficiency.
Install and start Mixeway Flow
Effortless Integration with Mixeway Flow
Getting started with Mixeway Flow is incredibly simple. We’ve designed the platform to integrate seamlessly into your existing workflows, so you can start securing your projects without any hassle. Whether you’re setting it up for the first time or managing ongoing operations, Mixeway Flow offers a user-friendly experience that makes security accessible for everyone on your team.
Mixeway Flow have all required and most needed scan engines built in – You need nothing more
➡️ SAST engine: Bearer (https://github.com/Bearer/bearer) – SAST scan is performed on the source code created and written by the team’s developers looking for any places that might be a source for problems related with any type of injections or other threats.
Scan requirements: None. Scan is performed for every change without any conditions.
➡️ SCA engine: OWASP Dependency Track (https://github.com/DependencyTrack/dependency-track) – Integrating SCA scanning into Your software development lifecycle help You properly manage dependencies You introduce to the codebase.
Scan requirements: In order to trigger SCA engine there has to be sbom.json file
located in the root of the repository
➡️ IaC engine: KICS (https://github.com/checkmarx/kics) – This type of scan verify Dockerfiles, terraform, kubernetes deployments and much more configurations that can be deployed looking for the misconfiguration or bad practices to be alerted.
Scan requirements: None. Scan is performed for every change without any conditions
➡️Secret Leaks engine: gitleaks (https://github.com/gitleaks/gitleaks) – Most severe incidents in the Public Cloud (but not only) occurred due to misconfigurations, hardcoded keys or keys accidentally pushed to the git repository. This kind of tests help You detect such problems and give You the timeframe needed to properly rotate leaked secrets.
Scan requirements: None. Scan is performed for every change without any conditions.
