{"id":68346,"date":"2026-11-15T16:21:15","date_gmt":"2026-11-15T23:21:15","guid":{"rendered":"https:\/\/sn1persecurity.com\/wordpress\/documentation\/scan-engine\/"},"modified":"2026-11-15T16:21:15","modified_gmt":"2026-11-15T23:21:15","slug":"scan-engine","status":"publish","type":"page","link":"https:\/\/sn1persecurity.com\/wordpress\/documentation\/scan-engine\/","title":{"rendered":"Scan Engine v11.1"},"content":{"rendered":"<div class=\"sn-breadcrumb\"><a href=\"\/wordpress\/documentation\/\">Documentation<\/a><span class=\"sep\">\/<\/span><span>Scan Engine v11.1<\/span><\/div>\n<p><strong>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.<\/strong><\/p>\n<p>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 <a href=\"\/wordpress\/sn1per-se-v11-1-released\/\">Sn1per SE v11.1 release announcement<\/a>.<\/p>\n<blockquote>\n<p><strong>For authorized security testing only.<\/strong> 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.<\/p>\n<\/blockquote>\n<h2 id=\"contents\">On this page<\/h2>\n<ul>\n<li><a href=\"#upgrade\">Upgrading to v11.1<\/a><\/li>\n<li><a href=\"#configuration-profiles\">Where settings live<\/a><\/li>\n<li><a href=\"#active-directory\">Active Directory mode<\/a><\/li>\n<li><a href=\"#ai\">AI analysis and agentic scanning<\/a><\/li>\n<li><a href=\"#kali-tools-fallback\">Kali tools fallback<\/a><\/li>\n<li><a href=\"#playwright\">Playwright: XSS verification, authenticated crawling and form injection<\/a><\/li>\n<li><a href=\"#mcp-server\">Sn1per MCP Server<\/a><\/li>\n<li><a href=\"#change-detection\">Change detection, attack trees, KEV and EPSS<\/a><\/li>\n<li><a href=\"#recon\">Recon and web discovery<\/a><\/li>\n<li><a href=\"#integrations\">Ticketing and Nessus<\/a><\/li>\n<li><a href=\"#templates\">Detection templates<\/a><\/li>\n<li><a href=\"#hardening\">Security hardening and self-maintenance<\/a><\/li>\n<li><a href=\"#removed-settings\">Removed and renamed settings<\/a><\/li>\n<\/ul>\n<h2 id=\"upgrade\">Upgrading to v11.1<\/h2>\n<p>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:<\/p>\n<ul>\n<li><strong>CLI:<\/strong> run <code>sniper -u<\/code> (or <code>sniper --update<\/code>) as root.<\/li>\n<li><strong>Web UI:<\/strong> open the <strong>Updates<\/strong> menu option in the Sn1per Professional or Sn1per Enterprise web UI to check for and install the update.<\/li>\n<\/ul>\n<pre><code class=\"language-bash\">sudo sniper -u<\/code><\/pre>\n<p>The update keeps your existing <code>conf\/ad<\/code> profile and API key file (<code>conf\/.GLOBAL_API_KEYS<\/code>), removes retired templates and plugins, and writes a structured log to <code>\/usr\/share\/sniper\/install.log<\/code>. The full list of changes ships with the update as <code>\/usr\/share\/sniper\/CHANGELOG.md<\/code>.<\/p>\n<h3 id=\"after-upgrade\">After upgrading: clean API keys out of old loot<\/h3>\n<p>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:<\/p>\n<pre><code class=\"language-bash\"># List loot files that contain an API key value (path and key name only)\nsudo \/usr\/share\/sniper\/bin\/sniper-mask-secrets --scan\n\n# Redact them in place, keeping owner, mode and modification time\nsudo \/usr\/share\/sniper\/bin\/sniper-mask-secrets --redact<\/code><\/pre>\n<p>Both options default to the <code>loot\/<\/code> directory and accept one or more paths. <code>--scan<\/code> exits 0 when it finds nothing and 1 when it finds key values. Masked values appear as <code>[REDACTED:&lt;NAME&gt;]<\/code>.<\/p>\n<h2 id=\"configuration-profiles\">Where settings live<\/h2>\n<p>Each scan loads one configuration profile from <code>\/usr\/share\/sniper\/conf\/<\/code>. Unless you pass a profile with <code>-c \/path\/to\/profile<\/code>, Sn1per picks it from the scan mode:<\/p>\n<table>\n<thead>\n<tr>\n<th>Scan mode (<code>-m<\/code>)<\/th>\n<th>Profile loaded<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>normal<\/code> and modes without their own profile<\/td>\n<td><code>conf\/default<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>flyover<\/code>, <code>stealth<\/code><\/td>\n<td><code>conf\/flyover<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>fullportscan<\/code><\/td>\n<td><code>conf\/fullportscan<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>vulnscan<\/code><\/td>\n<td><code>conf\/vulnscan<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>full_scan<\/code><\/td>\n<td><code>conf\/full_scan<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>recon_passive<\/code><\/td>\n<td><code>conf\/recon_passive<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>recon_active<\/code><\/td>\n<td><code>conf\/recon_active<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>ad<\/code> (new in v11.1)<\/td>\n<td><code>conf\/ad<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><code>\/usr\/share\/sniper\/sniper.conf<\/code> 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 <strong>Config Editor<\/strong>. API keys for AI providers and recon sources go in <code>conf\/.GLOBAL_API_KEYS<\/code>, which every scan loads. v11.1 ships the redacted templates <code>conf\/.GLOBAL_API_KEYS.example<\/code> and <code>conf\/.ad.example<\/code> instead of live credential files.<\/p>\n<blockquote>\n<p><strong>Check the profile you scan with.<\/strong> A few profiles ship with values that differ from <code>sniper.conf<\/code>. For example, CISA KEV and EPSS enrichment (<code>ENRICHMENT_ENABLED<\/code>) is on in <code>sniper.conf<\/code> and most profiles but off in <code>conf\/default<\/code>, the profile normal mode loads.<\/p>\n<\/blockquote>\n<h2 id=\"active-directory\">Active Directory mode<\/h2>\n<p>AD mode (<code>-m ad<\/code>, profile <code>conf\/ad<\/code>) 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.<\/p>\n<pre><code class=\"language-bash\"># Unauthenticated assessment of an internal range\nsudo sniper -t 10.0.0.0\/24 -m ad -w corp-ad\n\n# Credentialed assessment: set the AD_* credentials in conf\/ad first\nsudo nano \/usr\/share\/sniper\/conf\/ad\nsudo sniper -t dc01.corp.local -m ad -w corp-ad<\/code><\/pre>\n<table>\n<thead>\n<tr>\n<th>Setting (<code>conf\/ad<\/code>)<\/th>\n<th>Default<\/th>\n<th>Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>AD_DOMAIN<\/code><\/td>\n<td><code>\"\"<\/code><\/td>\n<td>AD DNS domain. When empty, Sn1per derives it from the scan&#8217;s own enumeration<\/td>\n<\/tr>\n<tr>\n<td><code>AD_USER<\/code> \/ <code>AD_PASS<\/code><\/td>\n<td><code>\"\"<\/code><\/td>\n<td>Domain account for the credentialed checks (Kerberoasting, delegation, account, privileged group and directory audits). Each credentialed check is skipped when <code>AD_USER<\/code> is empty<\/td>\n<\/tr>\n<tr>\n<td><code>AD_HASH<\/code><\/td>\n<td><code>\"\"<\/code><\/td>\n<td>NT hash, used only by the opt-in <code>AD_OVERPASS_HASH<\/code> setting<\/td>\n<\/tr>\n<tr>\n<td><code>AD_DC_IP<\/code><\/td>\n<td><code>\"\"<\/code><\/td>\n<td>Domain controller address. Defaults to the scan target<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>What AD mode covers:<\/p>\n<ul>\n<li><strong>Kerberos and delegation:<\/strong> Kerberoastable and AS-REP roastable accounts, unconstrained and constrained delegation, RC4-only and DES encryption types, krbtgt password age.<\/li>\n<li><strong>Privilege and ACLs:<\/strong> privileged group audit, dangerous ACLs, DCSync-capable principals, shadow credentials, domain trusts.<\/li>\n<li><strong>Hygiene:<\/strong> 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.<\/li>\n<li><strong>Protocol posture:<\/strong> LDAP signing and channel binding, SMB signing, and AD\/SMB CVE detection (<code>AD_CVE_SCAN<\/code>).<\/li>\n<li><strong>Attack paths:<\/strong> BloodHound collection (<code>BLOODHOUND_COLLECT<\/code>) and shortest-path-to-Domain-Admin queries (<code>BLOODHOUND_PATHFIND<\/code>), which use cypher-shell when it is installed and the bundled client <code>bin\/sniper-cypher<\/code> otherwise.<\/li>\n<li><strong>Offline hash cracking<\/strong> (<code>HASH_CRACKING<\/code>, on in <code>conf\/ad<\/code>): recovered AS-REP, Kerberoast and Timeroast hashes are cracked locally with hashcat, so no packets reach the target.<\/li>\n<\/ul>\n<p>Every finding rolls up into a <strong>0-100 AD posture score<\/strong> (higher is stronger) and is mapped to <strong>MITRE ATT&amp;CK, NIST 800-53, CIS Controls v8 and DISA STIG<\/strong> identifiers. Because each run is scored, you also get a scan-over-scan trend. The default port list (<code>DEFAULT_PORTS<\/code>) 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.<\/p>\n<h3 id=\"ad-live-attacks\">Live attack settings (disabled by default)<\/h3>\n<p>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.<\/p>\n<table>\n<thead>\n<tr>\n<th>Setting (<code>conf\/ad<\/code>)<\/th>\n<th>Default<\/th>\n<th>What it does<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>AD_PASSWORD_SPRAY<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>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<\/td>\n<\/tr>\n<tr>\n<td><code>AD_DEFAULT_CREDS<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>Guest\/null and vendor-default administrator pairs, with the same lockout guard<\/td>\n<\/tr>\n<tr>\n<td><code>AD_OVERPASS_HASH<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>Requests a Kerberos TGT from a recovered or supplied NT hash<\/td>\n<\/tr>\n<tr>\n<td><code>AD_CVE_EXPLOIT<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>Exploits the AD\/SMB CVEs that <code>AD_CVE_SCAN<\/code> detected. Refuses to run unless <code>AD_EXPLOIT=\"1\"<\/code> is also set<\/td>\n<\/tr>\n<tr>\n<td><code>AD_EXPLOIT<\/code> + <code>AD_ATTACKER_IP<\/code><\/td>\n<td><code>0<\/code> \/ <code>\"\"<\/code><\/td>\n<td>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<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"ai\">AI analysis and agentic scanning<\/h2>\n<p>v11.1 puts AI inside the scan: it triages each tool&#8217;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 <strong>off by default<\/strong> (<code>AI_ENABLED=\"0\"<\/code>) and each has its own switch.<\/p>\n<h3 id=\"ai-providers\">Providers<\/h3>\n<p>Set <code>AI_PROVIDER<\/code> to one of six providers. Cloud provider keys go in <code>conf\/.GLOBAL_API_KEYS<\/code>.<\/p>\n<table>\n<thead>\n<tr>\n<th><code>AI_PROVIDER<\/code><\/th>\n<th>Provider<\/th>\n<th>Credentials and settings<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>ollama<\/code> (default)<\/td>\n<td>Ollama<\/td>\n<td><code>OLLAMA_URL<\/code> (default <code>http:\/\/127.0.0.1:11434\/api\/generate<\/code>), <code>OLLAMA_MODEL<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>openai<\/code><\/td>\n<td>OpenAI<\/td>\n<td><code>OPENAI_API_KEY<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>anthropic<\/code><\/td>\n<td>Anthropic Claude<\/td>\n<td><code>ANTHROPIC_API_KEY<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>openrouter<\/code><\/td>\n<td>OpenRouter<\/td>\n<td><code>OPENROUTER_API_KEY<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>zai<\/code><\/td>\n<td>Z.ai<\/td>\n<td><code>ZAI_API_KEY<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>claudecode<\/code><\/td>\n<td>Claude Code CLI<\/td>\n<td>The <code>claude<\/code> CLI installed on the scanning host; <code>CLAUDE_CODE_MAX_TURNS<\/code> (default <code>10<\/code>)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<blockquote>\n<p><strong>Local by choice, not by default.<\/strong> The shipped <code>AI_MODEL<\/code> and <code>OLLAMA_MODEL<\/code> are <code>deepseek-v4.1-flash:cloud<\/code>, an Ollama <em>cloud<\/em> 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.<\/p>\n<\/blockquote>\n<pre><code class=\"language-bash\"># Local-only AI: every prompt stays on your own hardware\n# 1. On the Ollama host:  ollama pull your-local-model\n# 2. In the profile your scans load (for example \/usr\/share\/sniper\/conf\/default):\nAI_ENABLED=\"1\"\nAI_PROVIDER=\"ollama\"\nOLLAMA_URL=\"http:\/\/127.0.0.1:11434\/api\/generate\"\nOLLAMA_MODEL=\"your-local-model\"\nAI_MODEL=\"your-local-model\"\nAI_SCAN_ANALYSIS=\"1\"\nAI_SCAN_DECISIONING=\"1\"\nAI_VULNERABILITY_ANALYSIS=\"1\"\nSN1PER_AI_EXPLOIT_VERIFICATION=\"1\"\nAI_REPORT_ENHANCEMENT=\"1\"\n# Optional: a larger local model for the deep analysis stages\n# AI_PHASE2_MODEL=\"your-larger-local-model\"<\/code><\/pre>\n<h3 id=\"ai-settings\">Core settings<\/h3>\n<table>\n<thead>\n<tr>\n<th>Setting<\/th>\n<th>Default<\/th>\n<th>Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>AI_ENABLED<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>Master switch. No AI feature runs without it<\/td>\n<\/tr>\n<tr>\n<td><code>AI_PROVIDER<\/code> \/ <code>AI_MODEL<\/code><\/td>\n<td><code>ollama<\/code> \/ <code>deepseek-v4.1-flash:cloud<\/code><\/td>\n<td>Primary provider and model<\/td>\n<\/tr>\n<tr>\n<td><code>AI_FALLBACK_PROVIDER<\/code> \/ <code>AI_FALLBACK_MODEL<\/code><\/td>\n<td><code>\"\"<\/code><\/td>\n<td>Used when the primary provider is unavailable<\/td>\n<\/tr>\n<tr>\n<td><code>AI_TEMPERATURE<\/code> \/ <code>AI_MAX_TOKENS<\/code> \/ <code>AI_TIMEOUT<\/code><\/td>\n<td><code>0.1<\/code> \/ <code>4096<\/code> \/ <code>120<\/code><\/td>\n<td>Sampling temperature, response token limit and per-request timeout in seconds<\/td>\n<\/tr>\n<tr>\n<td><code>AI_MAX_QUERIES_PER_SCAN<\/code><\/td>\n<td><code>50<\/code><\/td>\n<td>Hard cap on AI queries per scan, enforced across parallel workers. A query that returns nothing gives its slot back<\/td>\n<\/tr>\n<tr>\n<td><code>AI_MAX_INPUT_TOKENS_PER_QUERY<\/code><\/td>\n<td><code>50000<\/code><\/td>\n<td>Input size limit per query<\/td>\n<\/tr>\n<tr>\n<td><code>AI_SANITIZE_ENABLED<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>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<\/td>\n<\/tr>\n<tr>\n<td><code>AI_SCAN_ANALYSIS<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>Sends each module&#8217;s output to the model when the module finishes, with tool-specific guidance. Findings are written as severity-ranked CSV to <code>vulnerabilities\/ai-findings-*.csv<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>AI_SCAN_DECISIONING<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>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 <code>[AI DECISIONING]<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>CLAUDE_CODE_ENABLED<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>At the end of a scan, Claude Code reviews the sorted vulnerability list in a read-only session<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3 id=\"ai-deep-analysis\">AI deep analysis, proof-level grading and the written assessment<\/h3>\n<p>Once a scan&#8217;s findings are aggregated, sc0pe runs the deep analysis stages in this order. Each stage needs <code>AI_ENABLED=\"1\"<\/code> and runs only when the scan produced findings.<\/p>\n<ol>\n<li><strong>White-box source review<\/strong> (optional): when <code>AI_VULNERABILITY_ANALYSIS<\/code> is on and <code>SN1PER_AI_SOURCE_REPO<\/code> points at a directory containing the application&#8217;s source code, a source review runs first so later stages can tie findings to code.<\/li>\n<li><strong>Five specialist analyses<\/strong> (<code>AI_VULNERABILITY_ANALYSIS<\/code>): 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 <code>MULTI_AGENT=\"1\"<\/code> the five run in parallel.<\/li>\n<li><strong>Proof-level grading<\/strong> (<code>SN1PER_AI_EXPLOIT_VERIFICATION<\/code>, needs <code>AI_VULNERABILITY_ANALYSIS<\/code>): each queued candidate is graded on four levels. <strong>Grading sends no traffic to the target<\/strong>: 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.<\/li>\n<li><strong>Security assessment<\/strong> (<code>AI_REPORT_ENHANCEMENT<\/code>): a written report built from every stage above, including the graded findings.<\/li>\n<\/ol>\n<table>\n<thead>\n<tr>\n<th>Proof level<\/th>\n<th>Meaning<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Level 1<\/td>\n<td>Weakly indicated (theoretical)<\/td>\n<\/tr>\n<tr>\n<td>Level 2<\/td>\n<td>Partial bypass achieved<\/td>\n<\/tr>\n<tr>\n<td>Level 3<\/td>\n<td>Confirmed by concrete evidence in the collected tool output<\/td>\n<\/tr>\n<tr>\n<td>Level 4<\/td>\n<td>Full impact demonstrated in the collected tool output<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>A grade is the model&#8217;s reading of existing evidence, not a new test. Treat Level 1 and 2 candidates as your next manual tests.<\/p>\n<table>\n<thead>\n<tr>\n<th>Setting<\/th>\n<th>Default<\/th>\n<th>Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>AI_VULNERABILITY_ANALYSIS<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>Five specialist analyses (and the source review when a repository is set)<\/td>\n<\/tr>\n<tr>\n<td><code>SN1PER_AI_SOURCE_REPO<\/code><\/td>\n<td><code>\"\"<\/code><\/td>\n<td>Path to the application&#8217;s source code for the white-box review<\/td>\n<\/tr>\n<tr>\n<td><code>SN1PER_AI_EXPLOIT_VERIFICATION<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>Proof-level grading of the specialists&#8217; candidates<\/td>\n<\/tr>\n<tr>\n<td><code>AI_REPORT_ENHANCEMENT<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>Written security assessment<\/td>\n<\/tr>\n<tr>\n<td><code>AI_PHASE2_PROVIDER<\/code> \/ <code>AI_PHASE2_MODEL<\/code><\/td>\n<td><code>\"\"<\/code><\/td>\n<td>A different provider or model for the deep stages, so triage can stay on a small, fast model<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Output, under the workspace&#8217;s loot directory:<\/p>\n<ul>\n<li><code>sn1per-ai\/deliverables\/<\/code>: each specialist&#8217;s report and candidate queue, the source review and the grading results.<\/li>\n<li><code>reports\/sn1per-ai-assessment-&lt;target&gt;-*.md<\/code> and <code>.html<\/code>: the written assessment.<\/li>\n<li><code>reports\/sniper-ai-vuln-analysis-&lt;target&gt;-*.txt<\/code> and <code>reports\/sniper-ai-report-&lt;target&gt;-*.txt<\/code>: single-file copies at the paths earlier versions used, so existing workflows keep working.<\/li>\n<\/ul>\n<p>Every stage counts against <code>AI_MAX_QUERIES_PER_SCAN<\/code>.<\/p>\n<h3 id=\"ai-metasploit\">AI-selected Metasploit modules and post-exploitation (disabled by default)<\/h3>\n<p>The engine is an MCP client for <a href=\"https:\/\/github.com\/GH05TCREW\/MetasploitMCP\" target=\"_blank\" rel=\"noopener nofollow\">MetasploitMCP<\/a>, which keeps a persistent connection to Metasploit&#8217;s RPC service.<\/p>\n<ul>\n<li><strong><code>MSF_SMART_EXPLOIT<\/code><\/strong> (needs <code>AI_ENABLED<\/code>): 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 <code>msfconsole<\/code> when no MCP server is configured, and saves each module&#8217;s output to the workspace.<\/li>\n<li><strong><code>MSF_POST_EXPLOIT<\/code><\/strong>: 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.<\/li>\n<\/ul>\n<blockquote>\n<p><strong>These run real exploit modules against the target without asking first.<\/strong> Both ship disabled. Enable them only for systems you are explicitly authorized, in writing, to exploit.<\/p>\n<\/blockquote>\n<table>\n<thead>\n<tr>\n<th>Setting<\/th>\n<th>Default<\/th>\n<th>Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>MSF_SMART_EXPLOIT<\/code> \/ <code>MSF_POST_EXPLOIT<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>AI module selection \/ automated post-exploitation<\/td>\n<\/tr>\n<tr>\n<td><code>METASPLOIT_MCP<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>Use a MetasploitMCP server at <code>METASPLOIT_MCP_HOST<\/code>:<code>METASPLOIT_MCP_PORT<\/code> (default <code>127.0.0.1:8085<\/code>)<\/td>\n<\/tr>\n<tr>\n<td><code>MCP_AUTO_START<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>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<\/td>\n<\/tr>\n<tr>\n<td><code>METASPLOIT_MCP_DOCKER<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>Run MetasploitMCP in Docker, published on <code>127.0.0.1<\/code> only<\/td>\n<\/tr>\n<tr>\n<td><code>MSFRPCD_HOST<\/code> \/ <code>MSFRPCD_PORT<\/code> \/ <code>MSFRPCD_PASSWORD<\/code><\/td>\n<td><code>127.0.0.1<\/code> \/ <code>55553<\/code> \/ <code>\"\"<\/code><\/td>\n<td>msfrpcd for auto-start. With no password set, a random one is generated per run<\/td>\n<\/tr>\n<tr>\n<td><code>MCP_TIMEOUT<\/code><\/td>\n<td><code>60<\/code><\/td>\n<td>Timeout in seconds for MCP calls<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"kali-tools-fallback\">Kali tools fallback<\/h2>\n<p>A scan used to skip any tool that was not installed on the host and could not be repaired. With <code>KALI_MCP=\"1\"<\/code> and <code>KALI_MCP_DOCKER=\"1\"<\/code>, v11.1 runs that tool in a Kali Linux container instead, through Kali&#8217;s own <code>mcp-kali-server<\/code>. The workspace is mounted at the same path inside the container, so the tool&#8217;s output lands in loot like any other. Sn1per never pulls or builds the image at scan time; build it once by hand:<\/p>\n<pre><code class=\"language-bash\"># Build the Kali tools image (extra apt packages are optional)\nsudo \/usr\/share\/sniper\/bin\/sniper-kali-mcp-build.sh\nsudo \/usr\/share\/sniper\/bin\/sniper-kali-mcp-build.sh nuclei ffuf<\/code><\/pre>\n<table>\n<thead>\n<tr>\n<th>Setting<\/th>\n<th>Default<\/th>\n<th>Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>KALI_MCP<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>Enable the Kali tools fallback<\/td>\n<\/tr>\n<tr>\n<td><code>KALI_MCP_DOCKER<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>Run it from the local Docker image. The fallback only runs when this is also on<\/td>\n<\/tr>\n<tr>\n<td><code>KALI_MCP_HOST<\/code> \/ <code>KALI_MCP_PORT<\/code><\/td>\n<td><code>127.0.0.1<\/code> \/ <code>8001<\/code><\/td>\n<td>Where the container&#8217;s API listens (published on <code>127.0.0.1<\/code> only)<\/td>\n<\/tr>\n<tr>\n<td><code>MCP_AUTO_START<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>With the two settings above, starts the container for the scan and stops it afterwards<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"playwright\">Playwright: XSS verification, authenticated crawling and form injection<\/h2>\n<p>v11.1 adds a headless Chromium layer driven by Playwright through a local bridge server, started automatically when one of these settings is on.<\/p>\n<ul>\n<li><strong>Browser-verified XSS<\/strong> (<code>PLAYWRIGHT_XSS_VERIFY<\/code>): 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 <code>web\/playwright-xss-verified-*.txt<\/code> and <code>.json<\/code>; findings that do not execute are reported as not verified.<\/li>\n<li><strong>Authenticated crawling<\/strong> (<code>PLAYWRIGHT_AUTH_CRAWL<\/code>): signs in with a real browser using the login URL, field selectors and test account below, then crawls behind the login. Discovered URLs (<code>web\/urls-authenticated-*.txt<\/code>) are merged into the URL list the web checks run against. The saved session (<code>web\/playwright-storage-state-&lt;target&gt;.json<\/code>) is readable by the scan user only.<\/li>\n<li><strong>Form injection<\/strong> (<code>PLAYWRIGHT_FORM_INJECT<\/code>): 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&#8217;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.<\/li>\n<\/ul>\n<blockquote>\n<p><strong>Form injection submits real forms on the target.<\/strong> It ships disabled. Enable it only on applications you are authorized to test.<\/p>\n<\/blockquote>\n<table>\n<thead>\n<tr>\n<th>Setting<\/th>\n<th>Default<\/th>\n<th>Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>PLAYWRIGHT_XSS_VERIFY<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>Browser verification of XSS findings<\/td>\n<\/tr>\n<tr>\n<td><code>PLAYWRIGHT_AUTH_CRAWL<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>Authenticated crawling<\/td>\n<\/tr>\n<tr>\n<td><code>PLAYWRIGHT_FORM_INJECT<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>POST form injection (authorized targets only)<\/td>\n<\/tr>\n<tr>\n<td><code>PLAYWRIGHT_HEADLESS<\/code><\/td>\n<td><code>1<\/code><\/td>\n<td>Run the browser headless<\/td>\n<\/tr>\n<tr>\n<td><code>PLAYWRIGHT_MAX_PAGES<\/code><\/td>\n<td><code>50<\/code><\/td>\n<td>Page cap per run<\/td>\n<\/tr>\n<tr>\n<td><code>PLAYWRIGHT_AUTH_URL<\/code><\/td>\n<td><code>\"\"<\/code><\/td>\n<td>Login page URL<\/td>\n<\/tr>\n<tr>\n<td><code>PLAYWRIGHT_AUTH_USER_FIELD<\/code> \/ <code>PLAYWRIGHT_AUTH_PASS_FIELD<\/code> \/ <code>PLAYWRIGHT_AUTH_SUBMIT<\/code><\/td>\n<td><code>#username<\/code> \/ <code>#password<\/code> \/ <code>#login-btn<\/code><\/td>\n<td>CSS selectors for the login form<\/td>\n<\/tr>\n<tr>\n<td><code>PLAYWRIGHT_AUTH_USERNAME<\/code> \/ <code>PLAYWRIGHT_AUTH_PASSWORD<\/code><\/td>\n<td><code>\"\"<\/code><\/td>\n<td>Test account for the crawl. Use a dedicated test account<\/td>\n<\/tr>\n<tr>\n<td><code>PLAYWRIGHT_MCP_PORT<\/code> \/ <code>PLAYWRIGHT_MCP_TIMEOUT<\/code><\/td>\n<td><code>9323<\/code> \/ <code>30<\/code><\/td>\n<td>Local bridge port and timeout<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<pre><code class=\"language-bash\">PLAYWRIGHT_XSS_VERIFY=\"1\"\nPLAYWRIGHT_AUTH_CRAWL=\"1\"\nPLAYWRIGHT_AUTH_URL=\"https:\/\/app.example.com\/login\"\nPLAYWRIGHT_AUTH_USER_FIELD=\"#username\"\nPLAYWRIGHT_AUTH_PASS_FIELD=\"#password\"\nPLAYWRIGHT_AUTH_SUBMIT=\"#login-btn\"\nPLAYWRIGHT_AUTH_USERNAME=\"test-user\"\nPLAYWRIGHT_AUTH_PASSWORD=\"test-password\"\n# Submits forms on the target: authorized applications only\n# PLAYWRIGHT_FORM_INJECT=\"1\"<\/code><\/pre>\n<h2 id=\"mcp-server\">Sn1per MCP Server<\/h2>\n<p>The engine&#8217;s MCP client calls other servers. The <a href=\"\/wordpress\/documentation\/mcp\/\">Sn1per MCP Server<\/a> 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.<\/p>\n<pre><code class=\"language-bash\"># Install the Sn1per MCP Server (beta) on the scanning host\nsudo apt install pipx\npipx ensurepath\npipx install sn1per-mcp<\/code><\/pre>\n<p>Scope, client setup and the security model are in the <a href=\"\/wordpress\/documentation\/mcp\/\">Sn1per MCP Server guide<\/a>; the <a href=\"\/wordpress\/sn1per-mcp-server\/\">launch post<\/a> lists every tool.<\/p>\n<h2 id=\"change-detection\">Change detection, attack trees, KEV and EPSS<\/h2>\n<ul>\n<li><strong>Scan-over-scan change detection:<\/strong> every scan stores a snapshot and a delta under <code>scans\/history\/<\/code> 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 <code>sniper -w example-corp -s weekly<\/code>) for continuous monitoring.<\/li>\n<li><strong>Attack tree builder<\/strong> (<code>modes\/attack_tree.sh<\/code>): chains a workspace&#8217;s findings into the paths an attacker would take and writes <code>scans\/attack-tree.json<\/code>.<\/li>\n<li><strong>CISA KEV and EPSS enrichment<\/strong> (<code>bin\/sniper-enrichment.sh<\/code>): 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.<\/li>\n<\/ul>\n<table>\n<thead>\n<tr>\n<th>Setting<\/th>\n<th>Default<\/th>\n<th>Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>SCAN_HISTORY_RETENTION<\/code><\/td>\n<td><code>10<\/code><\/td>\n<td>Number of per-scan snapshots kept under <code>scans\/history\/<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>ENRICHMENT_ENABLED<\/code><\/td>\n<td><code>1<\/code> (<code>0<\/code> in <code>conf\/default<\/code>)<\/td>\n<td>KEV and EPSS enrichment<\/td>\n<\/tr>\n<tr>\n<td><code>ENRICHMENT_KEV_UPDATE<\/code><\/td>\n<td><code>1<\/code><\/td>\n<td>Refresh the KEV catalog<\/td>\n<\/tr>\n<tr>\n<td><code>ENRICHMENT_EPSS_TIMEOUT<\/code><\/td>\n<td><code>30<\/code><\/td>\n<td>EPSS lookup timeout in seconds<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"recon\">Recon and web discovery<\/h2>\n<p>Subdomain enumeration is now a <strong>two-layer pipeline<\/strong>: permutations are seeded only from names that actually resolved, and capped by <code>DOMAINS_PERMUTATION_MAX<\/code>. On our regression target that meant 74x fewer candidates to resolve for the same results.<\/p>\n<pre><code class=\"language-bash\">sudo sniper -t example.com -m recon_active -w example-corp<\/code><\/pre>\n<table>\n<thead>\n<tr>\n<th>Setting<\/th>\n<th>Default<\/th>\n<th>Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>DOMAINS_PERMUTATION_MAX<\/code><\/td>\n<td><code>500000<\/code><\/td>\n<td>Cap on permutation candidates<\/td>\n<\/tr>\n<tr>\n<td><code>DOMAINS_DEFAULT<\/code><\/td>\n<td><code>wordlists\/domains-common.txt<\/code><\/td>\n<td>New default brute-force list (with <code>domains-permutations.txt<\/code> and <code>resolvers-trusted.txt<\/code>; <code>resolvers.txt<\/code> grew from 8 to 55 vetted resolvers)<\/td>\n<\/tr>\n<tr>\n<td><code>PURE_DNS<\/code><\/td>\n<td><code>1<\/code><\/td>\n<td>Default resolver. <code>SUBBRUTE_DNS<\/code> and <code>MASS_DNS<\/code> now run when enabled<\/td>\n<\/tr>\n<tr>\n<td><code>CRTNAME_SUBDOMAINS<\/code> \/ <code>AGNIOPS_SUBDOMAINS<\/code><\/td>\n<td><code>1<\/code><\/td>\n<td>New keyless subdomain sources: crt.name and agniops<\/td>\n<\/tr>\n<tr>\n<td><code>ALTERX<\/code> \/ <code>FINDOMAIN<\/code> \/ <code>ASSETFINDER<\/code><\/td>\n<td><code>1<\/code><\/td>\n<td>New enumeration settings<\/td>\n<\/tr>\n<tr>\n<td><code>NS_TAKEOVER_SCAN<\/code><\/td>\n<td><code>1<\/code><\/td>\n<td>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<\/td>\n<\/tr>\n<tr>\n<td><code>ZAP_SCAN<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>Headless OWASP ZAP scan, results imported into sc0pe findings. Sn1per starts the ZAP daemon itself; tune with <code>ZAP_HOST<\/code>, <code>ZAP_PORT<\/code> (<code>8090<\/code>), <code>ZAP_API_KEY<\/code>, <code>ZAP_TIMEOUT<\/code> (<code>3600<\/code>), <code>ZAP_THREADS<\/code> (<code>10<\/code>) and <code>ZAP_SPIDER_MAX_DEPTH<\/code> (<code>5<\/code>)<\/td>\n<\/tr>\n<tr>\n<td><code>MULTI_AGENT<\/code> \/ <code>MAX_PARALLEL_AGENTS<\/code><\/td>\n<td><code>0<\/code> \/ <code>3<\/code><\/td>\n<td>Parallel scan workers that run scan modules (and the five AI specialists) concurrently<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>katana now crawls headless with robots.txt and sitemap.xml discovery at depth 3, and curated TCP nuclei templates run against the bare target.<\/p>\n<h2 id=\"integrations\">Ticketing and Nessus<\/h2>\n<h3 id=\"ticketing\">Ticketing: GitHub Issues, Jira and ServiceNow<\/h3>\n<p>At the end of a scan, after findings and AD correlation are finalized, Sn1per opens one ticket per <em>new<\/em> finding at or above <code>TICKETING_MIN_SEVERITY<\/code> in every provider you enable. It reads the sc0pe findings (<code>vulnerabilities\/sc0pe-*.txt<\/code> in the workspace).<\/p>\n<ul>\n<li><strong>Title:<\/strong> <code>[Sn1per] SEVERITY - Finding (host)<\/code>. <strong>Body:<\/strong> workspace, host, severity, finding, evidence and the source file.<\/li>\n<li><strong>No duplicates:<\/strong> each finding is keyed on severity, title and host and recorded in <code>scans\/ticketing-filed.txt<\/code> in the workspace, so recurring and scheduled scans never file the same finding twice.<\/li>\n<li><strong>Ships disabled:<\/strong> nothing is sent unless <code>TICKETING_ENABLED=\"1\"<\/code> and at least one provider is enabled with its credentials. A provider that is enabled but missing a required setting is skipped.<\/li>\n<\/ul>\n<blockquote>\n<p><strong>Test your credentials before a real scan.<\/strong> A finding is recorded in <code>scans\/ticketing-filed.txt<\/code> 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.<\/p>\n<\/blockquote>\n<table>\n<thead>\n<tr>\n<th>Provider<\/th>\n<th>Request<\/th>\n<th>Authentication<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>GitHub Issues<\/td>\n<td><code>POST https:\/\/api.github.com\/repos\/&lt;GITHUB_ISSUES_REPO&gt;\/issues<\/code><\/td>\n<td>Personal access token (<code>GITHUB_ISSUES_TOKEN<\/code>) with Issues write access<\/td>\n<\/tr>\n<tr>\n<td>Jira<\/td>\n<td><code>POST &lt;JIRA_URL&gt;\/rest\/api\/2\/issue<\/code> in <code>JIRA_PROJECT_KEY<\/code>, issue type <code>JIRA_ISSUE_TYPE<\/code><\/td>\n<td>Basic auth <code>JIRA_USER<\/code>:<code>JIRA_API_TOKEN<\/code> (Jira Cloud: account email and API token)<\/td>\n<\/tr>\n<tr>\n<td>ServiceNow<\/td>\n<td><code>POST https:\/\/&lt;SERVICENOW_INSTANCE&gt;.service-now.com\/api\/now\/table\/&lt;SERVICENOW_TABLE&gt;<\/code>, setting <code>short_description<\/code> and <code>description<\/code><\/td>\n<td>Basic auth <code>SERVICENOW_USER<\/code>:<code>SERVICENOW_PASSWORD<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<table>\n<thead>\n<tr>\n<th>Setting<\/th>\n<th>Default<\/th>\n<th>Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>TICKETING_ENABLED<\/code><\/td>\n<td><code>0<\/code><\/td>\n<td>Master switch<\/td>\n<\/tr>\n<tr>\n<td><code>TICKETING_MIN_SEVERITY<\/code><\/td>\n<td><code>HIGH<\/code><\/td>\n<td><code>CRITICAL<\/code>, <code>HIGH<\/code>, <code>MEDIUM<\/code>, <code>LOW<\/code> or <code>INFO<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>GITHUB_ISSUES_ENABLED<\/code>, <code>GITHUB_ISSUES_REPO<\/code>, <code>GITHUB_ISSUES_TOKEN<\/code><\/td>\n<td><code>0<\/code> \/ <code>\"\"<\/code><\/td>\n<td>Repository as <code>owner\/repo<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>JIRA_ENABLED<\/code>, <code>JIRA_URL<\/code>, <code>JIRA_USER<\/code>, <code>JIRA_API_TOKEN<\/code>, <code>JIRA_PROJECT_KEY<\/code>, <code>JIRA_ISSUE_TYPE<\/code><\/td>\n<td><code>0<\/code> \/ <code>\"\"<\/code>, issue type <code>Task<\/code><\/td>\n<td>URL like <code>https:\/\/org.atlassian.net<\/code>. URL, user, token and project key are all required<\/td>\n<\/tr>\n<tr>\n<td><code>SERVICENOW_ENABLED<\/code>, <code>SERVICENOW_INSTANCE<\/code>, <code>SERVICENOW_USER<\/code>, <code>SERVICENOW_PASSWORD<\/code>, <code>SERVICENOW_TABLE<\/code><\/td>\n<td><code>0<\/code> \/ <code>\"\"<\/code>, table <code>incident<\/code><\/td>\n<td>Instance is the subdomain of <code>&lt;instance&gt;.service-now.com<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<blockquote>\n<p><strong>Only two profiles carry these settings.<\/strong> The ticketing settings ship only in <code>conf\/default<\/code> (normal mode) and <code>conf\/ad<\/code> (AD mode). They are not in <code>sniper.conf<\/code> or the other profiles (<code>flyover<\/code>, <code>fullportscan<\/code>, <code>full_scan<\/code>, <code>vulnscan<\/code>, <code>recon_passive<\/code>, <code>recon_active<\/code>, <code>all_disabled<\/code>, <code>all_web_port_scan<\/code>). Because every scan loads a profile, ticketing works only for scans that use <code>conf\/default<\/code> or <code>conf\/ad<\/code> unless you add the settings to the profile you scan with. In Sn1per Enterprise, the web UI Config Editor has toggles for them.<\/p>\n<\/blockquote>\n<p>For an overview, see <a href=\"\/wordpress\/sn1per-se-v11-1-released\/#ticketing\">ticketing in the v11.1 release announcement<\/a>.<\/p>\n<h3 id=\"nessus-launcher\">Nessus launcher<\/h3>\n<p>The <strong>Nessus launcher<\/strong> (<code>NESSUS=\"1\"<\/code>, default <code>0<\/code>) starts a Nessus scan of the target from normal mode using <code>NESSUS_HOST<\/code> (default <code>127.0.0.1:8834<\/code>), <code>NESSUS_USERNAME<\/code>, <code>NESSUS_PASSWORD<\/code> and <code>NESSUS_POLICY_ID<\/code>.<\/p>\n<h2 id=\"templates\">Detection templates<\/h2>\n<ul>\n<li><strong>56 new templates<\/strong>, 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.<\/li>\n<li><strong><code>templates\/nuclei-authenticated\/<\/code><\/strong>: a new directory for authenticated checks you run by hand.<\/li>\n<li>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.<\/li>\n<\/ul>\n<h2 id=\"hardening\">Security hardening and self-maintenance<\/h2>\n<ul>\n<li><strong>API keys never reach loot:<\/strong> key values are masked before they reach scan output, reports and logs. Clean older loot with <code>sniper-mask-secrets<\/code> (see <a href=\"#after-upgrade\">After upgrading<\/a>).<\/li>\n<li><strong><code>-dh<\/code><\/strong> deletes only the requested host, and refuses to run without a valid workspace and target. <strong><code>-d<\/code><\/strong> refuses an empty or invalid workspace name.<\/li>\n<li><strong><code>-dt<\/code><\/strong> stops only that workspace&#8217;s scans and their orphaned tools, not every matching process on the host.<\/li>\n<li><strong>Target-supplied names<\/strong> can no longer become file names, command options or paths.<\/li>\n<li><strong>Tool health check and self-repair:<\/strong> each scan starts with a toolchain check (<code>bin\/tool_health_check.sh<\/code>), and when a scan step needs a tool that is missing, <code>lib\/sniper-selfheal.sh<\/code> installs or repairs it before running it (or hands it to the <a href=\"#kali-tools-fallback\">Kali tools fallback<\/a> when that is enabled), so a broken dependency no longer means a silently incomplete scan.<\/li>\n<li><code>-fp<\/code> runs a full port scan again, and <code>sniper --help<\/code> matches the v11 engine.<\/li>\n<\/ul>\n<h2 id=\"removed-settings\">Removed and renamed settings<\/h2>\n<p>If an older profile or document refers to one of these settings, it has no effect in v11.1.<\/p>\n<table>\n<thead>\n<tr>\n<th>Removed or changed<\/th>\n<th>Use instead<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>QUICK_PORTS<\/code><\/td>\n<td><code>DEFAULT_PORTS<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>CENSYS_SUBDOMAINS<\/code> (Censys subdomain lookups)<\/td>\n<td>Removed. Use the other subdomain sources, including the keyless crt.name and agniops sources<\/td>\n<\/tr>\n<tr>\n<td>SubOver (<code>SUBOVER<\/code> now defaults to <code>0<\/code>; the installer no longer builds it)<\/td>\n<td><code>NUCLEI_TAKEOVER_SCAN<\/code>, <code>SUBJACK<\/code> and <code>NS_TAKEOVER_SCAN<\/code><\/td>\n<\/tr>\n<tr>\n<td>Unused Slack notification toggles<\/td>\n<td>Removed<\/td>\n<\/tr>\n<tr>\n<td><code>AI_AGENT_MODE<\/code>, <code>AI_PHASE2_URL<\/code><\/td>\n<td>Removed (no code read them). Use <code>AI_PHASE2_PROVIDER<\/code> \/ <code>AI_PHASE2_MODEL<\/code> for the deep stages<\/td>\n<\/tr>\n<tr>\n<td><code>SN1PER_AI_SOURCE_ANALYSIS<\/code><\/td>\n<td>Set <code>SN1PER_AI_SOURCE_REPO<\/code>; the repository path alone decides<\/td>\n<\/tr>\n<tr>\n<td><code>SN1PER_AI_VULN_ANALYSIS<\/code><\/td>\n<td><code>AI_VULNERABILITY_ANALYSIS<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>SN1PER_AI_REPORT_SYNTHESIS<\/code><\/td>\n<td><code>AI_REPORT_ENHANCEMENT<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>SN1PER_AI_PARALLEL_ANALYSIS<\/code><\/td>\n<td><code>MULTI_AGENT<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>SN1PER_AI_LARGE_MODEL<\/code><\/td>\n<td><code>AI_PHASE2_MODEL<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>SN1PER_AI_VULN_MAX_TOKENS<\/code>, <code>SN1PER_AI_EXPLOIT_MAX_TOKENS<\/code>, <code>SN1PER_AI_REPORT_MAX_TOKENS<\/code><\/td>\n<td>Removed. <code>AI_MAX_TOKENS<\/code> and <code>AI_MAX_INPUT_TOKENS_PER_QUERY<\/code> apply<\/td>\n<\/tr>\n<tr>\n<td>Duplicate <code>CLAUDE_CODE_MAX_TURNS<\/code>, <code>OPENROUTER_API_KEY<\/code> and <code>ZAI_API_KEY<\/code> entries<\/td>\n<td>Removed from <code>sniper.conf<\/code> and the profiles; previously the second copy silently won<\/td>\n<\/tr>\n<tr>\n<td><code>bin\/sniper-ai-scan-analysis.sh<\/code><\/td>\n<td>Removed on upgrade; <code>AI_SCAN_ANALYSIS<\/code> does the per-tool analysis<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>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 <code>CHANGELOG.md<\/code>.<\/p>\n<h2 id=\"see-also\">See also<\/h2>\n<ul>\n<li><a href=\"\/wordpress\/sn1per-se-v11-1-released\/\">Sn1per SE v11.1 release announcement<\/a><\/li>\n<li><a href=\"\/wordpress\/documentation\/configuration\/\">Configuration<\/a> and <a href=\"\/wordpress\/documentation\/usage\/\">Usage<\/a><\/li>\n<li><a href=\"\/wordpress\/documentation\/mcp\/\">Sn1per MCP Server<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>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\u2026<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":2284,"menu_order":75,"comment_status":"closed","ping_status":"closed","template":"page-templates\/template-doc-page.php","meta":{"_exactmetrics_skip_tracking":false,"_jetpack_hide_featured_image":false,"_jetpack_featured_image_duplicate_dismissed":0,"footnotes":""},"class_list":["post-68346","page","type-page","status-publish","hentry"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.5.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"Sn1per SE v11.1 docs: upgrade steps, Active Directory mode, AI analysis settings, Playwright XSS verification, Kali tools fallback, MCP and removed settings.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<link rel=\"canonical\" href=\"https:\/\/sn1persecurity.com\/wordpress\/documentation\/scan-engine\/\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\n\t\t<meta property=\"og:site_name\" content=\"Sn1perSecurity\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"Sn1per Scan Engine v11.1 Docs: AI, AD Mode and Playwright\" \/>\n\t\t<meta property=\"og:description\" content=\"Sn1per SE v11.1 docs: upgrade steps, Active Directory mode, AI analysis settings, Playwright XSS verification, Kali tools fallback, MCP and removed settings.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/sn1persecurity.com\/wordpress\/documentation\/scan-engine\/\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/sn1persecurity.com\/wordpress\/wp-content\/uploads\/2021\/10\/Sn1perSecurity-Attack-Surface-Management-header2.png\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/sn1persecurity.com\/wordpress\/wp-content\/uploads\/2021\/10\/Sn1perSecurity-Attack-Surface-Management-header2.png\" \/>\n\t\t<meta property=\"og:image:width\" content=\"1920\" \/>\n\t\t<meta property=\"og:image:height\" content=\"1080\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2026-11-15T23:21:15+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2026-11-15T23:21:15+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/Sn1persecurity-105784611869093\" \/>\n\t\t<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n\t\t<meta name=\"twitter:site\" content=\"@sn1persecurity\" \/>\n\t\t<meta name=\"twitter:title\" content=\"Sn1per Scan Engine v11.1 Docs: AI, AD Mode and Playwright\" \/>\n\t\t<meta name=\"twitter:description\" content=\"Sn1per SE v11.1 docs: upgrade steps, Active Directory mode, AI analysis settings, Playwright XSS verification, Kali tools fallback, MCP and removed settings.\" \/>\n\t\t<meta name=\"twitter:creator\" content=\"@sn1persecurity\" \/>\n\t\t<meta name=\"twitter:image\" content=\"https:\/\/sn1persecurity.com\/wordpress\/wp-content\/uploads\/2021\/10\/Sn1perSecurity-Attack-Surface-Management-header2.png\" \/>\n\t\t<script type=\"application\/ld+json\" class=\"aioseo-schema\">\n\t\t\t{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/sn1persecurity.com\\\/wordpress\\\/documentation\\\/scan-engine\\\/#breadcrumblist\",\"itemListElement\":[{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/sn1persecurity.com\\\/wordpress\\\/#listItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/sn1persecurity.com\\\/wordpress\\\/\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/sn1persecurity.com\\\/wordpress\\\/documentation\\\/#listItem\",\"name\":\"Documentation\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/sn1persecurity.com\\\/wordpress\\\/documentation\\\/#listItem\",\"position\":2,\"name\":\"Documentation\",\"item\":\"https:\\\/\\\/sn1persecurity.com\\\/wordpress\\\/documentation\\\/\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/sn1persecurity.com\\\/wordpress\\\/documentation\\\/scan-engine\\\/#listItem\",\"name\":\"Scan Engine v11.1\"},\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/sn1persecurity.com\\\/wordpress\\\/#listItem\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/sn1persecurity.com\\\/wordpress\\\/documentation\\\/scan-engine\\\/#listItem\",\"position\":3,\"name\":\"Scan Engine v11.1\",\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/sn1persecurity.com\\\/wordpress\\\/documentation\\\/#listItem\",\"name\":\"Documentation\"}}]},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/sn1persecurity.com\\\/wordpress\\\/#organization\",\"name\":\"Sn1perSecurity\",\"description\":\"Get an attacker's view of your organization with our all-in-one offensive security platform\",\"url\":\"https:\\\/\\\/sn1persecurity.com\\\/wordpress\\\/\",\"email\":\"support@sn1persecurity.com\",\"foundingDate\":\"2021-10-05\",\"numberOfEmployees\":{\"@type\":\"QuantitativeValue\",\"value\":2},\"logo\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/sn1persecurity.com\\\/wordpress\\\/wp-content\\\/uploads\\\/2022\\\/06\\\/Sn1perwhiteandcircleicontwitter.jpg\",\"@id\":\"https:\\\/\\\/sn1persecurity.com\\\/wordpress\\\/documentation\\\/scan-engine\\\/#organizationLogo\",\"width\":500,\"height\":500,\"caption\":\"Sn1perSecurity Logo\"},\"image\":{\"@id\":\"https:\\\/\\\/sn1persecurity.com\\\/wordpress\\\/documentation\\\/scan-engine\\\/#organizationLogo\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/Sn1persecurity-105784611869093\",\"https:\\\/\\\/x.com\\\/sn1persecurity\",\"https:\\\/\\\/www.instagram.com\\\/sn1persecurity\",\"https:\\\/\\\/www.youtube.com\\\/sn1persecurity\",\"https:\\\/\\\/www.linkedin.com\\\/in\\\/sn1persecurity\\\/\",\"https:\\\/\\\/github.com\\\/1N3\\\/Sn1per\"]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/sn1persecurity.com\\\/wordpress\\\/documentation\\\/scan-engine\\\/#webpage\",\"url\":\"https:\\\/\\\/sn1persecurity.com\\\/wordpress\\\/documentation\\\/scan-engine\\\/\",\"name\":\"Sn1per Scan Engine v11.1 Docs: AI, AD Mode and Playwright\",\"description\":\"Sn1per SE v11.1 docs: upgrade steps, Active Directory mode, AI analysis settings, Playwright XSS verification, Kali tools fallback, MCP and removed settings.\",\"inLanguage\":\"en-US\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/sn1persecurity.com\\\/wordpress\\\/#website\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/sn1persecurity.com\\\/wordpress\\\/documentation\\\/scan-engine\\\/#breadcrumblist\"},\"datePublished\":\"2026-11-15T16:21:15-07:00\",\"dateModified\":\"2026-11-15T16:21:15-07:00\"},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/sn1persecurity.com\\\/wordpress\\\/#website\",\"url\":\"https:\\\/\\\/sn1persecurity.com\\\/wordpress\\\/\",\"name\":\"Sn1perSecurity\",\"alternateName\":\"Sn1per\",\"description\":\"Get an attacker's view of your organization with our all-in-one offensive security platform\",\"inLanguage\":\"en-US\",\"publisher\":{\"@id\":\"https:\\\/\\\/sn1persecurity.com\\\/wordpress\\\/#organization\"}}]}\n\t\t<\/script>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"Sn1per Scan Engine v11.1 Docs: AI, AD Mode and Playwright","description":"Sn1per SE v11.1 docs: upgrade steps, Active Directory mode, AI analysis settings, Playwright XSS verification, Kali tools fallback, MCP and removed settings.","canonical_url":"https:\/\/sn1persecurity.com\/wordpress\/documentation\/scan-engine\/","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"BreadcrumbList","@id":"https:\/\/sn1persecurity.com\/wordpress\/documentation\/scan-engine\/#breadcrumblist","itemListElement":[{"@type":"ListItem","@id":"https:\/\/sn1persecurity.com\/wordpress\/#listItem","position":1,"name":"Home","item":"https:\/\/sn1persecurity.com\/wordpress\/","nextItem":{"@type":"ListItem","@id":"https:\/\/sn1persecurity.com\/wordpress\/documentation\/#listItem","name":"Documentation"}},{"@type":"ListItem","@id":"https:\/\/sn1persecurity.com\/wordpress\/documentation\/#listItem","position":2,"name":"Documentation","item":"https:\/\/sn1persecurity.com\/wordpress\/documentation\/","nextItem":{"@type":"ListItem","@id":"https:\/\/sn1persecurity.com\/wordpress\/documentation\/scan-engine\/#listItem","name":"Scan Engine v11.1"},"previousItem":{"@type":"ListItem","@id":"https:\/\/sn1persecurity.com\/wordpress\/#listItem","name":"Home"}},{"@type":"ListItem","@id":"https:\/\/sn1persecurity.com\/wordpress\/documentation\/scan-engine\/#listItem","position":3,"name":"Scan Engine v11.1","previousItem":{"@type":"ListItem","@id":"https:\/\/sn1persecurity.com\/wordpress\/documentation\/#listItem","name":"Documentation"}}]},{"@type":"Organization","@id":"https:\/\/sn1persecurity.com\/wordpress\/#organization","name":"Sn1perSecurity","description":"Get an attacker's view of your organization with our all-in-one offensive security platform","url":"https:\/\/sn1persecurity.com\/wordpress\/","email":"support@sn1persecurity.com","foundingDate":"2021-10-05","numberOfEmployees":{"@type":"QuantitativeValue","value":2},"logo":{"@type":"ImageObject","url":"https:\/\/sn1persecurity.com\/wordpress\/wp-content\/uploads\/2022\/06\/Sn1perwhiteandcircleicontwitter.jpg","@id":"https:\/\/sn1persecurity.com\/wordpress\/documentation\/scan-engine\/#organizationLogo","width":500,"height":500,"caption":"Sn1perSecurity Logo"},"image":{"@id":"https:\/\/sn1persecurity.com\/wordpress\/documentation\/scan-engine\/#organizationLogo"},"sameAs":["https:\/\/www.facebook.com\/Sn1persecurity-105784611869093","https:\/\/x.com\/sn1persecurity","https:\/\/www.instagram.com\/sn1persecurity","https:\/\/www.youtube.com\/sn1persecurity","https:\/\/www.linkedin.com\/in\/sn1persecurity\/","https:\/\/github.com\/1N3\/Sn1per"]},{"@type":"WebPage","@id":"https:\/\/sn1persecurity.com\/wordpress\/documentation\/scan-engine\/#webpage","url":"https:\/\/sn1persecurity.com\/wordpress\/documentation\/scan-engine\/","name":"Sn1per Scan Engine v11.1 Docs: AI, AD Mode and Playwright","description":"Sn1per SE v11.1 docs: upgrade steps, Active Directory mode, AI analysis settings, Playwright XSS verification, Kali tools fallback, MCP and removed settings.","inLanguage":"en-US","isPartOf":{"@id":"https:\/\/sn1persecurity.com\/wordpress\/#website"},"breadcrumb":{"@id":"https:\/\/sn1persecurity.com\/wordpress\/documentation\/scan-engine\/#breadcrumblist"},"datePublished":"2026-11-15T16:21:15-07:00","dateModified":"2026-11-15T16:21:15-07:00"},{"@type":"WebSite","@id":"https:\/\/sn1persecurity.com\/wordpress\/#website","url":"https:\/\/sn1persecurity.com\/wordpress\/","name":"Sn1perSecurity","alternateName":"Sn1per","description":"Get an attacker's view of your organization with our all-in-one offensive security platform","inLanguage":"en-US","publisher":{"@id":"https:\/\/sn1persecurity.com\/wordpress\/#organization"}}]},"og:locale":"en_US","og:site_name":"Sn1perSecurity","og:type":"article","og:title":"Sn1per Scan Engine v11.1 Docs: AI, AD Mode and Playwright","og:description":"Sn1per SE v11.1 docs: upgrade steps, Active Directory mode, AI analysis settings, Playwright XSS verification, Kali tools fallback, MCP and removed settings.","og:url":"https:\/\/sn1persecurity.com\/wordpress\/documentation\/scan-engine\/","og:image":"https:\/\/sn1persecurity.com\/wordpress\/wp-content\/uploads\/2021\/10\/Sn1perSecurity-Attack-Surface-Management-header2.png","og:image:secure_url":"https:\/\/sn1persecurity.com\/wordpress\/wp-content\/uploads\/2021\/10\/Sn1perSecurity-Attack-Surface-Management-header2.png","og:image:width":1920,"og:image:height":1080,"article:published_time":"2026-11-15T23:21:15+00:00","article:modified_time":"2026-11-15T23:21:15+00:00","article:publisher":"https:\/\/www.facebook.com\/Sn1persecurity-105784611869093","twitter:card":"summary_large_image","twitter:site":"@sn1persecurity","twitter:title":"Sn1per Scan Engine v11.1 Docs: AI, AD Mode and Playwright","twitter:description":"Sn1per SE v11.1 docs: upgrade steps, Active Directory mode, AI analysis settings, Playwright XSS verification, Kali tools fallback, MCP and removed settings.","twitter:creator":"@sn1persecurity","twitter:image":"https:\/\/sn1persecurity.com\/wordpress\/wp-content\/uploads\/2021\/10\/Sn1perSecurity-Attack-Surface-Management-header2.png"},"aioseo_meta_data":{"post_id":"68346","title":"Sn1per Scan Engine v11.1 Docs: AI, AD Mode and Playwright","description":"Sn1per SE v11.1 docs: upgrade steps, Active Directory mode, AI analysis settings, Playwright XSS verification, Kali tools fallback, MCP and removed settings.","keywords":null,"keyphrases":{"focus":{"keyphrase":"Sn1per SE v11.1 documentation","score":0,"analysis":[]}},"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"WebPage","isEnabled":true},"graphs":[]},"schema_type":"default","schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"breadcrumb_settings":null,"limit_modified_date":false,"ai":null,"created":"2026-11-15 23:21:15","updated":"2026-11-16 18:20:46","seo_analyzer_scan_date":null,"focus_keyword":"Sn1per SE v11.1 documentation","additional_keywords":null,"truseo_locale":null},"aioseo_breadcrumb":"<div class=\"aioseo-breadcrumbs\"><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/sn1persecurity.com\/wordpress\/\" title=\"Home\">Home<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">\u00bb<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/sn1persecurity.com\/wordpress\/documentation\/\" title=\"Documentation\">Documentation<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">\u00bb<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\tScan Engine v11.1\n\t\t<\/span><\/div>","aioseo_breadcrumb_json":[{"label":"Home","link":"https:\/\/sn1persecurity.com\/wordpress\/"},{"label":"Documentation","link":"https:\/\/sn1persecurity.com\/wordpress\/documentation\/"},{"label":"Scan Engine v11.1","link":"https:\/\/sn1persecurity.com\/wordpress\/documentation\/scan-engine\/"}],"jetpack_shortlink":"https:\/\/wp.me\/PdnW96-hMm","jetpack_likes_enabled":true,"jetpack_sharing_enabled":true,"jetpack-related-posts":[],"_links":{"self":[{"href":"https:\/\/sn1persecurity.com\/wordpress\/wp-json\/wp\/v2\/pages\/68346","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sn1persecurity.com\/wordpress\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/sn1persecurity.com\/wordpress\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/sn1persecurity.com\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sn1persecurity.com\/wordpress\/wp-json\/wp\/v2\/comments?post=68346"}],"version-history":[{"count":0,"href":"https:\/\/sn1persecurity.com\/wordpress\/wp-json\/wp\/v2\/pages\/68346\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/sn1persecurity.com\/wordpress\/wp-json\/wp\/v2\/pages\/2284"}],"wp:attachment":[{"href":"https:\/\/sn1persecurity.com\/wordpress\/wp-json\/wp\/v2\/media?parent=68346"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}