Skip to content

Scan Engine v11.1

19 min read Updated November 14, 2026 Sn1per SE v11.1 - Professional & Enterprise
Documentation/Scan Engine v11.1

Reference for what is new and changed in Sn1per Scan Engine (SE) v11.1: what each feature does, the settings that control it and their defaults.

Sn1per SE v11.1 is the scan engine behind Sn1per Professional and Sn1per Enterprise. It adds AI analysis inside the scan, a dedicated Active Directory mode, browser-based verification with Playwright, a Kali tools fallback, scan-over-scan change detection, CISA KEV and EPSS enrichment, an attack tree builder, 56 new detection templates and a rebuilt subdomain enumeration pipeline. For an overview of the release, read the Sn1per SE v11.1 release announcement.

For authorized security testing only. Every option on this page that acts against a target beyond scanning (AI-selected Metasploit modules, automated post-exploitation, Playwright form injection and the Active Directory live attack settings) ships disabled. Enable them only against systems you own or are explicitly permitted, in writing, to test, and within the scope of that permission.

On this page

Upgrading to v11.1

Sn1per SE v11.1 is available only to Sn1per Professional and Sn1per Enterprise customers. It is not published to the public GitHub repository, so you cannot get it by cloning the repository or running a fresh install from it. Upgrade an existing licensed install in either of two ways:

  • CLI: run sniper -u (or sniper --update) as root.
  • Web UI: open the Updates menu option in the Sn1per Professional or Sn1per Enterprise web UI to check for and install the update.
sudo sniper -u

The update keeps your existing conf/ad profile and API key file (conf/.GLOBAL_API_KEYS), removes retired templates and plugins, and writes a structured log to /usr/share/sniper/install.log. The full list of changes ships with the update as /usr/share/sniper/CHANGELOG.md.

After upgrading: clean API keys out of old loot

Earlier versions could copy API key values into resume files, verbose logs and some tool output. v11.1 masks them before they reach loot, reports or logs. To find and clean files written by earlier versions, run:

# List loot files that contain an API key value (path and key name only)
sudo /usr/share/sniper/bin/sniper-mask-secrets --scan

# Redact them in place, keeping owner, mode and modification time
sudo /usr/share/sniper/bin/sniper-mask-secrets --redact

Both options default to the loot/ directory and accept one or more paths. --scan exits 0 when it finds nothing and 1 when it finds key values. Masked values appear as [REDACTED:<NAME>].

Where settings live

Each scan loads one configuration profile from /usr/share/sniper/conf/. Unless you pass a profile with -c /path/to/profile, Sn1per picks it from the scan mode:

Scan mode (-m) Profile loaded
normal and modes without their own profile conf/default
flyover, stealth conf/flyover
fullportscan conf/fullportscan
vulnscan conf/vulnscan
full_scan conf/full_scan
recon_passive conf/recon_passive
recon_active conf/recon_active
ad (new in v11.1) conf/ad

/usr/share/sniper/sniper.conf holds the reference defaults quoted on this page. To change a setting for your scans, edit it in the profile your scans load, or select and edit that profile in the web UI Config Editor. API keys for AI providers and recon sources go in conf/.GLOBAL_API_KEYS, which every scan loads. v11.1 ships the redacted templates conf/.GLOBAL_API_KEYS.example and conf/.ad.example instead of live credential files.

Check the profile you scan with. A few profiles ship with values that differ from sniper.conf. For example, CISA KEV and EPSS enrichment (ENRICHMENT_ENABLED) is on in sniper.conf and most profiles but off in conf/default, the profile normal mode loads.

Active Directory mode

AD mode (-m ad, profile conf/ad) enumerates the SMB, LDAP, Kerberos and RPC surface of a domain, runs a defensive posture audit and correlates attack paths across hosts. Without credentials you get the exposed surface; with a low-privileged domain account the credentialed checks run as well.

# Unauthenticated assessment of an internal range
sudo sniper -t 10.0.0.0/24 -m ad -w corp-ad

# Credentialed assessment: set the AD_* credentials in conf/ad first
sudo nano /usr/share/sniper/conf/ad
sudo sniper -t dc01.corp.local -m ad -w corp-ad
Setting (conf/ad) Default Description
AD_DOMAIN "" AD DNS domain. When empty, Sn1per derives it from the scan’s own enumeration
AD_USER / AD_PASS "" Domain account for the credentialed checks (Kerberoasting, delegation, account, privileged group and directory audits). Each credentialed check is skipped when AD_USER is empty
AD_HASH "" NT hash, used only by the opt-in AD_OVERPASS_HASH setting
AD_DC_IP "" Domain controller address. Defaults to the scan target

What AD mode covers:

  • Kerberos and delegation: Kerberoastable and AS-REP roastable accounts, unconstrained and constrained delegation, RC4-only and DES encryption types, krbtgt password age.
  • Privilege and ACLs: privileged group audit, dangerous ACLs, DCSync-capable principals, shadow credentials, domain trusts.
  • Hygiene: stale and non-expiring passwords, passwords in account descriptions, GPP and LAPS exposure, GPO and SYSVOL audit, obsolete operating systems, insecure DNS updates, SCCM discovery, hybrid identity exposure.
  • Protocol posture: LDAP signing and channel binding, SMB signing, and AD/SMB CVE detection (AD_CVE_SCAN).
  • Attack paths: BloodHound collection (BLOODHOUND_COLLECT) and shortest-path-to-Domain-Admin queries (BLOODHOUND_PATHFIND), which use cypher-shell when it is installed and the bundled client bin/sniper-cypher otherwise.
  • Offline hash cracking (HASH_CRACKING, on in conf/ad): recovered AS-REP, Kerberoast and Timeroast hashes are cracked locally with hashcat, so no packets reach the target.

Every finding rolls up into a 0-100 AD posture score (higher is stronger) and is mapped to MITRE ATT&CK, NIST 800-53, CIS Controls v8 and DISA STIG identifiers. Because each run is scored, you also get a scan-over-scan trend. The default port list (DEFAULT_PORTS) now includes the AD ports (88, 464, 636, 3268, 3269, 5985, 5986, 9389, 47001 and UDP 123/464), so a normal scan recognizes domain controllers too.

Live attack settings (disabled by default)

AD mode is enumeration and a defensive audit out of the box. The settings below act against the domain, so each ships disabled. Turn them on one at a time, and only on domains you are authorized, in writing, to attack.

Setting (conf/ad) Default What it does
AD_PASSWORD_SPRAY 0 Sprays the harvested users and passwords with NetExec. The only AD setting that can lock out real accounts: it refuses to run until the domain lockout threshold has been read from the password policy, and never sends more than the threshold minus one passwords per observation window
AD_DEFAULT_CREDS 0 Guest/null and vendor-default administrator pairs, with the same lockout guard
AD_OVERPASS_HASH 0 Requests a Kerberos TGT from a recovered or supplied NT hash
AD_CVE_EXPLOIT 0 Exploits the AD/SMB CVEs that AD_CVE_SCAN detected. Refuses to run unless AD_EXPLOIT="1" is also set
AD_EXPLOIT + AD_ATTACKER_IP 0 / "" Runs the coerce-and-relay and ESC8 paths that correlation has already confirmed. Nothing fires unless both are set. Zerologon is never exploited; it stays check-only

AI analysis and agentic scanning

v11.1 puts AI inside the scan: it triages each tool’s output, can adjust which tools run next, can pick Metasploit modules per service, and at the end runs five specialist analyses over the findings, grades them by proof level and writes an assessment. Every AI feature is off by default (AI_ENABLED="0") and each has its own switch.

Providers

Set AI_PROVIDER to one of six providers. Cloud provider keys go in conf/.GLOBAL_API_KEYS.

AI_PROVIDER Provider Credentials and settings
ollama (default) Ollama OLLAMA_URL (default http://127.0.0.1:11434/api/generate), OLLAMA_MODEL
openai OpenAI OPENAI_API_KEY
anthropic Anthropic Claude ANTHROPIC_API_KEY
openrouter OpenRouter OPENROUTER_API_KEY
zai Z.ai ZAI_API_KEY
claudecode Claude Code CLI The claude CLI installed on the scanning host; CLAUDE_CODE_MAX_TURNS (default 10)

Local by choice, not by default. The shipped AI_MODEL and OLLAMA_MODEL are deepseek-v4.1-flash:cloud, an Ollama cloud model: Ollama forwards those prompts to a hosted service. To keep scan data inside your network, pull a model to your own hardware and set it as shown below.

# Local-only AI: every prompt stays on your own hardware
# 1. On the Ollama host:  ollama pull your-local-model
# 2. In the profile your scans load (for example /usr/share/sniper/conf/default):
AI_ENABLED="1"
AI_PROVIDER="ollama"
OLLAMA_URL="http://127.0.0.1:11434/api/generate"
OLLAMA_MODEL="your-local-model"
AI_MODEL="your-local-model"
AI_SCAN_ANALYSIS="1"
AI_SCAN_DECISIONING="1"
AI_VULNERABILITY_ANALYSIS="1"
SN1PER_AI_EXPLOIT_VERIFICATION="1"
AI_REPORT_ENHANCEMENT="1"
# Optional: a larger local model for the deep analysis stages
# AI_PHASE2_MODEL="your-larger-local-model"

Core settings

Setting Default Description
AI_ENABLED 0 Master switch. No AI feature runs without it
AI_PROVIDER / AI_MODEL ollama / deepseek-v4.1-flash:cloud Primary provider and model
AI_FALLBACK_PROVIDER / AI_FALLBACK_MODEL "" Used when the primary provider is unavailable
AI_TEMPERATURE / AI_MAX_TOKENS / AI_TIMEOUT 0.1 / 4096 / 120 Sampling temperature, response token limit and per-request timeout in seconds
AI_MAX_QUERIES_PER_SCAN 50 Hard cap on AI queries per scan, enforced across parallel workers. A query that returns nothing gives its slot back
AI_MAX_INPUT_TOKENS_PER_QUERY 50000 Input size limit per query
AI_SANITIZE_ENABLED 0 Two-way redaction for cloud providers: IP addresses, hostnames, credentials, tokens and file paths are replaced with placeholders before a prompt leaves the host and restored in the response
AI_SCAN_ANALYSIS 0 Sends each module’s output to the model when the module finishes, with tool-specific guidance. Findings are written as severity-ranked CSV to vulnerabilities/ai-findings-*.csv
AI_SCAN_DECISIONING 0 Partway through a scan, the model reviews the findings so far and turns tool categories on or off for the rest of the run (Metasploit exploitation, nmap scripts, nuclei, brute force, web vulnerability scanning). Only those five known settings are applied; every change is logged as [AI DECISIONING]
CLAUDE_CODE_ENABLED 0 At the end of a scan, Claude Code reviews the sorted vulnerability list in a read-only session

AI deep analysis, proof-level grading and the written assessment

Once a scan’s findings are aggregated, sc0pe runs the deep analysis stages in this order. Each stage needs AI_ENABLED="1" and runs only when the scan produced findings.

  1. White-box source review (optional): when AI_VULNERABILITY_ANALYSIS is on and SN1PER_AI_SOURCE_REPO points at a directory containing the application’s source code, a source review runs first so later stages can tie findings to code.
  2. Five specialist analyses (AI_VULNERABILITY_ANALYSIS): separate analyses for injection, XSS, authentication, SSRF and authorization review the evidence the scan collected (nmap, nuclei, sqlmap and Dalfox output, the aggregated findings, AI triage results, crawled URLs, headers, technology fingerprints and browser-verified XSS results). Each writes a report and a queue of candidate findings with the endpoint, parameter, sink, observed defenses, confidence and a witness payload. With MULTI_AGENT="1" the five run in parallel.
  3. Proof-level grading (SN1PER_AI_EXPLOIT_VERIFICATION, needs AI_VULNERABILITY_ANALYSIS): each queued candidate is graded on four levels. Grading sends no traffic to the target: the model only judges evidence the scan already collected, and is instructed to assign Level 3 or higher only when that tool output proves it.
  4. Security assessment (AI_REPORT_ENHANCEMENT): a written report built from every stage above, including the graded findings.
Proof level Meaning
Level 1 Weakly indicated (theoretical)
Level 2 Partial bypass achieved
Level 3 Confirmed by concrete evidence in the collected tool output
Level 4 Full impact demonstrated in the collected tool output

A grade is the model’s reading of existing evidence, not a new test. Treat Level 1 and 2 candidates as your next manual tests.

Setting Default Description
AI_VULNERABILITY_ANALYSIS 0 Five specialist analyses (and the source review when a repository is set)
SN1PER_AI_SOURCE_REPO "" Path to the application’s source code for the white-box review
SN1PER_AI_EXPLOIT_VERIFICATION 0 Proof-level grading of the specialists’ candidates
AI_REPORT_ENHANCEMENT 0 Written security assessment
AI_PHASE2_PROVIDER / AI_PHASE2_MODEL "" A different provider or model for the deep stages, so triage can stay on a small, fast model

Output, under the workspace’s loot directory:

  • sn1per-ai/deliverables/: each specialist’s report and candidate queue, the source review and the grading results.
  • reports/sn1per-ai-assessment-<target>-*.md and .html: the written assessment.
  • reports/sniper-ai-vuln-analysis-<target>-*.txt and reports/sniper-ai-report-<target>-*.txt: single-file copies at the paths earlier versions used, so existing workflows keep working.

Every stage counts against AI_MAX_QUERIES_PER_SCAN.

AI-selected Metasploit modules and post-exploitation (disabled by default)

The engine is an MCP client for MetasploitMCP, which keeps a persistent connection to Metasploit’s RPC service.

  • MSF_SMART_EXPLOIT (needs AI_ENABLED): for each open port, the model gets the nmap fingerprint and the matching Metasploit modules and picks the 3 to 5 auxiliary or exploit modules most likely to succeed. Sn1per runs them against the target through MetasploitMCP, or through msfconsole when no MCP server is configured, and saves each module’s output to the workspace.
  • MSF_POST_EXPLOIT: when a scan opens a Metasploit session, Sn1per runs a first round of situational-awareness commands through it (user, host name, network interfaces, operating system) via MetasploitMCP and records the results as evidence.

These run real exploit modules against the target without asking first. Both ship disabled. Enable them only for systems you are explicitly authorized, in writing, to exploit.

Setting Default Description
MSF_SMART_EXPLOIT / MSF_POST_EXPLOIT 0 AI module selection / automated post-exploitation
METASPLOIT_MCP 0 Use a MetasploitMCP server at METASPLOIT_MCP_HOST:METASPLOIT_MCP_PORT (default 127.0.0.1:8085)
MCP_AUTO_START 0 Start msfrpcd and MetasploitMCP for the run and stop them afterwards. It only stops what it started, and declines to attach to an msfrpcd that is already running
METASPLOIT_MCP_DOCKER 0 Run MetasploitMCP in Docker, published on 127.0.0.1 only
MSFRPCD_HOST / MSFRPCD_PORT / MSFRPCD_PASSWORD 127.0.0.1 / 55553 / "" msfrpcd for auto-start. With no password set, a random one is generated per run
MCP_TIMEOUT 60 Timeout in seconds for MCP calls

Kali tools fallback

A scan used to skip any tool that was not installed on the host and could not be repaired. With KALI_MCP="1" and KALI_MCP_DOCKER="1", v11.1 runs that tool in a Kali Linux container instead, through Kali’s own mcp-kali-server. The workspace is mounted at the same path inside the container, so the tool’s output lands in loot like any other. Sn1per never pulls or builds the image at scan time; build it once by hand:

# Build the Kali tools image (extra apt packages are optional)
sudo /usr/share/sniper/bin/sniper-kali-mcp-build.sh
sudo /usr/share/sniper/bin/sniper-kali-mcp-build.sh nuclei ffuf
Setting Default Description
KALI_MCP 0 Enable the Kali tools fallback
KALI_MCP_DOCKER 0 Run it from the local Docker image. The fallback only runs when this is also on
KALI_MCP_HOST / KALI_MCP_PORT 127.0.0.1 / 8001 Where the container’s API listens (published on 127.0.0.1 only)
MCP_AUTO_START 0 With the two settings above, starts the container for the scan and stops it afterwards

Playwright: XSS verification, authenticated crawling and form injection

v11.1 adds a headless Chromium layer driven by Playwright through a local bridge server, started automatically when one of these settings is on.

  • Browser-verified XSS (PLAYWRIGHT_XSS_VERIFY): loads each XSS proof-of-concept URL from Dalfox and nuclei in the browser and marks it verified only when the payload executes (a JavaScript dialog, a console marker or injected DOM). Verified hits are recorded as High findings with evidence and a screenshot in web/playwright-xss-verified-*.txt and .json; findings that do not execute are reported as not verified.
  • Authenticated crawling (PLAYWRIGHT_AUTH_CRAWL): signs in with a real browser using the login URL, field selectors and test account below, then crawls behind the login. Discovered URLs (web/urls-authenticated-*.txt) are merged into the URL list the web checks run against. The saved session (web/playwright-storage-state-<target>.json) is readable by the scan user only.
  • Form injection (PLAYWRIGHT_FORM_INJECT): fills discovered POST forms with a uniquely marked payload, submits them in the browser and reports a form only when that marker executes, so a page’s own scripts are never reported as XSS. Forms whose action, name or submit text looks destructive (delete, payment, password, send and similar) are never submitted, GET forms are left to the DAST checks, and forms behind a login reuse the authenticated crawl session.

Form injection submits real forms on the target. It ships disabled. Enable it only on applications you are authorized to test.

Setting Default Description
PLAYWRIGHT_XSS_VERIFY 0 Browser verification of XSS findings
PLAYWRIGHT_AUTH_CRAWL 0 Authenticated crawling
PLAYWRIGHT_FORM_INJECT 0 POST form injection (authorized targets only)
PLAYWRIGHT_HEADLESS 1 Run the browser headless
PLAYWRIGHT_MAX_PAGES 50 Page cap per run
PLAYWRIGHT_AUTH_URL "" Login page URL
PLAYWRIGHT_AUTH_USER_FIELD / PLAYWRIGHT_AUTH_PASS_FIELD / PLAYWRIGHT_AUTH_SUBMIT #username / #password / #login-btn CSS selectors for the login form
PLAYWRIGHT_AUTH_USERNAME / PLAYWRIGHT_AUTH_PASSWORD "" Test account for the crawl. Use a dedicated test account
PLAYWRIGHT_MCP_PORT / PLAYWRIGHT_MCP_TIMEOUT 9323 / 30 Local bridge port and timeout
PLAYWRIGHT_XSS_VERIFY="1"
PLAYWRIGHT_AUTH_CRAWL="1"
PLAYWRIGHT_AUTH_URL="https://app.example.com/login"
PLAYWRIGHT_AUTH_USER_FIELD="#username"
PLAYWRIGHT_AUTH_PASS_FIELD="#password"
PLAYWRIGHT_AUTH_SUBMIT="#login-btn"
PLAYWRIGHT_AUTH_USERNAME="test-user"
PLAYWRIGHT_AUTH_PASSWORD="test-password"
# Submits forms on the target: authorized applications only
# PLAYWRIGHT_FORM_INJECT="1"

Sn1per MCP Server

The engine’s MCP client calls other servers. The Sn1per MCP Server works the other way round: it lets the AI assistant you already use drive your self-hosted Sn1per, including the 11.x engine used by SE, Professional and Enterprise. It is free and open source (Apache-2.0), runs locally over stdio, refuses scans of targets outside the scope you configure, records every scan, cancel, delete and export request in a local audit log, and returns findings, ports, subdomains and technologies as structured data with secrets redacted by default.

# Install the Sn1per MCP Server (beta) on the scanning host
sudo apt install pipx
pipx ensurepath
pipx install sn1per-mcp

Scope, client setup and the security model are in the Sn1per MCP Server guide; the launch post lists every tool.

Change detection, attack trees, KEV and EPSS

  • Scan-over-scan change detection: every scan stores a snapshot and a delta under scans/history/ in the workspace: new and removed hosts, ports, URLs, subdomain takeovers and vulnerabilities, plus the movement of the workspace risk score. Pair it with scheduled scans (for example sniper -w example-corp -s weekly) for continuous monitoring.
  • Attack tree builder (modes/attack_tree.sh): chains a workspace’s findings into the paths an attacker would take and writes scans/attack-tree.json.
  • CISA KEV and EPSS enrichment (bin/sniper-enrichment.sh): adds the CISA Known Exploited Vulnerabilities flag and the EPSS exploit-prediction score to vulnerability findings, so an actively exploited medium stands out from an unexploited critical.
Setting Default Description
SCAN_HISTORY_RETENTION 10 Number of per-scan snapshots kept under scans/history/
ENRICHMENT_ENABLED 1 (0 in conf/default) KEV and EPSS enrichment
ENRICHMENT_KEV_UPDATE 1 Refresh the KEV catalog
ENRICHMENT_EPSS_TIMEOUT 30 EPSS lookup timeout in seconds

Recon and web discovery

Subdomain enumeration is now a two-layer pipeline: permutations are seeded only from names that actually resolved, and capped by DOMAINS_PERMUTATION_MAX. On our regression target that meant 74x fewer candidates to resolve for the same results.

sudo sniper -t example.com -m recon_active -w example-corp
Setting Default Description
DOMAINS_PERMUTATION_MAX 500000 Cap on permutation candidates
DOMAINS_DEFAULT wordlists/domains-common.txt New default brute-force list (with domains-permutations.txt and resolvers-trusted.txt; resolvers.txt grew from 8 to 55 vetted resolvers)
PURE_DNS 1 Default resolver. SUBBRUTE_DNS and MASS_DNS now run when enabled
CRTNAME_SUBDOMAINS / AGNIOPS_SUBDOMAINS 1 New keyless subdomain sources: crt.name and agniops
ALTERX / FINDOMAIN / ASSETFINDER 1 New enumeration settings
NS_TAKEOVER_SCAN 1 NS delegation takeover detection: names delegated to a nameserver that does not host a zone for them, a larger win for an attacker than a CNAME takeover
ZAP_SCAN 0 Headless OWASP ZAP scan, results imported into sc0pe findings. Sn1per starts the ZAP daemon itself; tune with ZAP_HOST, ZAP_PORT (8090), ZAP_API_KEY, ZAP_TIMEOUT (3600), ZAP_THREADS (10) and ZAP_SPIDER_MAX_DEPTH (5)
MULTI_AGENT / MAX_PARALLEL_AGENTS 0 / 3 Parallel scan workers that run scan modules (and the five AI specialists) concurrently

katana now crawls headless with robots.txt and sitemap.xml discovery at depth 3, and curated TCP nuclei templates run against the bare target.

Ticketing and Nessus

Ticketing: GitHub Issues, Jira and ServiceNow

At the end of a scan, after findings and AD correlation are finalized, Sn1per opens one ticket per new finding at or above TICKETING_MIN_SEVERITY in every provider you enable. It reads the sc0pe findings (vulnerabilities/sc0pe-*.txt in the workspace).

  • Title: [Sn1per] SEVERITY - Finding (host). Body: workspace, host, severity, finding, evidence and the source file.
  • No duplicates: each finding is keyed on severity, title and host and recorded in scans/ticketing-filed.txt in the workspace, so recurring and scheduled scans never file the same finding twice.
  • Ships disabled: nothing is sent unless TICKETING_ENABLED="1" and at least one provider is enabled with its credentials. A provider that is enabled but missing a required setting is skipped.

Test your credentials before a real scan. A finding is recorded in scans/ticketing-filed.txt once Sn1per has attempted to file it, whether or not the provider accepted it, and the attempt is not reported in the scan output. If a token was wrong, or a provider was skipped for a missing setting, fix it and then clear that file (or remove the affected lines) so the next scan files those findings again.

Provider Request Authentication
GitHub Issues POST https://api.github.com/repos/<GITHUB_ISSUES_REPO>/issues Personal access token (GITHUB_ISSUES_TOKEN) with Issues write access
Jira POST <JIRA_URL>/rest/api/2/issue in JIRA_PROJECT_KEY, issue type JIRA_ISSUE_TYPE Basic auth JIRA_USER:JIRA_API_TOKEN (Jira Cloud: account email and API token)
ServiceNow POST https://<SERVICENOW_INSTANCE>.service-now.com/api/now/table/<SERVICENOW_TABLE>, setting short_description and description Basic auth SERVICENOW_USER:SERVICENOW_PASSWORD
Setting Default Description
TICKETING_ENABLED 0 Master switch
TICKETING_MIN_SEVERITY HIGH CRITICAL, HIGH, MEDIUM, LOW or INFO
GITHUB_ISSUES_ENABLED, GITHUB_ISSUES_REPO, GITHUB_ISSUES_TOKEN 0 / "" Repository as owner/repo
JIRA_ENABLED, JIRA_URL, JIRA_USER, JIRA_API_TOKEN, JIRA_PROJECT_KEY, JIRA_ISSUE_TYPE 0 / "", issue type Task URL like https://org.atlassian.net. URL, user, token and project key are all required
SERVICENOW_ENABLED, SERVICENOW_INSTANCE, SERVICENOW_USER, SERVICENOW_PASSWORD, SERVICENOW_TABLE 0 / "", table incident Instance is the subdomain of <instance>.service-now.com

Only two profiles carry these settings. The ticketing settings ship only in conf/default (normal mode) and conf/ad (AD mode). They are not in sniper.conf or the other profiles (flyover, fullportscan, full_scan, vulnscan, recon_passive, recon_active, all_disabled, all_web_port_scan). Because every scan loads a profile, ticketing works only for scans that use conf/default or conf/ad unless you add the settings to the profile you scan with. In Sn1per Enterprise, the web UI Config Editor has toggles for them.

For an overview, see ticketing in the v11.1 release announcement.

Nessus launcher

The Nessus launcher (NESSUS="1", default 0) starts a Nessus scan of the target from normal mode using NESSUS_HOST (default 127.0.0.1:8834), NESSUS_USERNAME, NESSUS_PASSWORD and NESSUS_POLICY_ID.

Detection templates

  • 56 new templates, including 2026 CVE detections for WordPress, Microsoft SharePoint, vBulletin, GitHub Enterprise Server, NGINX, Apache HTTP Server (mod_http2 and mod_md), Drupal, JFrog Artifactory, Citrix NetScaler, PHP, GitLab and Progress WS_FTP, an HTTP/2 cleartext (h2c) exposure check, the GraphQL debug surface, missing CAA and DNSSEC records, verified unrestricted Google Maps API keys and 16 AD/SMB findings.
  • templates/nuclei-authenticated/: a new directory for authenticated checks you run by hand.
  • Duplicate, dead and false-positive-prone templates were retired, and nuclei template ID collisions with upstream are detected and excluded. Findings now carry the full evidence line.

Security hardening and self-maintenance

  • API keys never reach loot: key values are masked before they reach scan output, reports and logs. Clean older loot with sniper-mask-secrets (see After upgrading).
  • -dh deletes only the requested host, and refuses to run without a valid workspace and target. -d refuses an empty or invalid workspace name.
  • -dt stops only that workspace’s scans and their orphaned tools, not every matching process on the host.
  • Target-supplied names can no longer become file names, command options or paths.
  • Tool health check and self-repair: each scan starts with a toolchain check (bin/tool_health_check.sh), and when a scan step needs a tool that is missing, lib/sniper-selfheal.sh installs or repairs it before running it (or hands it to the Kali tools fallback when that is enabled), so a broken dependency no longer means a silently incomplete scan.
  • -fp runs a full port scan again, and sniper --help matches the v11 engine.

Removed and renamed settings

If an older profile or document refers to one of these settings, it has no effect in v11.1.

Removed or changed Use instead
QUICK_PORTS DEFAULT_PORTS
CENSYS_SUBDOMAINS (Censys subdomain lookups) Removed. Use the other subdomain sources, including the keyless crt.name and agniops sources
SubOver (SUBOVER now defaults to 0; the installer no longer builds it) NUCLEI_TAKEOVER_SCAN, SUBJACK and NS_TAKEOVER_SCAN
Unused Slack notification toggles Removed
AI_AGENT_MODE, AI_PHASE2_URL Removed (no code read them). Use AI_PHASE2_PROVIDER / AI_PHASE2_MODEL for the deep stages
SN1PER_AI_SOURCE_ANALYSIS Set SN1PER_AI_SOURCE_REPO; the repository path alone decides
SN1PER_AI_VULN_ANALYSIS AI_VULNERABILITY_ANALYSIS
SN1PER_AI_REPORT_SYNTHESIS AI_REPORT_ENHANCEMENT
SN1PER_AI_PARALLEL_ANALYSIS MULTI_AGENT
SN1PER_AI_LARGE_MODEL AI_PHASE2_MODEL
SN1PER_AI_VULN_MAX_TOKENS, SN1PER_AI_EXPLOIT_MAX_TOKENS, SN1PER_AI_REPORT_MAX_TOKENS Removed. AI_MAX_TOKENS and AI_MAX_INPUT_TOKENS_PER_QUERY apply
Duplicate CLAUDE_CODE_MAX_TURNS, OPENROUTER_API_KEY and ZAI_API_KEY entries Removed from sniper.conf and the profiles; previously the second copy silently won
bin/sniper-ai-scan-analysis.sh Removed on upgrade; AI_SCAN_ANALYSIS does the per-tool analysis

The installer also stopped installing tools the engine never ran or that duplicated an apt package (among them Findsploit and its ExploitDB clone, vulscan and censys-subdomain-finder) and removes them from upgraded installs. The complete list is in CHANGELOG.md.

See also

Something missing, unclear, or out-of-date?

Email the team