Running a scan
Point SecNxt at a target and get prioritised findings in minutes.
Overview
The 'New scan' screen is where security testing starts. You choose what to test — source code, dependencies, a website, an API, a mobile app or cloud configuration — provide the target, and SecNxt does the rest.
Each scan type maps to a dedicated engine tuned for that surface, so you get depth rather than a shallow one-size-fits-all check.
How it works
When you launch a scan, SecNxt creates a scan record scoped to the current workspace and the asset you choose.
The matching engine runs (in the cloud, or on your self-hosted runner for private targets), streams progress, and writes findings back as it goes.
Findings are de-duplicated, assigned a severity and verification tier, and passed through the AI Threat Predictor for prioritisation.
How to use it
- 1Open 'New scan' from the sidebar.
- 2Pick the scan type that matches your target (e.g. Website URL Scan for a live web app).
- 3Select or create the asset the scan belongs to.
- 4Enter the target details (repository, URL, package manifest, etc.).
- 5Start the scan and watch live progress; results appear under Vulnerabilities and on the dashboard.
When to use it
- First-time baseline of a new application or client environment.
- Re-testing after a fix to confirm an issue is resolved.
- Pre-release security gate before shipping.
Tips & best practices
- For private or internal targets, enrol a self-hosted runner so code and traffic never leave your network.
- Group related targets under one asset so findings and history stay together.
FAQ
- How long does a scan take?
- Most scans finish in minutes, though large codebases, deep web crawls or full VAPT engagements take longer.
- Can I schedule scans to run automatically?
- Yes — continuous re-assessment lets you run scans on a recurring schedule and track posture over time.
Related guides
Source code scanning (SAST)
Find vulnerabilities in your own code before it ships.
Dependency scanning (SCA)
Detect known-vulnerable open-source packages in your dependencies.
Website / web app scanning (DAST)
Test a running web application the way an attacker would.
API endpoint scanning
Test REST and GraphQL APIs for auth, injection and data-exposure flaws.
VAPT — Vulnerability Assessment & Penetration Testing
Audit-grade, human-verified penetration testing with defensible reporting.
Assets (projects & targets)
The specific things you scan — a repo, a site, an API, a cloud account.