
Find vulnerabilities
prioritize remediation
Vulnerability Scanner checks code, dependencies, container images and exposed assets. It combines CVSS severity, EPSS likelihood, CISA KEV evidence and code reachability to prioritize fixes. Findings use SARIF and component inventories use SBOMs.
Deployment consultationWe’ll confirm the scope and deployment environment during the consultation. Deployment guide
On each commit or image push,
rescan only what changed
Commits, builds, registry pushes, and cloud configuration changes trigger scans. Vulnerability Scanner compares with the previous results and checks changed files and layers first. Initial and follow-up scan times vary with repository size and the environment.
- Add a scan stage to GitHub Actions, GitLab CI, and Jenkins pipelines
- Scan images on push to Harbor or ECR
- Rescan domains and IP ranges on a set schedule
example-lib 4.2.12 minutes ago
src/config/payment.ts2 minutes ago
ingress/api-gw1 hour ago
node:22-alpine1 hour ago
Findings most likely to be exploited
come first
Findings with the same CVSS score of 9.8 can have different priorities. We consider whether the vulnerable function is called, whether the service is reachable from the internet, the EPSS probability, whether it appears in KEV, and whether a public exploit exists. Assets you mark as important, such as payment or authentication systems, receive more weight.
- Lower priority for dependency vulnerabilities with no reachable call path
- Scores are recalculated when EPSS and KEV data change. Updates can be imported offline on isolated networks.
- You set the criticality of your assets
See where to fix each issue and who owns it,
along with a proposed change for review
Each finding identifies the file path, line number, and team responsible for the code. We prepare a draft PR for straightforward fixes such as updating a dependency or moving a hardcoded key to an environment variable. When a fix requires a logic change, we provide an explanation and reference code for the developer to review.
- Identify owners from CODEOWNERS and commit history
- Draft PRs require a manual merge
- Rescan after a fix is applied, then close the Jira ticket
- "example-lib": "4.2.1" + "example-lib": "4.2.2" - const KEY = "hardcoded-example"; + const KEY = process.env.PAYMENT_KEY;
Key features
SAST · SCA
Review in-house code and third-party libraries in one list
Containers and images
Check OS package vulnerabilities by image layer and settings such as containers running as root
External attack surface
Forgotten subdomains, exposed management ports, and public storage buckets
SBOM · AI-BOM
SBOMs in CycloneDX and SPDX formats, plus an inventory of internal AI models
IaC and cloud configuration
Flag misconfigurations in Terraform and Kubernetes manifests, such as rules that allow 0.0.0.0/0
Isolated execution
Outbound traffic is blocked on analysis nodes
How it works
Integration
Connect to Git, CI, registries, and cloud accounts with read-only access
Collection
Code and image layers that changed since the last scan
Analysis
Rule matching, taint analysis, and dependency tree analysis
Priorities
Score findings using EPSS, CISA KEV, reachability, and asset criticality
Remediation and verification
Open a draft PR or ticket, then rescan after the change is applied
Integration tools and methods
Integrations use APIs and syslog. We’ll confirm what each tool supports based on its version and your operating environment.
Deployment options
| Method | Description | Recommended |
|---|---|---|
| On-premises and isolated networks | The platform runs in your data center. Offline packages deliver detection rule and model updates so the platform can operate without an external connection. | Finance, public sector, and defense |
| Dedicated cloud | A dedicated environment serves one customer in a South Korean cloud region. | Enterprises and healthcare |
| Managed | In this MDR option, Genox handles security monitoring. We’ll confirm the scope and response procedures during the consultation. | Small and medium-sized businesses and mid-market companies |
| MSSP partners | The security service provider operates separate tenants for each customer. | Security service providers |
Frequently asked questions
Where is the source code processed?
For on-premises deployments, we analyze source code in your environment. For dedicated cloud deployments, we use an environment reserved for your organization. We review what data is transferred and where it is stored during deployment planning.
Can I use this alongside my current SAST tool?
Yes. If your existing tool exports SARIF, Vulnerability Scanner can import its findings, deduplicate them, and rank them using the same criteria. Your existing rules stay in place.

Discuss deploying Vulnerability Scanner
Tell us about your operating environment, and we’ll explain what the demo and proof of concept can cover.