You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can now scope an engagement by host and account as well as by domain. adscan ci and adscan start take --scope-allow and --scope-deny (IPs, CIDRs, ranges, host names, SIDs, DNs, DOMAIN\name, UPNs) and --scope-allow-file / --scope-deny-file, and deny always wins. A mistake in the list stops the run before anything is sent, naming the file and the line. Domain controllers an allow list does not name are used for directory reads only, unless you pass --scope-dc-access full. The scope holds from the first packet, the unauthenticated guest and null-session checks included, and every host is asked about again right before it is contacted. It stays in the workspace for later runs, and the scope command in the shell shows it, changes it (asking before it widens) and explains why a given host is in or out. Both reports list what the scope kept out and, separately, what ADscan could not confirm as in scope and left alone. The Enterprise platform sets the same scope per workspace.
Ctrl+C during a scan, or while any shell command runs, now opens a menu instead of closing ADscan. You can stop the current step and keep what it found, skip the rest of the phase, stop the scan, or keep going. Port scans, user enumeration, the SMB host sweep, post-compromise access checks and bulk credential dumps all stop this way. A stopped step reports a partial result, and hosts it did not reach are reported as not checked, never as having no access. Both reports name every step or phase the operator cut short, and adscan ci stops cleanly on the first Ctrl+C and exits 3.
A stopped scan can be resumed. Reopening a workspace offers to resume a phase that was cut short, by you or by a memory stop, and reruns only that phase. Running adscan ci again on a stopped scan resumes it, says where it stopped and skips the hosts and phases already finished. Over a finished scan, with a different account or after the engagement scope changed, ci starts clean and says so. The resume offer names a changed scope before you choose, and a resumed scan holds every contact and step to the current scope.
New adscan license command for ADscan PRO, and PRO now installs with adscan install --license-file and your key file. The licence picks the edition and the image downloads from ADscan's own registry, with no GitHub account and no docker login. Run adscan license activate once with the key from your onboarding email; every launch then verifies the licence stored on your machine, and an online launch also checks in with the licence server, waiting two seconds at most. The check-in sends the installation and licence identifiers and the engine version, never scan data. status shows when your contract ends, with reminders from 30 days out; check finds what stops a machine from reaching the server (the proxy, DNS, port 443, TLS inspection or a wrong clock); deactivate releases the seat, keeping the queue when the server cannot be reached. A machine with no route to ADscan activates and refreshes through a file, with --relay-out and adscan license relay import. The free CLI stays free and source-available under BSL 1.1 and needs no licence.
adscan recheck re-verifies much more without a new scan, always read-only. It now covers AD CS findings (ESC1 to ESC9, ESC11, ESC13 and ESC15, without requesting a certificate), delegated rights over objects, LAPS and gMSA password reads, DCSync rights, and the signing, channel binding, NTLM, LDAPS and Kerberos RC4 settings of the domain controller. -u/--username and -p/--password re-check with an account of your choosing, used for that run only and never stored, and --path takes the attack-path id each report now prints. Anything it cannot read stays "not re-checked" with the reason, never fixed, and an AD CS check decided from a value on the CA host names the read the account could not obtain. adscan recheck --json and adscan engagement --json write only the JSON document to stdout.
An audit report can carry no compliance mapping when the organisation follows none of the six frameworks ADscan maps: pass --frameworks none or tick None, and the report says that no framework applies, by the assessor's decision. The framework is asked for up front, and leaving it blank is still refused. The compliance annex also reads segregation of duties on each AD CS certification authority: a CA that enforces role separation evidences ISO 27001 A.5.3, ENS op.acc.3, DORA Art. 9(4)(c) and NIS2 Art. 21(2)(i), and one that does not, while an account outside the built-in administration groups holds both CA Administrator and Certificate Manager, is a non-conformity naming that account.
ADscan shows what your cleanup account can undo before it changes anything, as a checklist per forest, domain and certification authority in scope, printed by cleanup_credential check, adscan ci and adscan start and stated in the report. With a cleanup account supplied, the Audit policy runs the AD CS techniques on each CA where ADscan confirmed, read-only, that the account can revoke the certificate there, and skips them on any other CA.
Both reports say when a scan did not run under the scan policy agreed with the client, naming both policies and their digests. The agreed policy is set per workspace on the Enterprise platform, or in a scan config as agreed_policy.
Changed
ADscan PRO now requires an activated licence. From 15.0.0 the PRO image starts no new assessment on a machine that has not activated one. Your activation key arrives by email. Run adscan update, then adscan license activate once and paste the key. Without a licence, adscan start, adscan ci, adscan execute and adscan recheck stop with a message that names this fix, and adscan ci exits 78. Your workspaces and reports are untouched, and adscan deliver renders them without a licence. The 14.0.0 PRO image keeps working if you pin it, until that build expires on 10 December 2026. The free CLI needs no licence.
A PRO image no longer stops working 30 days after it was built. Your licence decides how long PRO runs, and each release image carries a two-year limit of its own, so a version you pin keeps working for as long as your licence does within those two years. PRO images are published on ADscan's own registry, and the copies on Docker Hub and GHCR stop receiving new versions after a transition period.
Every PRO licence registers the domains it assesses, the free trial included, and --offline no longer turns that off. A domain is sent as a code derived from your licence key with a size band for its number of accounts, never its name or any client data. A partner licence also sends, for each run, how many accounts, computers, domain controllers and certificate authorities it counted, so the partner and ADscan compare the same usage figures. Other licences send the band only and keep the counts in their own adscan license register export. A new domain is never refused on its first scan, and when ADscan cannot be reached it keeps working for its grace period, 7 days unless your agreement says otherwise.
Telemetry now identifies each install by a random installation ID created on first run, instead of an ID derived from the machine. On a machine with a PRO licence, every telemetry event, the sanitized terminal output included, also carries the licence's id, the seat id and the label we gave the licence, so we can find a failed run and help you without asking for logs. It never carries a name or an email address, and domains, hostnames, IP addresses, users and credentials are still pseudonymized or removed before anything leaves your machine. Linking telemetry to a licence holder is processing of personal data and we treat it that way. adscan license activate states what PRO sends, set telemetry off global, --no-telemetry or ADSCAN_TELEMETRY=0 turn telemetry off, and the licence keeps working with it off.
The attack graph now lives in a store inside the workspace, and attack_graph.json is an export of it. Each host's results are saved as they arrive, so saving costs the same on the thousandth host as on the first and a stopped scan resumes from the last host saved. The exported file of a large directory is a fraction of its former size.
A directory too large for the machine's memory now ends with a declared gap instead of a crash, and needs far less memory to begin with. Collection, graph building, attack-path discovery and report rendering each stop before the system would kill the scan and keep what they finished. The terminal says what stopped, the memory ADscan reached against its limit, how to give it more where it is running, and the next step, which is to reopen the workspace and choose Resume. Both reports and the Enterprise platform state which part was not evaluated, and adscan ci exits 3. The scan, its summary and the report stages no longer each recompute the attack routes, since the first computation is reused: discovery on a directory of 275,000 relationships peaks at 0.7 GB where it took 1.2 GB, and ranking choke points on a directory of 58,000 objects and 900,000 relationships takes seconds where it ran for more than two hours without finishing. A small directory where a few groups control most accounts, which used to stop with no routes, now gets a declared sample of routes in a few seconds. The supported minimum is 1 GB of free memory, and the launcher refuses to start below it unless you pass --allow-low-memory.
Every attack step now says why it did not run or did not complete, in both reports and on the Enterprise platform, in plain words such as a host that did not answer, a credential the target refused or a hash captured and not cracked. A step behind one your scan policy excludes reads as depending on that step, a step behind one that did not complete says so, and a step of an attended run that no operator was asked about reads as awaiting approval. When the scan could not establish the cause it says so, and it never credits a defensive product. Until now many such steps carried no reason at all.
The reports now say what each figure counts. The rotation action lists the accounts ADscan holds a usable credential for and says that krbtgt is handled by its own reset, while the password recovery figures count every account whose hash was extracted and tested; the two differ on most assessments and used to be worded alike. A path ADscan did not walk end to end reads "Domain Compromise Reachable", and only a route executed to its end keeps the past tense. The DA paths figure and the routes called validated end to end count only routes walked to full domain compromise, the Critical and High counts on the end-of-run card match the recap and the report, and unattended runs consider every listed route for execution, past the 20 the panel shows.
The terminal now reads cleanly at 80 columns. The attack-path table, the trust matrix and the choke-point list print every route and domain name in full and move low-priority columns under the route when the window is narrow. Accounts, groups and hosts are named the way the reports name them, jon.snow where the terminal used to print JON.SNOW@NORTH.SEVENKINGDOMS.LOCAL, and attack steps keep their technical names. CVE findings show their public CVE id and no CVSS number, so a check that is not a CVE no longer carries a score.
A Group Policy object is now named by the display name it has in Group Policy Management, followed by the first characters of its GUID, as in "Default Domain Policy (31B2F340)", instead of by its bare GUID. This holds in attack steps, attack-path tables, both reports and the Enterprise platform. Remediation and verification commands still point at the object's own distinguished name.
The Security Assessment Report now opens with a "Do this week" list, the credential custody actions first and then the first three fixes, each with its page. It prints at full size where it used to be shrunk to 87 percent, explains each attack technique once, gathers the commands that reproduce an attack by hand in a new Appendix R, and prints the fix command and its check on each Critical or High finding.
Every report now renders without an outbound connection, and in the typography it was designed in. The typefaces ship with ADscan instead of loading from Google Fonts and the PDF renderer refuses any request that would leave the machine, so an air-gapped render reads the same as an online one. Commands print as the console they run in, a Windows window for PowerShell and SQL Server, a Linux terminal for shell commands and the ADscan prompt for ADscan's own verbs, and copying one out of the PDF gives you the command alone. A long domain or client name no longer runs off the edge of the cover.
Planting NTLMv2 capture bait on writable shares now begins with one checklist of the writable hosts instead of a separate prompt for each host, and the hosts you pick are planted without being asked again. On an audit nothing is pre-selected, since the bait leaves a file on the share, so you opt in by choosing hosts; in a lab every host is pre-selected.
Fixed
The end-of-scan Audit Summary no longer reports a clean posture when findings exist. It now lists the hygiene findings the scan recorded, says plainly when the collector finished and found none, and says when there is no reading at all instead of calling that clean.
The file reviews no longer exhaust memory on an estate with large file servers, database servers or hosts, which used to end the scan. Network shares, SQL Server drives and hosts reviewed over WinRM are each read in small replies, filtered to the file types the review reads, and only the files it can read are kept, so memory no longer grows with the number of files. Every share is still listed in full, whatever the folder and however deep, and every drive is still searched whole. When a listing reaches its bound, runs out of time or ends on an error, the review continues on the files kept and both the report and the platform state how much was covered: how many shares were listed in full, how many files were listed, and that the rest was not evaluated. A listing that ran out of time used to be dropped or counted as complete, and reading a large file back from a SQL Server used to grow memory with the square of its size.
Deleted accounts are no longer counted as users. A scan that reached Domain Admin also read the directory's Deleted Objects container, and the accounts in it were counted as ordinary users holding a path to compromise, so the headline could read 11 of 11 on a directory with 9 such users. A deleted account is now left out of every user, computer and group count, belongs to no group and starts no attack path. The right to restore one is still reported.
A result that could look clean is now declared instead. A domain controller that stops answering partway through a scan has its checks recorded as not evaluated, the terminal no longer says the host appears clean, adscan ci exits 3, and coverage.json and technical_report.json name the phase that did not finish; a later run that reaches it again closes the gap. A certification authority that refuses its permissions to a low-privileged account gets one calm line and an incomplete CA-administration check, and is given up on after 90 seconds. An SMB sub-collection you deselect appears as not collected, chosen by the operator. A scan that stops in preflight no longer closes with every phase ticked and a Loot Summary, and an incomplete run ends by saying that what it collected is in the workspace, marked incomplete.
Guest SMB sessions work again. Since 14.0.0, RID cycling and share enumeration as guest were never sent. A guest probe now uses a name unique to the engagement (adscan- and eight random characters) that is first confirmed absent from your directory, so it can never count as a failed sign-in on one of your accounts, and the share view shows which identity each session used. Every sign-in of the share credential search is decided by the account-lockout protection before any tool starts, and a sign-in it withholds ends the search instead of falling back to a tool that signed in as the built-in Guest account. Password spraying no longer guesses against the cleanup account you supplied, and a blank-password spray that finds Guest accepting an empty password reports it as guest access rather than storing a domain credential. Both reports declare any host guest access was never asked of.
A change left in place by a scan that was killed is now undone by the next run of the same workspace. A resumed scan retries it with the cleanup account first, as it would a change of its own, and lists it for manual cleanup only when no account can undo it or the attempt fails, with that reason. It used to mark the change for manual cleanup without trying. This covers an xp_cmdshell enable on a SQL Server, whose manual instruction now restores both settings it changed, xp_cmdshell and show advanced options, to the values recorded before the change.
Kerberos over TCP no longer fails for an account whose reply from the domain controller arrives in two parts with the last one to four bytes in the second. Every sign-in as that account to that service used to fail with an "Insufficient data" error, which could stop an AD CS enrollment or a registry read on the CA host. If a reply does arrive cut short or unreadable, ADscan now says so in those words instead of reporting a generic failure.
An unattended run executes a route again when its first runnable step is one the session can start, whatever technique that step is. Since routes are drawn through to the domain, a route that began with a Backup Operators escalation, a local credential read, a scheduled task or a SQL Server step was listed as needing a credential and skipped, because it was judged on a later step whose account is only controlled once the earlier steps succeed. The host clock is also synchronised with the domain controller before the post-compromise Kerberos steps instead of being skipped, a domain you have already compromised is treated as authenticated by Kerberos roasting, password cracking and SMB spidering, and the phase no longer prints "bound to a different event loop".
A Kerberoasting or AS-REP roasting finding now states how many accounts are exposed to offline password recovery and, apart from that, how many passwords were recovered and for which accounts. It used to list every exposed account and then say they were recovered offline, even when one ticket out of three was cracked or none was.
A Start here row no longer contradicts its own figures. A fix whose routes start from an ordinary user account, or from a group that account belongs to, now counts that user. It used to read that no ordinary user runs through the technique and that its paths start from computer or group footholds, with the executed count in the place of the paths it closes. Where a fix's paths start is now read from the paths themselves, in both reports and on the Enterprise platform.
A group you created is now written as your directory writes it wherever an attack route names it. The Security Assessment Report, the Playbook, the free report and the terminal panels used to write a group such as CastelblackAdmins in lower case in the route section while the remediation steps kept its real casing. Only user and computer account names are typed in lower case.
Telemetry now pseudonymizes every directory object an attack step or a scan-policy line names, a Group Policy object's GUID and display name included, while your terminal still shows them in full. Windows constants such as well-known SIDs and the two default GPOs stay readable, because they identify no organisation. workspace purge-secrets also redacts the previous graph export that a stopped build sets aside, so a purged workspace keeps no recovered password, hash or key in any graph file. The telemetry off command shown at install and activation now names the machine-wide form, set telemetry off global.
--offline now also stops Windows tool downloads. The RODC step used to fetch its credential extractor from GitHub even in offline mode. It now uses only a cached or bundled copy, and when none is there it skips the step and records it as incomplete coverage.
The AD CS ESC8 and ESC11 relays, and the other coerce-and-relay steps, now run while background poisoning is active instead of being skipped because port 445 was taken. Capture and relay share the port, so the host the relay coerced is relayed and anyone else who authenticates is still captured.
Three components that an edition's build was missing now ship in it, so the step that needs them is no longer skipped for a library it cannot find: the IPv6 libraries the DHCPv6 step of the name-resolution technique needs, in the PRO build, and the KeePass and Group Policy Preferences readers, in the Windows build. Each already shipped in the other editions.
Ticking a family in the policy create and policy edit editor now turns every check in it on, and the editor shows how many checks of each family run before and after your choice. The editor, policy use, policy show and policy list print the same attack-step total for one policy, where they used to disagree.
Progress and the time remaining on the port scan and the SMB host collection are now accurate on a large directory of mostly offline hosts. The directory read and the graph save show a live panel with the elapsed time, so a long collection no longer looks frozen.
A new adscan ci scan of an existing workspace keeps its engagement history. It used to clear the whole workspace and open a new engagement, so the earlier runs, their rechecks and the reports already delivered from it were gone, and every finding read as new. Only the previous scan's results are replaced now.
A later scan with an account that sees less no longer marks findings as fixed when it could not read what they are graded from. Host registry settings that need a local administrator, SMBv1 on a host that gave no clear answer, share permissions the account could not read and CA permissions the authority refused now leave the finding or step "not re-checked" in the engagement history and on the Enterprise platform, and the history names the read that was missing.
A cleanup instruction is no longer left for a change that was never made. When an AD CS escalation step's write to the directory failed outright, because the account or object it targeted no longer existed, the change was recorded before the write and then listed for manual cleanup, telling you to undo something that was never written. A write that fails this way now leaves no record.
Removed
The PRO partner-tag prompt is gone. A PRO install takes its identity from its licence, so there is nothing to type on the first run, and adscan ci no longer refuses to start without a tag. --partner-tag and ADSCAN_PARTNER_TAG are still accepted and ignored, so existing scripts keep working.
The dark report theme and the standalone checklist deliverable are retired. Scripts that pass --theme dark or premium_dark, or set ADSCAN_PDF_THEME=premium_dark, keep working and get the corporate_light theme, and --only checklist renders the Security Assessment Report. Each prints one line saying so.
Output format
Integrators get a published, versioned contract for the files a scan writes. Each file family has a JSON Schema in adscan_core/engagement/schemas/, named after the file and its major version (technical_report.v2.json), and each file states the format version it was written in. A minor version only adds fields you can ignore. A major version comes with a new schema file, and the previous one stays available for two minor engine releases or 90 days, whichever is longer. This is the first release to publish these versions, so each line below gives, in brackets, the minor that introduced a field.
attack_graph.json 2.1 (breaking at 2.0, then additive). Edges no longer carry a knowledge object: the description, remediation and verification text of each technique is written once per relation under technique_knowledge at the root, keyed by the relation name, with a #tier0_direct variant for edges whose source is already Tier 0. The root may carry collection.stages, which says which collection stages ran, stopped or were skipped. A domain controller of a trusted domain found through a pivot now carries its role in the file (properties.primaryGroupID 516), and its domain gets a Domain node marked properties.synthesized_from = trusted_domain_inventory. When a build is stopped after the directory data moved on, the previous file gets a root export_state (current false, with the stage, reason and time of the stop), so it is never read as the current graph, and the next full export removes it; a file from an older engine that cannot be marked this way is renamed to attack_graph.previous.json. A node of kind GPO is labelled with its display name and the first 8 characters of its policy GUID, Default Domain Policy (31B2F340), or the full GUID when two GPOs would share that label, and carries gpo_guid (upper case, no braces) and displayname in properties; one whose display name could not be read keeps its GUID label. Each CVE finding carries its CVSS v3 vector next to the score, in evidence.extra.cvss_vector (2.1). Files in format 1.x stay readable for two minor engine releases or 90 days, whichever is longer, and during that window ADSCAN_ATTACK_GRAPH_FORMAT=1 writes 1.2 with the per-edge blocks, which makes the file much larger on a big directory.
attack_paths_snapshot.json 1.2 (additive). Each path carries path_id (1.1), the 64-character route fingerprint that stays stable across runs. The report prints its first 12 characters, the Enterprise platform keys its attack-path records on it, and adscan recheck --path takes any unambiguous prefix of 8 or more. The existing id field is a token local to one listing. A step whose endpoint is a GPO carries source_gpo_guid or target_gpo_guid in its details (1.2), next to source_dn and target_dn.
technical_report.json 2.13 (additive). Every new block is optional and absent when it does not apply, and each coverage block carries statement, the sentence the report prints. A finding that merges several producers of one weakness declares alias_keys (2.1). scan_policy_coverage may carry agreed_policy with name, revision, digest, matches and a reason when it does not match (2.2). A top-level compliance_decision records the framework answer, frameworks with its keys or none, and a missing block means nobody chose (2.3). Each domain may carry operator_stop_coverage, the steps and phases the operator stopped (2.4). A run under a PRO licence carries licence with license_id, grant_id, installation_id, edition and partner_tag (2.5). Each domain may carry resource_coverage, the stages that stopped for lack of memory (collection, graph_build, graph_export, attack_paths, chokepoint_analysis, report or unknown) with unit, examined, total and reason (2.6), and a stage entry may carry run_id (2.7). Each domain may carry guest_access_coverage, the hosts guest SMB access was never asked of (2.8). A run with an asset scope carries a top-level asset_scope summary, each in-scope domain may carry asset_scope_coverage with two separate populations, excluded and unconfirmed, of at most 200 named items each with exact counts, and host_enrichment_coverage may carry the reasondeselected with a deselected_parts list (2.9). asset_scope_coverage may carry entry_outcomes, what became of each scope entry as the client wrote it (2.10). A domain's assessment block may carry complete set to false and incomplete_phases, one entry per phase that ran but did not finish (phase_id, title, reasons, detail), where a reason starting target_unreachable means the domain controller stopped answering during that phase (2.11). resource_coverage may name two more stages, mssql_post_auth and mssql_file_review, and its reason may be listing_limit, a file listing on a database server that stopped at its fixed bound with examined the files listed (2.12). It may also name winrm_post_auth and winrm_file_review, the same two for a host reviewed over WinRM, and share_mapping and share_file_listing, the file review of network shares stopped for memory and shares whose file listing was cut short (examined the shares listed whole, total every share listed); its reason may also be listing_incomplete, a listing that ran out of time or ended on an error (2.13).
scope.json 1.2 (additive). The engagement scope file joins the output contract, with a published schema (engagement_scope.v1.json) and schema_versionscope-1.2. A new asset_scope block holds the allow and deny lists of hosts and accounts, dc_access, the revision, its digest, who decided it and when, how each entry resolved against the directory (resolution), and what was left alone because of it (refusals, backstop_hits). The block carries a record_id, and revisions are comparable only within one record. Files written as scope-1.0 and scope-1.1 carry no such block and stay valid.
inventory/*.json inventory-1.2 (additive). Every inventory file now carries the same envelope with schema_version and record_type, host_patch_level.json included. In gpos.json, name follows the same rule as the attack graph label, and properties carries gpo_guid and displayname (1.1). A record of a deleted object, which a scan reads only with a privileged account, carries tombstoned set to true; its enabled is the value the object had when it was deleted, so leave such a record out of any count of accounts (1.2).
environment_changes.json 1.2 (additive). A change whose revert is scheduled for the final pass of the run carries revert_scheduled (end_of_run). While it is present, revert_status holds the fallback that applies only if that revert does not happen, and the field is removed when the change is reverted or the pass ends. A change that reaches reverted_confirmed no longer keeps the by-hand instruction written while it was in place (manual_cleanup_instructions is null). The run's structured event stream announces such a change with the new environment_change_revert_scheduled event, and environment_change_failed is sent only when no revert will be attempted or the revert did not happen.
scan_summary.json 1.0 (additive). Now carries schema_version. A file without it was written by 14.0.0 or earlier.
memberships.json membership-1.0 (additive). A snapshot a run writes before any collection now also carries schema_version and domain.
The unauthenticated user list (users.json in each domain folder, the one outside inventory/) has a schema but no version marker, because the file is a JSON array. It moves into the inventory envelope at the next major release.
recheck_result.json adscan.recheck_result/1 (additive). The document adscan recheck --json prints, written in each run folder, now has a published schema (recheck_result.v1.json). It gains credential, which says whether the reads used the workspace's account or one given with --username and never carries a secret, and each item gains not_recheckable_reason, the declared reason it cannot be re-checked read-only.
events adscan.events/1 (additive). A run under an online PRO licence writes one licence_notice event at launch when the licence server was not reached, a domain is waiting to be registered or the contract end is near. A licence notice never changes the exit code, and 78 with license_refusal.json stays the only exit code the licence produces.
adscan license status --json 1.1 (additive). The output now carries schema_version and a published schema (license_status.v1.json). The fields contract_term, contract_ends_on (null when the contract has no end date), contract_days_remaining, document_valid_until, renews_automatically, last_refreshed_at, last_check_in_at, last_check_in_result and notice_level keep the contract and the licence document apart (1.0). A licence_notice block, null when the server answered and nothing is waiting or ending, carries the dates a platform needs, with server_reached, works_offline_until, contract_ends_on and the pending_domains each with its assessment_allowed_until (1.1).
adscan license check --json 1.0 (additive). New output with reachable, cause, fix, the route steps (proxy, dns, tcp, tls, health, clock, each with ok, detail and cause), sent, a licence summary and the same licence_notice block. Published as license_check.v1.json.
adscan license register export 1.2 (additive). Each usage line gains run_status (complete, partial or interrupted, null on a recheck) and domain_sizes, one entry per domain the run assessed, with no identifier. It counts users, computers split into servers, workstations and unknown operating system, enabled computers by privilege tier, domain controllers and enterprise certificate authorities (1.1). On a run with an asset scope it also carries computers_in_asset_scope, computers_excluded_by_asset_scope and computers_asset_scope_unconfirmed, the figures of the report's network-reach statement, and all three stay null without one (1.2). Every field is a whole number or null, and null means the run did not count it.
ledger adscan.ledger/1 (additive). An item that was not re-checked can carry the read that was missing after its reason code, as in check_skipped:host_registry_not_read. Split evaluation_reason on the first colon to read the code alone. coverage.json and observations.json gain the per-host families host.registry.*, host.smbv1 and smb.share_access, recorded on every run that sweeps hosts.