.svg)
Review
“As a software agency that builds custom software for our clients, it's important to keep vulnerabilities out of our code. Aikido does that job perfectly”
Manu D.B.
CTO at We Are
Software Supply Chain Security
Malware detection in dependencies
- Protect your app from software supply chain attacks
- Detects malware early, before a CVE is created
- Malware protection is typically exclusive to enterprises, but included in Aikido!
Powered by
Phylum
Importance of Malware Scanning
Why should you do malware scanning?
When you're infected hackers can easily extract data or install bitcoin miners.
With Malware, speed matters.
Real-time Detection
With malware infections, speed is of the essence. Aikido identifies malware before a CVE is created through Phylum’s threat feed. Continuously scanning packages such as NPM, Nuget & PyPi.
Prevent malicious code from entering your app
By integrating Aikido in your CI/CD you can block malicious code from being merged.
Features
Malware Scanning Features
1
Instant notifications
Get instant critical notifications via email or on Slack or Teams from the moment Aikido detects malware. Legacy SCA scanners won’t provide this protection.
2
Detects malicious packages
Malicious packages can do real damage, like hijacking system resources for cryptocurrency mining or obfuscating your code. Think of data leaks or massive server costs.
3
Malware threat feed
Check out which malware packages are currently detected in public registries, directly in your Aikido software supply chain attacks report.
Check out the feed
Aikido's other scanners
Built on reliable open source security scanners, all combined in one platform. Enhanced with our own code to cover any scanning gaps.
Cloud
Cloud posture management (CSPM)
Detects cloud infrastructure risks across major cloud providers.
Leverages
CloudSploit
Custom Rules Engine
Code & Containers
Open source dependency scanning (SCA)
Continuously monitors your code for known vulnerabilities, CVEs and other risks.
Leverages
Trivy
Syft
Grype
Custom Rules Engine
Code
Secret Detection
Checks your code for leaked and exposed API keys, passwords, certificates, encryption keys, etc...
Leverages
Gitleaks
Code
Static code analysis (SAST)
Scans your source code for security risks before an issue can be merged.
Leverages
Semgrep
Gosec
Custom Rules
Code
Infrastructure as code
Scans Terraform, CloudFormation & Kubernetes infrastructure-as-code for misconfigurations.
Leverages
Checkov
Containers
Container image scanning
Scans your container OS for packages with security issues.
Leverages
Syft
Grype
AWS Inspector
Custom Scanner
Domain
Surface monitoring (DAST)
Dynamically tests your web app’s front-end to find vulnerabilities through simulated attacks. Built on ZAP & Nuclei.
Leverages
ZAP
Nuclei
Custom Rules
Code & Containers
Open source license scanning
Monitors your licenses for risks such as dual licensing, restrictive terms, bad reputation, etc..
Leverages
Syft
Grype
Custom Rules
Code
Malware detection in dependencies
Prevents malicious packages from infiltrating your software supply chain. Powered by Phylum.
Leverages
Phylum
Code & Containers
Outdated Software
Checks if any frameworks & runtimes you are using are no longer maintained.
Leverages
endoflife.date
Custom
Connect your own scanner
Imports and auto-triages findings from your current scanner stack.
Import from
GitHub Advanced Security
SonarQube
FAQ
More to explore
Is Aikido's software pentested?
Yes. We run a yearly pentest on our platform and also have an ongoing bug bounty program to ensure the security of Zen is continuously tested by a wide range of security experts.
Can I also generate an SBOM?
You can create a CycloneDX SBOM or csv export with one click. Just go to the Licenses & SBOM report where you'll get a full overview of all the packages & licenses you're using.
What do you do with my source code?
Aikido does not store your code after analysis has taken place. Some of the analysis jobs such as SAST or Secrets Detection require a git clone operation. More detailed information can be found on docs.aikido.dev.
Do I need to give access to my repos to test out the product?
When you log in with your VCS we don’t get access to any of your repositories. You can manually give access to the repositories you’d like to scan. It’s also possible to test out the platform using sample repositories.
I don’t want to connect my repository. Can I try it with a test account?
Of course! When you sign up with your git, don’t give access to any repo & select the demo repo instead!
Does Aikido make changes to my codebase?
We can’t & won’t, this is guaranteed by read-only access.
More to explore
Trusted by development teams around the world
.svg){kind=icon}
Get started for free
No credit card required.
