Scantide Auditor PowerShell helps administrators understand what is actually reachable inside their own networks: hosts, web ports, service banners, TLS certificates, response titles, CMDB coverage, and evidence that can be exported into a clear HTML report.
The script is intended for administrators, security teams, infrastructure teams, and asset owners who need a practical view of internal network exposure without installing agents or running intrusive tests.
Internal network visibility
Scan approved internal ranges to see which hosts respond, which common services are reachable, and which systems may need follow-up.
CMDB comparison
Compare discovered hosts against known asset data so teams can spot missing, stale, or unexpected records.
Readable evidence reports
Create HTML reports that show the facts: host, port, title, banner, TLS subject, certificate names, CMDB status, and timestamps.
Important: this is a visibility and inventory tool for networks you own or are authorized to review. It is not designed to exploit systems, brute-force logins, bypass authentication, or modify remote hosts.
Why this matters in plain language
Many companies have more systems online than they think. Some are old test servers, forgotten admin portals, temporary devices, printers, appliances, or servers that were never added correctly to the asset inventory. Scantide helps turn that uncertainty into a list you can actually review.
Unknown systems create blind spots
If a device is reachable but not listed in the CMDB, nobody may be responsible for patching it, monitoring it, backing it up, or removing it when it is no longer needed.
Open services explain exposure
A host that only responds to HTTPS is different from a host exposing FTP, old web admin pages, remote access services, or mail protocols. The report helps you see what is actually reachable.
Certificates reveal useful clues
TLS certificates often show hostnames, service names, expiry dates, and ownership hints. This can help find forgotten systems or certificates that need renewal.
Web titles make reports readable
A port number alone is not always helpful. Capturing the web server title and basic response information makes it easier to identify what a service actually is.
CMDB gaps become visible
When the scan finds something that is not in the inventory, the team can decide whether to register it, investigate it, or remove it.
Reports support cleanup work
The goal is not only to find things. The goal is to create evidence that helps infrastructure, operations, and security teams agree on what needs attention.
What the script can check
Exact checks depend on the version and options you enable, but the PowerShell auditor is designed around practical asset and service evidence.
Host discovery
Review IP ranges and collect response evidence from hosts that appear reachable during the scan.
Port and service checks
Check common ports and service responses such as HTTP, HTTPS, SSH, FTP, SMTP, DNS, IMAP, POP3, and custom configured ports.
TLS certificate review
Inspect visible certificate fields such as subject, issuer, DNS names, expiry dates, and certificate mismatch clues.
Web response metadata
Collect basic web evidence such as status, title, server header, redirects, and HTTP/HTTPS availability where available.
ServiceNow / CMDB signals
Mark discovered hosts as known or not found in the asset inventory when CMDB integration data is available.
Timestamped scan evidence
Include scan date, network range, duration, and report context so results can be compared over time.
HTML output
Generate a visual report that can be shared with operations teams, system owners, or audit stakeholders.
Non-invasive review
Focus on observable network and service data rather than exploitation, credential attacks, or intrusive vulnerability testing.
How to interpret the findings
A finding does not automatically mean something is dangerous. It means there is evidence worth understanding. The report is designed to help teams decide what to verify, document, patch, or remove.
Known and expectedDocumented asset, expected service, normal certificate state.
Good operational rule: treat the report as a triage list. Start with systems that are reachable, missing from CMDB, exposing sensitive services, or using certificates that are expired, near expiry, or hard to identify.
How to run it
Run the script from a Windows machine or server that is allowed to reach the target network range. Use an account and location that match your organization’s scanning policy.
Basic example
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
.\ScantideAuditor.ps1 -Network 10.24.48.0/24
Typical workflow
Choose an approved internal range, for example a server VLAN or site subnet.
Run the script from an allowed admin workstation or scanning host.
Open the generated HTML report and review hosts, ports, certificates, and CMDB status.
Send the cleanup list to the relevant system owners or infrastructure team.
Tip: if your environment blocks PowerShell scripts by policy, do not weaken global security settings. Use a controlled, approved process such as a signed script, a temporary process-level execution policy, or your organization’s software deployment tooling.
Recommended use cases
The PowerShell script is most useful when the goal is to create a practical inventory and exposure baseline for internal networks.
Before an audit
Check that important systems are known, documented, and not exposing unexpected services before an external or internal review.
After network changes
Run a comparison after migrations, firewall changes, segmentation work, VLAN changes, or server cleanup projects.
CMDB hygiene
Find systems that exist on the network but are missing, outdated, or incorrectly represented in the asset inventory.
Certificate cleanup
Find certificates that are expired, near expiry, incorrectly named, or attached to services that nobody recognizes.
Legacy service review
Identify old services such as FTP, legacy admin pages, or unexpected mail services that may need retirement or restriction.
Operations handover
Create a clear report that helps different teams agree on what is known, what is unknown, and what needs action.
What the report helps answer
A good report should not just say that something was found. It should help the team understand what the finding means and what to do next.
Which hosts responded in this network range?
Which services are reachable on each host?
Which web pages expose titles, server headers, redirects, or login portals?
Which certificates are visible, expired, near expiry, or difficult to map to an owner?
Which discovered hosts are missing from the CMDB?
Which systems may belong to old projects, test environments, or forgotten appliances?
Which findings should be sent to system owners for verification?
Which findings should become cleanup, firewall, patching, or documentation tasks?
Safety and scope
Scantide Auditor PowerShell is built for authorized visibility. It should be used only on networks where you have permission to perform inventory and exposure review.
Use on approved ranges
Run it only against networks you own, manage, or are explicitly authorized to assess.
No credential attacks
The scanner is not intended for password guessing, brute forcing, exploitation, or bypassing access controls.
Document the result
Use the report to improve asset ownership, CMDB accuracy, certificate hygiene, firewall rules, and service cleanup.
Prioritization context
CVE and jurisdiction context
Auditor findings become more useful when they are connected to known vulnerability context and infrastructure ownership/location context. The goal is prioritization and evidence, not automatic blame.
CVE review signals
Open ports, service banners, web titles, certificates and server headers may reveal product or version hints that can be compared with CVE information. Treat this as a pointer for follow-up: a visible version may be wrong, patched by backporting, hidden behind a proxy, or not exploitable in the local configuration.
Infrastructure and jurisdiction signals
For internal and branch-office reviews, provider, country, ASN, cloud region, mail routing and external dependencies can matter. These signals help teams understand whether systems depend on unexpected providers, regions or legal environments, especially where policy, compliance or data-residency requirements apply.
FAQ
Is this a hacking tool?
No. It is an inventory and exposure review script for authorized internal networks. It collects observable service and metadata evidence so administrators can clean up and document their environment.
Does every open port mean there is a problem?
No. Many open ports are normal. The important question is whether the service is expected, documented, patched, restricted, and owned by the right team.
Why does CMDB comparison matter?
If a system is reachable but not in the asset inventory, it can be missed by patching, monitoring, backup, lifecycle management, and incident response processes.
Why collect web titles and certificate names?
They help humans identify systems faster. A hostname, web title, certificate subject, or DNS name can reveal whether the service belongs to a known application, old project, appliance, or test environment.
Can this replace vulnerability scanning?
No. It is better viewed as a visibility, inventory, and evidence tool. It can help decide where deeper vulnerability review is needed, but it is not a replacement for full vulnerability management.
Can non-security teams use the report?
Yes. The output is meant to be readable by operations, infrastructure, application owners, and asset managers. The point is to make cleanup and ownership discussions easier.
Need the full setup and usage guide?
The PowerShell manual explains prerequisites, safe scanning scope, common parameters, report interpretation, CMDB comparison, troubleshooting, and recommended operating practices for internal network reviews.
PowerShell manual
Use the manual when deploying the script for the first time, explaining the report to colleagues, or standardizing how internal scans should be run and documented.
The guide covers how to choose a network range, understand discovered hosts, read evidence rows, compare against asset inventory, and turn findings into cleanup actions.
Part of the Scantide visibility ecosystem
Scantide Auditor PowerShell focuses on internal networks. Scantide Observe focuses on website privacy and browser-visible behavior. Scantide Observe Mobile brings similar visibility to Android. Together they help explain what systems, websites, and services are doing in a way people can act on.
Scantide is split into focused tools so the right audience gets the right kind of evidence quickly.
Use Observe for live website behavior, Online for public domain checks, Dashboard for monitoring,
and Auditor when you need authorized internal network visibility.
Observe browser extension
For Chrome, Edge, Brave and Firefox. Shows trackers, cookies, scripts, security headers, forms, contacted hosts and browser-visible website risk while you browse.
For Android users who want to share a URL from a browser or app and understand website privacy, scripts, trackers, infrastructure and jurisdiction context on mobile.
For Windows admins reviewing authorized internal networks. Finds reachable hosts, visible services, web responses, TLS clues and CMDB gaps in clear HTML reports.
For mobile field checks and quick local network visibility. Useful for Wi-Fi review, nearby network context and on-site authorized infrastructure checks.